NASA Procedural Requirements (NPRs)
The table below details Steps 8 thru 10. Steps 1 thru 7 are on Page 1 and Steps 11 thru 14 are on Page 3. For ancillary file uplink or a configuration file update that does not change any of the source code, see Page 4.
|
# |
Task |
Phase |
Primary |
Notes |
|---|---|---|---|---|
|
8 |
PI to generate Software Requirements Specification (SRS). |
Requirements / Development of Software |
PI (4-8 weeks) |
This specification defines the functional requirements, performance, and the interface requirements for the software. (Ref: SWE-50 of the NPR 7150.2 Rev D) The SRS is needed for the GCAR. |
|
9 |
PI to generate Software Test Plans/Procedures (STP). |
Planning / Testing |
PI (4-8 weeks) |
The objective for the ROI Integration testing where these test plans and procedures will be used is for verifying that the software works in its intended environment. The requirements are verified but the data is not necessarily validated. The validation of the data would be the responsibility of the PI or their designated representative. These software test plans and procedures are usually a subset of the user acceptance test and performed by ROI personnel in the flight like simulated environment. (Ref: SWE-065 of the NPR 7150.2 Rev D) It is recommended to have test cases in independent order and screenshots, if applicable. The PI will need to include a test plan that assesses every possible scenario, but it is recommended to have an abbreviated test plan for use with SSC/Integrated Load testing (operational like testing, bare minimum to ensure software works correctly). (Ref: SWE-073 of the NPR 7150.2 Rev D) Test plans should include out of bounds/stress testing scenarios. (Ref: SWE-065 of the NPR 7150.2 Rev D |
|
10 |
PI to generate and perform User Acceptance Testing (UAT). |
Testing |
PI (4-8 weeks) |
The objective for the user acceptance testing is for validation that the software performs the intended function as needed by the PI in providing the necessary tasks from the perspective of the crew user in order to obtain the data necessary for the research project. The responsibility for this type of validation lies with the PI or their designed representative. (Ref: SWE-073 of the NPR 7150.2 Rev D) |
|
* - Primary Responsibility |
||||