What is important when deciding to include a software requirement in a project or release?

Document type: Conference Papers
Peer reviewed: Yes
Author(s): Claes Wohlin, Aybüke Aurum
Title: What is important when deciding to include a software requirement in a project or release?
Conference name: 4th International Symposium on Empirical Software Engineering
Year: 2005
Pagination: 237-246
ISBN: 0-7803-9507-7
Publisher: IEEE
City: Noosa Heads, AUSTRALIA
ISI number: 000236352200025
Organization: Blekinge Institute of Technology
Department: Department of Software Engineering and Computer Science (Institutionen för programvaruteknik och datavetenskap)
Dept. of Software Engineering and Computer Science S-372 25 Ronneby
+46 455 38 50 00
http://www.bth.se/eng/ipd/
Language: English
Abstract: The requirements on software systems are so many that not all requirements may be included in the next development project or the next release. This means that it is necessary to select a set of requirements to implement in the forthcoming project, and hence to postpone the implementation of other requirements to a later point in time. In this selection process different criteria are used. In many cases, the criteria are not officially stated, but rather implicitly used by the decision-makers. However to be able to support this decision-making process, it is important to know and understand the underlying reasons for the decisions. This paper presents an empirical study of the decision criteria. In particular the paper focuses on how different perspectives have different influence on the decision-making process. It is concluded that business-oriented and management-oriented criteria are more important than technical concerns related to software architecture, impact analysis, dependency between requirements and software evolution.
Subject: Software Engineering\General
Edit