Configuration Management System Research Articles

Qualitative Assessments of the Software Architectures of Configuration Management Systems

The Configuration Management (CM) is a very important area of concentration in software development and maintenance processes. Quality parameters for Configuration Management Tools' architectural designs require rigorous identification and measurement. Two methods for quantitative assessment of quality parameters of the software architectures are proposed. These methods are based upon modularization properties, like, cohesion type, coupling type, module complexity, module size and others. Looking at the problems with the studied tools, like, low flexibility, interoperability, etc., and recent requirements for the CM tools, a new architectural model has been proposed[1]. All the three models are assessed on quality parameters applying both the methods with an objective to validate the superiority of the proposed model.

JBOOM: Java Based Object Oriented Model of Software Configuration Management

Most of the present Software Configuration Management systems deal with version and configurations in the form of files and directories, the need today is to have a Software Configuration Management system that handles versions and configurations directly in terms of functions (program module). A major objective of this research is the use of Java in the Software Configuration Management systems. An object-oriented language provides both design and implementation in an integrated manner. We have proposed a model that expresses change evolution in terms of class hierarchies. As the changes evolve so does the class hierarchy, it can be further extended and existing classes can be extended.

Facilitating software evolution research with kenyon

Software evolution research inherently has several resource-intensive logistical constraints. Archived project artifacts, such as those found in source code repositories and bug tracking systems, are the principal source of input data. Analysis-specific facts, such as commit metadata or the location of design patterns within the code, must be extracted for each change or configuration of interest. The results of this resource-intensive "fact extraction" phase must be stored efficiently, for later use by more experimental types of research tasks, such as algorithm or model refinement. In order to perform any type of software evolution research, each of these logistical issues must be addressed and an implementation to manage it created. In this paper, we introduce Kenyon, a system designed to facilitate software evolution research by providing a common set of solutions to these common logistical problems. We have used Kenyon for processing source code data from 12 systems of varying sizes and domains, archived in 3 different types of software configuration management systems. We present our experiences using Kenyon with these systems, and also describe Kenyon's usage by students in a graduate seminar class.

Software reuse in product populations

Consumer products are becoming increasingly software intensive. The software complexity of individual products grows, while the diversity of products increases and the lead time must decrease. Software reuse is the answer to this, not only within a family but also between families of consumer products. We have devised an approach based upon a software component technology to enable reuse. This paper describes that approach, and it zooms in on two important aspects of component-based development. One aspect concerns the prediction of system properties from properties of components, which we illustrate using thread synchronization as example. The other aspect concerns branching of our software in our configuration management systems, where our analysis leads to the discovery that we may be constantly rewriting our own code and to the definition of the turn-over factor to quantify this. We end this paper with a brief validation of our approach.

영상처리 알고리즘 개발을 위한 소프트웨어형상관리시스템

The importance of software is getting high in development of the digital device (digital camcoder, digital camera, mp3 player, ....). And because the sire of software becomes larger and complicated, the necessity of software configuration management (to solves a software crisis) is increased. The general software configuration management system shows lack of the property and features of software development environment for image processing algorithm due to its wide range to be covered. Image processing algorithm development environment has properties like repetitive analysis and simulation using visual programming environment where, beside support of elementary development functions. component(or library) can be combined and tested interactively. Moreover, the method to look fast and effectively for component having similar function is required. In this paper, we present the system which supports the software configuration management method for a simulation tool and the property in the visual programming environment. And we relate our system to real simulation tool so as to check its ability as the software configuration management system for image processing algorithm development environment.

Configurable product views based on geometry user requirements

This paper describes an approach at Volvo Truck Corporation where geometry users' requirements are utilised to define configurable product views. The paper is derived from a research framework on geometry management. The objective of the research framework is to improve reuse of geometry by providing relevant geometry-based product information, so-called geometric product views, through application of configuration management. In order to provide relevant product views, specific fundamental product information must exist. This type of information will vary depending on the different types of product views. Several examples on product view are presented. The product views are realised by a developed configuration management system, an example of a configured product view is presented as proof of concept. The configuration management system is currently under industrial implementation.

