Relations: when to use which
Typed links tell an agent why a requirement exists, how it is achieved and what limits it.
For: Product owner, Project lead
The ones you use most
| Relation | Use it when |
|---|---|
| Refines | A requirement details another one level up the why-chain (objective ← business ← stakeholder ← functional / non-functional). |
| Realizes | A technical requirement says how a functional or non-functional one is achieved. |
| Constrains | A constraint limits specific requirements. Without it, the constraint applies project-wide. |
| Replaces | A new record supersedes an old one of the same type. |
| Conflicts with | Two records cannot both hold. An open conflict blocks Authority. |