You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

Industry evaluation of the Requirements Abstraction Model

Authors:

Tony Gorschek , Per Garre , Stig Larsson , Claes Wohlin

Research group:

Industrial Software Engineering

Publication Type:

Journal article

Venue:

Requirements Engineering Journal

Publisher:

Springer London

Abstract

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.12

Bibtex

@article{Gorschek1140,
author = {Tony Gorschek and Per Garre and Stig Larsson and Claes Wohlin},
title = {Industry evaluation of the Requirements Abstraction Model},
volume = {12},
number = {3 (on-line first)},
month = {May},
year = {2007},
journal = {Requirements Engineering Journal},
publisher = {Springer London},
url = {http://www.es.mdu.se/publications/1140-}
}