Reengineering of educational material: a systematic approach

In electronic learning, keeping learning material up-to-date is a recurring problem. In the past, this has mostly been done manually, with a frequent consequence that material becomes outdated since manual updates are neither systematic nor applied often enough. In this paper, we take a software engineering perspective on the problem of updating learning material for electronic platforms, and show how reengineering can help in this context. Specifically, we present a reference model for an e-learning reengineering process, and cast this model into the architecture of a component and configuration management system. Finally, we indicate how the approach can be exploited by showing an example, and outlining a global reuse strategy for educational material using software product lines.

SubCM: a tool for improved visibility of software change in an industrial setting

Software configuration management is the discipline of managing large collections of software development artefacts from which software products are built. Software configuration management tools typically deal with artefacts at fine levels of granularity - such as individual source code files - and assist with coordination of changes to such artefacts. This paper describes a lightweight tool, designed to be used on top of a traditional file-based configuration management system. The add-on tool support enables users to flexibly define new hierarchical views of product structure, independent of the underlying artefact-repository structure. The tool extracts configuration and change data with respect to the user-defined hierarchy, leading to improved visibility of how individual subsystems have changed. The approach yields a range of new capabilities for build managers, and verification and validation teams. The paper includes a description of our experience using the tool in an organization that builds large embedded software systems.

Inventorying Information Technology Systems: Supporting the "Paradigm of Change"

One of the most significant failures of the IT profession is the absence of systems to gather, support, and supply information for managing software items. Most IT professionals, if they consider software management, think in terms of version or configuration control license and patch management. Version control systems (VCSs) and software configuration management (SCM) systems aim to manage versions of individual software objects with support for linking into sets for release purposes. This has nothing to do with addressing the issues of controlling large amounts of geographically disbursed software, executing on different kinds of systems, maintained by hundreds to thousands of programmers. Software systems are the only major organizational asset with no real support for managing them based on information technology. An appropriate IT inventory management facility is the cornerstone of an integrated set of technologies, called the "paradigm of change" designed to address constantly changing technologies and business processes.

XML-based configuration management for IP network devices

As the Internet continues to grow, the tasks of operations and management of IP networks and systems are becoming more difficult. Over the past few years, much effort has been given to improve the deficiencies of SNMP, but most have failed to be standardized. One critical deficiency of SNMP is in the area of configuration management. Recent work focuses on the use of XML technology for network and service management as an alternative or complementary approach to SNMP. This article presents the IETF's latest effort, Netconf, which is viewed by many as a promising revolutionary solution for configuration management. To validate this new effort, we present the design and implementation of an XML-based configuration management system based on Netconf. We also discuss our experience with XCMS and make some suggestions for improving the current Netconf protocol.

Project Management Approaches at Techlogix

This case examines the different project management approaches at Techlogix. Some are highly structured and formal while others are relatively unstructured and informal. The Engyro project involved the development of an Applications Service Provider (ASP) Payments System through a highly structured formal project management system, which created few problems in terms of product specification changes and development. However, a Financial Management System (FMS) developed for the Government of Guam through a relatively unstructured and informal project management approach proved to be a bad experience for Techlogix. The CEO wanted to standardize a highly structured project management system for the company. The project managers at Techlogix feared that a highly structured system would reduce flexibility available to project managers. They felt that a structured configuration and change management system would require a lengthy process to bring about changes in a project's specifications. This would eventually discourage change and create customer dissatisfaction or force the project managers to circumvent standardized procedures creating other problems. This case is useful for examining the factors relevant to project management approaches.

Mae---a system model and environment for managing architectural evolution

