search menu icon-carat-right cmu-wordmark

Software Risk Management

Technical Report
This 1996 report studies problems with requirements engineering that are not adequately addressed by specification techniques, with an elicitation method being proposed to handle these issues.
Publisher

Software Engineering Institute

CMU/SEI Report Number
CMU/SEI-96-TR-012

Abstract

There are many problems associated with requirements engineering, including problems in defining the system scope, problems in fostering understanding among the different communities affected by the development of a given system, and problems in dealing with the volatile nature of requirements. These problems may lead to poor requirements and the cancellation of system development, or else the development of a system that is later judged unsatisfactory or unacceptable, has high maintenance costs, or undergoes frequent changes. By improving requirements elicitation, the requirements engineering process can be improved, resulting in enhanced system requirements and potentially a much better system.

Requirements engineering can be decomposed into the activities of requirements elicitation, specification, and validation. Most of the requirements techniques and tools today focus on specification, i.e., the representation of the requirements. This report concentrates instead on elicitation concerns, those problems with requirements engineering that are not adequately addressed by specification techniques. An elicitation methodology is proposed to handle these concerns.

This new elicitation methodology strives to incorporate the advantages of existing elicitation techniques while comprehensively addressing the activities performed during requirements elicitation. These activities include fact-finding, requirements gathering, evaluation and rationalization, prioritization, and integration. Taken by themselves, existing elicitation techniques are lacking in one or more of these areas.

Cite This Technical Report

Christel, M., & Kang, K. (1996, June 1). Software Risk Management. (Technical Report CMU/SEI-96-TR-012). Retrieved May 19, 2024, from https://insights.sei.cmu.edu/library/software-risk-management/.

@techreport{christel_1996,
author={Christel, Michael and Kang, Kyo},
title={Software Risk Management},
month={Jun},
year={1996},
number={CMU/SEI-96-TR-012},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://insights.sei.cmu.edu/library/software-risk-management/},
note={Accessed: 2024-May-19}
}

Christel, Michael, and Kyo Kang. "Software Risk Management." (CMU/SEI-96-TR-012). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, June 1, 1996. https://insights.sei.cmu.edu/library/software-risk-management/.

M. Christel, and K. Kang, "Software Risk Management," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Report CMU/SEI-96-TR-012, 1-Jun-1996 [Online]. Available: https://insights.sei.cmu.edu/library/software-risk-management/. [Accessed: 19-May-2024].

Christel, Michael, and Kyo Kang. "Software Risk Management." (Technical Report CMU/SEI-96-TR-012). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 1 Jun. 1996. https://insights.sei.cmu.edu/library/software-risk-management/. Accessed 19 May. 2024.

Christel, Michael; & Kang, Kyo. Software Risk Management. CMU/SEI-96-TR-012. Software Engineering Institute. 1996. https://insights.sei.cmu.edu/library/software-risk-management/