-
Notifications
You must be signed in to change notification settings - Fork 19
Requirements Mapping Matrix
Edwin Z. Crues edited this page Jun 8, 2020
·
1 revision
| Section | SWE# | Requirements Text | Compliance Status | Comment |
|---|---|---|---|---|
| 3.1 | Software Life Cycle Planning | |||
| 3.1.2 | 033 | The project manager shall assess options for software acquisition versus development. | Yes | No commercial software exists. |
| 3.1.3 | 013 | The project manager shall develop, maintain, and execute software plans that cover the entire software life cycle and, as a minimum, address the requirements of this directive with approved tailoring. | Yes | |
| 3.1.10 | 042 | The project manager shall require the software developer(s) to provide NASA with electronic access to the source code developed for the project in a modifiable format. | Yes | TrickLab GitLab Server |
| 3.1.11 | 139 | The project manager shall comply with the requirements in this NPR that are marked with an ”X” in Appendix C consistent with their software classification. | Yes | This matrix |
| 3.1.12 | 121 | Where approved, the project manager shall document and reflect the tailored requirement in the plans or procedures controlling the development, acquisition, and deployment of the affected software. | Yes | |
| 3.1.13 | 125 | Each project manager with software components shall maintain a requirements mapping matrix or multiple requirements mapping matrices against requirements in this NPR, including those delegated to other parties or accomplished by contract vehicles or Space Act Agreements. | Yes | This matrix |
| 3.5 | Software Classification Assessments | |||
| 3.5.1 | 020 | The project manager shall classify each system and subsystem containing software in accordance with the highest applicable software classification definitions for Classes A, B, C, D, E, and F software in Appendix D. | Yes | Currently Class E |
| 3.5.2 | 176 | The project manager shall maintain records of each software classification determination, each software Requirements Mapping Matrix, and the results of each software independent classification assessments for the life of the project. | Yes | |
| 3.6 | Software Assurance and Software Independent Verification & Validation | |||
| 3.6.1 | 022 | The project manager shall plan and implement software assurance per NASA-STD-8739.8. | Yes | |
| 3.7 | Safety-critical Software | |||
| 3.7.1 | 205 | The project manager, in conjunction with the SMA organization, shall determine if each software component is considered to be safety-critical per the criteria defined in NASA-STD-8739.8. | Yes | |
| 3.10.2 | 148 | The project manager shall evaluate software for potential reuse by other projects across NASA and contribute reuse candidates to the NASA Internal Sharing and Reuse Software systems. However, if the project manager is a contractor, then a civil servant must pre-approve all such software contributions; all software contributions should include, at a minimum, the following information: a. Software Title. b. Software Description. c. The Civil Servant Software Technical Point of Contact for the software product. d. The language or languages used to develop the software. e. Any third party code contained therein and the record of the requisite license or permission received from the third party permitting the Government’s use, if applicable. |
Yes | See Home page TrickHLA |
| 3.11 | Software Cybersecurity | |||
| 3.11.2 | 156 | The project manager shall perform a software cybersecurity assessment on the software components per the Agency security policies and the project requirements, including risks posed by the use of COTS, GOTS, MOTS, OSS, or reused software components. | Yes | |
| 3.11.6 | 155 | The project manager shall address identified cybersecurity vulnerabilities and weaknesses. | Yes | None currently identified. |