Ocean Observatories Initiative

OOI CI Release 3 (Scope To Complete) Kick-Off

Tim Ampe: System Development Manager

Release 3 Kick-off

La Jolla, CA October 3, 2013

1

Agenda

• Rationale and Process for Release• Dates, Phases, and Content for Release• Tasks, Jira Tickets and Progress Tracking• Team Formations and Organizational Structure• Deliverables and Milestones• Integration Team’s Role• User Interface Plan• System Engineering’s Role• Support for Release 2 and Marine Integration• Source Code Management and Branching Strategy

2

Scope To Complete Rationale and Process• Release 2 was late, requiring re-plan• Prioritization of remaining functionality was performed

– Starting Point: PI (John Orcutt) prioritized List– Initial focus: Delivarables/Milestones/Tasks required for PI Priority 1

capabilities– Planning consultant assisted with tasking/pricing– Mapped Priority 1 capabilities to Deliverables– Created consolidated spreadsheet of mapped

Deliverables/Milestones/Tasks– Initial review of all milestones by team to identify/drop duplicates,

clean up list– Identified and assigned “stakeholder” roles and voted priorities– Generated proposed prioritized list, timeframe, and budget– Many Milestones “fell off the edge”

3

Scope To Complete Rationale and Process

• L4/L3/L2 Requirements mapped to milestones/deliverables

• Presented plan to OL and Marine IOs at OOI Tiger Team Meeting end of July– Reprioritization of deliverables/milestones based on OL/Marine IO

Feedback– Shortening of timeframe for development and elimination of R4– Outcome from OOI Tiger Team meeting for STC (R3):

• 21 Deliverables• 35 Milestones• 20 Developers• 5.5 months

4

Dates and Phases for Release 3 (STC)• Construction 10/1/13 - 3/31/14

– ~5.5 months excluding holidays to develop functionality– Includes integration and testing of each Deliverable/Milestone as they are

finished – not done at the end

• System Verification 4/1/14 - 5/2/14– ~1 month to complete any “straggler” deliverables, fix bugs, verify

requirements, and complete remaining integration testing– Initial Operating Capability Review

• System Transition 5/5/14 - 6/2/14– ~1 month to fix bugs and complete end-to-end testing– Product Readiness Review

• System Commissioning 6/3/14 - 6/30/14– System Validation by OL with support from CI– Ending in System being Commissioned and made available to scientific

community

Content of Release 3 (STC)• 21 Deliverables with 35 Milestones and associated tasks

• Associated Jira Bugs (Mapped to Milestones) and Requirements• https://confluence.oceanobservatories.org/display/CIDev/R3+Deliverables+and+Milestones

Tasks, Jira Tickets and Progress Tracking• Each Deliverable has 1 or more Milestones and each Milestone has set of Tasks

• Tasks will go into JIRA and Tracked with burndown charts as we did in R2

• When all milestones in deliverable completed, integrated into OOIN test system and validated by integration (ITV) team

7

Example R2 JIRA Burndown

8

Team Formations and Org Structure

9

R. Singh: UCSDL. Campbell: ASASenior Developer 1: ASASenior Developer 2: ASADeveloper 1: ASA

C. Rueda: MBARIS. Said: UCSDC. Cowart: UCSDSenior Developer 1: ASADeveloper 1: ASA

P. Armstrong: ANLP. Kediyal: UCSDSenior Developer 1: ASASenior Developer 2: ASA

Senior Developer 1: ASASenior Developer 2: ASASenior Developer 3: ASA

B. Bollenbacher: UCSDIntegration Engineer 1: ASAIntegration Engineer 2: ASAIntegration Engineer 3: ASA

Deliverable and Milestone Preparation

• Deliverable and Milestone Examples on Confluence:– Deliverable

• https://confluence.oceanobservatories.org/display/CIDev/D053+Data+Access+Service

– Milestones• https://confluence.oceanobservatories.org/display/CIDev/D017+IPython+Not

ebook+Integration• https://confluence.oceanobservatories.org/display/CIDev/M088+Data+QC+m

anagement

• For each Milestone:– Use Cases– Assigned Requirements– Verification Procedures for each Requirement– Validation Procedures for milestone/deliverable

10

Integration Team’s Role

• Formal validation of Deliverables/Milestones in OOIN test system

• Integration assistance for Data Agents/Instrument Agents• Release Documentation• Interaction with Marine IOs during Marine IO testing• Manage build and test infrastructure• Manage OOIN test systems• Load testing and load testing infrastructure• Tracking of Code Coverage• Etc.

11

User interface Plan

• UI Development moving to Raytheon Web Solutions – Pasadena, CA

• Development done under CI System Development Manager and OceanLeadership’s supervision

• Initial kick-off discussion shortly• Two month evaluation + Four month development effort• R3 UI milestone development + R2 UI Bug fixes• R3 UI milestone Integration with OOIN services joint

responsibility

12

System Engineering’s Role

• One FTE System Engineer– Likely filled by OceanLeadership (Kathy Carr/Bill Bergen)

• Requirements refinement and tracking• Assistance/Review of Milestone Use Cases• Requirements testing procedures and verification test

execution• Risk Management and Change Control

13

Support for Release 2 and Marine Integration

• Release 2 Updates to support Marine Deployments– Bug fixes on REL2.0 Branch and any new UI screens– Integration of Dataset Agent/Drivers, Instrument Agent/Drivers,

Platform Agent/Drivers, Data Product Transform Functions

• Maintenance of R2 OOIN system(s)

14

Source Code Mgmt & Branching Strategy

• Confluence page sent to team last week– https://confluence.oceanobservatories.org/display/CIDev/

Transition+from+Release+2.0+to+Pre-Release+3.0– REL2.0 Support Branch Created– Should Review References– Luke to cover in detail

15