ECSS Verification — General Method Selection (space-systems/ecss/e1002-method-general)
Use when the task is selecting, for a single requirement, the
verification method or combination of methods under
ECSS-E-ST-10-02C clause 5.2.2.1 -- test, analysis, review-of-design,
inspection -- applying the applicability rules for the requirement's
category, the precedence among methods, and the completeness rules
for the resulting verification plan.
Domain quick reference
- Clause 5.2.2.1 recognizes four verification methods: test (the
requirement is verified by observing the actual behavior of the
item, or a representative model of it, under real or simulated
conditions), analysis (verified by calculation, modeling, or
similarity to previously verified items), review-of-design (verified
by examining the design process and its records rather than the
hardware/software product itself), and inspection (verified by
visual or dimensional examination of a physical characteristic).
A requirement may be closed by one method or by a stated combination
of more than one.
- Not every method is eligible for every requirement category:
a purely procedural requirement (e.g. "a safety analysis shall be
performed and recorded") is closed by review-of-design, not by
testing the hardware; a workmanship requirement (e.g. "connectors
shall be free of visible damage") is closed by inspection, not by
analysis; a functional or performance requirement is normally closed
by test or analysis. Proposing a method outside the category's
eligible set is a plan error, not a stylistic choice.
A safety-critical requirement additionally always requires test in
its method set -- analysis alone, even if otherwise eligible, is
never sufficient to close it.
- The four methods carry an implicit precedence from most to least
rigorous: test, then analysis, then review-of-design, then
inspection. Selecting a lower-rigor method while a higher-rigor one
is eligible is allowed, but only when the plan states a rationale
substantial enough to justify the deviation (e.g. "test is
destructive to the flight unit" or "test access is not physically
possible in the assembled configuration") -- a rationale that is
missing or too brief to carry that justification is itself a
finding against the plan.
- A verification plan is a set of these per-requirement method
decisions; it is summarized by rolling up how many requirements each
method closes and which requirement ids fail their eligibility,
rationale, or safety-critical rule -- the plan is not complete until
that non-compliant list is empty.
Workflow
- Categorize the requirement (functional, performance, physical,
workmanship, design-process, or safety-critical). Reject an
unrecognized category before selecting a method.
- Look up the methods eligible for that category and filter the
requirement's proposed method(s) against it. A requirement with no
eligible method left after filtering is a plan error.
- Require a non-empty, stated rationale for every requirement's
method choice; a missing rationale is a plan error regardless of
which method was chosen.
- If the requirement is safety-critical, confirm test is among the
selected methods; a safety-critical requirement closed by analysis
alone is a plan error.
- Determine the primary (most rigorous) method actually selected.
If a more rigorous method was eligible but not selected, check the
rationale is substantial enough to justify the deviation; a brief
or generic rationale for a precedence deviation is a plan warning.
- Aggregate every requirement's outcome into a plan summary: counts
of requirements closed per method, and the list of requirement ids
that are not compliant. The plan is complete only when that list is
empty.
Pitfalls
- Accepting a method the requirement's category does not make
eligible (e.g. closing a workmanship requirement by analysis) just
because it was written in the verification matrix -- the category
determines the eligible set, not the plan author's preference.
- Treating a safety-critical requirement closed by analysis-only as
compliant because analysis is eligible for its category in general
-- the safety-critical rule additionally always requires test in the
method set, independent of general category eligibility.
- Reading a one-line or boilerplate rationale as sufficient to skip a
more rigorous eligible method -- a precedence deviation needs a
rationale specific enough to explain why the higher-rigor method was
not used, not just a rationale field that is merely non-empty.
- Rolling up a plan's method counts without checking each
requirement's individual compliance -- a requirement can have a
countable primary method and still be non-compliant (missing
rationale, ineligible method, or a violated safety-critical rule).
Behavior contract (gate 3)
The category-eligibility, safety-critical, precedence-deviation, and
plan-roll-up logic is exercised by the gate 3 contract test:
scripts/test_e1002_method_general.py against
scripts/e1002_method_general_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1002_method_general.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1002-method-general3description: "Use when you need to determine which verification method or combination of methods -- test, analysis, review-of-design, inspection -- satisfies a requirement under ECSS-E-ST-10-02C clause 5.2.2.1: categorize the requirement, filter to the methods eligible for that category, enforce that a safety-critical requirement always carries test, apply the test-over-analysis-over-review-of-design-over-inspection precedence rule with a stated rationale whenever a more rigorous eligible method is skipped, and roll up a verification plan's per-method counts and its non-compliant requirement ids. Trigger: ecss, e-st-10-02c, verification method selection, test analysis review-of-design inspection, method precedence, verification plan completeness, safety-critical verification, method applicability rules."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/e1002-method-general15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-02c, verification-method, test, analysis, review-of-design, inspection, verification-plan]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Verification — General Method Selection (space-systems/ecss/e1002-method-general)2324Use when the task is selecting, for a single requirement, the25verification method or combination of methods under26ECSS-E-ST-10-02C clause 5.2.2.1 -- test, analysis, review-of-design,27inspection -- applying the applicability rules for the requirement's28category, the precedence among methods, and the completeness rules29for the resulting verification plan.3031## Domain quick reference3233- Clause 5.2.2.1 recognizes four verification methods: test (the34 requirement is verified by observing the actual behavior of the35 item, or a representative model of it, under real or simulated36 conditions), analysis (verified by calculation, modeling, or37 similarity to previously verified items), review-of-design (verified38 by examining the design process and its records rather than the39 hardware/software product itself), and inspection (verified by40 visual or dimensional examination of a physical characteristic).41 A requirement may be closed by one method or by a stated combination42 of more than one.43- Not every method is eligible for every requirement category:44 a purely procedural requirement (e.g. "a safety analysis shall be45 performed and recorded") is closed by review-of-design, not by46 testing the hardware; a workmanship requirement (e.g. "connectors47 shall be free of visible damage") is closed by inspection, not by48 analysis; a functional or performance requirement is normally closed49 by test or analysis. Proposing a method outside the category's50 eligible set is a plan error, not a stylistic choice.51 A safety-critical requirement additionally always requires test in52 its method set -- analysis alone, even if otherwise eligible, is53 never sufficient to close it.54- The four methods carry an implicit precedence from most to least55 rigorous: test, then analysis, then review-of-design, then56 inspection. Selecting a lower-rigor method while a higher-rigor one57 is eligible is allowed, but only when the plan states a rationale58 substantial enough to justify the deviation (e.g. "test is59 destructive to the flight unit" or "test access is not physically60 possible in the assembled configuration") -- a rationale that is61 missing or too brief to carry that justification is itself a62 finding against the plan.63- A verification plan is a set of these per-requirement method64 decisions; it is summarized by rolling up how many requirements each65 method closes and which requirement ids fail their eligibility,66 rationale, or safety-critical rule -- the plan is not complete until67 that non-compliant list is empty.6869## Workflow70711. Categorize the requirement (functional, performance, physical,72 workmanship, design-process, or safety-critical). Reject an73 unrecognized category before selecting a method.742. Look up the methods eligible for that category and filter the75 requirement's proposed method(s) against it. A requirement with no76 eligible method left after filtering is a plan error.773. Require a non-empty, stated rationale for every requirement's78 method choice; a missing rationale is a plan error regardless of79 which method was chosen.804. If the requirement is safety-critical, confirm test is among the81 selected methods; a safety-critical requirement closed by analysis82 alone is a plan error.835. Determine the primary (most rigorous) method actually selected.84 If a more rigorous method was eligible but not selected, check the85 rationale is substantial enough to justify the deviation; a brief86 or generic rationale for a precedence deviation is a plan warning.876. Aggregate every requirement's outcome into a plan summary: counts88 of requirements closed per method, and the list of requirement ids89 that are not compliant. The plan is complete only when that list is90 empty.9192## Pitfalls9394- Accepting a method the requirement's category does not make95 eligible (e.g. closing a workmanship requirement by analysis) just96 because it was written in the verification matrix -- the category97 determines the eligible set, not the plan author's preference.98- Treating a safety-critical requirement closed by analysis-only as99 compliant because analysis is eligible for its category in general100 -- the safety-critical rule additionally always requires test in the101 method set, independent of general category eligibility.102- Reading a one-line or boilerplate rationale as sufficient to skip a103 more rigorous eligible method -- a precedence deviation needs a104 rationale specific enough to explain why the higher-rigor method was105 not used, not just a rationale field that is merely non-empty.106- Rolling up a plan's method counts without checking each107 requirement's individual compliance -- a requirement can have a108 countable primary method and still be non-compliant (missing109 rationale, ineligible method, or a violated safety-critical rule).110111## Behavior contract (gate 3)112113The category-eligibility, safety-critical, precedence-deviation, and114plan-roll-up logic is exercised by the gate 3 contract test:115scripts/test_e1002_method_general.py against116scripts/e1002_method_general_logic.py (stdlib unittest, offline). Run:117python3 scripts/test_e1002_method_general.py118119## Compliance120121- ECSS standards are freely downloadable (ESA); cite the source and122 paraphrase per standards-map.yaml.123- compliance: STANDARDS-REF, gated: false.