Docstoc

Slides - MSE Studio

Document Sample
Slides - MSE Studio Powered By Docstoc
					End of Semester Presentation
        Summer 2007



            9 August 2007

          Team SoS - Summer 2007 EOSP   1
                   Agenda

•   Background
•   Milestones
•   Practices
•   Implementation
•   Quality Assurance
•   Conclusion
•   Demo

                  Team SoS - Summer 2007 EOSP   2
               Stakeholders - 1
Background | Milestones | Practices | Implementation | QA | Conclusion

  Person                            Summer 2007 Roles
 Roni Burd                                 Team Lead
                                         Client Liaison
                                       Planning Manager
Nitin Prasant
                                       Process Manager
Uma Menon                              Development Lead
                                     Requirements Engineer
                                         Chief Architect
Sean Duggan
                                      Documentation Lead
                                          Testing Lead
Matt Weyant
                                       Support Manager
                         Team SoS - Summer 2007 EOSP                     3
                 Stakeholders - 2
  Background | Milestones | Practices | Implementation | QA | Conclusion


• Client: L-3 Communications
  – Matthew DeLaquil
  – Dr. Jerry Fudge


• Mentors
  – Cliff Huff
  – John Robert


                           Team SoS - Summer 2007 EOSP                     4
                Problem Statement
Background | Milestones | Practices | Implementation | QA | Conclusion

Key

  High Flying
  Platforms

  Low Flying
  Platforms

  Land-based
  Platforms

  Mobile
  Beacon

  Immobile
  Beacons

  Weather

  Foliage

                         Team SoS - Summer 2007 EOSP                     5
      Milestones & Deliverables
   Background | Milestones | Practices | Implementation | QA | Conclusion

• Developed an aggressive schedule with
  full-function release at the end of July
  – Rescheduled around client’s availability
  – Delivered final release on-time
• Deliverables
  – Simulation Engine
  – Documentation
      • User Manual
      • Developer Manual

                            Team SoS - Summer 2007 EOSP                     6
                          Milestones
Background | Milestones | Practices | Implementation | QA | Conclusion

         6/18/2007                                           6/18/2007
       SimEngine 1.0      6/17/2007
                                                           SimEngine 1.0
      Documentation 1.0                                       UAT 1.0
          UAT 1.0           6/24/2007

                                                             7/9/2007
                              7/1/2007
                                                          SimEngine 2.0
                                                             GUI 1.0
         7/16/2007            7/8/2007                   Documentation 1.0
       SimEngine 2.0                                         UAT 2.0
      Documentation 2.0
                            7/15/2007
          UAT 2.0
                                                            7/26/2007
                            7/22/2007                     SimEngine 3.0
         7/23/2007                                           GUI 2.0
       SimEngine 3.0        7/29/2007
                                                         Documentation 2.0
      Documentation 3.0                                      UAT 3.0
          UAT 3.0
                              8/5/2007

        Planned            8/9/2007                         Actual

                           Team SoS - Summer 2007 EOSP                       7
      Milestones & Deliverables
   Background | Milestones | Practices | Implementation | QA | Conclusion

What we did well
• Scheduled and planned scope of milestones
  based on estimation
• Shipped only stable components

What could have been better
• Coordinated milestones with individual
  commitments



                            Team SoS - Summer 2007 EOSP                     8
                          Practices - 1
      Background | Milestones | Practices | Implementation | QA | Conclusion

                 Practice                                    Reflection
Incremental SDLC
Postmortem meetings, status
meetings
Standup meetings

Roles
QA practices

Key           Excellent          Good

                               Team SoS - Summer 2007 EOSP                     9
                          Practices - 2
      Background | Milestones | Practices | Implementation | QA | Conclusion


                 Practice                                    Reflection
Planning meetings, 2-week detailed
planning window
Earned Value tracking
Knowledge sharing
Risk management

Configuration management

Key           Excellent          Good

                               Team SoS - Summer 2007 EOSP                     10
                Risk Management
   Background | Milestones | Practices | Implementation | QA | Conclusion


• Mini-SRE (last semester)
  – Laid the groundwork for the risk management
  – Ignored implementation section of risk
    taxonomy-based questionnaire
  – Did not identify many risks we faced this
    semester
• No outstanding risks
• 18 top ranked risks were mitigated

                            Team SoS - Summer 2007 EOSP                     11
             Planning & Tracking
   Background | Milestones | Practices | Implementation | QA | Conclusion


