Monitoring Requirements Through Their Lifecycle

Beyond tracking a requirement's basic status, monitoring checks that the right supporting artifacts exist at each stage of its lifecycle — a model built during analysis, documentation written during specification, test cases created before validation — and that each one is actually reviewed and approved on schedule, not just produced and forgotten.

This task catches a specific, easy-to-miss failure mode: a requirement that looks "on track" by status label alone, but is quietly missing one of its required supporting artifacts, which only becomes a crisis once someone needs that missing piece and it isn't there.

Study focus: a scenario where a requirement reaches the development stage but its test cases were never actually written or reviewed is testing a monitoring gap — the status tracking alone didn't catch the missing supporting artifact.