2018
DOI: 10.1007/978-3-030-01177-2_37
|View full text |Cite
|
Sign up to set email alerts
|

Risk Management in Software Engineering: What Still Needs to Be Done

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 8 publications
0
3
0
Order By: Relevance
“…This article presents a framework that categorizes risks based on their relative importance and perceived level of control over the project manager. The framework is classified into four quadrants: customer mandate, scope and requirements; execution; and the environment [52]. However, risk analysis becomes very difficult or impractical for large projects because the research only focuses on quantitative aspects and ignores qualitative elements.…”
Section: What Is the Results Of The Research?mentioning
confidence: 99%
“…This article presents a framework that categorizes risks based on their relative importance and perceived level of control over the project manager. The framework is classified into four quadrants: customer mandate, scope and requirements; execution; and the environment [52]. However, risk analysis becomes very difficult or impractical for large projects because the research only focuses on quantitative aspects and ignores qualitative elements.…”
Section: What Is the Results Of The Research?mentioning
confidence: 99%
“…In [8], Boehm split risk assessment into three phasesidentification, analysis, and prioritization -and risk control into three other phases: management planning, resolution (or mitigation), and monitoring. Other researchers may change the categories to which these steps belong to, such as in [14], where risk assessment is made up of phases for identification, analysis, prioritization, planning, and resolution, and risk control is made up of only one phase, which is monitoring, but the key concepts and phases remain the same.…”
Section: Impactmentioning
confidence: 99%
“…Risk identification and analysis are preemptive actions designed to anticipate and prepare for potential issues. It implies identifying potential risks, evaluating their likely impact and frequency, and formulating strategies for mitigation or contingency plans to tackle them proactively [5]. Risks can be categorized using different criteria, including their origin, type, or impact on the project [6].…”
Section: Introductionmentioning
confidence: 99%