Workflows for defence programmes
Defence programmes are judged on format as much as content: the section order, the verbal forms, the verification paragraph that mirrors every requirement paragraph. MIL-STDs are government works, so runs follow them directly.
19 workflows
Requirement specification document
Turn your requirements into a Word spec, grouped by subsystem, with a traceability appendix.
Preliminary Design Review (PDR) deck
Preliminary Design Review deck with mission context, architecture, and open items.
Design FMEA from architecture
Draft a Design FMEA from your architecture and export it to Excel.
Excel requirements import
Import every row of your spreadsheet as a requirement, with your IDs kept exactly.
Requirements coverage report
What the model is actually missing, triaged, before any of it becomes a ticket.
Requirements reconciliation with Jira
Four difference lists between the model and Jira. Read-only in both systems.
Requirement change impact analysis
The full blast radius of a requirement change, drafted as a Jira change request.
Pull request interface check
Comment on a pull request only where it contradicts the documented interface.
Requirement IDs with no implementation
Code claiming requirements that no longer exist, and the reverse, held apart.
Model change to code impact
What in the codebase now contradicts a model change, opened as linked issues.
Jama baseline migration
A whole baseline across, with the trace links, and a list of every edge it had to cut.
Jama drift report
Where Jama and the model disagree, established before anyone decides what to do.
Jama suspect link triage
The suspect backlog sorted into safe to clear, genuinely broken, and needs a human.
Polarion requirements to architecture
Give Polarion requirements an architecture to point at, one accepted link at a time.
Polarion traceability gap report
Requirement to architecture to verification to result, with every break in the chain named.
Polarion round trip without breaking baselines
Changes come across into In Work requirements. Frozen ones get a change request instead.
Confluence hazard log mirror
The hazard picture published for people outside the safety team, with implemented kept apart from verified.
Verify mission requirements in Ansys STK
Access, coverage, link and lifetime computed against the limit, with the scenario recorded in full.
Teamcenter change impact on the model
What a change board is about to decide without knowing which requirements it breaks.
Other industries