bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

idtabs-1

1. Requirements

6.3.7 The Center-level Engineering Technical Authority shall keep records of projects' compliance matrices, waivers, and deviations against this NPR.

1.1 Notes

NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this requirement.

1.2 Applicability Across Classes

...

f1
g1
h1
ansc1
asc1
bnsc1
csc1
bsc1
esc1
cnsc1
dnsc1
dsc1
ensc1

...

idtabs-2

2. Rationale

The Center Engineering Technical Authority (TA) is required to maintain records for each project's compliance with NPR 7150.2 and records for requested and approved deviations and waivers for each project. This activity supports the Center-level TA's responsibility to monitor and control the use of procedural requirements. It provides appropriate reference material to support continuity in the event of a change in the delegated Center-level software TA. It also provides the software TA with sufficient current and historical knowledge to analyze compliance data and develop a consistent approach for interpreting the requirements of NPR 7150.2 across a number of Center projects.

Panel

Records maintained by the Engineering TA can also be used during Office of the Chief Engineer (OCE) appraisal activity (see SWE-129 ) for evaluating TA performance. 

...

idtabs-3

3. Guidance

The requirement for the Engineering TA to keep records of compliance, deviations, and waivers supports project management, appraisal activities by the Office of the Chief Engineer (OCE), and provides a quantitative basis for evaluating the TA process. Enough detail regarding these records is kept to provide sufficient information for use and reference during the life cycle of the project, as well as for comparisons and lessons learned across projects. The minimum set of documentation includes the project's software compliance matrix, waiver/deviation request package, and the final disposition (approval/disapproval). Records are to be kept in a managed repository.

The waiver/deviation request contains:

  • Project identification.
  • Scope and duration of the requested waiver/deviation.
  • Justification.
  • Risk characterization.
  • Identification of requirement(s) subject to waiver/deviation.
  • Criticality.
  • Mitigating factors.

...

The Center configuration management process is employed for the management of these records by the TA.

...

Panel

The Engineering TA considers that decisions on compliance, deviations, and waivers are likely to be among the more important decisions the TA can make on these types of requests by a Center or project. This type of information will be reviewed extensively in the event of a mishap or accident. The decisions are likely to receive greater review and evaluation by management and members of the public. See the lessons learned below for additional considerations.

...

Div
idtabs-4

4. Small Projects

No additional guidance is available for small projects.

...

idtabs-5

5. Resources

...

toolstable

...

idtabs-6

6. Lessons Learned

The NASA Lessons Learned database contains the following lessons learned related to TA records:

...