ECSS System Engineering — System Analysis Scope and Schedule (space-systems/ecss/e10-system-analysis)
Use when the task is scoping and scheduling the system analyses required
by ECSS-E-ST-10C clause 5.3.1 -- categorizing each analysis by type
(mission, functional, interface, environmental, operational), confirming
its objective and outputs are defined, and checking that it is scheduled
early enough to feed the project phase that depends on it.
Domain quick reference
- Clause 5.3.1 groups system analyses into five types, each with a
distinct object of study: mission (does the concept meet the mission
need across its operational scenarios), functional (do the allocated
functions cover the required behavior without gaps or conflicts),
interface (are the boundaries between elements/segments consistent and
complete), environmental (does the design tolerate the induced and
natural environments it will encounter), and operational (do the
operations concept and procedures actually achieve the mission in the
intended timeline). Every analysis instance is categorized into exactly
one of these five types before it is scoped further.
- A project phase (feasibility, preliminary design, detailed design,
verification) accumulates a required set of analysis types: feasibility
needs at minimum a mission analysis; preliminary design adds functional
and environmental; detailed design and verification add interface and
operational. An analysis type is not "done" once scoped at its earliest
phase -- it stays required through every later phase, refined as the
design matures.
- Scoping an analysis means recording, at minimum, its objective (why the
analysis is being run) and its defined outputs (what artifact or
decision it produces); an analysis with either left blank has not
actually been scoped, regardless of what type it is labeled.
- Scheduling an analysis means assigning it to the phase by which it must
be complete. Each analysis type has an earliest phase that first
requires it (e.g. mission analysis is required from feasibility
onward); an analysis scheduled to complete later than that earliest
phase cannot feed the decision it exists to support, and is a
scheduling violation even if its objective and outputs are otherwise
well defined.
Workflow
- For each candidate system analysis, categorize it as mission,
functional, interface, environmental, or operational. Reject an
unrecognized analysis type before it enters the review.
- Confirm the analysis records a non-empty objective and a non-empty
list of outputs; flag either omission independently -- one being
present does not excuse the other being missing.
- Confirm the analysis has a scheduled phase on record; flag its
absence. If a scheduled phase is recorded, it must be one of the
project's recognized phases -- reject an unrecognized phase value.
- Compare the analysis's scheduled phase against the earliest phase
that requires its type; flag the analysis if it is scheduled later
than that earliest phase.
- For the project's current phase, determine the full set of analysis
types required by that phase (cumulative from all earlier phases)
and compare it against the set of types actually scoped; flag any
required type with no corresponding analysis on record.
- Aggregate the per-analysis findings and the missing-analysis-type
findings; the project's system analysis planning is not compliant
until both are empty.
Pitfalls
- Treating a required analysis type as satisfied because an analysis
of that type exists somewhere in the plan, without checking that its
objective and outputs are actually filled in -- an analysis entry
with a type label and nothing else is not a scoped analysis.
- Scheduling an analysis for the same phase whose decision it is meant
to inform rather than before it -- an analysis type's earliest
required phase is the phase it must feed, so a completion date at
that same phase is already too late for this leaf's check, which
flags anything scheduled later than the earliest required phase and
relies on programme scheduling discipline to place it appropriately
ahead of that phase's start.
- Assuming a later project phase inherits compliance from an earlier one
-- a required analysis type must still be checked at every later
phase, since a design change can invalidate an analysis scoped
earlier even though the type was originally satisfied.
- Silently dropping an analysis with an unrecognized type or an
unrecognized scheduled phase instead of rejecting it -- a typo in
either field should surface as an error, not disappear from the
review.
Behavior contract (gate 3)
The analysis-type categorization, objective/output completeness,
scheduling, and phase-coverage logic is exercised by the gate 3 contract
test: scripts/test_e10_system_analysis.py against
scripts/e10_system_analysis_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_system_analysis.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-system-analysis3description: "Use when scoping and scheduling ECSS-E-ST-10C system analyses for a space project: classify a required system analysis as mission, functional, interface, environmental, or operational, determine which analysis types a given project phase requires, verify each analysis definition carries a non-empty objective and defined outputs, and check whether an analysis is scheduled early enough to feed the phase that first requires it. Trigger: ecss, e-st-10-system-scope, system-analysis, mission-analysis, functional-analysis, interface-analysis, environmental-analysis, operational-analysis, analysis-scheduling."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/e10-system-analysis15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, system-analysis, mission-analysis, functional-analysis, interface-analysis, environmental-analysis, operational-analysis]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — System Analysis Scope and Schedule (space-systems/ecss/e10-system-analysis)2324Use when the task is scoping and scheduling the system analyses required25by ECSS-E-ST-10C clause 5.3.1 -- categorizing each analysis by type26(mission, functional, interface, environmental, operational), confirming27its objective and outputs are defined, and checking that it is scheduled28early enough to feed the project phase that depends on it.2930## Domain quick reference3132- Clause 5.3.1 groups system analyses into five types, each with a33 distinct object of study: mission (does the concept meet the mission34 need across its operational scenarios), functional (do the allocated35 functions cover the required behavior without gaps or conflicts),36 interface (are the boundaries between elements/segments consistent and37 complete), environmental (does the design tolerate the induced and38 natural environments it will encounter), and operational (do the39 operations concept and procedures actually achieve the mission in the40 intended timeline). Every analysis instance is categorized into exactly41 one of these five types before it is scoped further.42- A project phase (feasibility, preliminary design, detailed design,43 verification) accumulates a required set of analysis types: feasibility44 needs at minimum a mission analysis; preliminary design adds functional45 and environmental; detailed design and verification add interface and46 operational. An analysis type is not "done" once scoped at its earliest47 phase -- it stays required through every later phase, refined as the48 design matures.49- Scoping an analysis means recording, at minimum, its objective (why the50 analysis is being run) and its defined outputs (what artifact or51 decision it produces); an analysis with either left blank has not52 actually been scoped, regardless of what type it is labeled.53- Scheduling an analysis means assigning it to the phase by which it must54 be complete. Each analysis type has an earliest phase that first55 requires it (e.g. mission analysis is required from feasibility56 onward); an analysis scheduled to complete later than that earliest57 phase cannot feed the decision it exists to support, and is a58 scheduling violation even if its objective and outputs are otherwise59 well defined.6061## Workflow62631. For each candidate system analysis, categorize it as mission,64 functional, interface, environmental, or operational. Reject an65 unrecognized analysis type before it enters the review.662. Confirm the analysis records a non-empty objective and a non-empty67 list of outputs; flag either omission independently -- one being68 present does not excuse the other being missing.693. Confirm the analysis has a scheduled phase on record; flag its70 absence. If a scheduled phase is recorded, it must be one of the71 project's recognized phases -- reject an unrecognized phase value.724. Compare the analysis's scheduled phase against the earliest phase73 that requires its type; flag the analysis if it is scheduled later74 than that earliest phase.755. For the project's current phase, determine the full set of analysis76 types required by that phase (cumulative from all earlier phases)77 and compare it against the set of types actually scoped; flag any78 required type with no corresponding analysis on record.796. Aggregate the per-analysis findings and the missing-analysis-type80 findings; the project's system analysis planning is not compliant81 until both are empty.8283## Pitfalls8485- Treating a required analysis type as satisfied because *an* analysis86 of that type exists somewhere in the plan, without checking that its87 objective and outputs are actually filled in -- an analysis entry88 with a type label and nothing else is not a scoped analysis.89- Scheduling an analysis for the same phase whose decision it is meant90 to inform rather than before it -- an analysis type's earliest91 required phase is the phase it must feed, so a completion date at92 that same phase is already too late for this leaf's check, which93 flags anything scheduled *later* than the earliest required phase and94 relies on programme scheduling discipline to place it appropriately95 ahead of that phase's start.96- Assuming a later project phase inherits compliance from an earlier one97 -- a required analysis type must still be checked at every later98 phase, since a design change can invalidate an analysis scoped99 earlier even though the type was originally satisfied.100- Silently dropping an analysis with an unrecognized type or an101 unrecognized scheduled phase instead of rejecting it -- a typo in102 either field should surface as an error, not disappear from the103 review.104105## Behavior contract (gate 3)106107The analysis-type categorization, objective/output completeness,108scheduling, and phase-coverage logic is exercised by the gate 3 contract109test: scripts/test_e10_system_analysis.py against110scripts/e10_system_analysis_logic.py (stdlib unittest, offline). Run:111python3 scripts/test_e10_system_analysis.py112113## Compliance114115- ECSS standards are freely downloadable (ESA); cite the source and116 paraphrase per standards-map.yaml.117- compliance: STANDARDS-REF, gated: false.