The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
This paper describes the experiences gained in the CMEX project, an ESSI Process Improvement Experiment on revising the change control system in one department of Sysdeco GIS AS, a Norwegian software house. The aim of the project was to install ClearCase, a configuration management system, and to measure and evaluate the impact of the new system on processes and products. This paper describes the...
This paper describes a systematic approach for collecting and analysing software configuration management (SCM) requirements. The analysis is based on Pr2imer, Practical Process Improvement for Embedded Real-Time Software, which is a framework for process improvement. Pr2imer applies interviews for qualitative analysis and assessment, such as BOOTSTRAP, for quantitative analysis. It also includes...
An SCM database contains data which can be used as input for Software Metrics. Both data for Size-Oriented Metrics, and information for Process-Oriented Metrics are available from SCM systems. This paper describes measurements taken from an SCM database used at ABB Industrial Systems. The SCM tool is change-oriented and collects information about changes in Change Request (CR) documents. As CRs are...
PRCS is an attempt to provide a version-control system for collections of files with a simple operational model, a clean user interface, and high performance. PRCS is characterized by the use of project description files to input most commands, instead of a point-and-click or a line-oriented interface. It employs optimistic concurrency control and encourages operations on the entire project rather...
This paper describes Historian, a version control system that supports comprehensive versioning and features to aid history navigation. Comprehensive versioning is supported through frequent and automated creation of versions which typically results in a large number of versions. To reduce user overhead in history navigation, the hierarchical structure present in most documents is utilized to support...
When deploying new SCM (software configuration management) tools, implementers sometimes focus on perfecting fine-grained activities, while unwittingly carrying forward poor, large-scale practices from their previous jobs or previous tools. The result is a well-executed blunder. This paper promotes some high-level best practices that reflect the authors' experiences in deploying SCM.
This paper describes a model, denoted architectural software configuration management, that minimises the gap between software design and configuration management by allowing developers to do configuration- and version control of the abstractions and hierarchy in a software architecture. The model emphasises traceability and reproducibility by unifying the concepts version and bound configuration...
Software Configuration Management (SCM) is the discipline of controlling the evolution of a software product. Product Data Management (PDM) is the disciple of designing and controlling the evolution of a product design. For a long time, these two domains have been disconnected, but they probably share common concepts and techniques. Furthermore, any large product development includes a substantial...
Engineering data management and software configuration management have been evolving fairly independently. On the other hand, it has been observed earlier that many parallels exist [10]. In this paper, we examine the similarities of and differences between EDM and SCM. Many concepts are similar, but there are some differences concerning the objects to be managed. As a consequence, some sophisticated...
This paper presents a technique for product configuration modelling based on object-orientation and attribute grammars. The technique allows efficient interactive configurator tools to be generated for specified product families. Additional benefits include a high degree of checkability, early validation, readability, and reusability. The technique is particularly aimed at mass-customization products...
In software configuration management, little attention has been paid to the evolution of system models, that is, the description of the components that make up a system, and the relationships between them. We present an extension to the version set model based on description logic, where roles, set-valued features, model relationships between version sets. Relationships are versioned with their components;...
This paper describes the facilities currently available to support auditing and traceability within a system which provides fine-grained configuration and version management. We contend that the relationship between the configuration management system and the underlying version control system is a critical factor which governs many aspects of the facilities supporting traceability. The model of traceability...
Over the past few years, research into system modeling has dwindled in favor of other interests in the field of configuration management. Outside influence, in the form of the emergence of the discipline of software architecture, demands that renewed attention is paid to system modeling because it places new requirements on, and offers new opportunities to, system modeling. In this paper we investigate...
Software Version Control Systems (VCSs) are used to store the versions of program source code created throughout the software development cycle. The traditional purpose of such systems has been mostly administrative, providing the safe storage of source code and the ability to recreate earlier versions, as well as tracking the progress of new feature development and problem resolution. Software developers...
As part of an investigation of scalable development techniques for systems written in the Javaℳ programming language, the Forest Project is building JP, a prototype distributed programming environment. For extensibility and usability, a mechanism is required to coordinate the activity of multiple editor programs (each specializing in particular source types) with the JP versioning system. The JP architecture...
In this paper, we report on our experiences from developing and using a tool to provide optimal version control support during co-operative development of hierarchical documents. The main problem in co-operative work is to maintain an overview of how the document is evolving, and at the same time to maintain a complete version history. We extend traditional version control in the sense that we provide...
Versioning of hypertext documents is in many aspects very similar to versioning of software systems (and their components). In the paper we concentrate on an analysis of similarities and differences between them with the intention of possibly finding in the area of software configuration management a starting point for a new method of version control in hypertext systems. Then, we have proposed a...
Software distribution via networks provides timeliness and continual evolution that is not possible with physical media distribution methods. Organizations such as Microsoft, Marimba, and the Desktop Management Task Force are strengthening their efforts to package software systems in ways that are conducive to network distribution. The result of these efforts has led to the creation of software description...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.