bannerc

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tabsetup
1. The Requirement
1. The Requirement
12. Rationale
23. Guidance
34. Small Projects
45. Resources
56. Lessons Learned
Div
idtabs-1

1. Requirements

4.6.4 The project manager shall complete, prior to delivery, verification that all software requirements identified for this delivery have been met, that all approved changes have been implemented and that all defects designated for resolution prior to delivery have been resolved.

1.1 Notes

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

1.2 Applicability Across Classes

 Text

Applicable b
a1
b1
csc1
c1
d0
dsc0
e0
f1
g0
h0

Div
idtabs-2

2. Rationale

TextSoftware requirements volatility metrics are the total number of requirements compared to requirement changes over time. It may include additions, changes, and reduction of requirements. Requirements volatility can affect the estimations of cost, time, effort, and the successes of the product. Requirements volatility during software project development is known to be the most critical risk, so managing this to success in software project.

Div
idtabs-3

3. Guidance

Text



Div
idtabs-4

4. Small Projects

No additional guidance is available for small projects.

Div
idtabs-5

5. Resources

5.1 References

refstable
 

5.2 Tools

Include Page
Tools Table Statement
Tools Table Statement
 

Div
idtabs-6

6. Lessons Learned

There are currently no Lessons Learned identified for this requirement.