When are the acceptance criteria for user acceptance testing defined?
A. When the deliverables of the system design have been agreed.
B. When the deliverables of the requirements analysis have been agreed.
C. When the software has been completed and has passed system testing
D. When the users have had the opportunity to use the software for a period of time.
|
Download Printable PDF. VALID exam to help you PASS. |
 |
B – , C too late
Acceptance criteria is an attribute of requirement in requirements catalogue entry (see Debra Paul et al. Appendix 11A). Requirements catalogue, in turn, is the output of Analysis, Define Requirement or Define and Agree Business Requirements phase in Waterfall, ‘V’ model or Agile Systems development lifecycles respectively. This is why I went for answer B. The answer D would be partialy correct in case of Agile, because there is “Elaborate solution requirements“ phase in iterative part of Agile lifecycle, where initial requirements could be considerably changed or amended, thus causing changes in acceptance criteria set. And yes, I know, that formally after requirements analysis, requirements should be validated and documented properly to get final requirements document, which then has to be maintained throughout subsequent lifecycle phases 🙂
Isn’t it a bit late?