2013
DOI: 10.1007/s00766-013-0168-5
|View full text |Cite
|
Sign up to set email alerts
|

Assessing requirements-related risks through probabilistic goals and obstacles

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
34
0

Year Published

2014
2014
2016
2016

Publication Types

Select...
5
1

Relationship

1
5

Authors

Journals

citations
Cited by 38 publications
(34 citation statements)
references
References 20 publications
0
34
0
Order By: Relevance
“…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%
See 4 more Smart Citations
“…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%
“…A risk has a probability of occurrence and one or multiple consequences. Each consequence has a severity in degree of loss of satisfaction of the corresponding objective [5,8]. Risks may cover undesirable situations such as safety hazards [16,18], security threats [12,26] or data inaccuracies [14] dependent on the type of objective they negatively impact on.…”
Section: Introductionmentioning
confidence: 99%
See 3 more Smart Citations