• Planning
  – Developed milestone-driven plan based on
    estimation
  – Used Project to identify task dependencies
  – Revised estimates based on historical data
• Tracking
  – Used automated Excel sheets to track WBS
  – Consolidated week-wise and cycle-wise data

                            Team SoS - Summer 2007 EOSP                     12
    Implementation Tracking
Background | Milestones | Practices | Implementation | QA | Conclusion




                         Team SoS - Summer 2007 EOSP                     13
                   Effort Distribution
     Background | Milestones | Practices | Implementation | QA | Conclusion




Total effort = 2045 hours
                              Team SoS - Summer 2007 EOSP                     14
                  Earned Value
Background | Milestones | Practices | Implementation | QA | Conclusion




                         Team SoS - Summer 2007 EOSP                     15
                        Implementation Effort
               Background | Milestones | Practices | Implementation | QA | Conclusion
Effort (hrs)




                                        Team SoS - Summer 2007 EOSP                     16
                 Implementation Effort - %
             Background | Milestones | Practices | Implementation | QA | Conclusion
Percentage




                                              Cycle
                                      Team SoS - Summer 2007 EOSP                     17
               Planning & Tracking
     Background | Milestones | Practices | Implementation | QA | Conclusion

What we did well
•   Smoothed transition from 12- to 48-hour weeks
•   Analyzed dependencies
•   Managed task granularity
•   Used historical data to adjust plan

Only 3% of the total effort was unplanned

What could have been better
• Managed individual work loads at the outset

                              Team SoS - Summer 2007 EOSP                     18
                               Design
    Background | Milestones | Practices | Implementation | QA | Conclusion

What we did well
• Reused techniques from experiments
• Used architecture to identify implementation
  dependencies
• Leveraged detailed design to increase productivity

What could have been better
• Designed testability into the architecture
• Completed deployment view for build environment



                             Team SoS - Summer 2007 EOSP                     19
                 Implementation - 1
     Background | Milestones | Practices | Implementation | QA | Conclusion

What we did well
•   Employed three build-environments
•   Created library of reusable code
•   Coded to the interfaces
•   Allocated work according to architectural
    components

What could have been better
• Infrastructure/tooling
• Interface change management

                              Team SoS - Summer 2007 EOSP                     20
                Implementation - 2
    Background | Milestones | Practices | Implementation | QA | Conclusion


Lines of Java application code                                         1,322

Lines of C++ application code                                         29,651
Lines of C++ test code                                                13,341
Lines of code documentation                                           11,534
Total                                                         55,848 LOC

Time in implementation                                         1430.37 hrs

Productivity                                                39.04 LOC/hr

                             Team SoS - Summer 2007 EOSP                     21
               Implementation - 3
   Background | Milestones | Practices | Implementation | QA | Conclusion

• Case study 1 – Sim monitor
  – Protocol
  – FSP modeling (Really)
• Case study 2 – Data manager
  – Performance (speed, file size)
  – XML           plain text
• Case study 3 – GUI
  – Complexity, scalability
  – Single resource
  – Canvas config           tree config
                            Team SoS - Summer 2007 EOSP                     22
               Documentation - 1
   Background | Milestones | Practices | Implementation | QA | Conclusion

• Consisted of:
  – User’s Guide
  – Input file format
  – Developer’s Guide
  – System Architecture Document (SAD)
  – Source code documentation

Page count = 115 hand-built pages + 1,531
 generated pages
                            Team SoS - Summer 2007 EOSP                     23
               Documentation - 2
   Background | Milestones | Practices | Implementation | QA | Conclusion

What we did well
• Documented use cases of the top-ranked quality
  attribute scenarios
• Delivered documentation incrementally

What could have been better
• Created documentation standard earlier in the
  semester
• Created detailed plan for documentation earlier and
  executed it


                            Team SoS - Summer 2007 EOSP                     24
          Engineering Highlights
   Background | Milestones | Practices | Implementation | QA | Conclusion

• Radio Frequency (RF) propagation and loss
  models – international standards
  – Rain loss (ITU-R P.838-3)
  – Clouds and fog loss (ITU-R P.840-3)
  – Absorption by atmospheric gases (ITU-R P.676-6)
• RF signal detection
  – Generalized Marcum-Q function
• Simulator scheduling
• Eclipse Modeling Framework
• Dynamic library loading
                            Team SoS - Summer 2007 EOSP                     25
              Quality Assurance - 1
      Background | Milestones | Practices | Implementation | QA | Conclusion


               Technique                                     Reflection
