This project is read-only.

Part III - Accepting Software

Part I introduced several models to help us think about the role of acceptance testing in the overall context of the software development lifecycle. Part II described the acceptance process from the perspectives of commonly occurring roles played by the people involved in making the acceptance and readiness decisions on typical projects. Part III addresses the process of accepting software, applying the concepts introduced in Parts I and II. In Part III, we outline the main activities that lead to the acceptance decision and describe strategies for their effective management.

Chapter 17 – Planning for Acceptance introduces the practices used by one or more of the roles described in Part I to plan the activities that will provide the decision makers with the data that they need to make an acceptance decision.
Chapter 18 – Assessing Software introduces the acceptance testing and verification techniques used in software assessment, with particular emphasis on test definition, execution and maintenance. It addresses both functional and non-functional acceptance testing.
Chapter 19 – Managing the Acceptance Processintroduces the practices used to manage acceptance test execution and acceptance decision-making and addresses the tradeoffs between different approaches to these activities.
Chapter 20 – Streamlining the Acceptance Processdescribes the organization of the acceptance process to optimize the acceptance schedule and the resources used in the acceptance decision by focusing on three main strategies: incremental development, waste reduction by avoiding “overproduction” and concurrent execution of the activities underlying software acceptance.

Last edited Nov 6, 2009 at 12:54 AM by rburte, version 1


No comments yet.