Conference
Software Configuration Management Workshop
About: Software Configuration Management Workshop is an academic conference. The conference publishes majorly in the area(s): Software development & Software configuration management. Over the lifetime, 120 publications have been published by the conference receiving 2225 citations.
Topics: Software development, Software configuration management, Software system, Configuration Management (ITSM), Software construction
Papers
1 May 1991
TL;DR: The intent of this paper’s intent is to highlight the user concepts provided by existing CM sysgiven in texts such as [3] and [4].
Abstract: There has been considerable progress con1.1 Definition of Configuration Management cerning support for software configuration management Software CM is a discipline for controlling the evolution (CM) in environments and tools. This paper’s intent is to of software systems. Classic discussions about CM are highlight the user concepts provided by existing CM sysgiven in texts such as [3] and [4]. A standard definition tems. These are shown as a spectrum. In the spectrum, taken from IEEE standard 729-1983 [16] highlights the folconcepts are seen as extensions to, or generalizations of, lowing operational aspects of CM: other concepts. There is difficulty associated with extract• Identification: an identification scheme ing concepts from CM systems since there is no commonreflects the structure of the product, identifies ality in terminology concerning CM functionality throughcomponents and their type, making them out the software engineering community and many CM unique and accessible in some form. systems implement variations on concepts. As a result, each • Control: controlling the release of a product concept presented is described as it exists in one particular and changes to it throughout the lifecycle by CM system. A part of highlighting the concepts involves having controls in place that ensure consistent software via the creation of a baseline product. discussing the scope of issues important to users of CM systems. No single CM system provides all the function• Status Accounting: recording and reporting the status of components and change requests, ality required by the different kinds of users of CM sysand gathering vital statistics about components tems. Rather, each CM system addresses some part of the in the product. spectrum of concepts. To complete the report, the CM ca• Audit and review: validating the completepabilities of the systems used as examples are briefly deness of a product and maintaining consistency scribed. among the components by ensuring that the product is a well-defined collection of components.
199 citations
1 May 1991
TL;DR: A structure-oriented merge tool that is applicable to software documents written in arbitrary languages, preserves their context-free correctness, and also takes binding of identifiers to their declarations into account is presented.
Abstract: Merging revisions of software documents after development has branched into multiple lines is a difficult task. Previous approaches to merging are either based on text files or refer to specific languages. These approaches do not meet the requirements to a merge tool which is to be integrated into a multilingual structure-oriented environment. In this paper, we present a structure-oriented merge tool that is applicable to software documents (requirements definitions, software architecture descriptions, module implementations, etc.) written in arbitrary languages, preserves their context-free correctness, and also takes binding of identifiers to their declarations into account.
126 citations
1 Oct 1989
TL;DR: The change oriented model of versioning is presented, which focuses strongly on functional changes in a software product and therefore can be seen as an alternative to the traditional, “version oriented” models.
Abstract: We present the change oriented model of versioning, which focuses strongly on functional changes in a software product and therefore can be seen as an alternative to the traditional, “version oriented” models. The change oriented model is used as a basis for the versioning in the EPOS software engineering database, which features an integrated transaction and versioning mechanism.
79 citations
25 Mar 1996
TL;DR: Results indicate that modern delta compression algorithms based on Ziv-Lempel techniques significantly outperform diff, a popular but older delta compressor, in terms of compression ratio.
Abstract: Delta algorithms compress data by encoding one file in terms of another. This type of compression is useful in a number of situations: storing multiple versions of data, distributing updates, storing backups, transmitting video sequences, and others. This paper studies the performance parameters of several delta algorithms, using a benchmark of over 1300 pairs of files taken from two successive releases of GNU software. Results indicate that modern delta compression algorithms based on Ziv-Lempel techniques significantly outperform diff, a popular but older delta compressor, in terms of compression ratio. The modern compressors also correlate better with the actual difference between files; one of them is even faster than diff in both compression and decompression speed.
71 citations
5 Sep 2005
TL;DR: This work introduces a flexible version control system for UML model elements, named Odyssey-VCS, which allows the configuration of both the unit of versioning and unit of comparison for each specific project, respecting the different needs of the diverse development scenarios.
Abstract: Many current version control systems use a simple data model that is barely sufficient to manipulate source-code. This simple data model is not sufficient to provide versioning capabilities for software modeling environments, which are strongly focused on analysis and architectural design artifacts. In this work, we introduce a flexible version control system for UML model elements. This version control system, named Odyssey-VCS, deals with the complex data model used by UML-based CASE tools. Moreover, it allows the configuration of both the unit of versioning and unit of comparison for each specific project, respecting the different needs of the diverse development scenarios.
71 citations
Performance Metrics
| Year | Papers |
|---|---|
| 2005 | 10 |
| 2000 | 1 |
| 1998 | 19 |
| 1997 | 16 |
| 1996 | 22 |
| 1991 | 22 |