Fagan Inspections
Peer reviews
Unit testing
Integration testing
Profiling

Key           Excellent          Good

                               Team SoS - Summer 2007 EOSP                     26
           Quality Assurance - 2
   Background | Milestones | Practices | Implementation | QA | Conclusion


What we did well
• Profiling found performance bottlenecks
• Benchmark scenarios (14) ensured the
  correctness of our simulator
  – “M”, Flatso, and Spikey scenarios – we’ll meet
    them later 
• Specific tests verified quality attributes
• We built a detailed test plan
                            Team SoS - Summer 2007 EOSP                     27
           Quality Assurance - 3
   Background | Milestones | Practices | Implementation | QA | Conclusion


What could have been better
• Unit testing framework
• Continuous integration server
  – Too time-consuming to maintain
• Underestimation of testing effort
  – Testing took twice as long as we expected



                            Team SoS - Summer 2007 EOSP                     28
             Defect Severity Distribution
         Background | Milestones | Practices | Implementation | QA | Conclusion
Number




                                  Team SoS - Summer 2007 EOSP                     29
             Defect Detection Technique
         Background | Milestones | Practices | Implementation | QA | Conclusion
Number




                                  Team SoS - Summer 2007 EOSP                     30
               Defect Artifact Distribution
         Background | Milestones | Practices | Implementation | QA | Conclusion
Number




                                  Team SoS - Summer 2007 EOSP                     31
      Application of MSE Principles
    Background | Milestones | Practices | Implementation | QA | Conclusion


      Course                                       Technique
Models                      FSP modeling, Z modeling

Methods                     Norman’s design principles
                            Planning, estimation, tracking, risk
MSD
                            management
Architecture                ATAM, QAW
                            Testing, static analysis, performance
Analysis
                            profiling, QA plan
                             Team SoS - Summer 2007 EOSP                     32
               Deliverable Status
   Background | Milestones | Practices | Implementation | QA | Conclusion


          Deliverable                                     Status
Simulation Engine Framework

User Manual

Developer Manual




                            Team SoS - Summer 2007 EOSP                     33
                Deliverable Status
    Background | Milestones | Practices | Implementation | QA | Conclusion


           Deliverable                                     Status
Simulation Engine Framework

User Manual

Developer Manual

14 Default Plug-ins




                             Team SoS - Summer 2007 EOSP                     34
                Deliverable Status
    Background | Milestones | Practices | Implementation | QA | Conclusion


           Deliverable                                     Status
Simulation Engine Framework

User Manual

Developer Manual

14 Default Plug-ins

Graphical User Interface


                             Team SoS - Summer 2007 EOSP                     35
            Plan for next semester
     Background | Milestones | Practices | Implementation | QA | Conclusion


•   GUI enhancements
•   Additional documentation
•   Knowledge transfer to client
•   Bug fixes
•   Poster session + EOSP
•   Individual reflection papers


                              Team SoS - Summer 2007 EOSP                     36
Why We Had a Successful Summer
• Effective, efficient team practices
• No burn-out! (Remember the 55 KLOC?)
• Cohesive, “performing” team

  Delivered on-time, beyond scope,
  with high quality


              Team SoS - Summer 2007 EOSP   37
  Demo




Team SoS - Summer 2007 EOSP   38
Questions?




 Team SoS - Summer 2007 EOSP   39
Backup slides




  Team SoS - Summer 2007 EOSP   40
       Design – quality attributes

   Kept goals in mind
   Helped understand alternatives

   Example:
    – Usability: The “scenario configurer” is able to
      configure a small scenarios in 15 min.

    – GMF was not helping achieve this scenario.


                     Team SoS - Summer 2007 EOSP        41
                               ACDM
Architectural
  Drivers

    Reviews
(3 Evaluations +
 1 mini-ATAM)
                                    3 iterations          Architecture

11 Experiments

Key

      Process   Iteration

                            Team SoS - Summer 2007 EOSP                  42
                       Constraints

•       Technical
    –    Must use C++ for the simulation engine
    –    Must run on a standard Windows PC
    –    Must not need recompilation of the entire application
         for certain changes
    –    Must use object-oriented model
•       Business
    –    Must be delivered by August 9th 2007
    –    Must be developed by a team of 5
    –    Must use human-readable/editable input files
    –    Must produce output to be read by Excel
                         Team SoS - Summer 2007 EOSP             43
         Top Quality Attributes
