Workflows for ECSS programmes
A Technical Requirements Specification and System Requirements Document per ECSS-E-ST-10-06C, interface requirements and control documents per the annexes of ECSS-E-ST-10-24C, and a requirements audit against 10-06C. ECSS standards are publicly available, so runs follow their published structure directly.
Audit against the model
Runs that cross-examine what the model holds and hand back ranked findings with the evidence behind each one. A findings report, never a compliance claim.
Generate from the model
Runs that read the model and produce the deliverable, with the sections the model cannot fill named rather than invented.
Requirement specification document
Turn your requirements into a Word spec, grouped by subsystem, with a traceability appendix.
Interface Requirements Document (IRD)
The obligations on an interface, stated per end, including the interfaces that have none.
Interface Control Document (ICD)
The agreed interface design, with a coverage table saying which sections the model could not fill.