OCEAN OBSERVATORIES INITIATIVE. Release 2 Schedule. OOI CI Release 2 Kickoff M a y 2,

Transcription

1 OCEAN OBSERVATORIES INITIATIVE Release 2 Schedule M a y 2,

2 Top-Down Through the Schedule Project Releases Anatomy of a Release 2 Phases in a Release Inception Phase in Detail: Iterations Milestones in Inception Phase The First Iteration Design Period This Week 2

3 Project Releases 3

4 Anatomy of a Release 4

5 Anatomy of a Release 2 5/2 9/2/2011 3/2/2012 8/31/ /26/2012 5

6 Phases in a Release Inception reaching consensus among the stakeholders on the objectives for a release Elaboration defining the optimal system architecture, addressing its riskiest elements and getting the stakeholders to commit to construction of the release Construction all of the technology choices and new software are integrated into the relevant subsystems, and the subsystems are integrated into a complete CI release Transition release against user requirements, deployment into the appropriate CyberPoPs throughout the system of systems, and training of users and operators. 6

7 Reviews in a Release Life Cycle Objectives Declare the initial scope Life Cycle Architecture Declare and demonstrate the architecture to achive the scope Initial Operating Capability Demonstrate the ability of the system to execute all functionality Product Readiness Review Review all artifacts to ensure system is fully ready to deploy X

8 Inception Phase in Detail Main purpose: Reaching consensus among the stakeholders on the objectives for a release. During the inception phase, it is anticipated that new requirements and use cases will be discovered and that the baseline set of requirements will be evaluated for accuracy and completeness. 7

9 Inception Phase in Detail: Goals Establishing the software scope and interfaces at the level of an operational concept, a clear set of success criteria and a welldefined definition of what is and is not within the release Defining the critical use cases for the system and the resulting concepts of operation that will in turn force design trade-offs Demonstrating one or more candidate architectures that fulfill the use cases and concepts of operation A refined plan, including cost and schedule, for the subsequent elaboration phase that builds on the Annual Work Plan Clear definition and prototyping of the critical risks that require early mitigation 8

10 Inception Phase in Detail: Activities Elicitation of requirements and use cases that circumscribe the user (scientific, educational and operator) view of the system, and their capture in a suitable repository Carrying out design trade-offs, resolving design ambiguities and evaluating candidate technologies at a level that is sufficient to synthesize at least one candidate architecture, and demonstration that the candidate architectures are feasible. Such demonstration is typically achieved through exploratory vertical prototyping of critical parts of candidate architectures and integration of critical technologies. Preparing for the elaboration phase, including risk management as defined in the CI Risk Management Plan and detailed planning for the elaboration iterations X

11 Inception Phase in Detail: Iterations Iteration 1: 5/2 to 6/24 Theme: Inspection, Collection, Definition Iteration 2: 6/27 to 8/21 Theme: Execution to Completion and Delivery Life Cycle Objectives Review: 8/22 to 9/2 Are the requirements understood by the stakeholders, and are they consistent with the critical use cases? Have the critical risks been identified and mitigated through exploratory prototypes? Is there at least one candidate architecture that assuage the critical risks? Are the candidate architectures feasible, as demonstrated through analysis and prototyping? Do the selected key technologies satisfy the architectural needs? Is the elaboration phase plan credible? 9

12 Milestones in Inception Phase Iteration 1: 5/2 to 6/24 Iteration 2: 6/27 to 8/21 Life Cycle Objectives Review: 8/22 to 9/2 10

13 Release 2 Iteration 1 11

14 Release 2 Iteration 1 12

15 Release 2 Iteration 1 13

16 Design Period Week 1 5/2: Kickoff 5/2-5/4: Initial Subsystem Meetings (times TBD) 5/4: Weekly Status Meeting (time TBD) 5/6: Biweekly Assessment Report Due Week 2 5/11: Weekly Status Meeting (time TBD) 5/13: Finalized Iteration Task Plan 14

17 This Week See Coordination 15

18 OCEAN OBSERVATORIES INITIATIVE Release 2 Logistics M a y 2,

19 Tools and Procedures Task Tracking and Reporting: Jira Task Documentation: Confluence Collaborative Calls: WebEx Collaborative Documents: Google docs Collaborative Note-Taking: Etherpad Training Needed 17

20 OCEAN OBSERVATORIES INITIATIVE Coordination M a y 2,

21 This Week 5/2-5/4: Initial Subsystem Meetings (times TBD): COI: CEI: DM: S&A: A&S: EOI: UX: 5/4: Weekly Status Meeting (time TBD): TBD: Logistics Details TBD: Training with Tools 5/6: Biweekly Assessment Report Due 19