book

User Acceptance Testing

by Brian Hambling, Pauline van Goethem

May 2013

Intermediate to advanced

226 pages

6h 13m

English

BCS, The Chartered Institute for IT

Read now

Unlock full access

What this book is aboutThe role of UATThe costs and benefits of UATThe value of UAT – the reasons we need to do itStakeholders – who this book is forHow to get the best from this bookChecklistsCase studies
What is UAT?Why test ISs?Business vulnerabilityThe UAT processFrom UAT to service deliveryUAT and contractsStakeholders in UATChapter summary
Business requirementsBusiness intent and user expectationsAcceptance criteriaThe requirement typesPrioritising business requirementsThe relationship between business requirements and UATThe relationship between development and UATScope of UATBuilding a test basis for UATChapter summary

What is testing?Test typesTesting processesTest-case design techniquesTesting approaches for UATReviewsChapter summary
Stakeholders and the UAT teamKey roles in a UAT teamCreating a successful teamTraining the teamUAT training contentThe team life cycleDealing with team conflictThe working environment and working patternsBasic disciplinesChapter summary
The IS life cycle as a series of transitionsPlanning for transitionsUAT as a transitional phaseUAT as an event and UAT as a processChapter summary
Deciding what we want to achieveAcceptance criteriaUAT objectivesEntry criteriaDefining the testing we will needCreating a test basis for UATSetting up the test management controlsChapter summary
The hierarchy of test designIdentifying test conditionsDesigning test casesDesigning test scriptsData creationChapter summary
The testing scheduleImplementing the test scheduleIdentifying progressThe status reportThe post-testing summaryChapter summary
How do we decide whether or not to accept a system?When the testing has to stopThe risk of releaseMeasuring the risk of releaseDefining and evaluating emergency-release criteriaDecision process for evaluating UAT resultsTest summary report conclusionsThe final release decisionChapter summary
Post-UAT reportingEnd-user trainingPreparing a roll-out strategyImplementationPost-implementation defect correctionsMeasuring business benefitsThe end of UAT?Chapter summary
Initiating the UAT project checklist (sponsor)Planning the UAT project checklist (UAT team leader)UAT test design checklistUAT test execution checklistUAT release decision checklistPost-UAT actions checklist
Chapter 1Chapter 2Chapter 3Chapter 4Chapter 5Chapter 6Chapter 7Chapter 8Chapter 9
The training processThe training consultant role

Content preview from User Acceptance Testing

4 THE UAT TEAM

In Chapter 1 the concept of stakeholders, each with a different role to play in an implementation, was introduced. The sponsor commissions the system and signs the cheques, the manager is responsible for delivering the benefits of the system, the end-user operates the system and the developer builds the system. Each role has a different contribution to make to the project and each role has different objectives. UAT represents the first time that all the roles will potentially reach a moment of resolution regarding their own goals and responsibilities. The sponsor will know whether the cheque should be signed, the manager will know whether the business benefits will be delivered, the end-users will know whether the system works ...