Page History
...
| Rev | SWE 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; | ||||||||
| C |
| ||||||||
| Difference between C and D | Reword to specify changes to be done with "approved tailoring". | ||||||||
| D |
|
...
