Arc Skills / Verification and validation

Review a verification matrix against ECSS-E-ST-10-02

Arc Skills checks matrix rows, linked artifacts, and project applicability against an inspected ECSS verification edition. If controlled clauses are absent, it returns a useful completeness review and leaves ECSS conformance undetermined.

Use this skill

Use Arc Skills to review the supplied verification matrix against the applicable ECSS-E-ST-10-02 basis.

Inputs:
- Matrix, requirement baseline, and verification plan revisions
- Linked Test, Run, analysis, and inspection evidence
- Project-controlled ECSS edition, tailoring, and relevant clause excerpts

Return row-level findings with evidence locator, action, and reconciled coverage counts.
Inspect linked artifacts before judging sparse cells. If clauses are unavailable, leave ECSS conformance unresolved

Set up the toolkit · Read the skill instructions

What you provide and what you get

Inputs and outputs
What you have	How it is used	What you get
Matrix and baseline	Fixes row denominator and requirement identity	Coverage audit
Linked evidence	May supply data omitted from sparse cells	Trace verdict
Controlled ECSS basis	Establishes applicable clause criteria	Source-grounded or unresolved conformance

A sparse Pass row with no linked run record

Illustrative engineering example.

VM-1 contains three requirement rows. Its R-4 line says Pass but lists no article or result locator; a linked T-9 record is named but unavailable. The controlled ECSS edition and tailoring are not supplied.

VM-1: R-4 | Test | subsystem | T-9 | Pass
VM-1: R-5 | Inspection | unit | I-5 | Planned
VM-1: R-6 | Analysis | system | A-6 | Planned
ECSS edition, tailoring, and clause excerpts: [not supplied].

A sparse Pass row with no linked run record — illustrative output
Matrix row	Engineering observation	Action / ECSS locator
R-4	Pass claim lacks accessible article and result evidence.	Inspect T-9 Run and configuration; ECSS clause [pending source].
R-5	Planned inspection is visible, not executed evidence.	Retain planned status; check criterion and procedure link.
R-6	Planned analysis is visible, not a completed result.	Locate analysis assumptions, report, and approval state.

All three baseline rows are present. One claims Pass without accessible evidence and two remain planned; zero rows can be called demonstrated from the material supplied.

The R-4 concern is about traceability and evidence sufficiency, not a claimed violation of an invented ECSS clause. Once the project edition, tailoring, and actual linked records are inspected, the reviewer can decide whether a specific ECSS obligation applies.

Inspect links before judging cells

Record requirement baseline, matrix revision, verification plan, and ECSS edition/tailoring.
Reconcile all rows and inspect linked Test, Run, analysis, or inspection artifacts.
Assess whether each row covers the full obligation and current article.
Cite an ECSS clause only after reading its controlled text and applicability.

Questions about this task

Is an empty matrix cell always a defect?

No. The fact may live in a controlled linked artifact; verify the link and content first.

Can this example claim ECSS compliance?

No. The applicable clauses and tailoring are absent, so only an engineering completeness observation is supported.

Sources and further reading

ECSS-E-ST-10-02C verification: Official standard identification and scope; project edition and tailoring govern applicability.
NASA Systems Engineering Handbook: Lifecycle and requirements guidance; the example decisions are illustrative.

The ECSS publisher page identifies the standard and scope; no controlled clause text or project tailoring is used in this example.