[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
research-article

Managing a man-rated software development program via risk mitigation

Published: 01 July 2008 Publication History

Abstract

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.

References

[1]
Defense Acquisition University Acquisition Community Connection Risk Management Community website April 23, 2008, : https://acc.dau.mil/rm
[2]
Jiantao Pan, "Software Reliability," April 23, 2008, http://www.ece.cmu.edu/~koopman/des_s99/sw_reliability/#concepts
[3]
IEEE12207-0---IEEE/EIA Std 12207.0-1996, "Software life cycle processes," IEEE Computer Society, March 1998.
[4]
IEEE12207-1---IEEE/EIA Std 12207.1-1997, "Software life cycle processes - Life cycle data," IEEE Computer Society, April 1998.
[5]
IEEE12207-2---IEEE/EIA Std 12207.2-1997, "Software life cycle processes - Implementation considerations," IEEE Computer Society, April 1998.
[6]
IEEE982-1---IEEE Std-982.1-1988, "IEEE Standard Dictionary of Measures to Produce Reliable Software," IEEE Computer Society, June 1988.
[7]
DO178B---RCTA/DO-178B/ED-12B, "Software Considerations in Airborne Systems and Equipment," Federal Aviation Administration software standard, RTCA Inc., December 1992.
[8]
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.
[9]
SAE International---JA1002---"Software Reliability Program Standard" SAE International, January 2004.
[10]
SAE International---JA1003---Software Reliability Program Implementation Guide SAE International, January 2004.
[11]
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.
[12]
CMMI-SE/SW-Staged, V1.02, "CMMI for Systems Engineering/Software Engineering, Version 1.02, Staged Representation," CMU/SEI-2000-TR-018, November 2000.
[13]
SPICE98---ISO/IEC 15504:1998: "Software Process Improvement Capability Determination (SPICE)---Software Process Assessment," ISO/IEC/JTC1/SC7/WG10/N111, ISO 1998.
[14]
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
[15]
Levin, Robert E. GAO-05-182 "Information for Congress on Performance of Major Programs Can Be More Complete, Timely, and Accessible," March, 2005.
[16]
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
[17]
New York Times Phil Taubman "Lesson on How Not to Build a Navy Ship" April 25 2008.

Cited By

View all
  • (2018)Towards a Business-Driven Process Model for Knowledge Security Risk ManagementGlobal Business Expansion10.4018/978-1-5225-5481-3.ch014(270-288)Online publication date: 2018
  • (2017)Problems in Current Approaches for Risk Identification and Risk Analysis2017 International Conference on Computational Science and Computational Intelligence (CSCI)10.1109/CSCI.2017.172(999-1003)Online publication date: Dec-2017
  • (2015)Towards a Business-Driven Process Model for Knowledge Security Risk ManagementInternational Journal of Knowledge Management10.4018/IJKM.201510010111:4(1-18)Online publication date: 1-Oct-2015

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM SIGSOFT Software Engineering Notes
ACM SIGSOFT Software Engineering Notes  Volume 33, Issue 4
July 2008
69 pages
ISSN:0163-5948
DOI:10.1145/1384139
Issue’s Table of Contents

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 July 2008
Published in SIGSOFT Volume 33, Issue 4

Check for updates

Qualifiers

  • Research-article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)1
  • Downloads (Last 6 weeks)0
Reflects downloads up to 22 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2018)Towards a Business-Driven Process Model for Knowledge Security Risk ManagementGlobal Business Expansion10.4018/978-1-5225-5481-3.ch014(270-288)Online publication date: 2018
  • (2017)Problems in Current Approaches for Risk Identification and Risk Analysis2017 International Conference on Computational Science and Computational Intelligence (CSCI)10.1109/CSCI.2017.172(999-1003)Online publication date: Dec-2017
  • (2015)Towards a Business-Driven Process Model for Knowledge Security Risk ManagementInternational Journal of Knowledge Management10.4018/IJKM.201510010111:4(1-18)Online publication date: 1-Oct-2015

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media