04913nam 2200637 a 450 991078686170332120200520144314.01-62870-257-51-78017-168-4(CKB)2670000000370227(EBL)1192409(SSID)ssj0001140332(PQKBManifestationID)12501221(PQKBTitleCode)TC0001140332(PQKBWorkID)11221133(PQKB)11099743(Au-PeEL)EBL1192409(CaPaEBR)ebr10705867(CaONFJC)MIL559642(OCoLC)854971780(CaSebORM)9781780171678(MiAaPQ)EBC1192409(EXLCZ)99267000000037022720130603d2013 uy 0engur|n|---|||||txtccrUser acceptance testing[electronic resource] a step-by-step guide /Brian Hambling, Pauline van Goethem1st editionSwindon BCS20131 online resource (228 p.)Description based upon print version of record.1-78017-167-6 Includes bibliographical references and index.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 TYPESPRIORITISING 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 TRANSITIONTHE 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 SCHEDULEIDENTIFYING 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 CHECKLISTSINITIATING THE UAT PROJECT CHECKLIST (SPONSOR)PLANNING THE UAT PROJECT CHECKLIST (UAT TEAM LEADER); UAT TEST DESIGN CHECKLIST; UAT TEST EXECUTION CHECKLIST; UAT RELEASE DECISION CHECKLIST; POST-UAT ACTIONS CHECKLIST; APPENDIX B ANSWERS AND COMMENTS; CHAPTER 1; CHAPTER 2; CHAPTER 3; CHAPTER 4; CHAPTER 5; CHAPTER 6; CHAPTER 7; CHAPTER 8; CHAPTER 9; APPENDIX C UAT TRAINING; THE TRAINING PROCESS; THE TRAINING CONSULTANT ROLE; REFERENCES; INDEX; Back CoverEvery information system brought into service in every type of organisation requires user acceptance testing. This book is a hands-on manual for non-testing specialists to plan and carry out an effective acceptance test of an information system. It also identifies ways of making the process as simple and cost-effective as possible.Project managementConsumer behaviorProject management.Consumer behavior.005.14Hambling Brian873894Goethem Pauline van1513003MiAaPQMiAaPQMiAaPQBOOK9910786861703321User acceptance testing3747242UNINA