Quality Attribute                    Attribute Concern
  Extensibility      The developer should be able to add new
                     modules to the system easily
                     The developer should be able to add new
                     simulation objects
                     The developer should be able to add new
                     output parameters
  Performance        Need a system that performs simulations
                     according to given response measures
  Usability          The scenario configurer is able to configure
                     many scenarios in a small amount of time
                     The scenario configurer should be able to
                     diagnose the reason for failure without
                     difficulty
                    Team SoS - Summer 2007 EOSP                  44
Architecture - C&C




    Team SoS - Summer 2007 EOSP   45
                                          Defer binding time
Heartbeat
Manage event rate




                    Team SoS - Summer 2007 EOSP                46
                       Tactics

• Testability
  – Separate interfaces from implementation
  – Built in monitors
• Performance
  – Increase computational efficiency
• Modifiability
  – Hide information
  – Localize changes
• Availability
  – Exception

                    Team SoS - Summer 2007 EOSP   47
                Sensitivities

• Can’t guarantee performance with
  developer plug-in
  – Multiple calls, memory leaks, etc
• Performance is sensitive to switching time
  frequency




                   Team SoS - Summer 2007 EOSP   48
         Milestones - History

• First release on target except
  documentation not available yet
• Next milestone moved up to incorporate
  GUI release and match client window of
  availability
• Final release delayed due to failing tests
  and remaining issues. Some
  documentation and remaining issues
  pushed to the bug fix release
                 Team SoS - Summer 2007 EOSP   49
            Protocol Case Study

• Sim Monitor Protocol
  – Socket Communication between Sim Engine (Sim
    Monitor) and GUI (Sim Controller)
  – Initial protocol
     • START, ABORT, PROGRESS, HEARTBEAT
  – Gaps in states
  – FSP modeling for analysis
  – Modified protocol
     • HEARTBEAT one-way, SYN-ACK, END added
     • Timeouts
     • Cleaner, simpler logic
                     Team SoS - Summer 2007 EOSP   50
Protocol Case Study




     Team SoS - Summer 2007 EOSP   51
       Data Manager: Case Study

• Data Manager writes output files
• Initial: XML format, open with excel
• Issue 1: Correct tag closure warranted single file
  (~100 MB)
• Issue 2: Stack operations for XML write took a
  lot of time
• Side points: Client uses Excel 2002 (little XML
  support), Excel lists used
• Solution: Pipe-delimited flat-file output
• Result: 40% faster small scenario run, 5MB files
                    Team SoS - Summer 2007 EOSP    52
              GUI Case Study

• GUI – Eclipse Modeling Framework
• Initial:
  – Canvas like a map
  – Platforms and beacons (icons) dragged-dropped
• Issue:
  – Not scalable
• Resolution:
  – Tree view instead of canvas view
  – Obtained client approval

                     Team SoS - Summer 2007 EOSP    53
                Integration Testing

           Metric                                      Result

Total Number of Tests:                                            66
Tests Completed:                                                  66
% Test Completed:                                               100%
Tests Passed:                                                     66
% Tests Passed:                                                 100%



                         Team SoS - Summer 2007 EOSP             54
                         Unit Testing

                Metric                                  Result


Total Number of Tests:                                            206

Tests Completed:                                                  206

% Test Completed:                                                100%

Tests Passed:                                                     206

% Tests Passed:                                                  100%


                          Team SoS - Summer 2007 EOSP             55
            Coding Standard

• Narrowly focused on cosmetic issues
  – Code beautifying tools are more efficient
• Was not updated
  – Boost library guidelines would have been
    helpful
  – Common errors found in reviews




                  Team SoS - Summer 2007 EOSP   56
               User Guide

• Covers installation and use of Simulation
  Engine and GUI
• Instructions illustrated with screenshots to
  increase clarity
• Parameters and format provided for
  configuration files and command line use
• Contains design decisions and known
  issues at time of product shipping

                  Team SoS - Summer 2007 EOSP   57
             Developer Guide
• Covers installation of project source code and
  tools to modify the code
• Employs step-by-step instructions illustrated with
  screenshots for common program modifications.
• Covers modifiability and extensibility scenarios
  for quality attribute scenarios 2 through 9
• Includes Software Architecture Document (SAD)
• Demonstrates protocol for event notification and
  socket communication
