Image Description -  0723-1

A chart is captioned “figure 1. Synchronizing IV&V with the Software
Development Life Cycle”.  The chart shows the overall project life
cycle for software development on top. Major project design activities
such as PDR, CDR, and test reviews are identified along this timeline.
Below the main project life cycle, the independent verification and
validation (IV&V) life cycle is identified.  Major phases of the IV&V
activities are synchronized with respect to the main project life cycle.
Below the IV&V life cycle, various documentation activities that take
place during verification and validation are listed in detail for each
major phase of the IV&V life cycle.

The overall project life cycle for software development begins with the
Concept activity.  Near the end of the Concept activity the Software
Preliminary Requirements Review (PRR) is conducted.  At the end of the
Concept activity the Contract is awarded.  Then the Requirements activity
commences.  Near the end of the Requirements activity the Software
Requirements Review is conducted.  The Design activity then commences.
During the Design activity the Preliminary Design Review (PDR) and the
Critical Design Review (CDR) are conducted.  Completion of the CDR marks
the beginning of the Implementation activity.  The Software Test Review is
conducted at the end of this activity and marks the beginning of the
Verification activity.  This activity continues until completion of the
Functional Configuration Inspection.  The Validation activity is then
initiated.  Validation continues until completion of the Configuration
Inspection at which time the Systems Integration activity begins.  Systems
Integration continues until completion of the Acceptance Review at which
point the Operations and Maintenance activity is initiated.  The IV&V life
cycle closely parallels the software development life cycle.  Note that
since the IV&V activities depend upon review of the products and
information developed during software development the IV&V activities
slightly lag their counterparts in the software development cycle.  During
the Concept activity the IV&V performs Concept Analysis activities.  As
the software development moves into Requirements activities, IV&V
transitions into Requirements Analysis activities.  During these
activities the Software Concept Evaluation, IV&V Software Requirements,
and IV&V Plan are developed.  As the software development activities
transition into Design activities, the IV&V moves into Design Verification
activities.  IV&V Requirements Evaluation, IV&V System Test Plan, IV&V
Acceptance Test Plan, IV&V Software Design, IV&V Design Evaluation, IV&V
Program Unit Test Plan, IV&V Integration Test Plan, IV&V Test Design
Specifications, and Implementation Problem Reports are the products that
result from these activities.  As the software development continues on
into Implementation activities, the IV&V moves into Implementation
Verification activities.  Component Test Results and Interface Results
are the products of the IV&V effort at this point.  As the software
development moves into Validation activities the IV&V moves into
Independent Verification and Validation.  Integration Problem Reports
are the products of these IV&V activities.  As the software development
moves into Systems Integration activities, the IV&V performs System
Integration Analysis as well as Operations and Maintenance Analysis
that continues for the remainder of the program.  IV&V Problem Reports,
Installation * Checkout, Configuration Management Reports, Flight
Software Problem Reports, IV&V Integration Test Reports, IV&V Acceptance
Tests Reports, O&M Problem Reports and the IV&V Final Report are the
IV&V documents developed during these activities.