Allocating Requirements to a Baseline

Once requirements are accepted or deferred, this task decides which accepted ones actually fit within real project constraints — scope, schedule, budget, and available resources — against the value each one brings, using prioritization and dependency-analysis tools to make the trade-offs explicit rather than arbitrary. The output is a requirements baseline: the agreed, documented set the project will actually build against.

Allocation is where idealized "we want everything" planning meets real-world limits — a requirement with high value but a hard dependency on a resource that isn't actually available this cycle may need to be pushed to a later baseline, even if nobody disputes its value.

Study focus: a scenario listing several requirements with value, cost, and dependency information, asking which belong in the current baseline given a stated constraint, is testing this allocation logic directly — not simply picking the highest-value items in isolation.