Invalid license: Your evaluation license of Refined expired.
bannerd

A. Introduction

B. Institutional Requirements

C. Project Software Requirements

D. Topics

E. Tools, References, and Terms

F. SPAN
(NASA Only)


Renew your license to continue

Your evaluation license of Visibility for Confluence expired. Please use the Buy button to purchase a new license.

Renew your license to continue

Your evaluation license has expired. Contact your administrator to renew your Scaffolding Forms & Templates license.

This page contains macros or features from a plugin which requires a valid license.

You will need to contact your administrator.

7.09 - NEW HTML Entrance and Exit Criteria - Sticky Table

Entrance and Exit Criteria

Background

This guidance provides the maximum set of life cycle review entrance and exit criteria for software projects and should be tailored for the project class.This guidance is a summarized collection of material from the following core documents: NPR 7123.1, Appendix G 041; version D of NPR 7120.5 (since superseded by version F) 082; and Center Procedures.

This guidance includes three types of information for each review:

  1.  Entrance criteria - Activities and products that are to be completed before the review can begin.
  2.  Items Reviewed - Items to be reviewed during review and used to confirm exit criteria; this information is typically available a couple of weeks prior to the review.
  3.  Exit / Success Criteria – Decisions and actions to be completed before the review is considered complete.

This guidance is focused on the responsibilities of the software engineering community throughout the project life cycle reviews. Therefore, the guidance includes reviews and products which are the primary responsibility of the software engineering community as well as software engineering community contributions to system activities and products, such as the Project Plan.

Note that different mission types (e.g., robotic vs. human) can have different life cycles and, therefore, different sets of life cycle reviews that apply.

This material considers a software project to be a system of systems as well as a single subsystem within the larger project. "System of systems" refers to a software project that includes software subsystems that perform functions allocated to them. Just as a project allocates requirements to hardware, software, external components, etc., software projects allocate software requirements to software subsystems.

This material has been reviewed by the Software Working Group and the Office of the Chief Engineer.

Source of Content

Including the resources in the list below, information was pulled and consolidated based on repetition between Center Process Asset Libraries (PALs) and documents (Ames Research Center (ARC), Jet Propulsion Laboratory (JPL), Goddard Space Flight Center (GSFC), Marshall Space Flight Center (MSFC), Stennis Space Center (SSC)).

See also 7.08 - Maturity of Life Cycle Products at Milestone Reviews. 

1.1 References

Click here to view master references table.

Renew your license to continue

Your evaluation license has expired. Contact your administrator to renew your Reporting for Confluence license.

Renew your license to continue

Your evaluation license of Visibility for Confluence expired. Please use the Buy button to purchase a new license.

1.2 Additional Guidance

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

Related Links

1.3 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

Renew your license to continue

Your evaluation license of Visibility for Confluence expired. Please use the Buy button to purchase a new license.

Mission Concept Review (MCR)

The MCR affirms the mission need and examines the proposed mission's objectives and the concept for meeting those objectives. Key technologies are identified and assessed. It is an internal review that usually occurs in the cognizant system development organization. ROM (Rough Order of Magnitude) budget and schedules are presented. (NPR 7120.5 082)

Trying to get sticky headings using advanced table plus

Error rendering macro 'table-plus'

Notify your Confluence administrator that "Advanced Tables for Confluence" requires a valid license. Reason: EXPIRED




Additional Supporting Material

  • The need for the mission is clearly identified.
  • Concept of operations available.
  • Preliminary risk assessment available, including technologies and associated risk management/mitigation strategies and options.
  • A Mission Concept Review (MCR) agenda, success criteria, and charge to the board have been agreed to by the technical team, project manager, and review chair.
  • Preliminary technical Plans and conceptual life cycle available.
  • A conceptual life cycle is available.
  • A top-level set of requirements are identified to meet the mission objectives.
  • The mission is feasible.
    • A solution has been identified that is technically feasible.
    • A rough cost estimate is within an acceptable cost range.
  • Draft cost and schedule estimates are available.
    • As developed by software (SW) developers and SW assurance personnel.
  • A technical search was done to identify existing assets/products that could satisfy the mission or parts of the mission
  • Software inputs/contributions provided for:
    • Preliminary Project Plan.
    • Preliminary Systems Engineering Management Plan (SEMP).
    • Development and analysis of alternative concepts (showing at least one feasible).

Software Assurance

  • Software assurance point of contact for the project has been identified
  • Software assurance personnel have reviewed the materials available for the review:
    • The top-level requirements
    • Mission concept of operations
    • Preliminary technical plans and the conceptual life cycle
    • Preliminary risk assessment
  • Software assurance personnel confirm that the software portions of the MCR Entrance Criteria are met prior to the review
  • Mission goals and objectives.
  • Analysis of alternative concepts.
  • Preliminary development approaches and acquisition plans.
  • Concept of operations.
  • Risk assessments.
  • Technical plans and conceptual life cycle to achieve the next phase.
  • Preliminary requirements.
  • Draft cost and schedule estimates.
  • Conceptual system design.
  • Software Process Root cause analysis results.
  • SA analysis showing uncovered software code percentage.

Software Assurance:

  • Attends review to gain an understanding of mission
  • Record and submit RIDS (Review Item Discrepancy)/RFAs on risks or issues identified
  • Review panel agrees that:
    • Technical planning is sufficient to proceed to the next phase.
    • Risk and mitigation strategies have been identified and are acceptable based on technical risk assessments.
    • Cost and schedule estimates are credible.
    • Mission goals and objectives are clearly defined and stated, unambiguous, and internally consistent.
    • Conceptual system design meets mission requirements, and the various system elements are compatible.
    • Technology dependencies are understood, and alternative strategies for the achievement of requirements are understood.
  • As applicable, the agreement is reached that:
    • Preliminary mission requirements are traceable to science objectives.
    • The operations concept clearly supports the achievement of science objectives.

Software Assurance:

  • Has gained an understanding of mission goals, objectives, preliminary requirements and operations concept
  • Confirms that all issues and risks have been recorded
  • Agrees with resolution of RIDS (Review Item Discrepancy)/RFAs submitted

System Requirements Review (SRR)

The SRR examines the functional and performance requirements defined for the system and the preliminary Program or Project Plan and ensures that the requirements and the selected concept will satisfy the mission. (NPR 7120.5 082)

  • If not performing a Software Requirements Review (SwRR), include SwRR criteria as part of SRR.
  • For software-only projects, the SwRR serves as the SRR.

Error rendering macro 'table-plus'

Notify your Confluence administrator that "Advanced Tables for Confluence" requires a valid license. Reason: EXPIRED
  • No labels
Page Editor: Tim Crumbley
NASA Official: Tim Crumbley
Accessibility
NASA Software Engineering Handbook - A service of the NASA Office of the Chief Engineer
NASA Privacy Statement
______________________________________________________________________________