| Description |
1 online resource (x, 215 pages) |
| Contents |
Copyright; CONTENTS; LIST OF FIGURES AND TABLES; AUTHORS; 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; 1 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; 2 BUSINESS REQUIREMENTS; BUSINESS REQUIREMENTS; BUSINESS INTENT AND USER EXPECTATIONS; ACCEPTANCE CRITERIA; THE REQUIREMENT TYPES |
|
Identifying progressthe status report; the post-testing summary; 9 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; 10 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?; appendix a uat checklists |
|
Prioritising business requirementsthe relationship between business requirements and uat; the relationship between development and uat; scope of uat; building a test basis for uat; 3 testing basics for uat; what is testing?; test types; testing processes; test-case design techniques; testing approaches for uat; reviews; 4 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; 5 uat as transition |
|
The is life cycle as a series of transitionsplanning for transitions; uat as a transitional phase; uat as an event and uat as a process; 6 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; 7 test design for uat; the hierarchy of test design; identifying test conditions; designing test cases; designing test scripts; data creation; 8 implementing the tests; the testing schedule; implementing the test schedule |
| Summary |
Annotation Every information system brought into service in every type of organisation requires user acceptance testing. It is by far the most common activity carried out by non-IT specialists. This book is designed to be a hands-on manual for non-testing specialists to plan and carry out an effective acceptance test of an information system. It provides a structured and step-by-step approach to effective acceptance testing and identifies ways of making the process as simple and cost-effective as possible |
| Bibliography |
Includes bibliographical references and index |
| Notes |
Print version record |
| Subject |
Consumer behavior.
|
|
Project management.
|
|
COMPUTERS -- Software Development & Engineering -- Quality Assurance & Testing.
|
|
Consumer behavior.
|
|
Project management.
|
| Form |
Electronic book
|
| Author |
Goethem, Pauline van
|
| ISBN |
1628702575 |
|
1780171676 |
|
1780171684 |
|
1780171692 |
|
9781628702576 |
|
9781780171678 |
|
9781780171685 |
|
9781780171692 |
|
