Requirements: Turning a Wish into a Testable Statement · seed 1 · A4, ink-friendly. The answer key prints on its own page for grown-ups.

Turning foggy wishes into checkable promises

Computing · Software Engineering · ages 19-20
Name ______________________   Date ____________

  1. A spec pairs one entry naming system behaviour with one entry naming a reply time bar. Which entry is functional?

    • The time bar entry
    • The behaviour entry
    • Both are functional

  2. Which sentence is a real requirement?

    • Results must show within two seconds on a home connection
    • The page should be nice
    • The search must feel fast

  3. A requirement must let a tester pass or fail it without asking the author.

    Circle one:   True   False

  4. Two lines say guests may borrow ten books and guests may borrow two books. What is this?

    • Two lines demanding opposite things, for review to catch
    • A functional and quality pair
    • A clean scope split

  5. A client says make checkout easy. What is your next move?

    • Promise it will feel smooth
    • Start building at once
    • Ask who checks out, doing what, with what pass mark

  6. Where does an accessibility rule like every image carries a text alternative belong?

    • Nowhere, it is too strict
    • With requirements, since anyone can run that check
    • Only in a design sketch

  7. A teammate calls this a requirement: the system must handle many users quickly. What is missing?

    • The measure, the circumstance, and who checks it
    • A longer adjective
    • Nothing, it is ready to build

  8. A spec grows wild with orphan lines nobody asked for. What discipline fixes it?

    • Add more wishes for balance
    • Hide the extra lines in an appendix
    • Trace each line back to a named need and cut orphans
LightMySky · lightmysky.comW1-mt_TFb-YNpvT1-s1

Answer key

For grown-ups. Fold this page away before handing over the rest.

Turning foggy wishes into checkable promises W1-mt_TFb-YNpvT1-s1

  1. The behaviour entry · Behaviour names what the system does; the time bar names how well.
  2. Results must show within two seconds on a home connection · Only the first line lets a stranger pass or fail it.
  3. True · Name input, outcome, and worst case, or the line is only a note.
  4. Two lines demanding opposite things, for review to catch · Reviews catch lines that demand opposite things before build starts.
  5. Ask who checks out, doing what, with what pass mark · Turn the fog into observer, action, and check before building.
  6. With requirements, since anyone can run that check · It names user, barrier, and exact check, the model shape.
  7. The measure, the circumstance, and who checks it · Fast hides the number, the condition, and the judge.
  8. Trace each line back to a named need and cut orphans · Each line earns its place from a parent need; orphans invite creep.
Worksheet · LightMySky