As with any other artifact produced as part of the software life cycle, software architectures evolve and this evolution must be managed. One approach to doing so would be to apply any of a host of existing configuration management systems, which have long been used successfully at the level of source code. Unfortunately, such an approach leads to many problems that prevent effective management of architectural evolution. To overcome these problems, we have developed an alternative approach centered on the use of an integrated architectural and configuration management system model. Because the system model combines architectural and configuration management concepts in a single representation, it has the distinct benefit that all architectural changes can be precisely captured and clearly related to each other---both at the fine-grained level of individual architectural elements and at the coarse-grained level of architectural configurations. To support the use of the system model, we have developed Mae, an architectural evolution environment through which users can specify architectures in a traditional manner, manage the evolution of the architectures using a check-out/check-in mechanism that tracks all changes, select a specific architectural configuration, and analyze the consistency of a selected configuration. We demonstrate the benefits of our approach by showing how the system model and its accompanying environment were used in the context of several representative projects.

Configurable Product Views Based on Geometry User Requirements

AbstractThis paper describes an approach at Volvo Truck Corporation where geometry users’ requirements are utilised to define configurable product views. The paper is derived from a research framework on geometry management. The objective of the research framework is to improve reuse of geometry by providing relevant geometry-based product information, so-called geometric product views, through application of configuration management. In order to provide relevant product views, specific fundamental product information must exist. This type of information will vary depending on the different types of product views. Several examples on product view are presented. The product views are realised by a developed configuration management system, an example of a configured product view is presented as proof of concept. The configuration management system is currently under industrial implementation.

CCMS: A geographically distributed concurrent change and configuration management system

In recent years, large-scale software development has involved collaboration among teams of people whose members are dispersed around the globe. Software change and configuration management (SCCM) is an essential discipline that affects all steps of the software development process, from the definition of requirements and prototyping to the final packaging and delivery of a product to a customer. Particularly in a geographically distributed environment, a good SCCM process makes it possible to produce higher-quality software and to reduce time-to-market. The concurrent change management system (CCMS) provides an out-of-the-box, customizable SCCM process framework that allows teams of project managers, architects, developers, testers, and integrators to manage product defects that have been reported, features and enhancements that have been requested, and versions of product artifacts and third-party components that provide solutions for such defects and features over multiple releases in a geographically distributed environment. The CCMS, which uses Java <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">∗</sup> /Java Database Connectivity (JDBC <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">∗</sup> ) and the database replication technologies of Oracle and Rational's ClearCase <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">∗</sup> /MultiSite, <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">∗</sup> was developed by Lucent Technologies over the past 7 years. In this paper we describe the high-level architecture and the process framework of the CCMS. The process framework will also be described with examples of the use of CCMS. © 2003 Lucent Technologies Inc.

Performance test and analysis for an adaptive load balancing mechanism on distributed server cluster systems

As the next generation of Internet services requires more highly scalable and available server systems, the cost-effective cluster of a large number of distributed computers becomes a popular solution. In this paper, we investigate to design and develop a server load balancing mechanism on cluster architecture, called the ALBM cluster. In order to construct the more scalable and reliable Internet service system, the ALBM cluster system consists of independent but co-operable components. The ALBM cluster system supports adaptive load balancing among servers via its adaptive load balancer (ALB) component in Layer 4 level and Layer 7 level. The Management Station (M-Station) and the Administrator Console are in charge of cluster management, system configuration management, and performance counter management. The Node Service is a system-level agent that is deployed into a server node. The node management and cluster management are the major tasks of the agent. Beside, the ALBM cluster is a flexible open system whose features of functionality can change or be easily expanded without affecting the rest of the system. In this paper, we also present a set of our experimental results to compare the performance of the ALBM cluster with that of LVS scheduling cluster system. We compare performance results of the ALBM with RR, LC, and WLC scheduling algorithms of a LVS cluster in both of homogeneous and heterogeneous system environments.

Recomposition: Coordinating a Web of Software Dependencies

