bannerc

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

Compare with Current View Page History

Version 1 Next »

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

Change of intent

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

Reworded requirement.
- Added the word development for clarity
- Removed safety criticality of the software as a factor
- changed approved tailoring to approved 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