A lightweight technique for assessing risks in requirements analysis
A lightweight technique for assessing risks in requirements analysis
- Author(s): K. Boness ; A. Finkelstein ; R. Harrison
- DOI: 10.1049/iet-sen:20070068
For access to this article, please select a purchase option:
Buy article PDF
Buy Knowledge Pack
IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.
Thank you
Your recommendation has been sent to your librarian.
- Author(s): K. Boness 1 ; A. Finkelstein 2 ; R. Harrison 3
-
-
View affiliations
-
Affiliations:
1: School of Systems Engineering, University of Reading, Reading, UK
2: Department of Computer Science, UCL, London, UK
3: Department of Computer Science, Stratton Edge Consulting, Cirencester, UK
-
Affiliations:
1: School of Systems Engineering, University of Reading, Reading, UK
- Source:
Volume 2, Issue 1,
February 2008,
p.
46 – 57
DOI: 10.1049/iet-sen:20070068 , Print ISSN 1751-8806, Online ISSN 1751-8814
A simple and practical technique for assessing the risks, that is, the potential for error, and consequent loss, in software system development, acquired during a requirements engineering phase is described. The technique uses a goal-based requirements analysis as a framework to identify and rate a set of key issues in order to arrive at estimates of the feasibility and adequacy of the requirements. The technique is illustrated and how it has been applied to a real systems development project is shown. How problems in this project could have been identified earlier is shown, thereby avoiding costly additional work and unhappy users.
Inspec keywords: software engineering; risk analysis
Other keywords:
Subjects: Software engineering techniques
References
-
-
1)
- B.W. Boehm . Software risk management: principles and practices. IEEE Software , 1 , 32 - 41
-
2)
- J. Mylopoulos , L. Chung , B. Nixon . Representing and using nonfunctional requirements: a process oriented approach. IEEE Trans. Software Eng. , 6 , 483 - 497
-
3)
- `IEEE guide for developing system requirements specifications', IEEE Std. 1233-1996, June 1996, IEEE.
-
4)
- van Lamsweerde, A., Dardenne, A., Delcourt, B., Dubisy, F.: `The KAOS Project: knowledge acquisition in automated specification of software', Proc. AAAI Spring Symp. Series, March 1991, Stanford University, AAAI, p. 59–62.
-
5)
- Dardenne, A., Fickas, S., van Lamsweerde, A.: `Goal-directed concept acquisition in requirements elicitation', Proc. 6th EEE Workshop System Specification and Design, 1991, Como, Italy, p. 14–21.
-
6)
- B.W. Boehm . A spiral model of software development and enhancement. Computer , 5 , 61 - 72
-
7)
- F.A.C. Pinheiro . (2002) Requirements honesty, Int. Workshop on Time-Constrained Requirements Engineering (TCRE′02).
-
8)
- M. Jackson . (2000) Problem frames: analysing and structuring software development problems.
-
9)
- Cornford, S.L., Feather, M.S., Hicks, K.A.: `DDP – a tool for life-cycle risk management', Proc. IEEE Aerospace Conf, 2001, Big Sky, Montana, p. 441–451.
-
10)
- M. Keil , P.E. Cule , K. Lyytinen , R.C. Schmidt . A framework for identifying software project risks. Commun. ACM , 11 , 76 - 83
-
11)
- A. Rashid , P. Sawyer , A. Moreira , J. Araujo . (2002) Early aspects: a model for aspect-oriented requirements engineering, Requirements Engineering 2002 (RE′02).
-
12)
- Hall, J.G., Jackson, M., Laney, R.C., Nuseibeh, B., Rapanotti, L.: `Relating software requirements and architectures using problem frames', Tenth Int. IEEE Conf. Requirements Engineering, 2002, Los Alamitos, CA, IEEE Computer Society Press, p. 137–144.
-
13)
- L. Rising , N. Janoff . The scrum software development process for small teams. IEEE Software , 4 , 26 - 32
-
14)
- E. Baniassad , P.C. Clements , J. Araújo , A. Moreira , A. Rashid , B. Tekinerdogan . Discovering early aspects. IEEE Software , 1 , 61 - 70
-
15)
- P. Bernader , A. Andrews , A. Aurum , C. Wohlin . (2006) Requirements prioritization, Engineering and managing software requirements.
-
16)
- B. Freimut , L.C. Briand , F. Vollei . Determining inspection cost-effectiveness by combining project data and expert opinion. IEEE Trans. Software Eng. , 12 , pp 1074 - 1092
-
17)
- L. Wallace , M. Keil . Software project risks and their effect on outcomes. Commun. ACM , 4 , 68 - 73
-
18)
- Darimont, R.: `Requirements engineering with objectiver: from goal analysis to automatically derived requirements documents', Int. Conf. Requirements Engineering (RE03), 2003, IEEE Computer Society Press, Los Alamitos, CA, RE'03 Exhibitors' Track.
-
19)
- L. Wallace , M. Keil , A. Rai . How software project risk affects project performance: an investigation of the dimensions of risk and an exploratory model. Decision Sci. , 2 , 289 - 321
-
20)
- Ruhe, G., Eberlein, A., Pfahl, D.: `Quantitative WinWin: a new method for decision support in requirements negotiation', Proc. 14th Int. Conf. Software Engineering and Knowledge Engineering (SEKE′02), July 2002, Ischia, Italy, p. 159–166.
-
21)
- J. Karlsson , K. Ryan . A cost-value approach for prioritizing requirements. IEEE Software , 5 , 67 - 74
-
22)
- J. Karlsson , C. Wohlin , B. Regnell . An evaluation of methods for prioritizing software requirements. J. Information Software Technol. , 939 - 947
-
1)
Related content
