bannerc

Last used in rev NPR 7150.2C

RevSWE Statement
A

2.2.9 If a system or subsystem evolves to a higher software classification as defined in Appendix E, then the project shall update its plan to fulfill the added requirements per the Requirements Mapping Matrix in Appendix D.

Difference between A and B

Added requirements for downgrading software to a lower class and/or changing safety criticality. Added verbiage for having tailoring approved.

B

3.5.4 If a system or subsystem evolves to a higher or lower software classification as defined in Appendix D, or there is a change in the safety criticality of the software, then the project manager  shall update their plan to fulfill the applicable requirements per the Requirements Mapping and Compliance Matrix in Appendix C and any approved tailoring.

Difference between B and C

"Added the word development for clarity;
Removed safety criticality as a factor;
Changed ""tailoring"" to ""changes"";
Added ""initiate adjustments to applicable supplier contracts to fulfill the modified requirements""."

C

2.2.8 If a system or subsystem development evolves to meet a higher or lower software classification as defined in Appendix D then the project manager shall update their plan to fulfill the applicable requirements per the Requirements Mapping Matrix in Appendix C and any approved changes, and initiate adjustments to applicable supplier contracts to fulfill the modified requirements.



  • No labels