Lesson 6 · Requirements and traceability

Writing requirements, linking tasks, trace statuses and gaps in the matrix.

Goal of this lessonTo write a requirement, link it to tasks and read from the matrix what is met and what is a gap.

Trace status	Meaning
Not covered	No task or change implements it.
In progress	Tasks exist, not all done.
Implemented	All its tasks are done, or a merged change names it.
Verified	The state is Verified and the work is done.
Gap	The state claims more than the evidence: approved with nothing implementing it, or implemented while work is still open.

Step by step

Write the requirement
Project › Requirements › New: title, kind, MoSCoW priority (Must, Should, Could, Won't), source, acceptance criteria and verification method. It gets a key like REQ-0001; developers write that key in their PRs.
Link the tasks and read the trace
On the Tasks tab add the tasks that implement it. Coverage is the share of tasks done; the trace status is computed from the evidence, never chosen by hand.
12345
1. State: Draft → In Review → Approved → Implemented → Verified.
2. Trace: the status computed from the evidence.
3. Coverage: the share of tasks done.
4. The tasks implementing it.
5. The task counter.
Read the matrix
The Requirements list is the traceability matrix. A red row is a gap that needs closing.
12345
1. Priority (MoSCoW).
2. The coverage bar.
3. Trace status.
4. The gap flag.
5. A gap row: approved with no work implementing it.

Question: "How was the synchronisation-drift requirement verified?"
Answer: The requirement form: task T163, the merged PRs, verification method Test, the verification note and date — on one screen.

Can you change the trace status by hand?

No; it is computed from tasks and merged changes. The state is what you change.

What does 'REQ-0012' in a PR do?

It links the PR to the requirement; merged into the default branch it becomes evidence.