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
Processing Requirements by Software Configuration Management
Publication Type:
Conference/Workshop Paper
Venue:
euromicro 99, proceedings of the 25th EUROMICRO conference
Publisher:
IEEE, Computer society
Abstract
Short development life cycles, the importance of time-to-
market and fast changes in technology influence the
requirements engineering process. Requirements are
exposed to changes during the entire development life
cycle, and decisions related to requirements and system
design are moving toward developers. For this reason it is
important to keep requirement changes under control during
the entire development process. This control can be
achieved by utilizing Configuration Management (CM)
functions and in particular Change Management.
This paper describes a model for managing requirements
using CM functions. A requirements specification is
defined as an hierarchic structure, in which elements of the
structure are isolated requirements designated Requirements
Specification Items. Having items under version
control it is possible to get a better overview of the requirements
change process. In the implementation phase,
requirement items are associated with Change Requests
which define implementations to be introduced in the system.
When using Change Requests as links between
requirements and the implemented functions we achieve a
greater awareness of requirements and a better overview
over the requirement process. Furthermore it provides a
foundation for reuse of requirements when new systems
are built.
Bibtex
@inproceedings{Crnkovic66,
author = {Ivica Crnkovic and Peter Funk and Magnus Larsson},
title = {Processing Requirements by Software Configuration Management},
month = {September},
year = {1999},
booktitle = {euromicro 99, proceedings of the 25th EUROMICRO conference},
publisher = {IEEE, Computer society},
url = {http://www.es.mdu.se/publications/66-}
}