Assuring Quality Through Acceptance Testing: In-House Training
It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community.
It is the business analyst's job to define the business problem to be solved by IT. It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. The business analyst is not only concerned with the testing itself, but also with the management and monitoring of the users doing the acceptance testing, and recording, analyzing, and evaluating the results.
What you will Learn
Upon completion, participants will be able to:
Create a set of acceptance test cases
Manage and monitor an acceptance test stage where users perform the testing
Work with the development team in the systems testing stage
Assess the solution once it is in the business environment
Foundation Concepts
The role of the business analyst
An introduction to the BABOK® Guide
BA roles and relationships through the project life cycle
Introduction to assuring software quality through acceptance testing
The Scope of IT Testing
Overview of testing stages
The testing process
Testing documentation
Pre-Acceptance Testing
The BA's role in testing
Early development testing stages (unit and integration)
Late development testing stage (system)
The Acceptance Test Stage - Part I (Planning, Design, and Development)
Overview of user acceptance testing
Acceptance test planning
Designing user acceptance tests
Developing individual user acceptance test cases
Building effective user acceptance test scenarios
The Acceptance Test Stage - Part II (Execution and Reporting)
Operating guidelines
Execution
Reporting
Post-Acceptance Testing
Overview
Project implementation
Project transition (project closure)
Production through retirement
Testing Commercial Off-the-Shelf (COTS) Software
Overview
Selecting the software
Implementing the software
Summary
What did we learn and how can we implement this in our work environments?