CAPM Practice: Validate requirements through product delivery
Question 65 of 68 in Validate requirements through product delivery
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: System testing validates technical correctness against specifications; business acceptance testing validates that the solution meets business needs and stakeholder acceptance criteria — both are necessary but serve different validation purposes
Explanation
System testing focuses on technical requirements (does the system function correctly?). Business acceptance testing focuses on business requirements (does the solution meet business needs?). A system that passes all technical tests can still fail business acceptance if requirements were misunderstood.
**Why not A:** System testing and business acceptance testing are not identical activities performed by different teams. They validate fundamentally different things — system testing validates technical correctness, while business acceptance testing validates that the solution meets real business needs.
**Why not B:** Business acceptance testing is not conducted exclusively by executives. It involves business stakeholders and end users who can assess whether the solution meets their operational needs and acceptance criteria. Executives may participate, but they are not the only testers.
**Why not C:** Neither form of testing is inherently more important. Both are necessary but serve different purposes. A system can pass all technical tests yet fail business acceptance if requirements were misunderstood, demonstrating that both validation types are essential.
Key Concept
This question covers Validate requirements through product delivery under Validate requirements through product delivery (Business Analysis Frameworks).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free