On the Fenwick portal project, testers confirm every function behaves exactly as the technical specification describes, and no defects remain against those documented requirements. At user acceptance, however, several stakeholders say the working solution does not actually support how they process orders day to day. What has most likely happened?
- AThe solution passed validation but failed verification, because it did not conform to its written specification
- BThe solution was rejected only because acceptance criteria were never written for any of its features
- CThe solution passed both validation and verification, so the stakeholder objections fall outside evaluation
- DThe solution passed verification but failed validation, because it does not meet the real business need in use Correct
Why A is wrong: This reverses the terms: conforming to the written specification is exactly what verification confirmed, so the solution passed verification, making this description inconsistent with the facts.
Why B is wrong: Missing acceptance criteria can cause disputes, but the scenario says testing was thorough against documented requirements, so the gap is a validation shortfall against the real need, not simply absent criteria.
Why C is wrong: It is tempting to treat clean testing as full success, but stakeholders reporting the solution does not fit their work is a validation failure, so it cannot have passed validation.
Why D is correct: Conforming to the specification is verification, which passed, while failing to support the stakeholders' actual work is a validation failure, which is the precise pattern the scenario describes.