Arc Skills / Standards and development assurance
Review a NASA software requirements mapping matrix
This task reviews a NASA software Requirements Mapping Matrix against the project’s class, selected directive revision and evidence index. Arc Skills returns reconciled row findings, including claims supported only by plans and tailoring that lacks approval.
Use this skill
Use Arc Skills to review the project Requirements Mapping Matrix against the supplied project-controlled NASA directive and Appendix C revision. Keep the original SWE IDs and class applicability marks.
Inputs:
- Project software classification and controlled matrix revision.
- Project mapping rows, rationale and tailoring approvals.
- Linked plans, execution records and assurance evidence.
Return row findings, evidence/version, approval question and counts checked versus unassessable. Distinguish planned activity from recorded execution and NASA engineering requirements from NASA-STD-8739.8 assurance obligations.What you provide and what you get
| What you have | How it is used | What you get |
|---|---|---|
| Class and Appendix C version | Selects invoked rows and authority column | Applicability basis |
| Project mapping and approvals | Tests claimed tailoring and row coverage | Row findings |
| Plans and execution records | Tests whether “met” has relevant evidence | Evidence gaps and counts |
Three mapping rows, three different issues
Illustrative engineering example.
The local worksheet has three selected rows, but omits their source SWE identifiers, class applicability marks and authority columns. The labels below are worksheet identities. The supplied artifacts allow a claim-evidence screen; they do not allow a completed Appendix C applicability review.
| Local row and claim | Evidence supplied | Finding | Next decision |
|---|---|---|---|
| M-1: activity performed; “met” | Plan P-2 names the activity; no execution record | The plan does not show that the claimed activity occurred; the exact source obligation is absent | Recover the SWE row and class mark; obtain execution evidence if the row requires performance |
| M-2: tailored out | Rationale R-5; approval field blank; source authority absent | No recorded approval; required tailoring route cannot be determined from this worksheet | Recover the source row and its authority column before routing the rationale |
| M-3: classification record maintained | Current signed class record C-1 and link in index | A classification artifact exists; adequacy for the omitted SWE obligation is unresolved | Compare exact source wording, class applicability and retained-record scope |
All 3 supplied claims were screened. Two have visible claim/record gaps and one has a relevant artifact. Appendix C applicability and final closure are unassessable for all 3 because the source SWE IDs, class marks and authority columns are absent. These overlapping observations are different measures: they are not a pass/fail partition or coverage of the complete directive.
NPR 7150.2D Appendix C identifies class marks, requirement identifiers and authority columns. A tailored row needs the documented route identified there, while a “met” row must be compared with its actual requirement wording. NASA-STD-8739.8B is a distinct source for software assurance and safety requirements and should have separate trace, rather than being folded into an NPR engineering row.
Reconcile applicability, activity and authority
- Freeze the project class and exact Appendix C revision before counting invoked rows.
- Compare each local claim with the controlled row wording and class mark.
- Check whether a linked artifact records completed activity or only planned work.
- Reconcile checked, missing and unassessable rows; route tailoring to the listed authority.
Questions about this task
Does “not applicable” need a rationale?
Yes when an invoked row is being relieved. The matrix should show the project-specific basis and required tailoring decision under the selected directive.
Can an execution plan close an execution obligation?
Only if the controlled requirement asks for planning. Where performance is required, look for a completed record and its revision.
Sources and further reading
- NASA NPR 7150.2D Appendix C: Official Requirements Mapping Matrix, including class applicability and tailoring route.
- NASA-STD-8739.8: NASA software assurance and software safety standard; distinct from NPR 7150.2D engineering requirements.
NPR 7150.2D Appendix C was inspected on 3 October 2026. The example deliberately omits source-row identity to show an incomplete mapping worksheet.