Reference Library Change Management
	This page provides access to a variety of downloadable papers that address change management issues. The following topics are considered: Component-Based Software Engineering (CBSE) - Related Configuration Management (CM) Checklists/Forms Content Management (CMS) General Technical Issues Component-Based Software Engineering (CBSE) - Related Configuration Management (CM) Applying Configuration Management Techniques to Component - Based Systems [PDF] Magnus Larsson This thesis applies Configuration Management (CM) principles and methods to component-based systems. This thesis presents a method to analyze dependencies between the components. To evaluate this method a prototype tool was developed which explores dependencies and stores them under version control. Component Configuration Management for Frameworks [PDF] Ivica Crnkovic, Magnus Larsson and Kung-Kiu Lau Object-oriented Design frameworks are increasingly recognized as better components than objects. This paper briefly explains the framework concept, shows a COM implementation, and discusses the accompanying configuration management issues. Next Generation Software Configuration Management System [PDF] Nathan DeBardeleben, Stacey Dorsey, Kim Hazelwood and Jonathan Perry In this paper a design is presented of a Next Generation Software Configuration Management System. The traditional features of the UNIX Make command are incorporated and expanded upon. Background information in the configuration management field is presented to show some of the many uses of configuration management today and the future. Examples of Make are given so as to be referenced throughout and used to explain how the system presented here meets the requirements of being upwardly compatible with Make. Software Architecture and Software Configuration Management [PDF] Bernhard Westfechtel and Reidar Conradi This paper examines the relations between software architecture and software configuration management. These disciplines overlap because they are both concerned with the structure of a software system being described in terms of components and relationships. On the other hand, they differ with respect to their focus (specific support for programming-in-the-large versus general support for the management of software objects throughout the whole life cycle). Several problems and alternatives concerning the integration of both worlds are discussed. Software Configuration Management: A Roadmap [PDF] Jacky Estublier This paper, in the first chapter summarizes the state of the art in SCM, showing the evolution along the last 25 years. Chapter 2 shows the current issues and current research work under way in the area. In chapter 3, the challenges SCM has to take up, as well as SCM future research are discussed. Software Configuration Management: State of the Art, State of the Practice [PDF] Karol Frühauf and Andreas Zeller Which are the open problems in Software Configuration Management (SCM)? The purpose of this paper is to ignite a discussion on current and future SCM directions. Based on the findings of a Dagstuhl Seminar on the current state of Software Engineering, the authors assess the state of SCM with the goal to identify effective SCM tasks and solutions, to establish a core body of SCM knowledge, and to denote remaining real-world SCM problems. Back to the top Checklists/Forms Configuration Management Checklist [DOC] Author Unknown For a project team /Project Manager/Configuration Manager to use when planning or reviewing the configuration management activities for a project. The checklist helps ensure that the appropriate items have been included for effective configuration management. Impact Analysis Checklist for Requirements Changes [DOC] Author Unknown This document contains checklists for implications of the proposed change and system elements affected by the proposed change. There is also a table with tasks to be done and hours of labor needed. An impact analysis report template is also given. Software Change Control Log [DOC] Author Unknown This log contains a form to log changes and also a form for detail status information. Software Change Request (SCR) Form [DOC] U.S. Department of Energy This form contains fields for basic information about the change requested. A technical evaluation and time estimates sections are also included. Software Management Program Software Configuration Management Checklist [DOC] Author Unknown This checklist is intended to provide system owners, project managers, configuration managers, and other information system development and maintenance professionals with guidance in identifying and planning software configuration management (SCM) activities. The checklist reflects recognized SCM activities to be performed throughout the information system (IS) life cycle. Back to the top Content Management (CMS) Automatic Generation of Content Management Systems from EER-Based Specifications [PDF] Sebastiano Vigna ERW is an innovative open-source system for handling complex databases using a Web browser. Once the details of an enhanced entity-relationship schema have been specified in XML, ERW generates a complete application that lets the user interact with the database. Then, specification percolation makes it possible to customize heavily the application while maintaining the flexibility of a model-driven approach. Content Management and XML [PDF] Paul G.L. Baan and Marc Y. Speyer The difference between content management systems and document management systems (which most content management systems are) lies in the appropriate use of XML related standards. The authors present how applying standard will enhance the value of your content. Future Trends of Content Management Systems (CMS) For e-Learning: A Tool Based Database Oriented Approach [PDF] JSR Subrahmanyam Ever since the inception of IT, Content Management Systems (CMS) came into existence in different forms such as system utilities, software tools, subset of authorizing systems etc. The large volume of content to be handed in the present-day context necessitates the visualization and conceptualization of new trends for immediate future development and deployment of Content Management Systems, especially for e-Learning environments. This paper provides overview of the trends for the evolution of such a unified Content Management System. Storage Strategy and Content Management [PDF] Roger Bitar This paper contains three parts. The first part defines content management. The second part describes advantages and limitations of storage architectures being used. The third part explains storage solutions from Sun Microsystems. XML Content Management based on Object - Relational Database Technology [PDF] B. Surjanto, N. Ritter and H. Loeser The authors introduce XCoP (XML Content Repository) as a repository which is based on an object-relational database management system (ORDBMS) and improves content management of XML documents thereby exploiting their structural information. It allows users to reuse and process textual portions of document contents, called fragments, thus avoiding data redundancy and, as a consequence, update anomalies on replicated data. Moreover, it enables collaborative development of documents and facilitates synchronization of fragment modification and versioning. Back to the top General Concepts in Configuration Management Systems [PDF] Susan Dart There has been considerable progress concerning support for software configuration management (CM) in environments and tools. This paper's intent is to highlight the user concepts provided by existing CM systems. There is difficulty associated with extracting concepts from CM systems since there is no commonality in terminology concerning CM functionality throughout the software engineering community and many CM systems implement variations on concepts. As a result, each concept presented is described as it exists in one particular CM system. To complete the report, the CM capabilities of the systems used as examples are briefly described. Separation of Concerns in Software Configuration Management [PDF] Mark C. Chu-Carroll Separation of concerns is one of the foundational rules of software engineering. In software configuration management (SCM) systems many important concerns remain un-separated, particularly the key concerns of program storage and program organization. This lack of separation limits the functionality that can be provided by the SCM system. The author has been building an SCM called Coven system based on separating the concerns of program storage, program organization, and inter-programmer coordination. The author believes that by separating these aspects of the SCM system, that the resulting system becomes more powerful, and enhances both the basic functionality of the system, in particular its ability to be used to handle separation of the overlapping concerns that make up the real systems developed using the SCM system. Chapter 31 Software Configuration Management [PDF] Robert Futrell, Donald Shafer and Linda Shafer This is a sample chapter from Quality Software Project Management. This chapter answers: What is software configuration management?, Why is SCM important?, Who is involved in SCM?, How Can Software Configuration Be Implemented in Your Organization?, and Where We Are in the Product Development Life Cycle? Software Configuration Management (SCM) A Practical Guide [DOC] Department of Energy Quality Managers Software Quality Assurance Subcommittee This document provides a practical guide for integrating software configuration management disciplines into the management of software engineering projects. Software configuration management is the process of identifying and defining the software configuration items in a system, controlling the release and change of these items throughout the system lifecycle, recording and reporting the status of configuration items and change requests, and verifying the completeness and correctness of configuration items. Contents include: what SCM is, SCM disciplines, tailoring SCM to different software environments, planning for SCM, and automated tools for SCM. Software Configuration Management Technologies and Applications [PDF] Software Technology Support Center The purpose of this report is to provide current information on basic Software Configuration Management (SCM) principles, methods, and technologies, and identifies their value in improving software quality. This report also provides an overview of SCM concepts, what it is and how to implement an SCM process as well as SCM standards, current trends and future directions for SCM, measurements and metrics, case studies, and lessons learned. The Past, Present, and Future of Configuration Management [PDF] Susan A. Dart This article discusses the past and present situation concerning CM systems in order to focus on the future CM challenges. The past is characterized as in-house CM solutions whereas the present is characterized by many third-party CM solutions. The future involves technological, process related, political, standardization and managerial challenges. One way of addressing these challenges is through the definition of a CM services model, which is briefly discussed. This article concludes by raising some questions about the nature of CM in relation to software engineering problems in general. Trends in Configuration Management [PDF] Carnegie Mellon University This slide presentation covers the following: the CM systems, the criteria, examination of systems, and observation of trends. Back to the top Technical Issues A Literature Review on the Quantification of Software Change [PDF] A.L. Powell This review surveys work from a number of different software research fields (including measurement, maintenance, estimation, and process improvement) that has, in some form, made a contribution to change measurement and management1. The review ends with a summary of open problems in the modeling and quantification of software change. Configuration Management Models in Commercial Environments [PDF] Peter H. Feiler A number of advances can be observed in recent commercial software development environments in support of configuration management (CM). These advances include: configurations as managed objects; transparent access to repositories; and, in addition to the familiar checkout/checkin model, three CM models based on configurations. This report analyzes the models with respect to their potential impact on the software development process, resulting in several observations. Some of the models exist in a number of variations, each impacting the software process differently. CM capabilities can be found not only in CM tools and environment frameworks, but also in development tools. Integration of such tools into environments raises the need for different CM models to interoperate. Configuration Management with Version Sets A Unified Software Versioning Model and its Applications [PDF] Andreas Zeller This book on configuration management is divided into five parts. Part one is the state of the art in SCM and contains: configuration management, components functionality, structure functionality, constriction functionality, team functionality, and future SCM requirements. Part two focuses on feature logic and contains: a SCM foundation, and feature logic. Part three is on the version set model and contains the chapters on: version and components, composting configurations, changes and revisions, constraints and repositories, cooperation techniques, and taming complexity. Part four is applications and contains: a SCM environment, representing version sets, handling version sets, a shell for version set access, the featured file system, performance studies, and efficient SCM. Part five contains a conclusion and frequently asked questions. Spectrum of Functionality in Configuration Management Systems [PDF] Susan Dart The Software Environments Project at the Software Engineering Institute has found considerable progress concerning support for software configuration management (CM) in environments and tools. This paper's intent is to highlight a spectrum of features provided by existing CM systems. The spectrum shows features as being extensions or generalizations of other features and these extensions represent the progress. As part of presenting the features, the scope of issues concerning users of CM systems is discussed. To complete the report, several configuration management systems are briefly described. Staying Afloat in a Sea of Versions or Software Configuration Management: The Vesta Approach [PDF] Roy Levin, Allan Heydon, Tim Mann and Yuan Yu This slide presentation presents software configuration management with the following topics: the software configuration management problem, Vesta's approach to a solution, key technical components of Vesta, and a summary. Towards Virtual Software Configuration Management A Case Study [PDF] Tua Rahikkala This paper presents an approach for defining software configuration management (SCM) requirements for a virtual software configuration (VSC). Contents include: basic concepts of SCM, SCM process definitions, virtual software corporations and SCM, SCM requirements analysis in VSC, towards virtual SCM process, developing SCM to meet VSC requirements, and validation. Unified Change Management from Rational Software: An Activity-Based Process for Managing Change [PDF] Rational Software Corporation This paper on change management contains the following contents: change in the software development process (market drivers, team dynamics), and unified change management which contains activities and artifacts (activity management, artifact management, UCM: five process areas, team adoption) and artifacts across the lifecycle (artifacts from analysis, artifacts from design, artifacts from testing, analysis, design, coding and testing artifacts). Version Control Integrations Conquering Revision Management with JBuilder™ 5 [PDF] Isabel Tifft This article discusses using JBuilder for version control. Topics include: why use version control, version control systems (VCS) support, differences (diffs) management, Rational® ClearCase® integration, Microsoft® Visual SourceSafe™ integration, and Concurrent Version System (CVS) integration. Back to the top