2010
DOI: 10.1007/s00766-010-0112-x
|View full text |Cite
|
Sign up to set email alerts
|

Goal-driven risk assessment in requirements engineering

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
87
0
1

Year Published

2013
2013
2021
2021

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 92 publications
(88 citation statements)
references
References 29 publications
0
87
0
1
Order By: Relevance
“…In addition, there is a line of research in the area of security risk assessment [29][30][31] where there is identification, assessment, and mitigation of risks to security mechanisms that will endanger the satisfaction of security requirements. However, the risk are investigated in isolation with limited support for cost/benefit trade-off analysis.…”
Section: Related Workmentioning
confidence: 99%
“…In addition, there is a line of research in the area of security risk assessment [29][30][31] where there is identification, assessment, and mitigation of risks to security mechanisms that will endanger the satisfaction of security requirements. However, the risk are investigated in isolation with limited support for cost/benefit trade-off analysis.…”
Section: Related Workmentioning
confidence: 99%
“…It is obtained from a simplication of the approach proposed in [19], following the path started in [20]. In [19], authors present a model for risk assessment where three layers are depicted: a goal layer where the goals and their relations are described, an event layer where events that can impact over the goals are described, and a treatment layer where a set of actions and their ability to mitigate the eect of events are modeled. In [20], the authors apply the model to a dierent eld, by focusing on eciency and QoS in data centers, focusing on the event layer.…”
Section: A Goal-oriented Model For Green Data Centersmentioning
confidence: 99%
“…For risk identification, scenario-based heuristics are available [2,29] as well as goal-oriented formal techniques [1,14]. For risk assessment, various kinds of quantitative techniques are available [3,5,8,25]. For risk control, the only work on countermeasure exploration is [14] where the obstacle resolution tactics mentioned in this paper are described.…”
Section: Related Workmentioning
confidence: 99%
“…They often arise from a natural inclination to believe that the software and its environment will always behave as expected; no requirements are engineered for cases where this optimistic assumption does not hold. Requirements completeness therefore calls for putting risk analysis at the heart of the RE process [2,3,5,8,13,14,20].…”
Section: Introductionmentioning
confidence: 99%