Mission Risk Diagnostic (MRD) Method Description
• Technical Note
Publisher
Software Engineering Institute
CMU/SEI Report Number
CMU/SEI-2012-TN-005DOI (Digital Object Identifier)
10.1184/R1/6575495.v1Topic or Tag
Abstract
Although most programs and organizations use risk management when developing and operating software-reliant systems, preventable failures continue to occur at an alarming rate. In many instances, the root causes of these preventable failures can be traced to weaknesses in the risk management practices employed by those programs and organizations. In particular, Software Engineering Institute (SEI) field experience indicates that programs and organizations throughout government and industry are unable to assess their risks effectively. For example, SEI independent assessments routinely uncover significant risks that have not been brought to the attention of key decision makers. When decision makers are unaware of significant risks, they are unable to take action to mitigate those risks. As a result, SEI researchers undertook a project to examine and improve the practice of risk assessment. The SEI has developed the Mission Risk Diagnostic (MRD) to assess risk in interactively complex, socio-technical systems across the life cycle and supply chain. To date, the SEI has employed the MRD in a variety of domains, including software acquisition and development, cybersecurity, software security, and business portfolio management. This technical note provides an overview of the MRD method.
Part of a Collection
Cybersecurity Engineering Research: Software Assurance Measurement and Analysis Collection
Cybersecurity Engineering Research: Cybersecurity Quality Metrics Collection
Cite This Technical Note
Alberts, C., & Dorofee, A. (2012, February 1). Mission Risk Diagnostic (MRD) Method Description. (Technical Note CMU/SEI-2012-TN-005). Retrieved November 22, 2024, from https://doi.org/10.1184/R1/6575495.v1.
@techreport{alberts_2012,
author={Alberts, Christopher and Dorofee, Audrey},
title={Mission Risk Diagnostic (MRD) Method Description},
month={{Feb},
year={{2012},
number={{CMU/SEI-2012-TN-005},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://doi.org/10.1184/R1/6575495.v1},
note={Accessed: 2024-Nov-22}
}
Alberts, Christopher, and Audrey Dorofee. "Mission Risk Diagnostic (MRD) Method Description." (CMU/SEI-2012-TN-005). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, February 1, 2012. https://doi.org/10.1184/R1/6575495.v1.
C. Alberts, and A. Dorofee, "Mission Risk Diagnostic (MRD) Method Description," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Note CMU/SEI-2012-TN-005, 1-Feb-2012 [Online]. Available: https://doi.org/10.1184/R1/6575495.v1. [Accessed: 22-Nov-2024].
Alberts, Christopher, and Audrey Dorofee. "Mission Risk Diagnostic (MRD) Method Description." (Technical Note CMU/SEI-2012-TN-005). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 1 Feb. 2012. https://doi.org/10.1184/R1/6575495.v1. Accessed 22 Nov. 2024.
Alberts, Christopher; & Dorofee, Audrey. Mission Risk Diagnostic (MRD) Method Description. CMU/SEI-2012-TN-005. Software Engineering Institute. 2012. https://doi.org/10.1184/R1/6575495.v1