【正文】 不實用的或者失敗的顯示在實際環(huán)境中才能出現(xiàn)的問題， α 和 β 測試提供了一個更加堅實的基礎(chǔ)來驗證結(jié)果。 ? 對于項目主管，測試支持了風險管理和項目進程的估計。 ? 質(zhì)量主管對于問題的識別以及對特定問題的動態(tài)趨勢較為感興趣。 ? 開發(fā)人員通常需要獲取反饋信息來驗證測試實施是否完整，是否符合標準，是否滿足質(zhì)量要求。 ? 對于需求工程師來說，測試對于驗證和確認需求是很有價值的。 簡言之，測試能夠通過降低計劃的不確定性和風險性來提升利益，作出相關(guān)的決定，努力控制把不必要的消耗減少到最低程度 (內(nèi)部原因 )。因此接下來的兩個問題是：什么是測試成本？什么是價值活動的測試利益？ 5 ValueBased Management of Software Testing Rudolf Ramler, Stefan Biffl and Paul Gr252。V tasks to operate as an investment activity” (Boehm and Huang, 2021). What are the contributions of testing if we look at it from a valuebased perspective? Fundamentally, we can consider two dimensions: The internal dimension of testing covers costs and benefits of testing. The external dimension emphasizes the opportunities and risks of the future system that have to be addressed. The key challenge in valuebased testing is to integrate these two dimensions, ., align the internal test process with the value objectives ing from the customers and the market. It bees clear that a pure focus on the technical aspects of testing (., the testing methods and tools) is inappropriate to align the internal and external dimensions. Instead, test management activities need to adopt a valuebased perspective. Figure 41 illustrates the external and internal dimensions of test management and their interdependencies. The internal dimension is similar to the scope of control of the test manager in the project. This dimension addresses costs from software testing practice as well as shortterm and longterm benefits of testing. The external dimension considers stakeholders and parameters outside the scope of control of the test manager. Valuebased test management anizes testing to satisfy value propositions of the stakeholders and to focus the team on the most worthwhile testing targets. The key question ing from the external view of software testing is: “How can we ensure the value objectives of the software system?” The goal is to reconcile stakeholder value propositions by focusing testing efforts on the most worthwhile parts of the software, the most important quality characteristics, and the most urgent symptoms of risks that threaten the value contribution of the project. Answering this question involves market opportunities and threats, projectspecific customer value propositions, as well as costs and benefits. Please refer to Chapter 1 for details about opportunities and risks and to Chapter 7 for elicitation and reconciliation of stakeholder value propositions. The internal view builds on the stakeholder value propositions and the test budget that represents the possible level of testing effort in a project. The key question in this view is: “How can we anize testing as an investment activity?”The goal is to achieve effective and efficient testing considering changes in development and budget reductions. Internal 8 project stakeholders consider how plans for software development and associated testing activities can contribute to stakeholder value propositions by supplying system functionality and performance, but also by limiting the impact of projectrelevant risks. Appropriate munication is necessary to balance the external and internal dimensions of testing to assure the consistency of testing objectives with stakeholder value propositions. Value Contribution of Testing Compared to other development activities such as coding or user interface design, testing does not create immediate