Skip to main content

2001 | Buch

Managing the Change: Software Configuration and Change Management

Software Best Practice 2

herausgegeben von: Michael Haug, Eric W. Olsen, Gonzalo Cuevas, Santiago Rementeria

Verlag: Springer Berlin Heidelberg

insite
SUCHEN

Über dieses Buch

C. Amting Directorate General Information Society, European Commission, Brussels th Under the 4 Framework of European Research, the European Systems and Soft­ ware Initiative (ESSI) was part of the ESPRIT Programme. This initiative funded more than 470 projects in the area of software and system process improvements. The majority of these projects were process improvement experiments carrying out and taking up new development processes, methods and technology within the software development process of a company. In addition, nodes (centres of exper­ tise), European networks (organisations managing local activities), training and dissemination actions complemented the process improvement experiments. ESSI aimed at improving the software development capabilities of European enterprises. It focused on best practice and helped European companies to develop world class skills and associated technologies to build the increasingly complex and varied systems needed to compete in the marketplace. The dissemination activities were designed to build a forum, at European level, to exchange information and knowledge gained within process improvement ex­ periments. Their major objective was to spread the message and the results of experiments to a wider audience, through a variety ofdifferent channels. The European Experience Exchange (tUR~X) project has been one ofthese dis­ semination activities within the European Systems and Software Initiative.~UR~X has collected the results of practitioner reports from numerous workshops in Europe and presents, in this series of books, the results of Best Practice achieve­ ments in European Companies over the last few years.

Inhaltsverzeichnis

Frontmatter

SPI, ESSI, EUREX

Frontmatter
1. Software Process Improvement A European View
Abstract
Enterprises in all developed sectors of the economy — not just the IT sector — are increasingly dependent on quality software-based IT systems. Such systems support management, production, and service functions in diverse organisations. Furthermore, the products and services now offered by the non-IT sectors, e.g., the automotive industry or the consumer electronics industry, increasingly contain a component of sophisticated software. For example, televisions require in excess of half a Megabyte of software code to provide the wide variety of functions we have come to expect from a domestic appliance. Similarly, the planning and execution of a cutting pattern in the garment industry is accomplished under software control, as are many safety-critical functions in the control of, e.g., aeroplanes, elevators, trains, and electricity generating plants. Today, approximately 70% of all software developed in Europe is developed in the non-IT sectors of the economy. This makes software a technological topic of considerable significance. As the information age develops, software will become even more pervasive and transparent. Consequently, the ability to produce software efficiently, effectively, and with consistently high quality will become increasingly important for all industries across Europe if they are to maintain and enhance their competitiveness.
Michael Haug, Eric W. Olsen, Gonzalo Cuevas, Santiago Rementeria
2. The EUREX Project
Abstract
The European Experience Exchange project (EUREX) was conceived, proposed, and carried out as an ESSI Dissemination Action (see Chapter 1). The overall objective of EUREX was to evaluate the experiences of several hundred ESSI Process Improvement Experiments (PIEs) and to make this experience accessible to a broad European audience in a convenient form. In particular, the goal was to collect and make available to interested practitioners information about Software Best Practice and its introduction in specific problem domains.
M. Haug, E.W. Olsen
3. The EUREX Taxonomy
Abstract
One of the most significant tasks performed during the EUREX project was the creation of the taxonomy needed to drive the Regional Workshops and, ultimately, the content of these Software Best Practice Reports. In this chapter, we examine in detail the process that led to the EUREX taxonomy and discuss how the taxonomy led to the selection of PIEs for the specific subject domain.
M. Haug, E.W. Olsen

Managing the Change: Configuration Management, Change Management

