Requirement specification document
Your requirements are already in the model. This turns them into the document a review board, a customer, or a regulator will accept, without retyping anything.
The problem this solves
Spec documents get written twice: once as engineering, once as formatting. Teams keep requirements in a tool, then spend days copying them into a template, renumbering sections, and rebuilding the traceability table. By the time it is signed, the model has moved on.
How it works
Turn your requirements into a Word spec, grouped by subsystem, with a traceability appendix.
The prompt
Read all requirements in [model name] and generate a formal System Requirements Specification as a Word document. Group by subsystem, include ID, statement, status, and verification method, and add a traceability appendix.
Replace the [bracketed] placeholders with your model and project names.
Example output
What you get
Document formats
Other tools hand you empty templates to type into. Because the document chain maps to requirement levels in the model — stakeholder needs at the top, system requirements below, satisfied by parts — one Dalus model emits the whole chain and cross-document traceability comes free.
The document is produced as a real Word file, not a chat response. Attach your house template or an example deliverable and the agent replicates its structure, headings, and numbering scheme.
Common questions
More Word workflows
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.
Compare your model against a counterparty ICD
Characteristic by characteristic against their document, with how each match was made.