Software risk management: principles and practices

Boehm, Barry

doi:10.1109/52.62930

Cited by 1,154 publications

(774 citation statements)

References 2 publications

Supporting

Mentioning

687

Contrasting

Unclassified

Order By: Relevance

“…In simple terms, a risk is an event that can affect the goals of a project [15]. So, RM in software projects can be taken as the application of a set of principles and practices to the identification, analysis and treatment of risk factors aiming to prevent a project from failing, despite the fact that a risk can alternatively be treated as an opportunity in many software projects.…”

Section: Requirement Risks and Argumentation Schemesmentioning

confidence: 99%

Argumentation Schemes for the Collaborative Debate of Requirement Risks in Software Projects

Siqueira

Fontoura

Bordini

et al. 2017

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

-Managing risks in real-world software projects is of paramount importance. A significant class of such risks is related to the engineering of requirements, commonly involving the presentation and analysis of risk management arguments from both software engineers and clients involved in collaborative debates. In this work, drawing inspiration from argumentation theory in Artificial Intelligence, we introduce a number of "argumentation schemes" and associated "critical questions" to support such discussions. In doing so, we propose schemes related to risks due to excessive numbers of requirements; inadequate client representatives and poor understanding of client needs; incorrect, incomplete and conflicting requirements, and complex and non-traceable requirements. We also present a case study where the developed schemes were used to support the discussion of requirement risks in the context of a research and prototyping software project for the Brazilian Army.

show abstract

Section: Requirement Risks and Argumentation Schemesmentioning

confidence: 99%

Argumentation Schemes for the Collaborative Debate of Requirement Risks in Software Projects

Siqueira

Fontoura

Bordini

et al. 2017

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…Since the 1970s, both academics and practitioners have written about managing risks of software projects [2,3,5]. Unfortunately, much of what has been published on risk management is based on studies limited to a narrow portion of the development process of software projects.…”

Section: Contribution and Related Workmentioning

confidence: 99%

“…Boehm introduces in [2] a risk management approach for software projects. The projects and environments that were the basis of Boehm's work might not, however, be representative for data warehouse projects.…”

Section: Contribution and Related Workmentioning

confidence: 99%

Risk-Management for Data Warehouse Systems

Bruckner

List

Schiefer

2001

Data Warehousing and Knowledge Discovery

View full text Add to dashboard Cite

Abstract. Data warehouse projects are notoriously difficult to manage and many of them end in failure. One explanation for the high failure rate is that managers are not taking prudent measures to assess and manage the risks involved in the data warehouse project. In this paper we introduce the goaldriven risk management approach of the easyREMOTE DWH framework. We classify the risks of a data warehouse system into categories of risk sources and discuss their consequences to the data warehouse project. Further, we show the relevance of risks to the go/no-go decision of the data warehouse project. Finally, we present an approach for documenting data warehouse risks.

show abstract

“…Risk management entails methods to mitigate risks that may occur during a software development project. Boehm [8] describes a framework for risk management consisting of two main steps, namely risk assessment (identification, analysis, and prioritization) and risk control (planning, resolution, and monitoring). Ropponen and Lyytinen [6] have identified six elements of software risk.…”

Section: Background and Related Workmentioning

confidence: 99%