Frontmatter
4. Perspectives
Abstract
This chapter presents an overview of Configuration Management, as well as some ideas about process management and planning for configuration management. In addition, four presentations from experts are included, each of them providing a different perspective on this topic. The intent is to provide a functional, clear-cut vision of this aspect of software best practice.
G. Cuevas
4.2.1. Software Configuration Management State of the Art
Abstract
Configuration management (CM) is the discipline of controlling changes in large and complex systems. Its goal is to prevent the chaos caused by the numerous corrections, extensions, and adaptations that are applied to any large system over its lifetime. The goal of CM is to ensure a systematic and traceable development process, such that a system is in a well-defined state with accurate specifications and verified quality attributes at all times.
W. F. Tichy
4.2.2. How Do We Implement the Theory of CM in Practice
Abstract
Configuration management has the word on it to be hard to understand and unnecessary bureaucratic. If you know its goals and main principles relatively simple processes can be implemented and used. Simplicity justifies the subject and makes it understandable.
U. Nyman
4.2.3. Impact of Configuration Management
Abstract
“Software Configuration Management is the backbone of the software development process, and when implemented correctly, helps ensure software quality and process improvement” [STSC94].
B. Kölmel, J. Eisenbiegler
4.2.4. The Role of Control Boards in Configuration Management
Abstract
The construction, implementation and exploitation of any data processing system normally present a series of problems generally associated with co-ordination and control that will affect not only the development phase, but also the exploitation and maintenance phases. These can be classified as:
  • Designation and identification of component elements
  • Change control of such elements
  • Library management
  • Different products versions management utilised for and in the development, either own or third parties
  • Systems construction to be delivered
  • Support tools
  • etc.
J. A. Calvo-Manzano, M. García, T. San Feliu, A. de Amescua
5. Resources for Practitioners
Abstract
Selecting a particular method or tool to solve the problems associated with the configuration management aspects of software development and maintenance can be a very complex problem in an of itself. The final decision to choose a particular tool is going to depend on the budget available as well as the tool’s capabilities. To assist with these problems, several different methods and tools are presented in the following sections. In the case of tools, we distinguish between commercial tools and public domain tools.
G. Cuevas
6. Experience Reports
Abstract
This chapter presents the experiences of eight companies that either implemented configuration and change management from scratch or improved their existing practices in these areas. Seven of them did so in the context of the European Systems and Software Initiative (ESSI) funded by the European Commission in the Calls of 1993, 1995 and 1996, whereas the remaining one corresponds to an internal, privately funded process improvement project. The list is not exhaustive, but it represents a sampling of similar actions taking place in software development organisations worldwide. It is hoped that this sample offers a glimpse of real configuration management implementation experiences and the associated potential benefits, as well as the risks and practical aspects to consider during the adoption process.
S. Rementeria
7. Lessons from the EUREX Workshops
Abstract
In this chapter we present results from the EUREX Workshops of Bilbao (Spain), Milan (Italy) and Karlsruhe (Germany), each of which addressed the subjects of Configuration and Change Management and Requirements Engineering. Following the workshop descriptions is a summary of the opinions, results, and conclusions derived by the authors from the complete workshop experience.
S. Rementeria
8. Significant Results
Abstract
Most of the participants in ESSI projects dealt with configuration management purely in a practical manner, working with tools and procedures from various commercial vendors to solve their immediate problems. However, we believe that standards are an appropriate way to organise and define configuration management processes generally. To that end, it can be said that Software Configuration Management is a control discipline within the software project. Configuration Management should be used throughout a product’s life cycle, in development as well as during the maintenance process until the product is withdrawn. Three objectives should be considered in Software Configuration Management:
  • Establish and maintain the integrity of a software product during its life cycle.
  • Control the evolution of a software product.
  • Facilitate the visibility of a product.
G. Cuevas, S. Rementeria

Process Improvement Experiments

Frontmatter
9. Table of PIEs
Abstract
Table 9.1 below lists each of the PIEs considered as part of the EUREX taxonomy within the problem domain of Configuration and Change Management.
Michael Haug, Eric W. Olsen, Gonzalo Cuevas, Santiago Rementeria
10. Summaries of PIE Reports
Abstract
ESSI in Context of Rail Station Information Display System Software
The main interest, in ESSI action, for SAIT Devlonics is to introduce practically the concepts available in the quality manual. SAIT Devlonics wants to have a Quality System which automates certain procedures/methods. They are:
  • to automate as much as possible the Software life cycle development;
  • to execute a Configuration Management on the PC environment;
  • to create a library of software components (reusability) and to incorporate its in the Configuration Management.
Michael Haug, Eric W. Olsen, Gonzalo Cuevas, Santiago Rementeria
Backmatter
Metadaten
Titel
Managing the Change: Software Configuration and Change Management
herausgegeben von
Michael Haug
Eric W. Olsen
Gonzalo Cuevas
Santiago Rementeria
Copyright-Jahr
2001
Verlag
Springer Berlin Heidelberg
Electronic ISBN
978-3-642-56614-1
Print ISBN
978-3-540-41785-9
DOI
https://doi.org/10.1007/978-3-642-56614-1