ECSS Human Factors — HFE Test Report DRD Validation (space-systems/ecss/e1011-test-drd)
Use when the task is to generate or validate the Human Factors Engineering (HFE)
test report required by ECSS-E-ST-10-11C Annex D (normative): checking that the
report satisfies the DRD's mandatory section list, that participant counts meet the
minimum threshold for the test type, that every finding carries a severity category,
that each finding is linked to at least one recommendation, and that all planned
test scenarios appear in the execution record.
Domain quick reference
- ECSS-E-ST-10-11C Annex D defines a normative DRD for the HFE test report, the
document produced after each HFE evaluation event. The DRD specifies mandatory
sections and content elements; a report submitted to a project review must satisfy
all of them before it can be formally accepted.
- Mandatory sections are: document identification (title, issue, date, reference),
objectives (what was being assessed and against which HFE requirements), test
environment (facilities, simulations, or mockups used), participants (count,
screening criteria, role summary), test scenarios (the tasks executed), results
(quantitative metrics such as task completion rate, error count, time on task),
findings (usability issues and non-conformances identified), and recommendations
(corrective or improvement actions linked to findings).
- Findings are categorized by severity: critical (prevents task completion or
creates a safety risk), major (significantly impairs task performance), or minor
(causes inconvenience with limited mission impact). An unrecognized severity
label is a non-conformance.
- Participant count minimums reflect accepted usability practice anchored in the
HFE assessment process requirements of the standard: at least three participants
for a formative evaluation (iterative design feedback during development) and at
least five for a summative evaluation (final acceptance verification).
- Every finding must be traceable to at least one recommendation; a finding with
no linked recommendation is an open action that blocks report closure.
- Scenario coverage: each scenario listed in the test plan must have a
corresponding execution record in the report; an unexecuted planned scenario
must be explicitly documented as a gap.
Workflow
- Verify the report contains all eight mandatory sections. Record each missing
section by name before moving to content checks; a missing section is a
DRD non-conformance regardless of what the remaining sections contain.
- Confirm the test type is recognized (formative or summative) and that the
participant count meets the corresponding minimum. An unrecognized test type
or a below-minimum count is a non-conformance.
- For each finding, confirm the severity is one of the three recognized levels
(critical, major, minor). Findings with an unrecognized severity label are
flagged individually.
- Check finding-to-recommendation traceability: every finding identifier must
appear as the target of at least one recommendation. List each unlinked
finding identifier as an open action.
- Check scenario coverage: compare the set of planned scenario identifiers to
the set of executed scenario identifiers. Return each planned scenario that is
absent from the execution record.
- Aggregate all findings; the report is DRD-compliant only when all five
violation lists (missing sections, participant violation, invalid severity
findings, unlinked findings, uncovered scenarios) are empty.
Pitfalls
- Accepting a report that lists all section headings but leaves content fields
empty — a section heading without content fails the DRD just as badly as a
missing section.
- Applying the summative minimum (five participants) to a formative evaluation —
the two test types have different minimum thresholds; applying the higher bar
to formative evaluations will reject valid iterative assessments.
- Treating a finding with severity "moderate" or "high" as equivalent to a
recognized level — the DRD recognizes exactly critical, major, and minor;
non-standard labels must be corrected, not carried forward.
- Counting a recommendation without an explicit finding reference as covering
all findings — linkage is per finding identifier; a generic recommendation
without a finding ID does not satisfy the traceability requirement.
- Marking scenario coverage satisfied when all scenarios were attempted but
some were aborted — an aborted scenario must appear in the execution record
with an explicit abort justification; it is not the same as a completed
execution.
Behavior contract (gate 3)
The mandatory-section check, participant count validation, finding severity
validation, finding-to-recommendation linkage check, and scenario coverage check
are exercised by the gate 3 contract test:
scripts/test_e1011_test_drd.py against scripts/e1011_test_drd_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e1011_test_drd.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1011-test-drd3description: "Use when generate and validate the Human Factors Engineering (HFE) test report against the ECSS-E-ST-10-11C Annex D Document Requirements Definition (DRD): confirm all mandatory sections are present and complete, verify participant counts meet the minimum for the test type (formative or summative), check that every finding is assigned a severity category (critical, major, or minor), confirm each finding has at least one linked recommendation, and verify that all planned test scenarios are represented in the execution record. Trigger: ecss, e-st-10-11c, hfe, human-factors, test-report, drd, findings, recommendations, usability-test."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/e1011-test-drd15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, hfe, human-factors, test-report, drd, findings, usability-test]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Human Factors — HFE Test Report DRD Validation (space-systems/ecss/e1011-test-drd)2324Use when the task is to generate or validate the Human Factors Engineering (HFE)25test report required by ECSS-E-ST-10-11C Annex D (normative): checking that the26report satisfies the DRD's mandatory section list, that participant counts meet the27minimum threshold for the test type, that every finding carries a severity category,28that each finding is linked to at least one recommendation, and that all planned29test scenarios appear in the execution record.3031## Domain quick reference3233- ECSS-E-ST-10-11C Annex D defines a normative DRD for the HFE test report, the34 document produced after each HFE evaluation event. The DRD specifies mandatory35 sections and content elements; a report submitted to a project review must satisfy36 all of them before it can be formally accepted.37- Mandatory sections are: document identification (title, issue, date, reference),38 objectives (what was being assessed and against which HFE requirements), test39 environment (facilities, simulations, or mockups used), participants (count,40 screening criteria, role summary), test scenarios (the tasks executed), results41 (quantitative metrics such as task completion rate, error count, time on task),42 findings (usability issues and non-conformances identified), and recommendations43 (corrective or improvement actions linked to findings).44- Findings are categorized by severity: critical (prevents task completion or45 creates a safety risk), major (significantly impairs task performance), or minor46 (causes inconvenience with limited mission impact). An unrecognized severity47 label is a non-conformance.48- Participant count minimums reflect accepted usability practice anchored in the49 HFE assessment process requirements of the standard: at least three participants50 for a formative evaluation (iterative design feedback during development) and at51 least five for a summative evaluation (final acceptance verification).52- Every finding must be traceable to at least one recommendation; a finding with53 no linked recommendation is an open action that blocks report closure.54- Scenario coverage: each scenario listed in the test plan must have a55 corresponding execution record in the report; an unexecuted planned scenario56 must be explicitly documented as a gap.5758## Workflow59601. Verify the report contains all eight mandatory sections. Record each missing61 section by name before moving to content checks; a missing section is a62 DRD non-conformance regardless of what the remaining sections contain.632. Confirm the test type is recognized (formative or summative) and that the64 participant count meets the corresponding minimum. An unrecognized test type65 or a below-minimum count is a non-conformance.663. For each finding, confirm the severity is one of the three recognized levels67 (critical, major, minor). Findings with an unrecognized severity label are68 flagged individually.694. Check finding-to-recommendation traceability: every finding identifier must70 appear as the target of at least one recommendation. List each unlinked71 finding identifier as an open action.725. Check scenario coverage: compare the set of planned scenario identifiers to73 the set of executed scenario identifiers. Return each planned scenario that is74 absent from the execution record.756. Aggregate all findings; the report is DRD-compliant only when all five76 violation lists (missing sections, participant violation, invalid severity77 findings, unlinked findings, uncovered scenarios) are empty.7879## Pitfalls8081- Accepting a report that lists all section headings but leaves content fields82 empty — a section heading without content fails the DRD just as badly as a83 missing section.84- Applying the summative minimum (five participants) to a formative evaluation —85 the two test types have different minimum thresholds; applying the higher bar86 to formative evaluations will reject valid iterative assessments.87- Treating a finding with severity "moderate" or "high" as equivalent to a88 recognized level — the DRD recognizes exactly critical, major, and minor;89 non-standard labels must be corrected, not carried forward.90- Counting a recommendation without an explicit finding reference as covering91 all findings — linkage is per finding identifier; a generic recommendation92 without a finding ID does not satisfy the traceability requirement.93- Marking scenario coverage satisfied when all scenarios were attempted but94 some were aborted — an aborted scenario must appear in the execution record95 with an explicit abort justification; it is not the same as a completed96 execution.9798## Behavior contract (gate 3)99100The mandatory-section check, participant count validation, finding severity101validation, finding-to-recommendation linkage check, and scenario coverage check102are exercised by the gate 3 contract test:103scripts/test_e1011_test_drd.py against scripts/e1011_test_drd_logic.py104(stdlib unittest, offline). Run:105python3 scripts/test_e1011_test_drd.py106107## Compliance108109- ECSS standards are freely downloadable (ESA); cite the source and110 paraphrase per standards-map.yaml.111- compliance: STANDARDS-REF, gated: false.