1 / 19

VAO Quarterly Management Review, Jan 21, 2011 WBS 4: Product Development

VAO Quarterly Management Review, Jan 21, 2011 WBS 4: Product Development. Ray Plante Gretchen Greene. Planned Work Year 1 (as of ~Oct ‘10). Planned Work from Q1. Accomplishments. Process Development Collaborated with User Support on Testing Plan Integral to Software Development process

abdul-gordon
Download Presentation

VAO Quarterly Management Review, Jan 21, 2011 WBS 4: Product Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VAO Quarterly Management Review, Jan 21, 2011WBS 4: Product Development Ray Plante Gretchen Greene

  2. Planned Work Year 1 (as of ~Oct ‘10)

  3. Planned Work from Q1

  4. Accomplishments Process Development Collaborated with User Support on Testing Plan Integral to Software Development process Drafted Software Development Plan Based on and mandated by PEP Process-oriented, targeted to developer team Lifecycle fully described; tool and policy still to be written Design of JIRA workflows for product development Provide a means for tracking progress via process defined in SDP Enables communication between developers, testers, and managers by reassigning issues Project Lifecyle Issue tracks overall progress Collaborated with Irene Barg on implementation; now ready for use

  5. Accomplishments Infrastructure Development Trac site: dev.usvao.org allows browsing by project Template pages for rapid creation of required documents Project Definition Document Progress Reports fever charts will be effective when project schedules are set Still in development: Project Development Plan, Testing Plan Creating controlled documents draft in Trac exported in ODT for finalizing in Word, publishing in PDF StrawmanHardware Architecture for Development and Test Systems Collaborated with User Support (Brian) on continuous integration tool study plan

  6. Accomplishments Project Work SEDs Detailed science requirements and schedule generated; under review Prototyping communications between SpecView and Sherpa Cross Matching Initial design plan & schedule generated Cross-match request interface specified Portal, Time-Series: scoping under way Registry: requirements study underway; added integrity testing VOView: design set; refactored library; alpha release imminent SSO: new OpenID-based implementation user control over privacy settings ADQL TAP Client: added asynchronous queries flexibility to variable compliance Support secured connections (prep for SSO security) Research into portal integration options

  7. Accomplishments Science Collaborations CANDELS CANDELS-VAO MOU completed; mutual areas of interest: VOEvents Tools to drill down from catalogs to images Tools for constructing and fitting SEDs from diverse data sets Advance catalog matching CANDELS reviewing SED requirements CANDELS-VAO presentation at AAS SMC MOU still under development

  8. Project Statuses

  9. Revising the Schedule Why behind? Cost of starting up distributed teams People transitioning from other projects Some doing this for the first time Attention by PD management (Plante/Greene) focused on establishing process We expected/hoped for more self-organization Some successes (namely SED project) Holiday break/AAS Will need to revise schedule Expected some revision based on coalesced design plans Need to address real process issues

  10. Major Issues Scoping for the remainder of the year Resources for Testing Small testing team: can we really cover testing and user feedback to the level spelled out in the Testing Plan? The more effective the requirements, the more work needed to track and validate them. Portal: will require extensive prototyping and interactions with a user group Need parallel R&P effort along side a pragmatic deliverable for Year 1 Interactions between Science Initiatives and Support Projects Cross education SI projects communicating what they need Support projects communicating what they can provide, how it might fit in How much do we depend on support project deliverables? Are the support project resources re-allocable? Contingency Planning How to interpret 50% in schedule What is the role of tiered priorities as a way of planning contingency? Staffing and scheduling?

  11. Going forward Cross-project education HW assignment for Support Projects: Two paragraph description of how work could fit into science initiatives Key discussion SI discussion telecons Review of HW; answer will SI ask for from Support Projects First one: Technologies for Cross-matching (Monday) Rapid review of Requirements SED project targeted for 2/3 All PDDs and reviews completed by 2/11 Contingency planning Would like to see tiered-prioritization of requirements as part of schedule planning

  12. Planned Work 2011 Q2 (Jan-Mar) • Schedule will fill out as requirements and plans come together

  13. SED Project Overview SED Project Team Project Lead – Janet Evans Science Requirements – Raffaele D’Abrusco / Jonathan McDowell (SAO) SED Library – Mark Cresitello-Dittmar / Joe Miller (SAO) SAO hire in work – expect late Feb; J Miller (from Chandra) filling staffing gap SED/NED Service – Joe Mazzarella / Rick Ebert / Olga Pevunova (IPAC) SED Service Framework – Doug Tody (NRAO) Specview – Ivo Busko (STScI) Sherpa – Stephen Doe / Brian Refsdal (SAO) SAO/VAO Hire in work The Yr1 SED components mainly exist from previous projects; the Yr1 VAO challenge is upgrading DM implem. to current standards and establishing a communication thread between components; We will provide SEDs from NED, read, write, edit, visualize, & fit uniform SEDs.

  14. SED Status Work Completed Established team working relationship & schedule – Early Nov Bi-weekly telecon / email list for communication SED Requirements Doc – last update Dec (RD/JCM) IVOA Note on Photometry/Spectrum/SED DM – End Nov (JCM) SED Science and Software presentations at IVOA – Early Dec (JCM&JDE) SED component derived requirements – End Dec (Each team) SED Lib (MCD), NED/SED (RE), Specview (IB), Sherpa (SD) Work Planned Designs for SED components – All/Working (End Jan) Use Case Doc – RD/Working (End Feb) Photometry/Spectrum/SED DM Stds with IVOA – JCM/Working (Est. Mar) SED Beta1 – Complete end-to-end Yr1 thread (Mid Feb - Apr 1) SED library (New Java Lib using current Spectrum DM standard) SED/NED Service (NED Service using current Spectrum DM standard) SED Service reference framework (for project archives (e.g. CANDELS))

  15. SED Status continued SED Beta1 continued Working SED Application Integrate components and provide interface to NED/SED Service Read SED, viz SED, edit SED, fit SED, write SED (SED/DM, Specview, Sherpa) Internal integration & test / Internal science evaluation Build regression tests / document science tests SED Beta2 (Early May – Early Jun) Component upgrades based on testing feedback Re-test with internal science group DM standards upgrade if IVOA process complete Year 1 requirements not complete in Beta1 VAO test / team regression tests, science test doc, use case doc as input Yr 1 Release (Mid Jun – End Jul) Includes bugfixes/enhancements from testing feedback Integrate into VAO framework – Jira, SVN, Documentation Downloadable on Linux/Mac & Web service are the targets

  16. Portal Progress Portal Vision What is the portal? Initial write-up posted by 2/1/11 AAS Positive feedback and suggestions on Portal Vision Deadlines for Release 1 Requirements process to include CfA VO User group Initial Task Breakdown Posted by 2/1/11 Development Process/Project Plan…

  17. Challenges Deadlines for Release 1 are very close Technical GUI: How best to present, filter and browse data Semantics: How to use data characterization to inform Clever one-box search Filtering of query results Fast Queries on distributed data holdings Managerial Very large project scope Touches most of the other VAO work Requires technical breakthroughs (See above) Resources very small relative to project scope Difficult to quantify available resources Distributed team

  18. Manage Challenges - Immediate Plans For Release 1, expedite the development process Immediately begin development towards core vision In particular, do not wait for further documents or reviews. Critical to get infrastructure in place to explore more detailed requirements and technical challenges. Focus on basic use cases, while keeping an eye towards extensibility of client and server side software. Functionality for Release 1 mostly dictated by what we are able to achieve within the core vision. I.e., we cannot determine a fixed list of Release 1 deliverables ahead of time. In parallel with development, continue: Requirements gathering and refinement Project planning for future work

  19. Manage Challenges - Dev Process Current SDP is too “waterfall” for the portal project. Current SDP is too heavy for a low resource project. Need to use a lean evolutionary process. Flexible requirements Driven by core vision Scope of work limited by project deadlines and resources Guided by science users Story-boarding of major use cases Feedback on initial implementations Minimize process and administrative overheads Includes making the process documentation as succinct as possible Deemphasize formal reviews with gates Emphasize informal reviews and communication

More Related