Needs & Requirements
Requirements, Status and Approval
Every requirement in the project, with its status, approval record and the attributes that track priority, ownership and open items.
Where to find it
- In the navigation rail: Needs & Requirements → Requirements.
Main actions
- The Requirements page is the Database filtered to requirements: sort, filter, edit in place and use the bulk tools. Click a row to see it in the inspector.
- Status runs Draft → In Review → Approved or Rejected. The inspector and the Entity View show Approve, Reject… (with an optional reason) and Reopen; each records your name and the date.
- Editing the name or description of an Approved requirement moves it back to In Review with the note “Text changed after approval”. Undo reverses both.
Attributes
| Attribute | Values |
|---|---|
| Priority | High, Medium, Low: importance to the stakeholders |
| Criticality | High, Medium, Low: consequence if the requirement is not met |
| Owner | Person or team responsible |
| Source | Stakeholder, document or standard it comes from |
| Verification Method / Level | Analysis, Demonstration, Inspection, Test; the level at which it is verified |
| TBD/TBR | None, TBD or TBR, with TBD Owner and TBD Due Date (see TBD/TBR Register) |
The Stakeholder Need label marks needs stated by stakeholders before they become system requirements.
Tips
- Holarch asks for your name the first time you approve; change it in Preferences.
- Computable attributes recompute when an attribute they read changes.