Configuration Management/Quality Assurance activity spans from Concept Exploration through the end of the life cycle.  Configuration Management Plans, Program Quality Assurance Plans, and QA audit reports are produced and maintained throughout this span.  Functional Configuration Audit and Physical Configuration Audit Checklists and Reports are also produced.

Additionally, there is ongoing operational/customer assessment taking place (represented on the diagram with a dotted, activity box with arrows on both ends).

In the Component Advanced Development, the Program Planning/Management activity produces these documents:

• Program Management Plan
• Data Management Plans
• Test and Evaluation Master Plan
• Economic Analysis (for MAIS programs)
• Life Cycle Cost Estimate
• Component Cost Analysis (performed by DFAS Resource Management Office)
• Cost Analysis Requirements Description (CARD) (for MAIS programs)
• Acquisition Program Baseline (APB)
• Clinger-Cohen Compliance Report (for MAIS programs)

Also in the Component Advanced Development subphase are three other activities: Operational Requirements Definition (which produces the Operational Requirements Document (ORD)); System Requirements Analysis (which produces the Command, Control, Communications, Computers and Intelligence (C4I) Support Plan, the System Requirements Specification (SRS), and the Joint Technical Architecture (JTA) Profile)); and System Architecture Design (which produces the Infrastructure Services Request and the System Architecture and Requirements Allocation Description (SARAD)).  In addition, during this subphase, the Information Assurance/Security activity begins and produces the definition portion of the System Security Authorization Agreement (SSAA).  The Information Assurance/Security activity continues over the rest of the life cycle.

Moving on to the System Development and Demonstration phase (System Integration subphase):  the Program Planning/Management activity produces the Continuity of Operations Plan (COOP) and updates the APB.  The Information Assurance/Security activity produces the Verification portion of the SSAA.  The Technical Project Planning/Management activity, which continues throughout this phase and into the first subphase of Production and Deployment, produces the Software Development Plan and the Software Process Improvement (SPI) Plan. The SPI Plan is not applicable to COTS.  The System Development activity (which indicates build (with a development IPT) or purchase (purchase/customize/integrate product(s))) is described in the next slide.  The Test Planning activity produces the Test Plans.

In the System Development and Demonstration phase, System Demonstration subphase, the Program Planning/Management activity produces a finalized APB and reviews the Clinger-Cohen Compliance Report.  The Verification portion of the SSAA is produced during the Information Assurance/Security activity.  The Deployment Planning activity produces the Transition Plans, Training Plans, Installation Plans, and finalizes the Infrastructure Services Request.

Also in this subphase, Developmental Test and Evaluation takes place, as well as Operational Test and Evaluation (which spans into the next phase).  The products of those activities are Test Scripts, Test Discrepancy Reports, Test Reports, and Compliance Certifications.

When you get to the Full-Rate Production and Deployment subphase of the Production and Deployment phase:

• The Operation and Performance Oversight activity produces audit reports, performance measurements, and program trouble reports (PTR)
• SSAA Security Operations and Compliance Validation is produced in the Information Assurance/Security activity
• Site Acceptance Test Reports are produced during the Deployment and Site Acceptance Test activity.

Near the bottom of the diagram, blue boxes are shown to represent baselines.  The Program Baseline is produced during Concept and Technology Development (Component Advanced Development) and contains the ORD, APB, and TEMP.  The Functional Baseline is produced at the beginning of System Development and Demonstration (System Integration) and includes the SRS and SARAD.  The Allocated Baseline is produced at the end of System Integration and consists of the Software Requirements Description (SRD), the Software Architecture Description (SAD), the Software Interface Design Description (SIDD), the Database Design Description (DBDD), and the Software Design Description (SDD).  The Product Baseline is produced during Production and Deployment and consists of the COTS Product Description and the SDD, SAD, SIDD, DBDD, and Software Configuration Index Record (SCIR).  The Operational Baseline is created during the Full-Rate Production and Deployment subphase and consists of the User's Manual and the Operator's Manual.

Management reviews are shown at the bottom of the diagram in yellow diamonds. They include:

• System Requirements Review (SRR), performed prior to Milestone B
• Release Reviews, performed during the System Development activity
• Implementation Readiness Review, performed in conjunction with the Full-Rate Production Decision Review
• Post Implementation Review, performed after the system/release has been deployed

Two audits, shown on the diagram as open black circles, occur prior to Milestone C. They are the Functional Configuration Audit and the Physical Configuration Audit.

A pink arrow (Changes to the Deployed System) appears at the rightmost of the diagram and leads to another slide in this diagram (System Maintenance).

Footnotes and a Legend also appear on the diagram.

