ECSS System Engineering — Environments and Design-and-Test Factors (space-systems/ecss/e10-env-design-factors)
Use when the task is to define, for a product, the system environments
it is exposed to and the design-and-test factors applicable to its
design and verification, per ECSS-E-ST-10C clause 5.3.2 -- mapping the
product's mission-phase exposure to applicable environment types,
deriving a design-and-test factor per environment from its engineering
domain and the product's verification approach, and checking that
every applicable environment has a captured limit level.
Domain quick reference
- Clause 5.3.2 calls for every product to have its applicable natural
and induced environments defined across the mission phases it
passes through (for example ground handling, launch, transfer
orbit, on-station operations), and for the design-and-test factor
used to convert a captured limit level into a test level to be
derived per environment from its engineering domain and the
product's chosen verification approach.
- An environment type belongs to exactly one engineering domain
(mechanical, thermal, radiation, electromagnetic); the domain, not
the mission phase, is what selects the design-and-test factor.
- A verification approach is either test-based (qualification test,
protoflight test, acceptance test), which uses a numeric
design-and-test factor to convert the limit level into the level
actually applied during test, or documentation-based (analysis,
similarity), which instead requires a recorded margin-of-safety
justification and has no numeric test level.
- A limit level is the environment level the product owner has
captured for one environment type from the applicable requirement
set; an applicable environment with no captured limit level is a
finding, independent of whether the eventual verification approach
is test-based or documentation-based.
Workflow
- Collect the product's declared mission phases and determine the
union of environment types applicable across them; reject an
unrecognized mission phase before it enters the assessment.
- For each applicable environment type, look up its engineering
domain; reject an unrecognized environment type.
- Determine whether the product's verification approach is
test-based or documentation-based. A documentation-based approach
has no numeric design-and-test factor -- route it to a recorded
margin-of-safety justification instead of a computed test level.
- For a test-based approach, look up the design-and-test factor for
each applicable environment's domain and compute its test level as
the captured limit level times that factor.
- Flag every applicable environment with no captured limit level,
regardless of verification approach.
- Aggregate the missing-limit-level findings and the computed test
levels per product; the product's environment definition is not
complete until the missing-limit-level list is empty.
Pitfalls
- Selecting the design-and-test factor by mission phase instead of by
engineering domain -- two environment types active in the same
phase (for example random vibration and electromagnetic
susceptibility during launch) can belong to different domains with
different factors, and collapsing them onto one phase-level factor
misapplies margin in both directions.
- Requesting a numeric design-and-test factor for a documentation-based
verification approach (analysis, similarity) -- these approaches
carry no test level by definition; substituting a factor anyway
fabricates a test level that was never physically applied.
- Treating an unset limit level as "no requirement" rather than a
finding -- an applicable environment with no captured limit level
means the requirement was never captured, which itself blocks the
environment definition from being complete, not a silent pass.
- Reusing a design-and-test factor from one verification approach
(for example qualification test) when the product has since moved
to another approach (for example protoflight test) -- the factor is
keyed to the approach actually being used, not to whichever value
was computed first.
Behavior contract (gate 3)
The mission-phase-to-environment lookup, environment-to-domain lookup,
verification-approach classification, design-and-test factor lookup,
test-level computation, and per-product review logic is exercised by
the gate 3 contract test: scripts/test_e10_env_design_factors.py
against scripts/e10_env_design_factors_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_e10_env_design_factors.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e10-env-design-factors3description: "Use when you define the natural and induced environments a4 product is exposed to across its mission phases under ECSS-E-ST-10C5 clause 5.3.2: determine the set of applicable environment types from the6 product's declared mission phases, identify the engineering domain each7 environment type belongs to, derive the design-and-test factor for that8 domain from the product's verification approach (qualification test,9 protoflight test, acceptance test, analysis, or similarity), compute the10 resulting test level from a captured limit level, and flag any applicable11 environment for which no limit level has been captured. Trigger: ecss,12 e-st-10c, environment definition, design and test factors, mission phase13 environment, qualification test, protoflight test, acceptance test,14 verification approach, limit level."15license: Apache-2.016compliance: STANDARDS-REF17standards:18 - id: ecss19 reference-only: true20gated: false21domain: space-systems22pack: space-systems23compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"24metadata:25 source: https://skillmd.com/skills/ashfordeou/e10-env-design-factors26 domain: space-systems27 subdomain: ecss28 tags: [ecss, e-st-10-system-scope, environment-definition, design-and-test-factors, mission-phase, verification-approach, test-level]29 version: 0.1.030 author: Aero Agent Skills31---3233# ECSS System Engineering — Environments and Design-and-Test Factors (space-systems/ecss/e10-env-design-factors)3435Use when the task is to define, for a product, the system environments36it is exposed to and the design-and-test factors applicable to its37design and verification, per ECSS-E-ST-10C clause 5.3.2 -- mapping the38product's mission-phase exposure to applicable environment types,39deriving a design-and-test factor per environment from its engineering40domain and the product's verification approach, and checking that41every applicable environment has a captured limit level.4243## Domain quick reference4445- Clause 5.3.2 calls for every product to have its applicable natural46 and induced environments defined across the mission phases it47 passes through (for example ground handling, launch, transfer48 orbit, on-station operations), and for the design-and-test factor49 used to convert a captured limit level into a test level to be50 derived per environment from its engineering domain and the51 product's chosen verification approach.52- An environment type belongs to exactly one engineering domain53 (mechanical, thermal, radiation, electromagnetic); the domain, not54 the mission phase, is what selects the design-and-test factor.55- A verification approach is either test-based (qualification test,56 protoflight test, acceptance test), which uses a numeric57 design-and-test factor to convert the limit level into the level58 actually applied during test, or documentation-based (analysis,59 similarity), which instead requires a recorded margin-of-safety60 justification and has no numeric test level.61- A limit level is the environment level the product owner has62 captured for one environment type from the applicable requirement63 set; an applicable environment with no captured limit level is a64 finding, independent of whether the eventual verification approach65 is test-based or documentation-based.6667## Workflow68691. Collect the product's declared mission phases and determine the70 union of environment types applicable across them; reject an71 unrecognized mission phase before it enters the assessment.722. For each applicable environment type, look up its engineering73 domain; reject an unrecognized environment type.743. Determine whether the product's verification approach is75 test-based or documentation-based. A documentation-based approach76 has no numeric design-and-test factor -- route it to a recorded77 margin-of-safety justification instead of a computed test level.784. For a test-based approach, look up the design-and-test factor for79 each applicable environment's domain and compute its test level as80 the captured limit level times that factor.815. Flag every applicable environment with no captured limit level,82 regardless of verification approach.836. Aggregate the missing-limit-level findings and the computed test84 levels per product; the product's environment definition is not85 complete until the missing-limit-level list is empty.8687## Pitfalls8889- Selecting the design-and-test factor by mission phase instead of by90 engineering domain -- two environment types active in the same91 phase (for example random vibration and electromagnetic92 susceptibility during launch) can belong to different domains with93 different factors, and collapsing them onto one phase-level factor94 misapplies margin in both directions.95- Requesting a numeric design-and-test factor for a documentation-based96 verification approach (analysis, similarity) -- these approaches97 carry no test level by definition; substituting a factor anyway98 fabricates a test level that was never physically applied.99- Treating an unset limit level as "no requirement" rather than a100 finding -- an applicable environment with no captured limit level101 means the requirement was never captured, which itself blocks the102 environment definition from being complete, not a silent pass.103- Reusing a design-and-test factor from one verification approach104 (for example qualification test) when the product has since moved105 to another approach (for example protoflight test) -- the factor is106 keyed to the approach actually being used, not to whichever value107 was computed first.108109## Behavior contract (gate 3)110111The mission-phase-to-environment lookup, environment-to-domain lookup,112verification-approach classification, design-and-test factor lookup,113test-level computation, and per-product review logic is exercised by114the gate 3 contract test: scripts/test_e10_env_design_factors.py115against scripts/e10_env_design_factors_logic.py (stdlib unittest,116offline). Run:117python3 scripts/test_e10_env_design_factors.py118119## Compliance120121- ECSS standards are freely downloadable (ESA); cite the source and122 paraphrase per standards-map.yaml.123- compliance: STANDARDS-REF, gated: false.