Conference Paper

A change process model in an SCM tool

To read the full-text of this research, you can request a copy directly from the author.


The paper is a survey of a change process model developed and used at ABB Industrial Products. The change process is based on a software configuration management (SCM) tool and the capability maturity model (CMM). CMM emphasizes the importance of controlling the changes made in a development project. The SCM tool, developed at ABB Industrial Products, is a change oriented tool, by means of which changes are managed through change requests. A change request is a document which describes changes processed in a software. During the development process, change requests collect information about the changes implemented in configuration items and they pass through different states. Since change requests are under version control, the data obtained from them give information about both the number and types of changes and the change process behavior. Experience has shown which an SCM tool that supports change management is very important in large software systems, especially in the project planning, verification and maintenance phases

No full-text available

Request Full-text Paper PDF

To read the full-text of this research,
you can request a copy directly from the author.

... It is thereby easier to move RS Items within the structure. A particular version of the requirements specification is generated from specified versions of RS items, i.e. from a specific configuration of RS items, designated a baseline [4]. ...
... To allow changes to be managed at the logical level rather than the physical level, it is essential to associate physical changes, i.e. changes performed on files, with Change Requests. SDE, a CM tool developed and used at ABB [3], uses Change Requests and, differing from other CM tools, keeps Change Requests under version control [4]. As requirements are starting points for the design and implementation of a system, it is natural to relate them to Change Requests which initiate activities in the implementation phase. ...
... A particular version of the requirements specification is generated from specified versions of RS items, i.e. from a specific configuration of RS items, designated a baseline [4]. ...
Conference Paper
Full-text available
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
... In [14] author presents change process model based on Software Configuration Management tool according to CMM [1]. Change process deals with logical changes of software, rather than with the component versions (classical version control systems). ...
Conference Paper
Full-text available
Nowadays many companies must adapt their business processes to persistent changes forced by technology, organizational or political factors. Business processes are usually supported by specialized software products. These software products also must adapt to changed business environments. Software users must have effective way to specify new requests for software they use. In this paper is presented model of modified submission phase for software change request process. This model is implemented and verified in ScenarioBuilder, a software used for management of networking scenarios in virtual network laboratory VNLab. VNLab is used for teaching networking concepts at university course.
... Most of the research related to change process has focus on activities realized in context of development environment. In [5] author presents change process model based on Software Configuration Management tool according to Capability Maturity Model (CMM) [6]. Author claims that using change management is very important in large software systems development, especially in project planning, verification and maintenance phases. ...
Conference Paper
Full-text available
Software systems change during the whole life cycle. Support for changes that origin in development process is provided by wide range of tools and techniques. Changes that appear during the software maintenance phase usually are driven by customers. These changes, specified as change requests, are usually submitted via developerspsila web site. After initial specification and submission these change requests pass the phases of standard change process that is integrated into software development process. Change requests specification should provide enough information for all phases of change request process. Support for change request specification is typically realized at developer side. In this paper is presented an approach in specifying change request in context of running application at customer side. This approach introduces modification of initial phase of standard change request process with aim to provide detailed specification of change request closely related to architecture of software.
... Erweitert man die Differenzwerkzeuge jedoch so, daß die Varianten gleichzeitig angezeigt und auch bearbeitet werden können, so könnte das eine Lösung sein, die es erlaubt,Änderungen, die für alle Varianten gelten, nur einmal durchführen zu müssen. Datenflußdiagramme, 150 Delta, 3,9,11,13,39,61,62,64,72,209 gerichtetes, 11, 12 mengenwertig, 11 operational, 11 symmetrisches, 11 Development-Support, 36 Differenz,7,9,11,13,26,68,74,75 ...
Siegen, Universiẗat, Diss., 2004. Computerdatei im Fernzugriff.
Conference Paper
For pt.I see Internat. Conf. Software Maintenance (1999). In large software organisations, a software maintenance process is seldom monolithic. Instead, it is a complex family of various processes collaborating with each other, where each process executes a clearly defined task. We describe and compare two change execution processes utilised within maintenance by two ABB organisations, namely ABB Automation Products AB and ABB Robotics AB. Thus, the paper is the report of the current state of practice in change execution at ABB. It also compares the collaborating maintenance processes used for the administration of software problems
An important problem in program development and maintenance is version control, i.e. the task of keeping a software system consisting of many versions and configurations well organized. The Revision Control System (RCS) is a software tool that assists with that task. RCS manages revisions of text documents, in particular source programs, documentation, and test data. It automates the storing, retrieval, logging and identification of revisions, and it provides selection mechanisms for composing configurations. This paper introduces basic version control concepts and discusses the practice of version control using RCS. For conserving space, RCS stores deltas, i.e. differences between successive revisions. Several delta storage methods are discussed. Usage statistics show that RCS's delta method is space and time efficient. The paper concludes with a detailed survey of version control tools.
This article provides an overview of the Capability Maturity Model® for Software (Software CMM®) and the concepts of software process maturity. (Capability Maturity Model and CMM are registered in the U.S. Patent and Trademark Office.) It contains a background discussion of why process is crucial to organizational and project success, a description of the development of the CMM, a detailed summary of the model, and a description of the model's use for process improvement and the evaluation of software suppliers; describes the use of the CMM in the context of the SEI's IDEALSM (IDEAL is a service mark of Carnegie Mellon University) approach to process improvement; summarizes some of the strengths and weaknesses of the current model and its use; characterizes the state of the practice and the return on investment for software process improvement; and concludes with a discussion of likely future directions for CMM-like models. Keywords: capability maturity model; trademark; Carnegie Mellon University; principles; total quality management; software; maturity model; uses; key process improvement; case studies
Bill Cutris et al, Capability Maturity Model for Software, Version1
  • C Mark
  • Paul
Mark C Paul, Bill Cutris et al, Capability Maturity Model for Software, Version1.1, Technical report CMU/SEI-93-TR-024, Software Engineering Institute, Carnegie Mellon University
RCS -A System for Version Control, Software and Practice Experience
  • F Walter
  • Tichy
Walter F. Tichy, RCS -A System for Version Control, Software and Practice Experience, 15(7):635-654, 1985