ECSS System Engineering — SE Management (space-systems/ecss/e10-se-mgmt)
Use when the task is managing the system engineering (SE) activities,
responsibilities and interfaces of the SE function as defined in the
System Engineering Plan (SEP), per ECSS-E-ST-10C clause 5.6.1 --
categorizing each SE activity, checking that its SEP responsibility
assignment and required interfaces to other project functions are on
record, and checking that its status is internally consistent.
Domain quick reference
- Clause 5.6.1 requires the SE function to manage its own activities,
responsibilities and interfaces as laid down in the SEP. This leaf
treats an SE activity as one of a fixed set of kinds: technical
management, requirements engineering, analysis, design definition,
verification, product-assurance interface, or risk management. Each
activity is categorized into exactly one kind before the rest of the
review runs.
- Every activity must have exactly one responsible role drawn from the
SEP's role list (SE manager, lead engineer, subsystem engineer,
product assurance engineer, project manager, customer
representative). An activity with no owner recorded is flagged as
unassigned; an owner outside the recognized role list is rejected
outright, since it signals the SEP role list itself was not consulted.
- Each activity kind carries a fixed set of external project functions
it must interface with under the SEP (e.g. verification must
interface with product assurance; technical management and risk
management must interface with project management; requirements
engineering must interface with the customer). A recorded interface
names its counterpart function; a required counterpart missing from
the activity's recorded interfaces is flagged.
- Each activity also carries a status: planned, in progress, complete,
or blocked. A blocked activity must record why (a blocking reason);
a completed activity must not depend on another activity that has
not itself reached complete -- an open prerequisite behind a
"complete" activity is a management-control gap, not a technical one.
Workflow
- Inventory every SE activity under the SEP and categorize each one
by kind. Reject an unrecognized activity kind before it enters the
review.
- For each activity, check the SEP responsibility assignment: flag a
missing owner; reject an owner that is not a recognized SEP role.
- For each activity, determine its required interface set from its
kind and check it against the activity's recorded interfaces; flag
each required counterpart that has no recorded interface. Reject an
interface naming an unrecognized counterpart function.
- For each activity, check status consistency: flag a blocked
activity with no recorded reason, and flag a complete activity that
depends on another activity not itself complete. Reject an
unrecognized status or a dependency id that does not resolve to a
known activity.
- Aggregate the responsibility, interface and status findings per
activity; the activity is not under SE management control until all
three lists are empty.
- Roll the per-activity reviews up to a program-level verdict; the
program is not compliant until every activity in it is compliant.
Pitfalls
- Treating an unassigned owner and an unrecognized owner the same way
-- a missing owner is a findable gap in the SEP responsibility
assignment, but a role outside the recognized SEP role list means
the assignment itself is malformed and must be rejected, not
silently logged as a finding.
- Skipping the required-interface check for an activity kind with no
recorded interfaces at all -- the check is driven by the activity's
kind, not by whether any interfaces happen to be present; an
activity that never records an interface it is required to have is
still a finding.
- Reading a "complete" status at face value without checking its
dependencies -- a completed activity that still depends on an
incomplete one is not actually under control, even though its own
status field says otherwise.
- Conflating a blocked activity that records a reason with one that
does not -- only the absence of a recorded reason is the finding;
a blocked activity with a documented reason is a normal, trackable
state, not a violation.
Behavior contract (gate 3)
The activity-kind categorization, responsibility-assignment,
interface-coverage, and status-consistency logic is exercised by the
gate 3 contract test: scripts/test_e10_se_mgmt.py against
scripts/e10_se_mgmt_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_se_mgmt.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-se-mgmt3description: "Use when manage the system engineering activities, responsibilities and interfaces of the SE function as defined in the System Engineering Plan (SEP) under ECSS-E-ST-10C clause 5.6.1: categorize each SE activity by kind, determine its assigned responsible role against the SEP responsibility assignment, verify each activity's required interfaces to other project functions (project management, product assurance, engineering disciplines, customer) are on record, and track activity status so a blocked activity carries a reason and a completed activity has no open prerequisite. Trigger: ecss, e-st-10-system-scope, se management, sep, responsibility assignment, interface control, system engineering plan, e-st-10c 5.6.1."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-se-mgmt15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, se-mgmt, sep, responsibility-assignment, interface-control]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — SE Management (space-systems/ecss/e10-se-mgmt)2324Use when the task is managing the system engineering (SE) activities,25responsibilities and interfaces of the SE function as defined in the26System Engineering Plan (SEP), per ECSS-E-ST-10C clause 5.6.1 --27categorizing each SE activity, checking that its SEP responsibility28assignment and required interfaces to other project functions are on29record, and checking that its status is internally consistent.3031## Domain quick reference3233- Clause 5.6.1 requires the SE function to manage its own activities,34 responsibilities and interfaces as laid down in the SEP. This leaf35 treats an SE activity as one of a fixed set of kinds: technical36 management, requirements engineering, analysis, design definition,37 verification, product-assurance interface, or risk management. Each38 activity is categorized into exactly one kind before the rest of the39 review runs.40- Every activity must have exactly one responsible role drawn from the41 SEP's role list (SE manager, lead engineer, subsystem engineer,42 product assurance engineer, project manager, customer43 representative). An activity with no owner recorded is flagged as44 unassigned; an owner outside the recognized role list is rejected45 outright, since it signals the SEP role list itself was not consulted.46- Each activity kind carries a fixed set of external project functions47 it must interface with under the SEP (e.g. verification must48 interface with product assurance; technical management and risk49 management must interface with project management; requirements50 engineering must interface with the customer). A recorded interface51 names its counterpart function; a required counterpart missing from52 the activity's recorded interfaces is flagged.53- Each activity also carries a status: planned, in progress, complete,54 or blocked. A blocked activity must record why (a blocking reason);55 a completed activity must not depend on another activity that has56 not itself reached complete -- an open prerequisite behind a57 "complete" activity is a management-control gap, not a technical one.5859## Workflow60611. Inventory every SE activity under the SEP and categorize each one62 by kind. Reject an unrecognized activity kind before it enters the63 review.642. For each activity, check the SEP responsibility assignment: flag a65 missing owner; reject an owner that is not a recognized SEP role.663. For each activity, determine its required interface set from its67 kind and check it against the activity's recorded interfaces; flag68 each required counterpart that has no recorded interface. Reject an69 interface naming an unrecognized counterpart function.704. For each activity, check status consistency: flag a blocked71 activity with no recorded reason, and flag a complete activity that72 depends on another activity not itself complete. Reject an73 unrecognized status or a dependency id that does not resolve to a74 known activity.755. Aggregate the responsibility, interface and status findings per76 activity; the activity is not under SE management control until all77 three lists are empty.786. Roll the per-activity reviews up to a program-level verdict; the79 program is not compliant until every activity in it is compliant.8081## Pitfalls8283- Treating an unassigned owner and an unrecognized owner the same way84 -- a missing owner is a findable gap in the SEP responsibility85 assignment, but a role outside the recognized SEP role list means86 the assignment itself is malformed and must be rejected, not87 silently logged as a finding.88- Skipping the required-interface check for an activity kind with no89 recorded interfaces at all -- the check is driven by the activity's90 kind, not by whether any interfaces happen to be present; an91 activity that never records an interface it is required to have is92 still a finding.93- Reading a "complete" status at face value without checking its94 dependencies -- a completed activity that still depends on an95 incomplete one is not actually under control, even though its own96 status field says otherwise.97- Conflating a blocked activity that records a reason with one that98 does not -- only the absence of a recorded reason is the finding;99 a blocked activity with a documented reason is a normal, trackable100 state, not a violation.101102## Behavior contract (gate 3)103104The activity-kind categorization, responsibility-assignment,105interface-coverage, and status-consistency logic is exercised by the106gate 3 contract test: scripts/test_e10_se_mgmt.py against107scripts/e10_se_mgmt_logic.py (stdlib unittest, offline). Run:108python3 scripts/test_e10_se_mgmt.py109110## Compliance111112- ECSS standards are freely downloadable (ESA); cite the source and113 paraphrase per standards-map.yaml.114- compliance: STANDARDS-REF, gated: false.