Book A.

Book B.
7150 Requirements Guidance

Book C.

References, & Terms

(NASA Only)

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
{tabsetup:1. The Requirement|2. Rationale|3. Guidance|4. Small Projects|5. Resources|}


h1. 1. Requirements

6.3.6 The NASA Headquarters' Office of the Chief Engineer shall review and have concurrence approval when a center defines subsets of requirements denoted by "P (Center)" in the Requirements Mapping Matrix in Appendix D for the indicated classes of software.

h2. {color:#003366}{*}1.1 Notes{*}{color}

NPR 7150.2A does not include any notes for this requirement.

h2. 1.2 Implementation Notes from Appendix D

NPR 7150.2A does not include any notes for this requirement.

h2. 1.3 Applicability Across Classes

This requirement applies to all classes and safety criticalities.


h1. 2. Rationale

In recognition of differences among projects and Centers, NPR 7150.2A allows flexibility in the implementation of many of its requirements.  These SWEs are marked as P (Center) in the NPR 7150.2A Appendix D Requirements Mapping Matrix. "P (Center)" can be conventionally read as "partial, Center determined". See SWE\-{color:#0000ff}140{color} for guidance on two methods for developing approved subsets of these requirements.


This text will be in the box.


The OCE maintains the review and concurrence approval of acceptable partial requirement sets at the Centers for the following reasons:
* to monitor and control the use of NASA engineering policy
* to maintain periodic oversight of compliance with engineering requirements throughout the Agency and its contractor community
* to gain or give insight into appropriate partial implementations

The flexibility provided by locally designated subsets of Agency software requirements enables tailoring of these requirements based on results of acceptable risks vs. resources trades that are to be performed by Center engineering organizations or the Engineering TA.{div3}

h1. 3. Guidance

NPR 7150.2A provides basic rules for the implementation of the P (Center) concept, but delegates the development of the actual approach and process steps down to each Center.  Because of this delegation Centers are able to develop subsets of requirements using the P (Center) approach that result in local adaptations to suit Center and application-unique needs. This general approach assures that Centers develop the requirements for their systems and work products to match the goals and objectives of their programs and projects. Centers are free to choose an approach that works best for their projects and applications (see SWE-140 in this Handbook for guidance on two different approaches).

Headquarters OCE will review each center's P (Center) approach and documentation during periodic surveys conducted at the Center. These Center surveys are nominally scheduled for every other year. (See SWE\-{color:#0000ff}129{color} for guidance on the OCE survey process for both Headquarters and center personnel.) Concurrence by OCE on the Center's approach and documentation occurs in the same time frame as the survey.

!exclamation.gif! Non-concurrences by the OCE, which may occur, will be based on an OCE judgment that the Center's approach fails to meet the intent of a requirement subset from NPR 7150.2A, or if it insufficiently addresses safety and/or prudent risk considerations.  In the event of a non-concurrence on the P (Center) approach and/or the non-null set requirements subset, the Center software POC and the OCE Survey Lead are to develop an action plan to resolve the issues related to the non-concurrence by the OCE. An individual project should be aware, however, that HQ OCE may review their compliance matrix and specific implementation of P (Center) requirements outside of these periodic surveys.


Each Center's Engineering Technical Authority Implementation Plan or its Software Requirements Procedure typically detail the chosen approach for developing the software P (Center) requirements.

h1. 4. Small Projects

The flexibility inherent in the P (Center) requirement statement can help small projects address the need to tailor software requirements.  With respect to documentation, Centers can choose to significantly lighten the documentation requirements in Chapter 5 of NPR 7150.2 for small projects.

h1. 5. Resources

1.      [NASA Space Flight Program and Project Management Requirements|], [NPR 7120.5D (NM-7120.81)|], 2009.

2.      [NASA Engineering and Program/Project Management Policy|], NPD 7120.4, 2010

Please reference table {color:#0000ff}XYZ{color} in this handbook for a list of tools in use at NASA that may be relevant to this requirement.  Note that this table should not be considered all-inclusive, nor is it an endorsement of any particular tool.  Check with your Center to see what tools are available to facilitate compliance with this requirement