• Final version delivered with first bug fix to catch
  the latest code changes
                    Team SoS - Summer 2007 EOSP    58
     Input File Format Documentation

• Explains the XML file format for input files
  – Describes each of the 24 elements and 57
    attributes available
     • Lists element names, abstract types, descriptions,
       and the minimum and maximum number of a given
       element allowed
     • Lists attribute names, descriptions, value types
       necessitude, ranges, and units
  – Describes minimum and maximum values and
    options for each value type
                    Team SoS - Summer 2007 EOSP        59
     Source code documentation

• Source code annotated by team and
  documentation compiled by Doxygen
• Enabled documentation at the source level
• Helped enforce good documentation
  habits
• Generated diagrams of code inheritance



                Team SoS - Summer 2007 EOSP   60
        Team Role Reflection

• Early development phase
  – Work stoppages often resulted in everyone
    trying to solve the problem
• After first release
  – Boundaries of responsibility clarified
  – Roles were effective after this




                   Team SoS - Summer 2007 EOSP   61
                  Meetings

• Daily Stand-up meetings:
  – Helped to monitor team’s daily progress
  – Served as a common platform to
    communicate issues
• Status meetings:
  – Milestone progress and Earned Value
    tracking were really valuable to help gauge
    the overall team progress
  – Bug distribution charts encouraged team to
    quickly close defects
                  Team SoS - Summer 2007 EOSP     62
        Postmortem Meetings

• Postmortem meetings:
  – Were effective to reflect and evaluate the
    release
  – Helped to readjust plan and effort distribution
  – Had a total of three
  – Gave many inputs for improving overall team
    processes



                   Team SoS - Summer 2007 EOSP    63
                               Tools - 1
                 Tool                                  Ease/Effectiveness
Visual Studio C++ IDE

Visual Studio Testing Suite

CPPUnit

Doxygen
Eclipse

Key

          Good           Team SoS - Summer 2007
                         Could Improve EOSP
                        Team SoS - Spring EOSP 2007
                                                        Frustrating
                                Team SoS - Summer 2007 EOSP                 64
                           Tools – 2
              Tool                                 Ease/Effectiveness
Subversion/Ankh

Excel, email, calendar

Eclipse Modeling
Framework
Wiki
Bugzilla
Key

       Good           Team SoS - Summer 2007
                      Could Improve EOSP
                     Team SoS - Spring EOSP 2007
                                                     Frustrating
                            Team SoS - Summer 2007 EOSP                 65
       Some Mitigated Risks - 1
               Risk                            Mitigation Strategies
Client is on vacation many days            Find alternate contact early,
during the summer; releases may           familiarize him/her with project.
not be tested properly by client           Re-scope releases
                                           Reschedule releases
Some people on the team are not            Assign domain experts
familiar with important                    Knowledge sharing
technologies (e.g., Java, C++,
                                           Pair programming
Eclipse framework) and tools; It
may take a lot longer to do the
coding tasks than was expected.
GMF is not scalable for a big              Ask client to choose:
scenario; GUI might not fulfill                  • Tree with no palette support
client's expectations
                                                 • The present canvas option
                                                 • Push the GUI completion date
                           Team SoS - Summer 2007 EOSP                            66
       Some Mitigated Risks - 2
               Risk                            Mitigation Strategies
Don't know if we can accomplish            Prototype Simulation Engine from
the quality attribute scenario for        detailed design to experiment
performance provided by client;            Change performance objective to just
Assumptions may turn out to be            below the Matlab run time
unrealistic.                               Convince client to use GPL or
                                          commercial libraries (for greater speed)
                                           Extend XML experiment to check file
                                          output times
                                           Modify existing QA scenarios and
                                          identify new ones for Performance.
Management intervention is                 Feedback to offending members
sometimes needed to get people             Align individual goals with team goals
working together; we may suffer            Reinforce mutual accountability and
delays                                    individual empowerment

                           Team SoS - Summer 2007 EOSP                               67
        Some Mitigated Risks - 3
                Risk                            Mitigation Strategies
Hidden assumptions made by                  Experiments
client and team about specific              Detailed design
requirements are not being
documented; discovery and
revalidation could take too much
time or we might make the wrong
assumptions
Other class assignments impinge In planning meetings, assume that no
upon our studio time, and some      work will get done till Wednesday night
require unpredictable effort; might and take on tasks accordingly
not be able to meet a given
deadline




                            Team SoS - Summer 2007 EOSP                       68
       Some Mitigated Risks - 4
               Risk                            Mitigation Strategies
