1 Southern Hemisphere Automated Snow/Ice (ASI) Gate 3 Review Appendix A September 14, 2010 Southern Hemisphere Automated Snow/Ice (ASI) Gate 3 Review Appendix.

Slides:



Advertisements
Similar presentations
QuEdge Testing Process Delivering Global Solutions.
Advertisements

Enterprise Performance Life Cycle (EPLC) Stage Gate Reviews
Requirements Specification and Management
S Y S T E M S E N G I N E E R I N G.
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
1 Lecture 3.2: Technical Reviews and Audits (SEF Ch 11) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Alternative Methodologies Ken Peffers UNLV March 2004.
Software life cycle processes Purpose n A new international standard (ISO/IEC 12207:1995(E) that –establishes a common framework for software life cycle.
Unit 191 Introduction to Software Engineering The objective of this section is to introduce the subject of software engineering. When you have read this.
Software Project Transition Planning
The Software Development Standards Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Effective Methods for Software and Systems Integration
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
S/W Project Management
EOSC Generic Application Security Framework
Software Engineering Term Paper
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Software Configuration Management
The Software Development Standards Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
Software Configuration Management (SCM)
The Software Development Standards Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
1 Configuration Management “The Cookbook Approach”
VST: dome THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS Ing. Davide Fierro THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
NASA’s Goddard Space Flight Center Systems Engineering Mike Pryzby Swales Aerospace August 16-17, 2005.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D.
© Mahindra Satyam 2009 Configuration Management QMS Training.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Lecture Introduction to Software Development SW Engg. Development Process Instructor :Muhammad Janas khan Thursday, September.
Software Quality Assurance Lecture # 6 By: Faraz Ahmed.
Core Banking Transformation: A Roadmap to a Successful Core Banking Product Implementation - PMI Virtual Library | | © 2008 Kannan S. Ramakrishnan.
What is Testing? Testing is the process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies.
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
COSC 4303 Software Engineering Introduction and Initial Planning of Group Projects Fall 2007.
Configuration Management Romuald Duperrier Head of Systems Engineering Division April 22, 2015.
Configuration Management- Basic Concepts. Agenda  Configuration Management process Overview  Process Stages  Planning & Setup  Control  Audit  Case.
Objectives Understand Corrective, Perfective and Preventive maintenance Discuss the general concepts of software configuration management.
 Establishing state-of-the-art coding, documentation, configuration management standards for the AWG.  Software development process comparable with CMMI.
Homework #1a Lifecycle Paper For each stage of the life cycle provide a list of items you think should be there. There should be at a minimum of five items.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
I. UML Tool review (Rhapsody) and II. Requirement and TEST in UML modeling May 31th 2005 KIM, YUN GOO Lab Seminar.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
PRODUCT VERIFICATION Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
SOFTWARE TESTING TRAINING TOOLS SUPPORT FOR SOFTWARE TESTING Chapter 6 immaculateres 1.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
The Software Development Standards
Supportability Design Considerations
Software Testing.
Key Management Issues for Software Reviews
Software Verification and Validation
Configuration Management Why do we need it? What does it do?
IEEE Std 1074: Standard for Software Lifecycle
V-Shaped SDLC Model Lecture-6.
Software Requirements
SQA Role during Software Requirements Phase
Engineering Processes
Gestion de la documentation pendant le cycle de développement
Software Quality Assurance Plans
[Work Order #] [ARB Date]
Instrument PDR Summary of Objectives
Managing the Test Process CS 4501 / 6501 Software Testing
Engineering Processes
PSS verification and validation
Configuration Management
Requirements Engineering
Presentation transcript:

1 Southern Hemisphere Automated Snow/Ice (ASI) Gate 3 Review Appendix A September 14, 2010 Southern Hemisphere Automated Snow/Ice (ASI) Gate 3 Review Appendix A September 14, 2010 Prepared By: Peter Romanov 1 and Ken Jensen 2 1 UMD/CICS 2 Raytheon MOS

2 ASI Gate 3 Review Appendix A – Review Entry and Exit Criteria

3   Entry # 1 - A Development Project Plan (DPP) has been written. The Gate 3 reviewers have access to the review version of the DPP.   Entry # 2 - A Project Status Report (PSR) has been written. The Gate 3 reviewers have access to the review version of the PSR.   Entry # 3 - A Gate 3 Document (G3D) has been written. The Gate 3 reviewers have access to the review version of the G3D.   Entry # 4 - A Project Baseline Report (PBR) has been written. The Gate 3 reviewers have access to the review version of the PBR. ASI Gate 3 Review Entry Criteria

4   Exit # 1 - Project plan and DPP are satisfactory   Exit # 2 - Project status and PSR are satisfactory   Exit # 3 - Project baseline and PBR are satisfactory   Exit # 4 - Project risks are acceptable   Exit # 5 - Status of risk mitigation actions is acceptable   Exit # 6 - Project is ready for the Design phase ASI Gate 3 Review Exit Criteria

5   Entry # 1 - A Gate 3 Review Report (G3RR) has been written. The CDR reviewers have access to the review version of the PDRR.   Entry # 2 - A Development Project Plan (DPP) has been written. The CDR reviewers have access to the review version of the DPP.   Entry # 3 - An Operations Concept Document (OCD) has been written. The CDR reviewers have access to the review version of the OCD.   Entry # 4 - A Requirements Allocation Document (RAD) has been written. The CDR reviewers have access to the review version of the RAD.   Entry # 5 - An Algorithm Theoretical Basis Document (ATBD) has been written. The CDR reviewers have access to the review version of the ATBD.   Entry # 6 - A Software Architecture Document (SWA) has been written. The CDR reviewers have access to the review version of the SWA. ASI Stage 1 CDR – Entry Criteria # 1-6

6   Entry # 7 - A Detailed Design Document (DDD) has been written for each software unit in the software architecture. The CDR reviewers have access to the review version of each DDD.   Entry # 8 - A Verification and Validation Plan (VVP) has been written. The CDR reviewers have access to the review version of the VVP.   Entry # 9 - A Project Status Report (PSR) has been written. The CDR reviewers have access to the review version of the PSR.   Entry # 10 - A Critical Design Document (CDD) has been written. The CDR reviewers have access to the review version of the CDD.   Entry # 11 - A Project Baseline Report (PBR) has been written. The CDR reviewers have access to the review version of the PBR. ASI Stage 1 CDR – Entry Criteria # 7-11

7  G3  Exit # 1 - G3R "Conditional Pass" items have been satisfactorily disposed of.   Exit # 2 – G3R "Defer" items have been satisfactorily disposed of.   Exit # 3 – Stage 1 Operations concept and OCD are satisfactory.   Exit # 4 – Stage 1 requirements identification is satisfactory.   Exit # 5 - Stage 1 requirements analysis is satisfactory.   Exit # 6 - Stage 1 requirements traceability is satisfactory. ASI Stage 1 CDR – Exit Criteria # 1-6

8   Exit # 7 - Stage 1 requirements tracking plan is satisfactory   Exit # 8 – Stage 1 algorithm theoretical basis and ATBD are satisfactory.   Exit # 9 – Stage 1 software architecture and SWA are satisfactory.   Exit # 10 – Stage 1 external interfaces are satisfactory.  s  Exit # 11 – Stage 1 software detailed design and DDDs are satisfactory.   Exit # 12 – Stage 1 verification and validation plan and VVP are satisfactory ASI Stage 1 CDR – Exit Criteria # 7-12

9   Exit # 13 – Stage 1 requirements allocation and RAD are satisfactory.   Exit # 14 – Stage 1 baseline and PBR are satisfactory.   Exit # 15 - Project risks and actions are acceptable.   Exit # 16 - Project status and PSR are satisfactory.   Exit # 17 - Project is ready for the Stage 1 Build phase ASI Stage 1 CDR – Exit Criteria # 13-17

10   Entry # 1 - A Stage 1 Critical Design Review Report (CDRR) has been written. The SRR reviewers have access to the review version of the Stage 1 CDRR.   Entry # 2 - A Development Project Plan (DPP) has been written. The SRR reviewers have access to the review version of the DPP.   Entry # 3 - An Operations Concept Document (OCD) has been written. The SRR reviewers have access to the review version of the OCD.   Entry # 4 - A Requirements Allocation Document (RAD) has been written. The SRR reviewers have access to the review version of the RAD.   Entry # 5 - An Algorithm Theoretical Basis Document (ATBD) has been written. The CDR reviewers have access to the review version of the ATBD.   Entry # 6 - A Software Architecture Document (SWA) has been written. The SRR reviewers have access to the review version of the SWA.   Entry # 7 - A Detailed Design Document (DDD) has been written for each software unit in the software architecture. The SRR reviewers have access to the review version of the DDDs. ASI Stage 1 SRR – Entry Criteria # 1-7

11   Entry # 8 - A Verification and Validation Plan (VVP) has been written. The CTR reviewers have access to the review version of the VVP.   Entry # 9 - A Users Manual (UM) has been written. The SRR reviewers have access to the review version of the UM.   Entry # 10 - An Operations Manual (OM) has been written. The SRR reviewers have access to the review version of the OM.   Entry # 11 - An Interface Control Document (ICD) has been written. The SRR reviewers have access to the review version of the ICD.   Entry # 12 - A System Description Document (SDD) has been written. The SRR reviewers have access to the review version of the SDD.   Entry # 13 - A System Maintenance Manual (SMM) has been written. The SRR reviewers have access to the review version of the SMM.   Entry # 14 - Pre-operational code units, external interfaces, ancillary data, and system test data have been integrated into a Stage 1 product processing system in the development environment. The SRR reviewers have access to the product processing system. ASI Stage 1 SRR - Entry Criteria # 8-14

12   Entry # 15 - A Unit Test Plan (UTP) has been written. The SRR reviewers have access to the review version of the UTP.   Entry # 16 - A Unit Test Report (UTR) has been written. The SRR reviewers have access to the review version of the UTR.   Entry # 17 - A System Test Plan (STP) has been written. The SRR reviewers have access to the review version of the STP.   Entry # 18 - A Verification and Validation Report (VVR) has been written. The SRR reviewers have access to the review version of the VVR.   Entry # 19 - A System Readiness Document (SRD) has been written. The SRR reviewers have access to the review version of the SRD.   Entry # 20 - A Project Baseline Report (PBR) has been written. The SRR reviewers have access to the review version of the PBR. ASI Stage 1 SRR - Entry Criteria # 15-20

13   Exit # 1 – Stage 1 CDR "Conditional Pass" items have been satisfactorily disposed of.   Exit # 2 – Stage 1 CDR "Defer" items have been satisfactorily disposed of.   Exit # 3 - The project plan and DPP are satisfactory   Exit # 4 - The Stage 1 requirements allocation and RAD are satisfactory.   Exit # 5 - The Stage 1 algorithm and ATBD are satisfactory.   Exit # 6 - The Stage 1 design documents (SWA and DDDs) are satisfactory. ASI Stage 1 SRR – Exit Criteria # 1-6

14   Exit # 7 - The Stage 1 operations documents (UM, OM, ICD, SDD, SMM) are satisfactory.   Exit # 8 - The Stage 1 delivery procedures, tools, training, support services, and documentation available to the users are satisfactory.   Exit # 9 – Stage 1 system test results and VVR are satisfactory.   Exit # 10 - The Stage 1 project baseline and PBR are satisfactory.   Exit # 11 - The Stage 1 SRRR documents updated status of project risks and actions. The risk status is acceptable.   Exit # 12 - The integrated Stage 1 product processing system is ready for delivery to operations. ASI Stage 1 SRR – Exit Criteria # 7-12

15   Entry # 1 - A Stage 1 System Readiness Review Report (SRRR) has been written. The CDR reviewers have access to the review version of the SRRR.   Entry # 2 - A Development Project Plan (DPP) has been written. The CDR reviewers have access to the review version of the DPP.   Entry # 3 - An Operations Concept Document (OCD) has been written. The CDR reviewers have access to the review version of the OCD.   Entry # 4 - A Requirements Allocation Document (RAD) has been written. The CDR reviewers have access to the review version of the RAD.   Entry # 5 - An Algorithm Theoretical Basis Document (ATBD) has been written. The CDR reviewers have access to the review version of the ATBD.   Entry # 6 - A Software Architecture Document (SWA) has been written. The CDR reviewers have access to the review version of the SWA. ASI Stage 2 CDR – Entry Criteria # 1-6

16   Entry # 7 - A Detailed Design Document (DDD) has been written for each software unit in the software architecture. The CDR reviewers have access to the review version of each DDD.   Entry # 8 - A Verification and Validation Plan (VVP) has been written. The CDR reviewers have access to the review version of the VVP.   Entry # 9 - A Project Status Report (PSR) has been written. The CDR reviewers have access to the review version of the PSR.   Entry # 10 - A Critical Design Document (CDD) has been written. The CDR reviewers have access to the review version of the CDD.   Entry # 11 - A Project Baseline Report (PBR) has been written. The CDR reviewers have access to the review version of the PBR. ASI Stage 2 CDR – Entry Criteria # 7-11

17  Stage 1 SR  Exit # 1 - Stage 1 SRR "Conditional Pass" items have been satisfactorily disposed of.   Exit # 2 – Stage 1 SRR "Defer" items have been satisfactorily disposed of.   Exit # 3 – Stage 2 Operations concept and OCD are satisfactory.   Exit # 4 – Stage 2 requirements identification is satisfactory.   Exit # 5 - Stage 2 requirements analysis is satisfactory.   Exit # 6 - Stage 2 requirements traceability is satisfactory. ASI Stage 2 CDR – Exit Criteria # 1-6

18   Exit # 7 - Stage 2 requirements tracking plan is satisfactory   Exit # 8 – Stage 2 algorithm theoretical basis and ATBD are satisfactory.   Exit # 9 – Stage 2 software architecture and SWA are satisfactory.   Exit # 10 – Stage 2 external interfaces are satisfactory.  s  Exit # 11 – Stage 2 software detailed design and DDDs are satisfactory.   Exit # 12 – Stage 2 verification and validation plan and VVP are satisfactory ASI Stage 2 CDR – Exit Criteria # 7-12

19   Exit # 13 – Stage 2 requirements allocation and RAD are satisfactory.   Exit # 14 – Stage 2 baseline and PBR are satisfactory.   Exit # 15 - Project risks and actions are acceptable.   Exit # 16 - Project status and PSR are satisfactory.   Exit # 17 - Project is ready for the Stage 2 Build phase ASI Stage 2 CDR – Exit Criteria # 13-17

20   Entry # 1 - A Stage 2 Critical Design Review Report (CDRR) has been written. The SRR reviewers have access to the review version of the Stage 2 CDRR.   Entry # 2 - A Development Project Plan (DPP) has been written. The SRR reviewers have access to the review version of the DPP.   Entry # 3 - An Operations Concept Document (OCD) has been written. The SRR reviewers have access to the review version of the OCD.   Entry # 4 - A Requirements Allocation Document (RAD) has been written. The SRR reviewers have access to the review version of the RAD.   Entry # 5 - An Algorithm Theoretical Basis Document (ATBD) has been written. The CDR reviewers have access to the review version of the ATBD.   Entry # 6 - A Software Architecture Document (SWA) has been written. The SRR reviewers have access to the review version of the SWA. ASI Stage 2 SRR – Entry Criteria # 1-6

21   Entry # 7 - A Detailed Design Document (DDD) has been written for each software unit in the software architecture. The SRR reviewers have access to the review version of the DDDs.   Entry # 8 - A Verification and Validation Plan (VVP) has been written. The CTR reviewers have access to the review version of the VVP.   Entry # 9 – An External Users Manual (EUM) has been written. The SRR reviewers have access to the review version of the EUM.   Entry # 10 - A System Maintenance Manual (SMM) has been written. The SRR reviewers have access to the review version of the SMM.   Entry # 11 - Pre-operational code units, external interfaces, ancillary data, and system test data have been integrated into a Stage 2 product processing system in the development environment. The SRR reviewers have access to the product processing system. ASI Stage 2 SRR - Entry Criteria # 7-11

22   Entry # 12 - A Unit Test Plan (UTP) has been written. The SRR reviewers have access to the review version of the UTP.   Entry # 13 - A Unit Test Report (UTR) has been written. The SRR reviewers have access to the review version of the UTR.   Entry # 14 - A System Test Plan (STP) has been written. The SRR reviewers have access to the review version of the STP.   Entry # 15 - A Verification and Validation Report (VVR) has been written. The SRR reviewers have access to the review version of the VVR.   Entry # 16 - A System Readiness Document (SRD) has been written. The SRR reviewers have access to the review version of the SRD.   Entry # 17 - A Project Baseline Report (PBR) has been written. The SRR reviewers have access to the review version of the PBR. ASI Stage 2 SRR - Entry Criteria # 12-17

23   Exit # 1 – Stage 2 CDR "Conditional Pass" items have been satisfactorily disposed of.   Exit # 2 – Stage 2 CDR "Defer" items have been satisfactorily disposed of.   Exit # 3 - The project plan and DPP are satisfactory   Exit # 4 - The Stage 2 requirements allocation and RAD are satisfactory.   Exit # 5 - The Stage 2 algorithm and ATBD are satisfactory.   Exit # 6 - The Stage 2 design documents (SWA and DDDs) are satisfactory. ASI Stage 2 SRR – Exit Criteria # 1-6

24   Exit # 7 - The Stage 2 operations documents (EUM and SMM) are satisfactory.   Exit # 8 - The Stage 2 delivery procedures, tools, training, support services, and documentation available to the users are satisfactory.   Exit # 9 – Stage 2 system test results and VVR are satisfactory.   Exit # 10 - The Stage 2 project baseline and PBR are satisfactory.   Exit # 11 - The Stage 2 SRRR documents updated status of project risks and actions. The risk status is acceptable.   Exit # 12 - The integrated Stage 2 product processing system is ready for delivery to operations. ASI Stage 2 SRR – Exit Criteria # 7-12