The requirements phase serves multiple purposes: freezing requirements establishes a stable baseline, understanding user needs ensures alignment, and defining testing scope sets boundaries. All three (D) are essential activities in this phase. Without frozen requirements, testing lacks a fixed target. Without understanding user needs, tests may miss acceptance criteria. Without scope definition, resources cannot be allocated effectively.