1 / 18

External Handover Process Karen Connors, PMP Deputy PM, Architecture and Integration OneSAF

One Semi-Automated Force (OneSAF). External Handover Process Karen Connors, PMP Deputy PM, Architecture and Integration OneSAF. Overview General Handover Criteria Build/Release Schedule Internal Process Flow for Handovers Electronic Process Guide (EPG) Dependency Meetings

zubeda
Download Presentation

External Handover Process Karen Connors, PMP Deputy PM, Architecture and Integration OneSAF

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. One Semi-Automated Force (OneSAF) External Handover ProcessKaren Connors, PMPDeputy PM, Architecture and IntegrationOneSAF

  2. Overview General Handover Criteria Build/Release Schedule Internal Process Flow for Handovers Electronic Process Guide (EPG) Dependency Meetings Builds 9/10 Important Dates Community Site Registration Forms Initial Handover Package Summary External Handover ProcessAgenda Briefing objective: Communicate the Handover Process to Co-developers.

  3. External Handover Process Overview • The Handover Process for External Co-Developers has recently beenreviewed and updated in order to coordinate the receipt of handovers in a more formal, controlled environment. • A&I and the PEO STRI continue to improve the process to streamline activities and communicate information to the community. • The Community website has been updated with handover deadlines, required artifacts (downloadable and web-enabled) and will incorporate additional process information in the near future. • The Government POC for Co-developer Handovers is: Oanh Tran Oanh.Tran@us.army.mil 407-384-3868

  4. External Handover ProcessGeneral Handover Criteria • Integration with OneSAF: It is expected that handovers are submitted for the purpose of integration into OneSAF, and that they are ready for integration. • Development baseline: Capabilities should be developed against the most recent generally available release. • Architectural compliance: Handover products should comply with architectural and design guidelines, protocols, language compatibilities, code structures, and documentation standards. • Testing: Capabilities must be tested during development to ensure that they operate as designed. • Classification: At present, all handover products must be unclassified.

  5. External Handover ProcessBuild/Release Schedule Release 3.0 1Q CY09 2008 2007 2009 MAR FEB Release 2.5 3Q CY08 JAN 3.0 Assessment DEC NOV Release 2.1 2Q CY08 OCT SEP AUG 2.0 29 FEB 2008 JUL JUN MAY Release 2.0 APR MAR FEB JAN DEC 2.0 Assessment Build 7 12/3 – 2/22 12 wks Build 8 2/25 – 5/2 10 wks Build 9 5/5 – 7/11 10 wks Build 10 7/14 – 9/19 10 wks Build 11 9/22 – 11/28 10 wks Build 12 12/1/08 – 2/20/09 12 wks

  6. External Handover ProcessProcess Flow for Handovers 5 1 2 4 Submit Registration Forms Receive results From Government Initial Handover Package Due External Dependency Meeting 3 Review Weeks 1 2 3 4 5 6 7 • Is there a level of interest in integrating with OneSAF? • Participate in an External Dependency Meeting (dates/forms posted on OneSAF.net) • Ready to move forward? • Submit Registration forms via website or e-mail forms to Oanh Tran (dates/forms posted on OneSAF.net) • Registration is reviewed and considered for integration into a OneSAF future release • Government will contact co-developer with results • Still being considered for the next release? • Turn in Initial Handover Package (dates/forms posted on OneSAF.net) 1 2 3 4 5

  7. External Handover ProcessInternal Process Flow for Handovers Next Steps (in coordination with Co-developer): Peer Review of Handover Package Defects addressed Request for Code/Documentation A&I Performs Detailed Review of Code/Documentation Engineering Change Control Board (ECCB) Meeting Integration and Test (co-developer participation desired) OneSAF Release

  8. External Handover ProcessRegistration Forms Registration Forms 1. Registration Form 2. List of Files Modified/Changed

  9. External Handover ProcessInitial Handover Package (1/2) • Initial Handover Package • 1. Handover Forms • Signatures and Feedback Form • This form documents completion at each phase of the handover process. • External Development Handover Form • This is the biggie! This form is where you begin in putting together a handover package. It contains all the documentation required, and criteria necessary, for a smooth and successful handover. • New/Modified Files Change List • This list should correspond with the files contained in the source build (see Software Included on the External Development Handover Form). Please include full paths for all files. • Known Handover Issues • Pretty self explanatory. You got "uh oh's" coming in? Let us know about them! • Analysis/Design Document • What did you add or change, and how did you accomplish the addition/modification? Feel free to add additional pages or make the cells bigger to accommodate your design descriptions. • List of Test Plans • List any test plans that were developed to test your new and/or modified functionality. • List of JUnit Tests • List all JUnit Tests that are new or were modified with your handover. • Domain Documentation List • Did you add new units? new models? new data? Excellent! This Document allows OneSAF to maintain traceability on the source of the new "stuff". Where did you get that data? What is the justification for those models and units?

  10. External Handover Process Initial Handover Package (2/2) • Initial Handover Package • 2. Compliance Checklist - External developer performs self-assessment • Infrastructure Compliance • Platform Compliance • User Interface Compliance • Process Compliance • Deployment Compliance • Verification Compliance • Performance Compliance

  11. External Handover ProcessElectronic Process Guide

  12. External Handover Process Electronic Process Guide 1. From the OneSAF.net internal development site (https://dev.onesaf.net/ or through the OneSAF Community page) find the Architecture & Integration Task Order link. 2. Locate the EPG button as shown.

  13. External Handover ProcessDependency Meetings New Calendar Feature POC and Form

  14. External Handover ProcessBuilds 9/10 Important Dates • External Dependency Meeting • 23 April 2008 (2 weeks before Build 9) • Build 9 Start – 5 May 2008 • Build 9 Complete – 11 July 2008 • External Dependency Meeting • 2 July 2008 (2 weeks before Build 10) • Build 10 Start – 14 July 2008 • Build 10 Complete – 19 September 2008

  15. External Handover ProcessCommunity Site New Calendar Feature

  16. External Handover ProcessCommunity Site

  17. External Handover ProcessSummary 5 1 2 4 Submit Registration Forms Receive results From Government Initial Handover Package Due External Dependency Meeting 3 Review Weeks 1 2 3 4 5 6 7 We are continuously improving the Handover Process

  18. Questions and Discussion External Handover Process

More Related