NASA Procedural Requirements (NPRs)

The table below detail steps for an ancillary file uplink or a configuration file update that does not change any of the source code of the software. For a new version of a previously delivered software, then the previous steps (1-14), starting on Page 1, will need to be reviewed for any changes necessary due to the new version of the software. If the function or purpose of the software has changed, the JF 1704 will need to be reviewed for any change in the classification or criticality that was previously assigned.

Page 1 Page 2 Page 3

Page 4

#

Task

Phase

Primary
Resp*

Notes

1

PI to perform User Acceptance Testing (UAT).

Testing

PI

(2 weeks)

The objective for the user acceptance testing is for validation that the software performs the intended function with the updated ancillary file or configuration file as needed by the PI.

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

2

PI to generate any update to the Software Test Plans/Procedures (STP).

Planning / Testing

PI

(2 weeks)

Update the Test Plans/Procedures as necessary for the update for the ROI Integration testing used for verifying that the update works in its intended environment. These software test plans and procedures are performed by ROI personnel in the flight like simulated environment. (Ref: SWE-02 of the NPR 7150.2 Rev D

3

PI to update the Version Description Document (VDD).

Delivery / Acceptance

PI

(2 weeks)

Update this document as necessary for the purpose of the update. (Ref: SWE-063 of the NPR 7150.2 Rev D)

4

PI to submit the updated VDD to ROI SWINT for review.

Delivery / Acceptance

ROI SWINT / ROI Element

(4 weeks)

ROI will review/update as necessary with the details regarding the identification, and storage, and installation of the update. Afterwards, ROI SWINT will submit to ROI CB for review and approval. The completed VDD is an item needed for GCAR.

* - Primary Responsibility