User acceptance testing : a step by step guide / Brian Hambling, Pauline Van Goethem

INTRODUCTION.. What this book is about.. • The role of UAT ..• The costs and benefits of UAT.. • The value of UAT – the reasons we need to do it.. • Stakeholders – who this book is for.. • How to get the best from this book.. • Checklists.. • Case studies.. THE IMPORTANCE OF UAT.. What is UAT?.. • Why test ISs?.. • Business vulnerability.. • The UAT process •.. From UAT to service delivery.. • UAT and contracts.. Stakeholders in UAT.. • Chapter summary.. BUSINESS REQUIREMENTS.. Business requirements.. • Business intent and user expectations.. • Acceptance criteria.. • Threquirement types.. • Prioritising business requirements.. • The relationship between business requirements and UAT.. • The relationship between development and UAT.. • Scope of UAT.. • Building a test basis for UAT.. • Chapter summary TESTING BASICS FOR UAT What is testing?.. • Test types.. • Testing processes.. • Test-case design techniques.. • Testing approaches for UAT.. • Reviews.. • Chapter summary..THE UAT TEAM Stakeholders and the UAT team.. • Key roles in a UAT team.. • Creating a successful team.. • Training the team.. • UAT training content.. •.. The team life cycle.. • Dealing with team conflict.. • The working environment and working patterns.. • Basic disciplines •.. Chapter summary UAT AS TRANSITION The IS life cycle as a series of transitions.. • Planning for transitions.. • UAT as a transitional phase.. • UAT as an event and UAT as a process.. • Chapter summary PREPARING FOR UAT – PLANNING Deciding what we want to achieve.. • Acceptance criteria..UAT objectives.. • Entry criteria..• Defining the testing we will need •.. Creating a test basis for UAT..• Setting up the test management controls.. •.. Chapter summary TEST DESIGN FOR UAT The hierarchy of test design.. • Identifying test conditions.. • Designing test cases.. • Designing test scripts.. • Data creation.. • Chapter summary IMPLEMENTING THE TESTS The testing schedule.. • Implementing the test schedule.. • Identifying progress.. • The status report.. • The post-testing summary.. • Chapter summary EVALUATING THE SYSTEM How do we decide whether or not to accept a system?.. • When the testing has to stop.. • The risk of release ..• Measuring the risk of release.. • Defining and evaluating emergency-release criteria • Decision process for evaluating UAT results.. • Test summary report conclusions.. • The final release decision.. • Chapter summary LIFE AFTER UAT Post-UAT reporting.. • End-user training.. • Preparing a roll-out strategy.. • Implementation • Post-implementation defect corrections.. • Measuring business benefits.. • The end of UAT? ..• Chapter summary