Specifying Detailed Metrics and Acceptance Criteria

Where Domain II's planning task set the project's overall business metrics, this task elaborates and specifies detailed, item-level acceptance criteria for each individual requirement — the specific, measurable conditions (often written in a given-when-then format) that determine whether that particular piece of the solution actually meets what was asked for.

These detailed criteria are what Domain V's evaluation work will later check the finished solution against, so vague or missing criteria here directly weakens the ability to objectively judge delivery later — "the feature should work well" isn't a criterion a tester can pass or fail against.

Study focus: a scenario asking you to write or critique acceptance criteria for a specific requirement, checking whether they're specific and measurable rather than subjective, is testing this exact task.