SwePub - search: id:"swepub:oai:DiVA.org:mdh-70...

Enumeration	Reference	Cover	Find
1.	Gorschek, Tony, et al. (author) Industry evaluation of the Requirements Abstraction Model 2008 In: Requirements Engineering Journal. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 12:3, s. 163-190 Journal article (peer-reviewed)abstract Software requirements are often formulated on different levels and hence they are difficult to compare to each other. To address this issue, a model that allows for placing requirements on different levels has been developed. The model supports both abstraction and refinement of requirements, and hence requirements can both be compared with each other and to product strategies. Comparison between requirements will allow for prioritization of requirements, which in many cases is impossible if the requirements are described on different abstraction levels. Comparison to product strategies will enable early and systematic acceptance or dismissal of requirements, minimizing the risk for overloading. This paper presents an industrial evaluation of the model. It has been evaluated in two different companies, and the experiences and findings are presented. It is concluded that the requirements abstraction model provides helpful improvements to the industrial requirements engineering process.

Gorschek, Tony, et al. (author)
Industry evaluation of the Requirements Abstraction Model
2008
In: Requirements Engineering Journal. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 12:3, s. 163-190
Journal article (peer-reviewed)abstract
- Software requirements are often formulated on different levels and hence they are difficult to compare to each other. To address this issue, a model that allows for placing requirements on different levels has been developed. The model supports both abstraction and refinement of requirements, and hence requirements can both be compared with each other and to product strategies. Comparison between requirements will allow for prioritization of requirements, which in many cases is impossible if the requirements are described on different abstraction levels. Comparison to product strategies will enable early and systematic acceptance or dismissal of requirements, minimizing the risk for overloading. This paper presents an industrial evaluation of the model. It has been evaluated in two different companies, and the experiences and findings are presented. It is concluded that the requirements abstraction model provides helpful improvements to the industrial requirements engineering process.

Träfflista för sökning "id:"swepub:oai:DiVA.org:mdh-7073" "