{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:37:15Z","timestamp":1750307835405,"version":"3.41.0"},"reference-count":17,"publisher":"Association for Computing Machinery (ACM)","issue":"4","license":[{"start":{"date-parts":[[2008,7,1]],"date-time":"2008-07-01T00:00:00Z","timestamp":1214870400000},"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":[[2008,7]]},"abstract":"<jats:p>This paper discusses a different approach to managing risk in a man-rated software system. This approach emphasizes identifying and targeting the right risks in order to apply effective mitigation activities. It addresses the risk of not understanding the customer wishes, of unreliable software product, and selection of inappropriate reuse. When the right risks are identified with sufficient granularity, resources can be focused on mitigating only those risks. Resources are not spent mitigating general risks or non-risks. The cost can be more correctly estimated and overruns controlled.<\/jats:p>","DOI":"10.1145\/1384139.1384147","type":"journal-article","created":{"date-parts":[[2008,7,22]],"date-time":"2008-07-22T13:04:05Z","timestamp":1216731845000},"page":"1-8","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":3,"title":["Managing a man-rated software development program via risk mitigation"],"prefix":"10.1145","volume":"33","author":[{"given":"Julia F.","family":"Varnell-Sarjeant","sequence":"first","affiliation":[{"name":"Lockheed Martin Space Systems Company"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2008,7]]},"reference":[{"key":"e_1_2_1_1_1","unstructured":"Defense Acquisition University Acquisition Community Connection Risk Management Community website April 23 2008 : https:\/\/acc.dau.mil\/rm  Defense Acquisition University Acquisition Community Connection Risk Management Community website April 23 2008 : https:\/\/acc.dau.mil\/rm"},{"key":"e_1_2_1_2_1","unstructured":"Jiantao Pan \"Software Reliability \" April 23 2008 http:\/\/www.ece.cmu.edu\/~koopman\/des_s99\/sw_reliability\/#concepts  Jiantao Pan \"Software Reliability \" April 23 2008 http:\/\/www.ece.cmu.edu\/~koopman\/des_s99\/sw_reliability\/#concepts"},{"volume":"1220","journal-title":"EIA Std","first-page":"0","key":"e_1_2_1_3_1"},{"volume":"1220","journal-title":"EIA Std","first-page":"1","key":"e_1_2_1_4_1"},{"volume":"1220","journal-title":"EIA Std","first-page":"2","key":"e_1_2_1_5_1"},{"key":"e_1_2_1_6_1","unstructured":"IEEE982-1---IEEE Std-982.1-1988 \"IEEE Standard Dictionary of Measures to Produce Reliable Software \" IEEE Computer Society June 1988.  IEEE982-1---IEEE Std-982.1-1988 \"IEEE Standard Dictionary of Measures to Produce Reliable Software \" IEEE Computer Society June 1988."},{"volume-title":"RTCA Inc.","year":"1992","author":"Equipment Federal Aviation","key":"e_1_2_1_7_1"},{"key":"e_1_2_1_8_1","unstructured":"DO248B---RCTA\/DO-248 Final Report for Clarification of DO-178B \"Software Considerations in Airborne Systems and Equipment \" Prepared by SC-190 October 12 2001.  DO248B---RCTA\/DO-248 Final Report for Clarification of DO-178B \"Software Considerations in Airborne Systems and Equipment \" Prepared by SC-190 October 12 2001."},{"key":"e_1_2_1_9_1","unstructured":"SAE International---JA1002---\"Software Reliability Program Standard\" SAE International January 2004.  SAE International---JA1002---\"Software Reliability Program Standard\" SAE International January 2004."},{"key":"e_1_2_1_10_1","unstructured":"SAE International---JA1003---Software Reliability Program Implementation Guide SAE International January 2004.  SAE International---JA1003---Software Reliability Program Implementation Guide SAE International January 2004."},{"key":"e_1_2_1_11_1","unstructured":"CMMI2000---CMMI-SE\/SW-Continuous V1.02 \"CMMI for Systems Engineering\/Software Engineering Version 1.02 Continuous Representation \" CMU\/SEI-2000-TR-019 November 2000.  CMMI2000---CMMI-SE\/SW-Continuous V1.02 \"CMMI for Systems Engineering\/Software Engineering Version 1.02 Continuous Representation \" CMU\/SEI-2000-TR-019 November 2000."},{"key":"e_1_2_1_12_1","unstructured":"CMMI-SE\/SW-Staged V1.02 \"CMMI for Systems Engineering\/Software Engineering Version 1.02 Staged Representation \" CMU\/SEI-2000-TR-018 November 2000.  CMMI-SE\/SW-Staged V1.02 \"CMMI for Systems Engineering\/Software Engineering Version 1.02 Staged Representation \" CMU\/SEI-2000-TR-018 November 2000."},{"volume-title":"ISO","year":"1998","key":"e_1_2_1_13_1"},{"key":"e_1_2_1_14_1","unstructured":"Young A Thomas \"Report of the Defense Science Board\/ Air Force Scientific Advisory Board Joint Task Force on Acquisition of National Security Space Programs \" Office of the Under Secretary of Defense For Acquisition Technology and LogisticsWashington D.C. 20301-3140 May 2003  Young A Thomas \"Report of the Defense Science Board\/ Air Force Scientific Advisory Board Joint Task Force on Acquisition of National Security Space Programs \" Office of the Under Secretary of Defense For Acquisition Technology and LogisticsWashington D.C. 20301-3140 May 2003"},{"volume-title":"Congress on Performance of Major Programs Can Be More Complete, Timely, and Accessible,\"","year":"2005","author":"Levin Robert E","key":"e_1_2_1_15_1"},{"key":"e_1_2_1_16_1","unstructured":"Ross Seider Tom Nolette On-Fire Associates \"Phase Containment Effectivity \" Boston Spin Feb. 17 2004 http:\/\/www.on-fireassociates.com\/PDF%20SPIN%202-17-04.pdf  Ross Seider Tom Nolette On-Fire Associates \"Phase Containment Effectivity \" Boston Spin Feb. 17 2004 http:\/\/www.on-fireassociates.com\/PDF%20SPIN%202-17-04.pdf"},{"key":"e_1_2_1_17_1","unstructured":"New York Times Phil Taubman \"Lesson on How Not to Build a Navy Ship\" April 25 2008.  New York Times Phil Taubman \"Lesson on How Not to Build a Navy Ship\" April 25 2008."}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1384139.1384147","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1384139.1384147","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T13:58:00Z","timestamp":1750255080000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1384139.1384147"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2008,7]]},"references-count":17,"journal-issue":{"issue":"4","published-print":{"date-parts":[[2008,7]]}},"alternative-id":["10.1145\/1384139.1384147"],"URL":"https:\/\/doi.org\/10.1145\/1384139.1384147","relation":{},"ISSN":["0163-5948"],"issn-type":[{"type":"print","value":"0163-5948"}],"subject":[],"published":{"date-parts":[[2008,7]]},"assertion":[{"value":"2008-07-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}