ECSS Qualification Stage & Heritage Tailoring (space-systems/ecss/e1002-qualification)
Use when the task is running the qualification stage of an
ECSS-E-ST-10-02C verification programme: closing design qualification
against requirements, tailored by product heritage, ahead of
acceptance and the qualification review (QR).
Domain quick reference
- ECSS-E-ST-10-02C clause 5.2.4.2 defines the qualification stage:
demonstrate, before acceptance, that the design (hardware, software,
and its production process) meets its requirements with adequate
margin, using the verification methods already assigned under clause
5.2.2 and a qualification or protoflight article.
- Table 5-1 tailors how much qualification evidence is needed by
product heritage: a new design needs full qualification against
every applicable requirement; an existing design reused unmodified
and within its previously-qualified envelope can close qualification
by similarity/heritage evidence instead of repeating tests; an
existing design that has been modified, or is applied outside its
previously-qualified envelope, needs delta qualification limited to
the requirements affected by the change or the envelope difference.
- A safety-critical requirement cannot be closed by heritage/similarity
alone once the design has changed or the envelope has moved -- it
needs delta (or full) qualification evidence specific to that
change, consistent with the safety-critical rule used for method
selection in the sibling e10-req-verif-methods leaf.
- The qualification stage cannot be declared complete, and cannot feed
the stage-closure check owned by the sibling e1002-stages leaf
(clause 5.2.4.1), until every product/requirement in scope is closed
with evidence matching its assigned scope.
Workflow
- For each product (or requirement) in the qualification scope,
capture its heritage inputs: is it a new design, has the design
been modified, is the intended application within the design's
previously-qualified envelope, and is it safety-critical.
- Classify the product into a Table 5-1 heritage category:
new design; heritage, unmodified and within envelope; or heritage,
modified or outside envelope.
- Derive the qualification scope from the category: new design ->
full qualification; unmodified-within-envelope heritage -> closed
by similarity; modified-or-outside-envelope heritage -> delta
qualification, escalated to full when the requirement is
safety-critical (heritage cannot waive it).
- Determine the evidence type required for the assigned scope (full:
qualification test or analysis result; similarity: heritage
dossier/similarity justification; delta: test or analysis on the
requirements affected by the change or envelope difference only).
- Record each product's qualification status: closed when evidence of
the matching type has been supplied, otherwise open.
- Before declaring the qualification stage complete and handing off
to acceptance / QR, confirm every product/requirement in scope is
closed; list any still open rather than assuming completion.
Pitfalls
- Closing a modified or envelope-exceeding design by heritage/
similarity alone instead of running delta qualification on the
affected requirements.
- Waiving qualification evidence for a safety-critical requirement
just because the parent product has heritage -- the escalation to
full/delta scope for safety-critical items is mandatory, not
discretionary.
- Treating a "delta" qualification as covering the whole product
rather than only the requirements affected by the specific change or
envelope difference.
- Declaring the qualification stage complete while some products or
requirements in scope are still open.
Behavior contract (gate 3)
The heritage-classification, scope-derivation, evidence-requirement,
and stage-completeness logic is exercised by the gate 3 contract test:
scripts/test_e1002_qualification.py against
scripts/e1002_qualification_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1002_qualification.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-qualification3description: "Use when running the qualification stage of an ECSS-E-ST-10-02C verification programme: closing design qualification against requirements before acceptance/QR, tailoring the qualification scope by product heritage category (Table 5-1: new design, unmodified heritage within envelope, modified or envelope-exceeding heritage), and confirming every product in scope is closed with matching evidence. Trigger: qualification stage, design qualification, heritage product category, Table 5-1, qualification by similarity, delta qualification, qualification review, QR, e-st-10-02, ecss, e-st-10c."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-qualification15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, qualification, heritage, verification-stage, delta-qualification]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Qualification Stage & Heritage Tailoring (space-systems/ecss/e1002-qualification)2324Use when the task is running the qualification stage of an25ECSS-E-ST-10-02C verification programme: closing design qualification26against requirements, tailored by product heritage, ahead of27acceptance and the qualification review (QR).2829## Domain quick reference3031- ECSS-E-ST-10-02C clause 5.2.4.2 defines the qualification stage:32 demonstrate, before acceptance, that the design (hardware, software,33 and its production process) meets its requirements with adequate34 margin, using the verification methods already assigned under clause35 5.2.2 and a qualification or protoflight article.36- Table 5-1 tailors how much qualification evidence is needed by37 product heritage: a new design needs full qualification against38 every applicable requirement; an existing design reused unmodified39 and within its previously-qualified envelope can close qualification40 by similarity/heritage evidence instead of repeating tests; an41 existing design that has been modified, or is applied outside its42 previously-qualified envelope, needs delta qualification limited to43 the requirements affected by the change or the envelope difference.44- A safety-critical requirement cannot be closed by heritage/similarity45 alone once the design has changed or the envelope has moved -- it46 needs delta (or full) qualification evidence specific to that47 change, consistent with the safety-critical rule used for method48 selection in the sibling e10-req-verif-methods leaf.49- The qualification stage cannot be declared complete, and cannot feed50 the stage-closure check owned by the sibling e1002-stages leaf51 (clause 5.2.4.1), until every product/requirement in scope is closed52 with evidence matching its assigned scope.5354## Workflow55561. For each product (or requirement) in the qualification scope,57 capture its heritage inputs: is it a new design, has the design58 been modified, is the intended application within the design's59 previously-qualified envelope, and is it safety-critical.602. Classify the product into a Table 5-1 heritage category:61 new design; heritage, unmodified and within envelope; or heritage,62 modified or outside envelope.633. Derive the qualification scope from the category: new design ->64 full qualification; unmodified-within-envelope heritage -> closed65 by similarity; modified-or-outside-envelope heritage -> delta66 qualification, escalated to full when the requirement is67 safety-critical (heritage cannot waive it).684. Determine the evidence type required for the assigned scope (full:69 qualification test or analysis result; similarity: heritage70 dossier/similarity justification; delta: test or analysis on the71 requirements affected by the change or envelope difference only).725. Record each product's qualification status: closed when evidence of73 the matching type has been supplied, otherwise open.746. Before declaring the qualification stage complete and handing off75 to acceptance / QR, confirm every product/requirement in scope is76 closed; list any still open rather than assuming completion.7778## Pitfalls7980- Closing a modified or envelope-exceeding design by heritage/81 similarity alone instead of running delta qualification on the82 affected requirements.83- Waiving qualification evidence for a safety-critical requirement84 just because the parent product has heritage -- the escalation to85 full/delta scope for safety-critical items is mandatory, not86 discretionary.87- Treating a "delta" qualification as covering the whole product88 rather than only the requirements affected by the specific change or89 envelope difference.90- Declaring the qualification stage complete while some products or91 requirements in scope are still open.9293## Behavior contract (gate 3)9495The heritage-classification, scope-derivation, evidence-requirement,96and stage-completeness logic is exercised by the gate 3 contract test:97scripts/test_e1002_qualification.py against98scripts/e1002_qualification_logic.py (stdlib unittest, offline). Run:99python3 scripts/test_e1002_qualification.py100101## Compliance102103- ECSS standards are freely downloadable (ESA); cite the source and104 paraphrase per standards-map.yaml.105- compliance: STANDARDS-REF, gated: false.