Version models for software configuration management

Conradi, Reidar; Westfechtel, Bernhard

doi:10.1145/280277.280280

Cited by 436 publications

(286 citation statements)

References 92 publications

Supporting

Mentioning

253

Contrasting

Unclassified

Order By: Relevance

“…This is consistent with the user interface of both tools, which allow users to operate on revisions but not deltas, and agrees with Conradi and Westfechtel's characterization of these systems as statebased [3]. That revision histories and revisions are stored in files, and revisions are stored as deltas, can be viewed as concrete representation issues.…”

Section: Rcssupporting

confidence: 85%

“…Using the taxonomy of systems provided in [3], CoMa is a version graph system, while PIE is a change-based versioning system. Since these are two different styles of system, we would expect these differences to be visible in a comparison of their containment models, and this is indeed the case.…”

Section: Comparing Different Types Of Configuration Management Systemmentioning

confidence: 99%

“…The past 27 years of research and commercial development have witnessed the creation of scores of configuration management systems, with Conradi and Westfechtel's survey listing 21 systems [3], and the CM Yellow Pages listing an additional 43 in the commercial sector [2]. Despite the existence of solid comprehensive survey work on configuration management systems [3], it is still the case today that developing a detailed understanding of the data model of a particular system requires labor-intensive study of the papers and documentation describing it.…”

Section: Introductionmentioning

confidence: 99%

“…Despite the existence of solid comprehensive survey work on configuration management systems [3], it is still the case today that developing a detailed understanding of the data model of a particular system requires labor-intensive study of the papers and documentation describing it. Worse, once developed, there is no modeling mechanism that allows this understanding to be represented in a way that both aids communication about the model, and permits cross-comparison with other system models.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Uniform Comparison of Configuration Management Data Models

Whitehead

Gordon

2003

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. The data models of a series of 11 configuration management systems-of varying type and complexity-are represented using containment data models. Containment data models are a specialized form of entityrelationship model in which entities may be containers or atoms, and the only permitted form of relationship is inclusion or referential containment. By using entities to represent the native abstractions of each system, and containment relationships to model inclusion and identifier references, systems can be modeled uniformly, permitting consistent cross-comparison of systems.

show abstract

Section: Rcssupporting

confidence: 85%

Section: Comparing Different Types Of Configuration Management Systemmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Uniform Comparison of Configuration Management Data Models

Whitehead

Gordon

2003

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Composition of software is provided by a list of components and based-rule selection mechanisms search the most appropriate version of each of them in a component repository [6]. Most of the time, no data model is provided (see for example, the industrial tool ClearCase [17]).…”

Section: Related Workmentioning

confidence: 99%

Software Product-Family Engineering

Bosch¹,

Florijn²,

Greefhorst³

et al. 2002

Lecture Notes in Computer Science

View full text Add to dashboard Cite

RésuméNous présentons, dans ce papier, un support d'aide à la conception collaborative de produits appartenant à une famille de produits. Le produit est modélisé par un arbre de composants et les contraintes de développement, utilisées pour guider le processus de conception, sont exprimées à l'aide d'un langage spécifique basé sur des expressions logiques. L'objectif principal de ProjectLeader est d'économiser le temps de conception en favorisant le travail simultané et en prévenant les retours en arrière. Ainsi, pour chaque intention de décision émise par un concepteur, ProjectLeader vérifie que la décision ne remettra pas en cause la possibilité d'atteindre un état correct du produit final, c'est-à-dire un état dans lequel toutes les contraintes sont vérifiées. Mots-clefs : conception collaborative, système à base de composants, modélisation et traitement de contraintes de conception, modélisation et traitement de la variabilité AbstractIn this paper we present a support that helps organizing distributed design of products belonging to a product family. We model the product to be developed as a component-based tree of object templates, develop a logic-based language that allows expressing diverse development constraints and use these constraints to guide the design process. The main objective of our support is to save time and development effort in increasing parallel work and avoiding roll-backs. For that, it reasons in terms of correctness of the future, final state of the product, and verifies that the product state after each operation allows the reacheability of such a state.

show abstract

Object versioning in an ODMG‐compliant object database system

Lee¹,

Kim²

1999

Softw: Pract. Exper.

View full text Add to dashboard Cite

In this paper, we describe the design and implementation of the SOP Object Version System which is built upon an object database system, called SOP (SNU ODBMS Platform). SOP is fully compliant with ODMG-93, a standard for object databases proposed by the Object Database Management Group (ODMG). To support object versioning in an ODMG C++ OML (Object Manipulation Language) environment, the SOP Object Version System provides a set of APIs (Application Programming Interfaces) as a class library. One important design goal of the SOP Object Version System was to achieve full compliance with ODMG-93 standard. That is, in designing the class library, we tried to utilize the ODMG-93 C++ OML interface as much as possible, while preserving its semantics as defined in ODMG-93. Our object version model follows the basic functionalities of mainstream object version models. Although this approach burdens programmers with the management of the application-specific version policy, it helps users to apply the SOP Object Version System to diverse application areas. Strictly speaking, the version concept discussed in this paper is about user-level versions. System-level version concepts, such as for concurrency control [1] and long duration transaction [2] is beyond the scope of this paper. This paper deals with the design and implementation of version facilities of the SOP Object Version System, which extends the SOP (SNU ODBMS Platform) system [19], which was developed from scratch at Seoul National University and is fully compliant with ODMG-93, the de facto object database standard proposed by the Object Data Management Group (ODMG) [20].In the early 1990s, ODBMS vendors recognized that the lack of a standard for object databases was a major limitation to their products' wide acceptance in the market. They learned that much of the relational database's success was attributable to its standard, SQL. Hence, they organized the ODMG in the summer of 1991 so as to make an object database standard allowing source code portability and interoperability between different ODBMS products. Since the publication of release 1.0, in the late 1993, the ODMG made several enhancements to the standard, release 1.1, 1.2 and 2.0 (as of 1997). The main components of the standards include (1) Object Model, the common data model to be supported by ODBMSs, (2) Object Definition Language (ODL), the specification languages for ODBMSs, (3) Object Query Language (OQL), a declarative language for querying and updating database objects, and (4) Object Manipulation Languages (OMLs), the bindings of ODBMSs to the popular object oriented languages C++, Smalltalk and Java (new in release 2.0 [22]). We assume in this paper that readers are familiar with the ODMG-93 standard, especially ODMG C++ OML and the C++ programming language [23].The SOP system supports ODL, OQL and C++ ODL/OML binding of the ODMG-93 standard (currently based on release 1.2 [20]). SOP consists of several main modules, including an object storage system Soprano [24,25], a cost-based query p...

show abstract

Version models for software configuration management

Cited by 436 publications

References 92 publications

Uniform Comparison of Configuration Management Data Models

Uniform Comparison of Configuration Management Data Models

Software Product-Family Engineering

Object versioning in an ODMG‐compliant object database system

Contact Info

Product

Resources

About