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

Experience with Change-oriented SCM Tools

Fulltext:


Authors:

Ivica Crnkovic

Publication Type:

Conference/Workshop Paper

Venue:

Proceedings Software Configuration Management SCM-7

Publisher:

Springer

Abstract

In the recent years two approaches in Software Configuration Management (SCM) tools have been emphasized: a Change-oriented model and a Version-model approach. This paper gives an overview of two Change-oriented SCM tools developed at ABB Industrial Sys-tems and describes the experience with their usage. The first tool is strictly change-oriented and it requires formal consistency of the entire software system. The second one is more pragmatic and less formal. It uses both Version and Change approach. The experience shows that a tool that supports a Change Management is very important in large software systems, especially in the verification and maintenance phase. Change Management is not only used as a part of a SCM tool, but in the entire development/maintenance process; in planning, producing release docu-mentation, etc. However, a usage of a strictly change-oriented tool has shown that programmers find the method too complicated and unpredictable. The second tool that controls software com-ponent versions, but also supports Change Management in the development process appears to be more effective.

Bibtex

@inproceedings{Crnkovic62,
author = {Ivica Crnkovic},
title = {Experience with Change-oriented SCM Tools},
month = {May},
year = {1997},
booktitle = {Proceedings Software Configuration Management SCM-7},
publisher = {Springer},
url = {http://www.es.mdu.se/publications/62-}
}