System Framing, Needs and Requirements

Review questions

Integrated synthesis: System Framing, Needs and Requirements

This subject starts by defining the system of interest, its boundary and its flows with the call centre, field crew and message provider. Learners distinguish elements the design team controls from external dependencies, then separate stakeholder needs from suggested features. They turn a need for reports not to disappear into a verifiable requirement with a threshold, observation point and test conditions. In the fictional maintenance case, rejecting 12 of 40 incomplete reports would lose 30%; retaining them for follow-up need not send a crew without a location. Learners build a trace matrix linking need, requirement, test and evidence limit. They finish by reviewing a proposed threshold change rather than making a small test pass through wording alone. The subject closes by reconciling resident, crew and centre needs into separate acceptance boundaries for registration and dispatch, with explicit denominators and decision triggers.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1Who owns the case store within the example boundary?
  2. Question 2Which statement needs a threshold before it becomes a testable display requirement?
  3. Question 3What does a requirement-to-test trace accomplish?
  4. Question 4After a saved report gains a verified location, when is a work order issued and when may the crew travel?