Scope of experiments keep         The scope of the experiment will be
changing; all experiments may not strictly defined by the Chief Scientist
get completed                      Any deviation has to be approved by
                                          the Chief Scientist on a case-to-case
                                          basis
Eclipse graphical framework is             Use existing examples to learn.
new and not well documented;               Get Acme source code
could spend too much time
requesting help, and it may not be
stable yet
While planning subtasks,                  Create dependency matrix while
dependency checks are not being           planning sub tasks and consult it during
done; tasks on the critical path          planning meeting.
may cause delays

                           Team SoS - Summer 2007 EOSP                               69
       Some Mitigated Risks - 5
              Risk                            Mitigation Strategies
We don't have concrete results for        Stress that client must test thoroughly
verification of a particular             to verify input with their tests or ours
scenario; application might not be        Explore alternatives with the client
functioning correctly                     We generate our scenarios and give
                                         results to client for validation
Documentation is not moving               Documentation Manager should be
forwards in time; quality of             actively involved
documentation might suffer                Add Doxygen automated generation
                                         to integration testing and release
Writing XML is slowing                    Write a new Data Manager plugin to
SimEngine; may not achieve               output values as pipe-delimited file
performance quality attribute




                          Team SoS - Summer 2007 EOSP                                70
       Some Mitigated Risks - 6
             Risk                           Mitigation Strategies
Management intervention is             Feedback to offending members
sometimes needed to get people         Align individual goals with team goals
working together; we may suffer        Reinforce mutual accountability and
delays                                 individual empowerment
GUI/SimEngine communications            Perform performance analysis and
is slowing performance; may not        testing
achieve performance quality             Do peer reviews on the algorithm and
attribute                              source code




                        Team SoS - Summer 2007 EOSP                              71
               Process Scorecard
      Process                     Objectives          Status

Software Process   Client involved with the process        <3

                   Planning accuracy                      27%

Planning           Planning accuracy                      3%
                   Tracking error                          2

                   Planning overhead                       5%
Tracking           Using historical data                  70%
                   Timely status meeting agendas          <12
Team Meeting       Timely client agendas                 100%
                   Active risk mitigation                100%
                   Email responsiveness                  100%
Communication
                   Email clearness                       100%
                   Team SoS - Summer 2007 EOSP             72
                   Email responsiveness                   90%
          Effort Tracking Per Area
(hours)




                     Cycle
                 Team SoS - Summer 2007 EOSP   73
              Default Plugins - 1
   Plugin Name                                     Purpose
AtmosphericLoss           Calculates signal loss due to atmospheric
                          interference
CloudsAndFogLoss          Calculates signal loss due to interference of
                          clouds and fog
FreeSpaceLoss             Calculates signal loss due to spacial
                          interference
RainLoss                  Calculates signal loss due to interference of
                          rain
DefaultPointingLoss       Calculates signal loss due to differences of
                          orientation
DefaultPolarizationLoss   Calculates signal loss due to differences of
                          polarization
                          Team SoS - Summer 2007 EOSP                     74
              Default Plugins - 2
    Plugin Name                                    Purpose
ConstantTransmission       Models constant transmission characteristics

LinearDecayTransmission Models linearly decaying transmission
                        characteristics

PulseTransmission          Models pulse transmission characteristics

DefaultDataManager         Implementation of result output using an
                           XML format

DelimitedDataManager       Implementation of result output using a
                           character-delimited format

MarcumQDetection           Implementation of signal detection according
                           to Marcum Q functions

                         Team SoS - Summer 2007 EOSP                      75
               Default Plugins - 3
    Plugin Name                              Purpose
DefaultPropagation   Implements a default calculation of
                     propagation gains and losses. Reads in a list
                     of Simulation and Environmental plugins and
                     employs them for calculation.

DefaultStepManager   Implements a default stepping model for the
                     simulation wherein plugins are informed
                     when the scenarios begins and ends, and
                     when timesteps (movement and sampling)
                     begin and end.




                     Team SoS - Summer 2007 EOSP                     76
                   Training

• Training
  – Knowledge initially concentrated in one or two
    individuals
  – Held training sessions for the team
  – Monitored under risk management




                  Team SoS - Summer 2007 EOSP    77
                 Implementation Effort Tracking
Effort (hours)




                                   Cycle
                          Team SoS - Summer 2007 EOSP   78

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:2
posted:1/21/2012
language:Latin
pages:78