The requirements engineering process with ETRM
Getting startedRequirements engineering is not a one-off write-up but a cycle: requirements are elicited, specified, connected with other requirements and evidence, reviewed, recorded as a binding state and exchanged with customers and suppliers. When something changes, the cycle starts again at the affected point. This help is structured along exactly these steps.
1 · Set up the project
A project defines which artifact types, attributes and link types are used. The ISO/IEC/IEEE 29148 profile provides a proven basic set; you add project-specific attributes such as ASIL or variant.
2 · Specify
Requirements are written in modules structured like documents: requirements specification, system specification, test specification. The wording check points out vague terms while you are still writing.
- Modules and document view
- The artifact page
- Table view, filters and bulk changes
- Wording check and glossary
3 · Analyse and link
Every system requirement is derived from a customer requirement, every test case verifies a requirement. Typed links make this visible; if a requirement changes, the dependent links are marked as suspect.
4 · Review and approve
Reviews collect the decision of the reviewers per artifact, approvals make a state binding, change requests control changes to approved content.
5 · Manage and evaluate
Baselines record immutable states; the comparison shows every change between two states. Metrics show where the project stands.
6 · Exchange data
Customers often deliver specifications as ReqIF, suppliers expect Excel or Word. ETRM reconciles repeated deliveries with your state instead of blindly overwriting it.
Tip: All steps can be followed in the sample project battery management system.