bannerd


7.08 - Maturity of Life Cycle Products at Milestone Reviews

1. Introduction and Chart

This chart summarizes current guidance approved by the NASA Office of the Chief Engineer (OCE) for software engineering life cycle products and their maturity level at the various software project life cycle reviews.   This chart serves as guidance only and NASA Center procedures should take precedence for projects at those Centers.

The chart was constructed using the software engineering products from NPR 7150.2 083, the project life cycle reviews from NPR 7123.1 041, previous work from the NASA Software Working Group to map products to life cycle reviews, and additional information gathered from these NPRs, NPR 7120.5 082, and individual NASA Center procedures.  Draft versions of the chart were reviewed by the NASA Software Working Group resulting in this chart which represents the current consensus guidance from this collection, collation, and review process.

The following maturity definitions from NPR 7120.5 are used in this table:

a. "Preliminary" is the documentation of information as it stabilizes but before it goes under configuration control. It is the initial development leading to a baseline.
Some products will remain in a preliminary state for multiple life cycle reviews. The initial preliminary version is likely to be updated at subsequent life cycle reviews but remains preliminary until baseline.
b. "Baseline" indicates putting the product under configuration control so that changes can be tracked, approved, and communicated to the team and any relevant stakeholders. The expectation on products labeled "baseline" is that they will be at least final drafts going into the designated life cycle review and baselined coming out of the life cycle review. Updates to baselined documents require the same formal approval process as the original baseline.
c. "Update" is applied to products that are expected to evolve as the formulation and implementation processes evolve. Only expected updates are indicated.
However, any document may be updated, as needed. Updates to baselined documents require the same formal approval process as the original baseline.

NPR 7150.2 does include life cycle products that are not included in the chart and there are life cycle reviews that are also not represented in the chart.  Insufficient information currently exists or consensus was not reached for those elements which will all be considered for future updates to this chart.

Links are provided where "Minimum Content" document topics are available. 

7150.2 Software Life Cycle Products

MCRSRRMDRSDRPDRCDRSIRTRRSARORR

Software Development Plan (SDP) / Software Management Plan (SMP) - 5.08 - SDP-SMP - Software Development - Management Plan

 

P

P

 B

 

U





Software Schedule

D

P

U

U

B

U





Software Cost Estimate

D

P

U

U

B

U





Software Configuration Management Plan (SCMP)
- 5.06 - SCMP - Software Configuration Management Plan


P

P

 

B

U





Software Test Plans
- 5.10 - STP - Software Test Plan





P

B

U

U



Software Test Procedures
- 5.14 - Test - Software Test Procedures






P

 

B



Software Test Reports
- 5.11 - STR - Software Test Report









F


Software Maintenance Plan
- 5.04 - Maint - Software Maintenance Plan

  

    

 D

 P

 P

 B

 U

Software Requirements Specification (SRS)
- 5.09 - SRS - Software Requirements Specification

 

P

 

 

B

U

 

U



Requirements on OTS s/w

 

P

 

 

B

U





Software Data Dictionary
- 5.07 - SDD - Software Data Dictionary




 

P

B





Software Design Description (Architectural Design)
- 5.13 - SwDD - Software Design Description




 

B

U

 

U



Software Design Description (Detailed Design)
- 5.13 - SwDD - Software Design Description




 

P

B

 

U



Interface Design Description
- 5.02 - IDD - Interface Design Description




 

P

B

 

U



Software User's Manual (SUM)
- 5.12 - SUM - Software User Manual










B

Records of Continuous Risk Management

P

U

U

U

U

U

 

 U

U


Measurement Analysis Results
- 5.05 - Metrics - Software Metrics Report




 

X

X





Operational Concepts (part of "Mission Operations Concept" or separate)

 

P

U

 U

B

U





Record of trade-off criteria & assessment (make/buy decision)




 

X

X





Acceptance Criteria and Conditions



 

 

P

B





Software Assurance and Software Safety (from NASA-STD-8739.8)

MCR

SRR

MDRSDRPDRCDRSIRTRRSARORR
Products









Software Assurance and Software Safety Plan(s)
- 8.51 - Software Assurance Plan

D
PBUU



