{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:41:43Z","timestamp":1750308103005,"version":"3.41.0"},"reference-count":5,"publisher":"Association for Computing Machinery (ACM)","issue":"4","license":[{"start":{"date-parts":[[2005,5,15]],"date-time":"2005-05-15T00:00:00Z","timestamp":1116115200000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGSOFT Softw. Eng. Notes"],"published-print":{"date-parts":[[2005,7]]},"abstract":"<jats:p>A classical problem facing many software projects is to determine when to stop testing and release the product for use. Risk analyses address such \"how much is enough?\" questions, by balancing the risk exposure of doing too little with the risk exposure of doing too much. However, it's difficult to quantify the relative probabilities and sizes of loss in order to provide practical approaches for determining a risk-balanced \"sweet spot\" operating point.In this paper, we provide a quantitative approach based on the COCOMO II cost estimation model, the COQUALMO quality estimation model and the Value Estimating Relationships.<\/jats:p>","DOI":"10.1145\/1082983.1083095","type":"journal-article","created":{"date-parts":[[2005,11,7]],"date-time":"2005-11-07T19:28:32Z","timestamp":1131391712000},"page":"1-5","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Determining how much software assurance is enough?"],"prefix":"10.1145","volume":"30","author":[{"given":"LiGuo","family":"Huang","sequence":"first","affiliation":[{"name":"University of Southern California"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Barry","family":"Boehm","sequence":"additional","affiliation":[{"name":"University of Southern California"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2005,5,15]]},"reference":[{"key":"e_1_2_1_1_1","doi-asserted-by":"publisher","DOI":"10.5555\/557000"},{"volume-title":"Eds.: Wiley","year":"2002","author":"Steece B.","key":"e_1_2_1_2_1"},{"key":"e_1_2_1_3_1","doi-asserted-by":"publisher","DOI":"10.1109\/MS.2004.1293073"},{"key":"e_1_2_1_5_1","first-page":"56","article-title":"Calculating the Value of Testing","author":"Bullock J.","year":"2000","journal-title":"Software Testing and Quality Engineering."},{"key":"e_1_2_1_6_1","doi-asserted-by":"publisher","DOI":"10.5555\/560726"}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1082983.1083095","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1082983.1083095","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T16:08:04Z","timestamp":1750262884000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1082983.1083095"}},"subtitle":["a value-based approach"],"short-title":[],"issued":{"date-parts":[[2005,5,15]]},"references-count":5,"journal-issue":{"issue":"4","published-print":{"date-parts":[[2005,7]]}},"alternative-id":["10.1145\/1082983.1083095"],"URL":"https:\/\/doi.org\/10.1145\/1082983.1083095","relation":{"is-identical-to":[{"id-type":"doi","id":"10.1145\/1083091.1083095","asserted-by":"subject"}]},"ISSN":["0163-5948"],"issn-type":[{"type":"print","value":"0163-5948"}],"subject":[],"published":{"date-parts":[[2005,5,15]]},"assertion":[{"value":"2005-05-15","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}