scientific article; zbMATH DE number 108411

From MaRDI portal
Publication:4023867





This book intends to explain the process of software configuration management within the software life cycle. It is designed for people ``bound by contractual agreements and requirements to use software configuration management and for those who may implement it as a matter of good business practice. The book is organized as follows. Some introductory chapters motivate and define configuration management and sketch its history. The main chapters define the role of configuration management (CM) in the software engineering process and deal with the main activities of CM: Identification, change control, status accounting, and configuration audits. The next two chapters deal with two activities that the author considers also to be important: interface control and subcontractor control. One chapter is devoted to CM in the support process (``software maintenance). The book concludes with chapters tackling support activities (such as library maintenance, tool selection, and training) and with a chapter on CM with Ada. The book covers the interesting higher level aspects of CM whereas more detailed or technical aspects such as version/revision management, configuration generation, release generation and management, and working with reused components are not treated. Moreover, the book has a strong bias towards system development for military and government agencies. This environment has some very specific properties with respect to CM, namely a traditional waterfall model of software development, a moderate number of fairly large configuration items, and military standards requiring special procedures and elaborate forms, especially for change control. Software in industrial and commercial projects as well as for software products on the other hand must typically deal with a large number of small configuration items (on the level of modules) and nontraditional software life cycle models where, for example, a software breakdown structure cannot be determined in advance. The book gives a good overview on CM standards and particularly on CM requirements for U.S. military and government projects. However, in my opinion the text is not suited as a general introduction to configuration management, especially for non-American readers. I found the text not very clear. Activities, procedures and illustrations are compiled from various sources. They do not consistently fit together. For people being not familiar both with CM and MIL standards the presentation is confusing. Moreover, the text suffers from the TMAU- syndrome (too many abbreviations used). Even worse, many abbreviations are nowhere explained. The glossary in Appendix One is incomplete. It does neither list all these items nor more familiar items such as CSC or CSU. The semantics of figures is often unclear and not sufficiently explained in the text. Figures 9.5 to 9.7 are worthless due to missing sources. The reproduction quality of many figures is poor. Some figures are nearly unreadable. Apparently, the author repeats a figure whenever it is referenced in the text. The captions of several figures are wrong or mixed up. References are presented as a consecutive collection of notes only. No references for further reading are provided. The typesetting quality of figures and appendices as well as the quality of proof-reading are below professional standards. When summing up, I arrive at the following conclusions. This book cannot be recommended as an introductory text to software configuration management. However, it provides useful information for people who are already familiar with the basics of CM, but must have additional knowledge of CM requirements and procedures in military or government projects.











This page was built for publication:

Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q4023867)