After completing this course, you will be able to
- describe the purpose of User Acceptance Testing and where it fits within the development life cycle.
- differentiate between static and dynamic UAT activities.
- recognize quality attributes of requirements documentation.
- apply the appropriate level of rigour when testing requirements.
- recognize defects in a Business Requirements Document.
- use a variety of techniques to clarify ambiguous requirements.
- facilitate a Requirements Walkthrough meeting.
This course is designed for business users and testers who want to learn how to verify user requirements before committing resources to the design and build phases. You can choose to use our case sample or bring in one of your own to work with instead. We'll walk you through the steps you should take to validate user requirements and determine whether they are ready for the next phase and, if not, what needs to be done to correct them. You will learn how to determine whether your requirements are consistent, accurate and clear, and will meet the level of quality product your organization needs.
Who should attend?
Business Users, Business Analysts and Quality Assurance Analysts who are responsible for the User Acceptance and business procedural testing process. If you are a business operations manager or team leader, you would also benefit because you'd gain a better understanding of the importance of high-quality requirements.
You should have a general knowledge of system development life cycles, and testing processes and principles.
- Where do business requirements come from?
- Who uses them?
- What are "good" requirements
- Why aren't they always good?
- When should requirements be tested?
Discussion: How do your requirements look?
- Overview of the testing process
- Requirements quality criteria
- Using checklists to assess quality
- Removing ambiguity and errors
Exercise: Recognizing requirements problems
- Inputs to the requirements test
- The review process step-by-step
- Conducting effective walkthroughs
- Documenting requirement defects
- Outputs from Requirements Test