Requirements management for continuous software product development
(2010) 14th International Conference on Evaluation and Assessment in Software Engineering (EASE), (2010)- Abstract
- Continuous software product development is increasingly becoming the norm. New requirements come in a constant stream and need to be assigned to projects to make it into a release. However, in the literature requirements management practices are project based and no longer naturally fit to this new setting.
Aim: Thus, it is of interest to understand the industrial practices for the identification of requirements and associated artifacts put under configuration control.
Method: An industrial survey with five companies was conducted to find out these industrial practices.
Results: The results of this survey show that with the need to manage more requirements also comes the need for... (More) - Continuous software product development is increasingly becoming the norm. New requirements come in a constant stream and need to be assigned to projects to make it into a release. However, in the literature requirements management practices are project based and no longer naturally fit to this new setting.
Aim: Thus, it is of interest to understand the industrial practices for the identification of requirements and associated artifacts put under configuration control.
Method: An industrial survey with five companies was conducted to find out these industrial practices.
Results: The results of this survey show that with the need to manage more requirements also comes the need for greater control. Large companies, however, often place similar control on products of all size. Moreover, regardless of size and requirements management practices, companies face the same problems.
Conclusions: All companies should keep requirements associated material under some form of control and updates to them should be communicated to the involved stakeholders and should be easy to access. The type of associated artifacts kept under control can be decided by the criteria given. (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/1748032
- author
- Khurum, Mahvish ; Barney, Sebastian LU ; Fogelström, Nina D. and Gorschek, Tony
- organization
- publishing date
- 2010
- type
- Contribution to conference
- publication status
- published
- subject
- conference name
- 14th International Conference on Evaluation and Assessment in Software Engineering (EASE), (2010)
- conference location
- Keele University, United Kingdom
- conference dates
- 2010-04-12 - 2010-04-13
- project
- Embedded Applications Software Engineering
- language
- English
- LU publication?
- yes
- id
- 2b1d36a0-d781-4475-9c27-6cac654998a3 (old id 1748032)
- alternative location
- http://www.bcs.org/server.php?show=conWebDoc.34779
- date added to LUP
- 2016-04-04 14:38:20
- date last changed
- 2018-11-21 21:21:27
@misc{2b1d36a0-d781-4475-9c27-6cac654998a3,
abstract = {{Continuous software product development is increasingly becoming the norm. New requirements come in a constant stream and need to be assigned to projects to make it into a release. However, in the literature requirements management practices are project based and no longer naturally fit to this new setting.<br/><br>
<br/><br>
Aim: Thus, it is of interest to understand the industrial practices for the identification of requirements and associated artifacts put under configuration control.<br/><br>
<br/><br>
Method: An industrial survey with five companies was conducted to find out these industrial practices.<br/><br>
<br/><br>
Results: The results of this survey show that with the need to manage more requirements also comes the need for greater control. Large companies, however, often place similar control on products of all size. Moreover, regardless of size and requirements management practices, companies face the same problems.<br/><br>
<br/><br>
Conclusions: All companies should keep requirements associated material under some form of control and updates to them should be communicated to the involved stakeholders and should be easy to access. The type of associated artifacts kept under control can be decided by the criteria given.}},
author = {{Khurum, Mahvish and Barney, Sebastian and Fogelström, Nina D. and Gorschek, Tony}},
language = {{eng}},
title = {{Requirements management for continuous software product development}},
url = {{http://www.bcs.org/server.php?show=conWebDoc.34779}},
year = {{2010}},
}