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


{alias:SWE-139} {tabsetup:1. The Requirement|2. Rationale|3. Guidance|4. Small Projects|5. Resources|6. Lessons Learned} {div3:id=tabs-1} h1. 1. Requirements
Wiki Markup
Tabsetup
1. The Requirement
1. The Requirement
12. Rationale
23. Guidance
34. Small Projects
45. Resources
56. Lessons Learned


Div
idtabs-1

1. Requirements

6.3.4

Centers

and

projects

shall

fully

comply

with

the

"shall"

statements

in

this

NPR

that

are

marked

with

an

"X"

in

Appendix

D

consistent

with

their

software

classification.

h2. {color:#003366}{*}

1.1

Notes{*}{color} NPR 7150.2 does not include any notes for this requirement. h2. 1.2 Applicability Across Classes This requirement applies to all classes and safety criticalities. {applicable:asc=1|ansc=1|bsc=1|bnsc=1|csc=1|cnsc=1|dsc=1|dnsc=1|esc=1|ensc=1|f=1|g=1|h=1} {div3} {div3:id=tabs-2} h1. 2. Rationale Earlier versions of NPR 7150.2 assumed that readers would accept requirements marked by an 'x' in the Appendix D as required activities. Experience with the earlier version of this NPR (I.e., NPR 7150.2) showed that this assumption was not universally confirmed. {panel} NPR 7150.2 was written to include the explicit statement in the requirement that full compliance with the requirement is necessary for those entries assigned an 'x' in Appendix D. {panel} The purpose of the Requirements Mapping Matrix in NPR 7150.2 is to essentially pre-tailor out requirements for less critical software systems (e.g., while Class A software has 132 invoked requirements, Class H has only 16). The purpose of the "x" label is to clarify the intent of NPR 7150.2 and to preclude any alternate interpretation of invoked requirements. This requirement affirms that designated Center and project personnel are to satisfy all invoked requirements of this NPR. The note further affirms that at least the safety aspects of an NPR requirement are to be satisfied if the requirement is simply labeled in NPR 7150.2, Appendix D as 'safety-only" (SO). This requirement makes a positive statement that the invoked requirement is to be fulfilled by the SWE's responsible party (indicated by the 4th column in the same Appendix D: Requirements Mapping Matrix). {note} Inherently, it affirms that fulfillment of requirements marked with an 'x' is the rule for specific NASA software classifications. {note} Deviations, waivers, and tailoring of the requirements of NPR 7150.2 are to follow the approved processes for requirements management (see [SWE-120] and [SWE-140]). {div3} {div3:id=tabs-3} h1. 3. Guidance There is currently no additional guidance specified for this requirement. {div3} {div3:id=tabs-4} h1. 4. Small Projects There is currently no guidance specific to small projects for this requirement. {div3} {div3:id=tabs-5} h1. 5. Resources No resources were identified for this requirement. {toolstable} {div3} {div3:id=tabs-6} h2. 6. Lessons Learned There are currently no Lessons Learned identified for this requirement. {div3} {tabclose}

Notes

If the requirement is marked with a "SO" in appendix D, the project is required to meet the requirement to the extent necessary to satisfy the safety critical aspects of the software.

1.2 Applicability Across Classes

This requirement applies to all classes and safety criticalities.


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



Div
idtabs-2

2. Rationale

Earlier versions of NPR 7150.2, NASA Software Engineering Requirements, assumed that readers would accept requirements marked by an "X" in Appendix D as required activities. Experience with the baseline version of this NPR, i.e., NPR 7150.2, showed that this assumption was not universally confirmed.


Panel

NPR 7150.2 was written to include the explicit statement in the requirement that full compliance with the requirement is necessary for those entries assigned an "X" in Appendix D.


The purpose of the Requirements Mapping Matrix in NPR 7150.2 is to essentially pre-tailor out requirements for less critical software systems, e.g., while Class A software has 111 invoked requirements for projects, Class H has only 16. The purpose of the "X" label is to clarify the intent of NPR 7150.2 and to preclude any alternate interpretation of invoked requirements.


Div
idtabs-3

3. Guidance

This requirement affirms that designated Center and project personnel are to satisfy all invoked requirements of this NPR. The note further affirms that at least the safety aspects of an NPR requirement are to be satisfied if the requirement is simply labeled in NPR 7150.2, Appendix D, as "safety only" (SO).

This requirement makes a positive statement that the invoked requirement is to be fulfilled by the SWE's responsible party (indicated by the 4th column in the same Appendix D, Requirements Mapping Matrix).


Note

Inherently, it affirms that fulfillment of requirements marked with an "X" is the rule for specific NASA software classifications.


Deviations, waivers, and tailoring of the requirements of NPR 7150.2 are to follow the approved processes for requirements management. (See SWE-120 and SWE-140.)


Div
idtabs-4

4. Small Projects

No additional guidance is available for small projects. The community of practice is encouraged to submit guidance candidates for this paragraph.


Div
idtabs-5

5. Resources


refstable

toolstable


Div
idtabs-6

6. Lessons Learned

There are currently no Lessons Learned identified for this requirement.