Meeting Minutes at etherpad.ooici.org/devteammtgs are archived to http://www.oceanobservatories.org/spaces/display/CIDev/Development+Team+Meetings

Date: 2010.03.08  (yyyy.mm.dd)
Description: CI Dev Team Meeting
Attendees:    (your name here)
John Graybeal
David Stuebe
Susanne Jul
Emilia Farcas
Roger Unwin
Claudiu Farcas
Alex Clemesha
Steve Foley
Arjuna Balasuriya
Joseph Curcio
Matt Rodriguez
Paul Hubbard
Brian Dunne
Qian Liu
Tim Freeman
Dorian Raymer

Agenda:
1. LCO Completion (really)
2. Elaboration Phase: Description and Charge
3. Jira Instructions for Design Period
4. Other LCO Wrapup

1. LCO Completion
spent the last week taking receipt

2. Elaboration Phase
a restart
    in the Inception tasks, suggest a closing of Inception tasks and refocusing as elaboration
    top level Inception goal was to describe viable architecture (but not assembled in full)
    the LCA review requires an end to end assembly of all the core components of architecture
        a representation of the R1 configuration (expected to remain reasonably intact into Construction, operational system)
Decisions that are being made now are engineering related, not just architectural.
if we find at LCA some components don't fit, we're open to change; 
    best practices would be to avoid that
we have completed design of the boat, starting to lay down the keel
in next two weeks, we need to understand what the end to end demonstration will be, and what will core components be

set of high-level tasks for Elaboration Plan
    what are named features that we will deliver for demonstrating end to end system at LCA?
    what are named components of the system? components, services, resources
        all resources express their behavior as services
        a component comprises a system, so may be a resouce
    how will we evaluation our success? metrics on tasks?
    how do the features and components relate to the requirements?
    
set of Jira tasks for R1I3 = E1I1 (Release 1 Elaboration: Iteration 1)
    what are named tasks that will be complete?
    what are named components of the system? components=services?
    what metrics do we have to confirm they are done?
            
line between (Inception and) Elaboration and Construction?
    end of Elaboration is functioning system with critical components, proving core system works
        this system is not a prototype, it is demonstration of actual intact system
        some peripheral elements can still be in stubs or not yet added (core system is all present)
        produces functional system
        Elaboration may throw away 50-75% of Inception code (guideline)
        if you're think you're doing prototyping in Elaboration, make sure it is appropriate to be doing so
            should be completed in (early?) first iteration, not shown at end
    end of Construction is complete tested system with all features present, ready for Operations team
        produces operational system
        Construction may throw away 10-25% of Elaboration code (guideline)

Potential conflicts/challenges in multi-institutional collaboration if less than 100%
    conflicts must be able to be brought forward and ameliorated
    any other grants organized this way? not that we know of, in NSF anyway
    asking for very large percent of developers' attention
    AI(John): schedule discussion to identify conflicts with the team leads; document these
    John will be focal point, and will need to identify/bring forward issues as he sees 
    
What are technical concerns/inputs for Design Period?
    sources
        LCO review
        Subsystem Assessment document & Jira tasks
        issues and inputs added today
        
    subsystems/activities  >>> update in Google docs:  to be provided <<<
            overall product description

• need concrete product descriptions to tie component specifications to
• pub-sub network represented in early prototype (toward NOAA data exchange use case)
• prototype with MBARI/NCSA informs instrument integration
• data store across multiple goegraphical sites, operating inside EPU
              COI
• AI-> (QIan) Add Claudiu, Emilia to Dev Leads
              CEI
              DM
              S&A
              Instrument Agent
                  Sensor prototype
              Observatories integration
                  IOOS collaboration
              User interfaces/user experience
• behind on this
• won't ask end users of R1 (not administrators) to download something in R1
• operator in R1 is our own operations team, process of deployable types may address this (CEI deliverable).
              
  What is the road map for these 2 weeks?
       core statement of product: week 1
       presentation next Monday to this meeting

Overall product description format?

• Michael's list is a notional start
• Format examples can be identified