bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Error formatting macro: alias: java.lang.NullPointerException
SWE-127 - P (Center) OCE Concurrence
Unknown macro: {div3}

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.

1.1 Notes

NPR 7150.2 does not include any notes for this requirement.

1.2 Applicability Across Classes

This requirement applies to all classes and safety criticalities.

Class

  A_SC 

A_NSC

  B_SC 

B_NSC

  C_SC 

C_NSC

  D_SC 

D_NSC

  E_SC 

E_NSC

     F      

     G      

     H      

Applicable?

   

   

   

   

   

   

   

   

   

   

   

   

   

Key:    A_SC = Class A Software, Safety Critical | A_NSC = Class A Software, Not Safety Critical | ... | - Applicable | - Not Applicable
X - Applicable with details, read above for more | P(C) - P(Center), follow center requirements or procedures

Unknown macro: {div3}

2. Rationale

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

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.

Unknown macro: {div3}

3. Guidance

NPR 7150.2 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-129] 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.

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.2, 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. However, the Headquarters OCE may review an individual project's 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.

Unknown macro: {div3}

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.

Unknown macro: {div3}

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

5.1 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.

Unknown macro: {div3}

6. Lessons Learned

There are currently no Lessons Learned identified for this requirement.

  • No labels