In this paper, I revisit theconcept of recomposition – all the work thatdevelopment organizations do to make sure thattheir product fits together and into a broaderenvironment of other technologies. Technologies, such as Configuration Management(CM) systems, can ameliorate some of a softwaredevelopment team's need to engage inrecomposition. However, technologicalsolutions do not scale to address other kindsof recomposition needs. This paper focuses onvarious organizational responses to the needfor recomposition. By organizational response,I mean how individuals engage in recompositionso that the organization can assemble softwaresystems from parts. Specifically, I describehow those responses are manifested in theday-to-day communications and responsibilitiesof individuals throughout the organization. Ialso highlight how changes in an organizationcomplicate recomposition. The paper concludeswith a discussion of three features of softwaredevelopment work that are revealed byrecomposition: the affects of environmentaldisturbances on development work, the types ofdependencies that require recomposition, andthe images of organizations required to managethe recomposition.

California Statewide Intelligent Transportation Systems Plan Evaluation: Case Study of Conformity with National Intelligent Transportation Systems Architecture

A statewide evaluation was conducted of Intelligent Transportation Systems (ITS) Strategic Deployment Plans in California. It found that all 12 plans covering the state will conform by April 8, 2005, with Federal Highway Administration and Federal Transit Administration ITS Architecture and Standards: Final Rule. Developing the plans greatly raised the knowledge and awareness of the potential benefits of integrated technology systems. Multiple layers of architecture have been identified, particularly in Southern California, where developments are most advanced. Experience with deployment of an interregional system of data exchange, Showcase, indicates that such systems require far more time and resources than could have been anticipated at the outset. Technology obsolescence and software documentation have become key issues that other regions will face as projects move from plans to major deployments. Funding the operation and maintenance of these systems is emerging as a major barrier to their successful implementation. So too is the need to educate senior management and elected officials about the infrastructure requirements of successful system integration. Funding the operations and maintenance and configuration management of systems will undoubtedly be the issue for focus in the next decade, as transportation professionals begin to fully understand the implications of the concept of regionally integrated ITS.

Network Control in ATM-Based LEO Satellite Networks

Low Earth Orbiting (LEO) satellite networks with on-board asynchronous transfer mode (ATM) switches hold the promise of offering an economically viable extension of terrestrial ATM systems by providing connectivity to areas where existing terrestrial networks are either infeasible or impractical. Network management in ATM LEO satellite networks is typically performed by the Network Control Center (NCC). The main contribution of this paper is to propose a network management system configuration with a stand-by solution and to describe an experimental Satellite Management Information Base (SMIB) that we have developed for implementation in ATM LEO satellite networks.

Software configuration management for the 21st century

The increasing complexity of both software systems and the environments in which they are produced is pressuring projects to improve the development process using innovative methods. The role of software configuration management (SCM) systems, policies, and procedures that help control and manage software development environments is being stretched beyond the conceptual boundaries it has had for the last decade. One of the key enablers of producing higher quality software is a better software development process. The SCM system must instantiate a quality process, allow tracking and monitoring of process metrics, and provide mechanisms for tailoring and continual improvement of the software development process. More than a dozen SCM systems are now available, each one having a distinct architecture and set of core functionalities. Currently, no single system provides all the key SCM functions in the best form. Thus, a project must assess its real needs and choose the right SCM system to meet its software development challenges. This paper focuses on the characteristics of SCM systems, the SCM challenges for Lucent Technologies, the principal SCM systems being used within the company, and the issues of choosing and successfully implementing the best SCM systems.

Testing and maintaining de‐localized software systems in a multi‐site environment using Web‐based tools

AbstractWeb‐based approaches used during software maintenance for testing de‐localized software in a multi‐site environment are described. The supporting infrastructure uses the Internet for communications and project management practices for procedural direction. Processes involve specifying personnel roles and using a configuration management system for test schedules and the handling of test results. Different testing strategies are used during various stages of the maintenance lifecycle; each has benefits and weaknesses. Test results are automated using scripts, and a Web interface is provided to obtain better tracking. This achieves a $24\times7$ operational effectiveness by using automation and regression testing mechanisms, and results in documented cost savings and software quality improvements. Copyright © 2002 John Wiley &amp; Sons, Ltd.