Skip to main content
Log in

Using Influence Diagrams to Aid the Management of Software Change

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

In a large software management programme, the number of software changes and enhancements requested for inclusion in the next software release often far exceeds the implementation resources available. Thus, during the preceding months before the final decision is made on which changes to include, there needs to be a way of incorporating all the different factors that influence these possible changes into a coherent set of information to enable good decisions to be made. This paper describes the use of influence diagrams to implement a risk model to formalise the combining of these different factors to aid the decision process. This model not only reflects the likelihood of all the necessary criteria for a requested change to be viable being met, but also considers the financial or other benefits to the organisation that would result from the change being included in the next software release.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Burgess, C., Dattani, I., Hughes, G. et al. Using Influence Diagrams to Aid the Management of Software Change. Requirements Eng 6, 173–182 (2001). https://doi.org/10.1007/PL00010358

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1007/PL00010358

Navigation