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.
Beschreibung
Welcome to IEEE Xplore 2.0: A lightweight technique for assessing risks in requirements analysis
%0 Journal Article
%1 boness08
%A Boness, K.
%A Finkelstein, A.
%A Harrison, R.
%D 2008
%J IET Software
%K agile goals requirements
%N 1
%P 46-57
%T A lightweight technique for assessing risks in requirements analysis
%V 2
%X 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.
@article{boness08,
abstract = {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.},
added-at = {2009-06-02T00:29:24.000+0200},
author = {Boness, K. and Finkelstein, A. and Harrison, R.},
biburl = {https://www.bibsonomy.org/bibtex/230334527936c5de018d7523b61deb3dd/neilernst},
description = {Welcome to IEEE Xplore 2.0: A lightweight technique for assessing risks in requirements analysis},
interhash = {007b25a56082f296cb664edefc7f2664},
intrahash = {30334527936c5de018d7523b61deb3dd},
issn = {1751-8806},
journal = {IET Software},
keywords = {agile goals requirements},
month = {February },
number = 1,
pages = {46-57},
timestamp = {2009-06-02T00:29:24.000+0200},
title = {A lightweight technique for assessing risks in requirements analysis},
volume = 2,
year = 2008
}