軟件測(cè)試管理中英文資料外文翻譯文獻(xiàn)-在線瀏覽
2024-09-28 17:05本頁(yè)面
【正文】 tivate the need for valuebased testing, describe practices supporting the management of valuebased testing, outline a framework for valuebased test management, and illustrate the framework with an example. Keywords: Valuebased software engineering, valuebased testing, cost of testing, benefits of testing, test management. Introduction Testing is one of the most important and most widely used approaches for validation and verification (Vamp。V aims at prehensively analyzing and testing software to determine that it performs the intended functions correctly, to ensure that it performs no unintended functions, and to measure its quality and reliability (Wallace and Fujii, 1989). According to IEEE (1990) testing is defined as “an activity in which a system or ponent is executed under specified conditions, the results are observed or recorded, and an evaluation is made of some aspect of the system or ponent.”Testing is widely used in practice and plays a central role in the quality assurance strategies of many organizations. As software pervades more and more critical tasks and affects everyday life, security, and well being of millions of people (Ferscha and Mattern, 2004), the importance of testing will increase in the future. Studies show that testing already consumes between 30 and 50% of software development costs (Beizer, 1990). Even higher percentages are not unmon for safetycritical systems. Finding more efficient ways to perform effective testing is therefore a key challenge in testing (Harrold, 2000). Managing software testing based on value considerations promises to tackle increasing testing costs and required effort. Valuebased test management could also provide guidance to better align testing investments with project objectives and business value. In Chapter 1, Boehm presents an impressive example of potential test cost savings (on project level as well as on global scale) by focusing testing on the most valuable aspects. The example illustrates that with an investmentoriented focus on testing 7% of the customer billing types (1 in 15) achieved 50% of the benefits of testing the software. Completely testing the system requires a constantly increasing effort and, due to decreasing marginal benefits, results in a negative return on investment. Although a “100% tested” status is not a practical goal, there is still room for a considerable amount of improvement and savings by better adjusting testing to its value contribution. The motivation for valuebased software engineering es from the fact that “much of current software engineering practice and research is done in a value neutral setting, in which every requirement, use case, object, and defect is treated as equally important” (Boehm, 2003). This is especially true for testing, where its indirect contribution to product value leads to a valueneutral perception of testing. The mon separation of concerns between development and testing exacerbates the problem. Testing is often reduced to a purely technical issue leaving the close relationship between testing and business decisions unlinked and the potential value contribution of testing unexploited. The objectives of this chapter are to motivate the need for valuebased management of testing, to explain its unde
環(huán)評(píng)公示相關(guān)推薦
鄂ICP備17016276號(hào)-1