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

Compare with Current View Page History

« Previous Version 21 Next »

SWE-194 - Delivery Requirements Verification

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
















Key:    - Applicable | - Not Applicable
A & B = Always Safety Critical; C & D = Sometimes Safety Critical; E - F = Never Safety Critical.

2. Rationale

Requirements are the basis for building a product that meets the needs of the project. They define the behavior of the system and the constraints under which the problem is to be solved. It is important that the implemented product is verified against the requirements to show that it actually meets all of the requirements.

However, requirements change over time and the documentation of the requirements is not always up to date. Also, for Agile approaches, not all of the requirements are necessarily documented up front. It is critical that the Project Manager use an appropriate method or tool to keep track of the requirements necessary for each delivery of the software and that these are kept up to date with any changes or defect resolutions.

The verification planning, execution, and results should include all requirements for that delivery. A traceability matrix that shows all of the planned and modified requirements to the test procedures/results is critical for showing compliance to this NPR requirement. Also critical are the test reports that show that each requirement verification passed.

3. Guidance

This requirement applies to all NASA centers and Software Classes A, B, C, D, and F.

For non-Agile lifecycle, an analysis of the baseline set of requirements and all change requests would need to be performed against the verification plans, procedures, and results to show that every requirement has been verified successfully.

For an Agile lifecycle, for each planned release, an analysis of the set of requirements associated with that release and all change requests associated with those requirements would need to be performed against the verification plans, procedures, and results to show that every requirement has been verified successfully. Additionally, any defect resolutions that were designated for inclusion in the release need to be analyzed against the verification procedures and results to ensure that they were resolved and successfully verified.

Keeping track of requirements changes can be done by several methods as described in SWE-053.

Verification is done by several methods. For guidance on inspections, see section 5.3 in the NPR. For guidance on testing, see section 4.5 in the NPR, specifically SWE-065, 066, 068, 071, and 191.

For this effort, having a complete bi-directionality between requirements, design, and verification is significant and will make the analysis easier.

SWE-053Manage Requirements Changes
SWE-065Test Plan, Procedures, Reports
SWE-066Perform Testing
SWE-068Evaluate Test Results
SWE-071Update Test Plans and Procedures
SWE-191Software Regression Testing

4. Small Projects

No additional guidance is available for small projects.

5. Resources

5.1 References

No references have been currently identified for this SWE. If you wish to suggest a reference, please leave a comment below.

5.2 Tools

Unable to render {include} The included page could not be found.

6. Lessons Learned

There are currently no Lessons Learned identified for this requirement.

7. Software Assurance


  • No labels