Tracking Requirements

Tracking requirements means maintaining a traceability artifact or tool that records each requirement's current status, where it originally came from, and how it relates to and depends on other requirements — not a one-time snapshot, but a continuously updated record. This is the day-to-day mechanics that make the traceability strategy set in Domain II actually real.

The practical payoff is evidence: when someone later asks "did we actually deliver what requirement R-204 asked for," a well-maintained tracking artifact answers that question directly, rather than requiring someone to reconstruct the history from memory or scattered emails.

Study focus: a scenario where a requirement's current status is unclear because the tracking artifact hasn't been updated in weeks is testing recognition that tracking is an ongoing discipline, not a document built once and left alone.