Slide 3:  This slide shows the two System Life Cycle Development Alternatives which can occur during the System Integration subphase.  On the left is Develop and on the right is Purchase/Customize/Integrate.  Both of these choices start with the Milestone B Review and the establishment of the Functional Baseline and end with a Release Review, the Interim Progress Review and the establishment of the Allocated Baseline.

In the Develop area, the Development Integrated Product Team (IPT) goes through cyclical iterations of software requirements analysis, software architecture design, software design, software coding, unit testing, and IPT review.  As a result of these iterations, the following documents are developed:  Software Requirements Description, Infrastructure Requirements Description, Test Scripts, Software Architecture Description, Software Interface Design Description, Database Design Description, Software Design Description, Software Configuration Index Record, User's Manual, Operator's Manual, Unit Test Report, and Application Release Checklist.  After the Interim Progress Review, formal testing begins.

In the Purchase/Customize/Integrate area, the following documents are developed: COTS Customization Plan, Software Interface Design Description, User's Manual, Operator's Manual, Software Configuration Index Record, and COTS Customized Product Description.  Also, the Software Requirements Description, Software Architecture Description, Test Scripts, Database Design Description, Software Design Description are produced for modifications only.

Slide 4:  This slide shows the process for the Production and Deployment phase for system maintenance. The deployed system would come into this process (as shown on the chart by a pink block arrow). Subphases and major reviews are shown across the top of the slide. They are: Capture and Identify; Analyze and Document; Validate, Approve, and Allocate; Requirements/Solution Review; Design; Design Review; Development; Test Readiness Review; Validate/Accept; Operational Test Readiness Review; Implementation Readiness Review; Field; Post Implementation Review; Measure Effectiveness. The approval process for the reviews performed during the maintenance phase are:

• Corporate-level Change Requests are reviewed and approved by CIO/BIE Council
• Business Line-level Change Requests are review and approved by Business Line Management Board
• System-level Change Requests are reviewed and approved by System CCB

During the Capture and Identify subphase, there is a Capture and Identify Change Request activity which produces the System Change Request. In the Analyze and Document subphase, an Impact Analysis activity shows on the chart, but no products are shown. During the Validate, Approve, and Allocate, the Requirements/Solution Review is performed. The Program Planning/Management activity is conducted over subphases Design, Development, Validate/Accept, and Field, with the products being the System Management Plan and the Customer Memorandum of Understanding (MOU). The Information Assurance/Security activity also spans from Design through Measure and Effectiveness, with the SSAA and the Accreditation Memo being maintained.  Release Planning is performed during the Design subphase, producing the Systems Requirements Specification, the System Architecture and Requirements Allocation Description, and the Infrastructure Services Request. The Technical Project Planning/Management activity spans from the Design subphase into the Field subphase. The product there is the Software Development Plan.

The System Manager briefs the tailored system life cycle at the requirements/solution review.  Starting with the Design subphase and going through the Development subphase, the Development Integrated Product Team (IPT) goes through cyclical iterations of software requirements analysis, software architecture design, software design, software coding, unit testing, and IPT review.  As a result of these iterations, the following documents are developed:  Software Requirements Description, Infrastructure Requirements Description, Test Scripts, Software Architecture Description, Software Interface Design Description, Database Design Description, Software Design Description, Software Configuration Index Record, User's Manual, Operator's Manual, Unit Test Report, and Application Release Checklist.  After the Interim Progress Review, formal testing begins.

During Design, Test Plans are produced during the Test Planning activity.  Then during Development, the Deployment Planning activity is performed, which produces the Installation Plans, Transition Plans, Training Plans, and finalizes the Infrastructure Services Request.  In the Validate/Accept subphase, the Developmental and Operational Test and Evaluation activities are performed and the Test Scripts, Test Discrepancy Reports, Test Reports, and Compliance Certifications are prepared.  During the Field subphase, the Deployment and Site Acceptance Test activity is performed and the Site Acceptance Test Reports are produced.  The Operation and Performance Oversight activity is performed during the Measure Effectiveness subphase and the Audit Reports, Performance Measurements, and Program Trouble Reports (PTR) are documented.

The On-Going Operational/Customer Assessment and the Configuration Management/Quality Assurance activities are ongoing through the maintenance cycle.

Audits and Baselines are shown across the bottom of the chart.  The Program and Functional Baselines (ORD, APB and TEMP and SRS and SARAD) are produced around the same time as the Design Review.  The Allocated Baseline (SRD, SAD, SIDD, DBDD, SDD) is produced around the same time and the Test Readiness Review.  The Functional Configuration Audit and the Physical Configuration Audit are performed during the Validate/Accept subphase before the Operational Test Readiness Review.  The Product Baseline (SDD, SAD, SIDD, SCIR, DBDD) is produced around the time of the Operational Test Readiness Review.  The Operational Baseline is produced per site around the time of the Post Implementation Review. Changes to appropriate documentation are required at each review to keep baselines current.