【正文】 f testing is plex and involves several different “clients,” who benefit from testing. Direct clients of testing are developers and project managers, who directly interact with the testing team (representing the internal dimension). However, in the spirit of valuebased software engineering important parties for testing are customers and users (representing the external view). Customers and users are the source of value objectives (see Chapter 7), which set the context and scope of testing. Within this context testing informs developers and project managers to what extent value objectives are met and where improvement is required. Clients of Testing Developers, project managers, quality managers, customers, analysts, end users, or maintenance staff benefit from a thorough analysis of the software system and rely on feedback for detecting problems, reducing uncertainty, making decisions, or improving products and processes. The following examples show the kind of feedback from testing required by different groups: ? Customers and users get information as to what extent mutually agreed requirements are satisfied and to what extent the software meets their value 9 propositions. Testing also provides visibility and insights about project progress. Passed tests reduce the odds of misbehavior and acceptance decisions are thus frequently based on the results of tests. When acceptance tests are impractical or fail to reveal hidden problems that bee visible only in realworld conditions, alpha and beta testing provide a more solid foundation for acceptance decisions. ? Marketing and product managers require information from testing for planning releases, pricing, promotion, and distribution. A gap between the actual quality and the quality expected by customers and users most certainly leads to misleading expectations and wrong assumptions that diminish or prevent value realization (Boehm, 2021b). In order to successfully manage these expectations and to satisfy individual and anizational objectives, reconciling customer needs with product design has to consider quality in addition to functionality. ? For project managers testing supports risk management and progress estimation. The focus is on identifying and eliminating risks that are potential value breakers and inhibit value achievements. Early detection of severe defects that significantly reduce project performance is a major objective. Ideally, testing reduces uncertainty and helps project managers to take better, more informed decisions, ., for defect removal, system stabilization, and release decisions. ? Quality managers are interested in the identification of problems and in particular problem trends. Results from testing are the input for the assessment of development performance and provide the basis for quality assurance strategies and process improvement. Rosenberg (2021) discusses how testing contributes to quality assurance and shows that problems need to be documented, corrected, and can then be used for process improvement。 簡(jiǎn)言之，測(cè)試能夠通過降低計(jì)劃的不確定性和風(fēng)險(xiǎn)性來提升利益，作出相關(guān)的決定，努力控制把不必要的消耗減少到最低程度 (內(nèi)部原因 )。 ? 開發(fā)人員通常需要獲取反饋信息來驗(yàn)證測(cè)試實(shí)施是否完整，是否符合標(biāo)準(zhǔn)，是否滿足質(zhì)量要求。 ? 對(duì)于項(xiàng)目主管，測(cè)試支持了風(fēng)險(xiǎn)管理和項(xiàng)目進(jìn)程的估計(jì)。 最直接的客戶是直接與測(cè)試小組有密切聯(lián)系的程序開發(fā)者和項(xiàng)目主管 。 內(nèi)部觀點(diǎn)是建立在價(jià)值主張的利益之上 ， 以及測(cè)試的預(yù)算代表著整個(gè)項(xiàng)目的一個(gè)大概水平 。 為了使內(nèi)部和外部?jī)煞矫嬉蛩叵嘟Y(jié)合 ， 只專注于技術(shù)方面的測(cè)試顯然是不恰當(dāng)?shù)?。 開發(fā)和測(cè)試的分離使得這問題顯得更為突出 。 因此軟件測(cè)試具有挑戰(zhàn)的就是尋找更多的有效途徑進(jìn)行有效的測(cè)試 。 關(guān)鍵詞 : 基于價(jià)值的軟件測(cè)試 ,基于 價(jià)值 的測(cè)試 ,測(cè)試成本 ,測(cè)試?yán)?,測(cè)試管理 前言 測(cè)試是軟件質(zhì)量保證過程中最重要和最廣泛使用的方法 。 畢業(yè)設(shè)計(jì) (論文