Cost estimate for the project’s Software Assurance and Software Safety support.DPBUUU



Requirements mapping table for the software assurance and software safety standard requirements
DPBUU



IV&V Project Execution Plan (if required)
- 8.53 - IV&V Project Execution Plan

PPPBUUUU
IV&V Project risk assessment  (if required)
PPBUUUU

Software Assurance schedule
PPBUU



Software Assurance Product Acceptance Criteria and Conditions


PPX



Software Assurance Requirement Analysis
- 8.54 - Software Requirements Analysis



PXUUU

Software Assurance and Software Safety hazard analysis
- 8.58 - Software Safety and Hazard Analysis



PXUUU

Software Assurance safety analysis
- 8.58 - Software Safety and Hazard Analysis



PPXUUU
Software Assurance design analysis
- 8.55 - Software Design Analysis



PPXUUU
Software source code quality analysis
- 8.56 - Source Code Quality Analysis





PX


Software Assurance test analysis
- 8.57 - Testing Analysis





PPXU
Software static code assessments




PPX

Analysis showing software code coverage percentage for safety-critical code






X

Analysis showing software code complexity for safety-critical code






X

Ongoing activities









Software Process Root Cause Analysis results



UUUUU
Software risks, findings, or known issues 
UUUUUUUUU
Evaluation of software changes


UUUUUUU
Software Assurance status reports, including Software Assurance metric analysis
- 8.52 - Software Assurance Status Reports


PPSPPSPPSPPSPPSPPSPPSPPS
Participation in Software Peer reviews

PPSPPSPPSPPSPPSPPSPPSPPS
Software Assurance process audits
- 8.59 - Audit Reports


PPSPPSPPSPPSPPSPPSPPSPPS
Software test witnessing




PPSPPSPPSPPSPPS
Software Assurance participation in milestone product reviews
PPSPPSPPSPPSPPSPPSPPSPPSPPS

Legends

Maturity Types 

F = Final,  D = Draft,  P = Preliminary,  B = Baseline,  U = Updated/Updated as required,  X = assume complete (final),
PPS = Per Project Schedule or Software Assurance Schedule as appropriate


Review Types

MCR = Mission Concept Review,SRR = System Requirements ReviewMDR = Mission Definition Review
SDR = System Definition ReviewPDR = Preliminary Design ReviewCDR = Critical Design Review
SIR = System Integration ReviewTRR = Test Readiness ReviewSAR = System Acceptance Review
ORR = Operational Readiness Review

See also SWE-024 - Plan Tracking, 7.09 - Entrance and Exit Criteria, 8.09 - Software Safety Analysis


1.1 Additional Guidance

Links to Additional Guidance materials for this subject have been compiled in the Relevant Links table. Click here to see the Additional Guidance tab in the Resources tab.

2. References

2.1 References



2.2 Tools


Tools to aid in compliance with this SWE, if any, may be found in the Tools Library in the NASA Engineering Network (NEN). 

NASA users find this in the Tools Library in the Software Processes Across NASA (SPAN) site of the Software Engineering Community in NEN. 

The list is informational only and does not represent an “approved tool list”, nor does it represent an endorsement of any particular tool.  The purpose is to provide examples of tools being used across the Agency and to help projects and centers decide what tools to consider.

2.3 Additional Guidance

Additional guidance related to this requirement may be found in the following materials in this Handbook:

2.4 Center Process Asset Libraries

SPAN - Software Processes Across NASA
SPAN contains links to Center managed Process Asset Libraries. Consult these Process Asset Libraries (PALs) for Center-specific guidance including processes, forms, checklists, training, and templates related to Software Development. See SPAN in the Software Engineering Community of NEN. Available to NASA only. https://nen.nasa.gov/web/software/wiki  197

See the following link(s) in SPAN for process assets from contributing Centers (NASA Only). 

SPAN Links



3. Lessons Learned

3.1 NASA Lessons Learned

No Lessons Learned have currently been identified for this requirement.

3.2 Other Lessons Learned

No other Lessons Learned have currently been identified for this requirement.


Redirection Notice

This page will redirect to 7.08 - Maturity of Life Cycle Products at Milestone Reviews.

  • No labels