Requirements diagrams¶
Use-case diagram¶
- Actors stay outside the system boundary; packages group related use cases inside it.
includeandextendrelations come from the front matter of the cards.- An actor is linked only to the use cases that no other use case of that actor includes.
- It is regenerated by
RUP indexfrom the cards: never edit it by hand.
One diagram per actor¶
When there are several actors, Pro also draws a diagram per actor with only the use cases that actor triggers, plus the ones they include or extend.
Wireframes¶
- One sketch per screen of the flow, drawn as a PlantUML salt layout so it stays text.
- Every field shown maps to a domain attribute or a parameter of the use case; every attribute the use case needs appears in some screen.
- Wireframes are PlantUML also when the project uses Mermaid, because Mermaid has no wireframe diagram.