Trace a Need to an Acceptance Decision
5 min read
Lesson objectives
- Trace need, requirement, test and change decision.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A trace is not simply an identifier in a spreadsheet. It is an argument that connects why a requirement exists to the design that addresses it and the evidence that will judge it. Start with the first need, a resident's need for a report not to disappear. the first requirement requires a unique identifier after saving the report. the first test saves 100 fictional reports and checks identifiers and what users actually see. Forward tracing exposes a need without implementation or evidence. Backward tracing exposes a requirement or test with no justified need. A link alone does not prove that a requirement is good or a test sufficient; it locates the question. Requirements management guidance follows relationships among expectations, requirements, changes and verification through the life cycle. Here we use a small matrix suited to the diploma case.
A useful row names the need and its owner, requirement and version, implementing architectural element, verification method, evidence status and acceptance decision. In the pump service, the second need is the crew's need for a usable location. the seventh location requirement prevents a field order without an accepted location. The dispatcher implements it, and the seventh location test tests accepted street text, accepted coordinates, an empty value and malformed text. Before deployment we must decide what accepted means: only a valid input format or an independently confirmed physical place? If the seventh location test checks format alone, its result is format verified, not location accurate. Naming the evidence boundary prevents an attractive green row from becoming a claim it cannot support.
Traceability has a practical limit. Linking every paragraph to every decision without discrimination turns the matrix into noise. Focus on links that affect a function, hazard or acceptance condition, and explain why the link belongs. the second need to the seventh location requirement is direct: protect the crew from a locationless order. the seventh location requirement to format test the seventh location test is only partial: it shows that the service blocks missing or malformed input, not that the location exists on the ground. Add a validation activity the location validation activity with field users on representative confirmed sites, and keep it distinct from requirement verification. If validation fails while the seventh location test passes, do not erase the valid test result. Identify the gap between the specified property and intended benefit, then revise the need, requirement or working procedure.
Use the trace when a meaningful change arrives, rather than only at release. Suppose the service adds telephone reporting. A call centre enters the report for the resident, so the resident may never see the case number on a screen. We need another route for communicating or retrieving the number and evidence that it works during the call. The original need, avoiding a lost report, remains. The observation point changes, so copying the screen test into the telephone path is invalid. Record the new version, decision date and test result. When a failure occurs later, the matrix should take the team back to the reason for each design choice, not merely list current component names.
Lesson summary
Link a need to its requirement and test, then identify links requiring review after an interface change.