Requirements linked to proof
A requirement diagram links a requirement to an element, a test, or another requirement. Use it when you need traceability: which need is satisfied, verified, or refined by what.
A class diagram is the neighbor for attributes and methods. C4 is the neighbor for people and systems around the software. Neither of those draws the requirement-to-test links this page is for.
Trace needs, not object structure
Choose a requirement diagram when a review asks what proves a need. Choose a class diagram when the review asks how objects are shaped. Choose C4 when the review asks which systems sit outside yours.
Repair the links
1. Name the link type
Say satisfies, verifies, or traces in the prompt. A plain arrow is ambiguous. Fix the verb on any link the draft guessed.
2. Attach a test where you claim proof
If a requirement has no test and you need one, add the test name and the verifies link. Do not leave an orphan need.
3. Remove design detail
Method bodies and table keys do not belong here. Move structure to a class diagram or an ER diagram.
How to phrase the prompt
Write each requirement as a short shall statement. Then name the element or test it connects to, and the verb. Keep identifiers stable if your team already uses them. Skip user-interface copy.
Trace draft questions
- How many requirements fit one diagram?
- One feature family, not the whole catalog. Split by area when links start crossing every box.
- Can I connect a requirement to another requirement?
- Yes. Say that one refines or traces to the other. Use a test link only when a test actually checks the need.
- The draft looks like a class diagram. Why?
- The prompt listed types and methods. Start with requirement names and their tests, and leave class members out.