ECSS Test Objectives (space-systems/ecss/e1003-objectives)
Use when the task is setting the objective of a test campaign under
ECSS-E-ST-10-03C: what a qualification, acceptance, or protoflight
campaign must demonstrate before its levels, durations, and conditions
are defined.
Domain quick reference
- ECSS-E-ST-10-03C clause 4.5 assigns each test campaign type a
distinct objective. Qualification testing demonstrates, on a
qualification (or protoflight) article, that the design meets its
requirements with margin beyond the levels and duration expected in
the mission environment -- it exists to uncover marginal design
weaknesses.
- Acceptance testing demonstrates the absence of workmanship and
manufacturing defects in the deliverable/flight article. It runs at
levels representative of the expected flight environment, with no
added margin, for the minimum duration needed to screen workmanship
-- adding margin or duration only risks damaging or consuming the
life of hardware that is meant to fly as-is.
- Protoflight testing is applied to a flight article that also serves
the qualification role, so it combines both objectives on one
article: it uses qualification-level severity to demonstrate margin,
but only the reduced, acceptance-like duration, so the flight
article's operational life margin is not consumed before flight.
- A test definition's level and duration are downstream of its
campaign's objective, not independent choices: the required level
and duration for a campaign are derived from what that campaign must
demonstrate, not set ad hoc per test.
Workflow
- Identify the test campaign type for the article under test:
qualification, acceptance, or protoflight.
- Derive the objective set assigned to that campaign: qualification
needs to demonstrate margin only; acceptance needs to screen
workmanship only; protoflight needs both, since it demonstrates
margin and screens workmanship on the same flight article.
- Derive the required test level from the objective set: margin
demonstration (qualification, protoflight) needs qualification
level; workmanship screening alone (acceptance) needs acceptance
level, representative of the expected flight environment.
- Derive the required duration class from the objective set and
whether the article is flight-life-at-risk: full duration only for
qualification (a dedicated, non-flight article); reduced duration
for acceptance and protoflight, since both put the deliverable or
flight article's remaining operational life at risk.
- Before test conditions and numeric levels/durations are defined
downstream (e1003-eq-qual / e1003-eq-acceptance /
e1003-eq-protoflight, e1003-test-conditions), validate any proposed
test definition's level and duration against the campaign's derived
objectives and flag mismatches rather than assuming they are
correct.
Pitfalls
- Running a qualification test at acceptance-level severity or
duration -- it will not demonstrate the design margin the
campaign exists to prove.
- Adding margin above flight levels to an acceptance test -- it does
not improve workmanship screening and instead risks damaging
deliverable or flight hardware that has no qualification margin.
- Running a protoflight test for the full qualification duration
instead of the reduced, acceptance-like duration -- it consumes the
flight article's operational life margin before it ever flies.
- Treating protoflight as "qualification testing on a flight article"
without also reducing duration, or as "acceptance testing with
extra margin" without recognizing it must still demonstrate margin
-- protoflight is the combination of both objectives, not either one
alone.
Behavior contract (gate 3)
The objective-assignment, required-level/duration-derivation, and
test-definition-validation logic is exercised by the gate 3 contract
test: scripts/test_e1003_objectives.py against
scripts/e1003_objectives_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1003_objectives.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1003-objectives3description: "Use when defining the test objectives for a qualification, acceptance or protoflight test campaign under ECSS-E-ST-10-03C clause 4.5: define the demonstrated-margin and workmanship-screen objectives assigned to each campaign type, derive the required test level (qualification level vs acceptance level) and duration class (full vs reduced) that those objectives imply, and validate a proposed test definition against the campaign's assigned objectives before test conditions, levels and durations are locked in downstream. Trigger: test objectives, qualification testing, acceptance testing, protoflight testing, demonstrated margin, workmanship screen, e-st-10-03, 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/e1003-objectives15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-03c, test-objectives, qualification, acceptance, protoflight]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Test Objectives (space-systems/ecss/e1003-objectives)2324Use when the task is setting the objective of a test campaign under25ECSS-E-ST-10-03C: what a qualification, acceptance, or protoflight26campaign must demonstrate before its levels, durations, and conditions27are defined.2829## Domain quick reference3031- ECSS-E-ST-10-03C clause 4.5 assigns each test campaign type a32 distinct objective. Qualification testing demonstrates, on a33 qualification (or protoflight) article, that the design meets its34 requirements with margin beyond the levels and duration expected in35 the mission environment -- it exists to uncover marginal design36 weaknesses.37- Acceptance testing demonstrates the absence of workmanship and38 manufacturing defects in the deliverable/flight article. It runs at39 levels representative of the expected flight environment, with no40 added margin, for the minimum duration needed to screen workmanship41 -- adding margin or duration only risks damaging or consuming the42 life of hardware that is meant to fly as-is.43- Protoflight testing is applied to a flight article that also serves44 the qualification role, so it combines both objectives on one45 article: it uses qualification-level severity to demonstrate margin,46 but only the reduced, acceptance-like duration, so the flight47 article's operational life margin is not consumed before flight.48- A test definition's level and duration are downstream of its49 campaign's objective, not independent choices: the required level50 and duration for a campaign are derived from what that campaign must51 demonstrate, not set ad hoc per test.5253## Workflow54551. Identify the test campaign type for the article under test:56 qualification, acceptance, or protoflight.572. Derive the objective set assigned to that campaign: qualification58 needs to demonstrate margin only; acceptance needs to screen59 workmanship only; protoflight needs both, since it demonstrates60 margin and screens workmanship on the same flight article.613. Derive the required test level from the objective set: margin62 demonstration (qualification, protoflight) needs qualification63 level; workmanship screening alone (acceptance) needs acceptance64 level, representative of the expected flight environment.654. Derive the required duration class from the objective set and66 whether the article is flight-life-at-risk: full duration only for67 qualification (a dedicated, non-flight article); reduced duration68 for acceptance and protoflight, since both put the deliverable or69 flight article's remaining operational life at risk.705. Before test conditions and numeric levels/durations are defined71 downstream (e1003-eq-qual / e1003-eq-acceptance /72 e1003-eq-protoflight, e1003-test-conditions), validate any proposed73 test definition's level and duration against the campaign's derived74 objectives and flag mismatches rather than assuming they are75 correct.7677## Pitfalls7879- Running a qualification test at acceptance-level severity or80 duration -- it will not demonstrate the design margin the81 campaign exists to prove.82- Adding margin above flight levels to an acceptance test -- it does83 not improve workmanship screening and instead risks damaging84 deliverable or flight hardware that has no qualification margin.85- Running a protoflight test for the full qualification duration86 instead of the reduced, acceptance-like duration -- it consumes the87 flight article's operational life margin before it ever flies.88- Treating protoflight as "qualification testing on a flight article"89 without also reducing duration, or as "acceptance testing with90 extra margin" without recognizing it must still demonstrate margin91 -- protoflight is the combination of both objectives, not either one92 alone.9394## Behavior contract (gate 3)9596The objective-assignment, required-level/duration-derivation, and97test-definition-validation logic is exercised by the gate 3 contract98test: scripts/test_e1003_objectives.py against99scripts/e1003_objectives_logic.py (stdlib unittest, offline). Run:100python3 scripts/test_e1003_objectives.py101102## Compliance103104- ECSS standards are freely downloadable (ESA); cite the source and105 paraphrase per standards-map.yaml.106- compliance: STANDARDS-REF, gated: false.