NASA Procedural Requirements (NPRs)
NASA Procedural Requirements are requirements documents for all NASA software. NPRs determine the software development process and requirements needed to obtain acceptance of software products according to NASA Standards.
NPR compliances need to be submitted for any software item - COTS, modified COTS, or developed software for NASA use. This includes contractor developed software, open source software, and firmware. The NPRs are applicable for both the flight and the Baseline Data Collection (BDC) versions of the software.
The table below details Steps 1 thru 7. Steps 8 thru 10 are on Page 2 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.
These documents may change as they go through ROI review.
Contact HRP Element if unable to access any of the links.
|
# |
Task |
Phase |
Primary |
Notes |
|---|---|---|---|---|
|
1 |
PI to obtain and review a copy of the NPR 7150.2D document and a template of the JF 1704 for familiarity. |
Pre–Funding / Proposal |
PI |
A majority of the PI software that is flown on the ISS will be classified as Class C (Not Safety Critical) software per the NPR 7150.2. Any supporting ground use (BDC) software will be Class D (Not Safety Critical) software. |
|
2 |
PI to complete a draft of the JF 1704 and sign as Project Engineer and Project Lead. |
Planning / After Funding |
PI (2 hours) |
JF 1704, Software Classification and Criticality Assessment, is a form from the NPR 7150.2 Rev D process that identifies the software classification and criticality of the software. This will determine the process and products required for the software. (Ref: SWE-020 and 176 of NPR 7150.2 Rev D) |
|
3 |
PI to submit JF 1704 to ROI SWINT for review. |
Planning / After Funding |
ROI SWINT / ROI Element (1 week) |
ROI will review/update as necessary. The completed JF 1704 will be an appendix item in the SDP and an item needed for GCAR. |
|
4 |
Submit the JF 1704 for signature approval. |
Planning / After Funding |
PI (2 weeks) |
Obtain SMA signatures, and submit to Division Chair Signature at HSEICB for concurrence. |
|
5 |
PI to generate a draft of the Software Development Plan (SDP)/Project Management Plan (PMP). |
Planning / After Funding |
PI (4-8 weeks) |
The SDP/PMP documents the planned development, management, responsibilities, and testing of the software, which includes the application software that is being developed and any server interface for the application database. This document will also include the preliminary schedule, configuration management of the software, and software assurance. (Ref: SWE-013 of the NPR 7150.2 Rev D) SDP is needed for the GCAR. |
|
6 |
PI to complete the NPR 7150.2 Compliance Matrix, using Excel Tool, dependent on the software classification. |
Planning / After Funding |
PI (2 days) |
This matrix will be an appendix item to the SDP. (Ref: SWE-125 of the NPR 7150.2 Rev D) Guidance: Cross reference the sections from the SDP that document compliance to the NPR requirement. |
|
7 |
PI to submit NPR 7150.2 Compliance Matrix and SDP to ROI SWINT for review. |
Planning / After Funding |
ROI SWINT / ROI Element (2 weeks) |
ROI SWINT, ROI Element, and Software Quality Assurance to review for concurrence. |
|
* - Primary Responsibility |
||||