An important problem in program development and maintenance is version control, i.e., the task of keeping a software system consisting of many versions and configurations well organized. The Revision Control System (RCS) is a software tool that assists with that task. RCS manages revisions of text documents, in particular source programs, documentation, and test data. It automates the storing, retrieval, logging and identification of revisions, and it provides selection mechanisms for composing configurations. This paper introduces basic version control concepts and discusses the practice of version control using RCS. For conserving space, RCS stores deltas, i.e., differences between successive revisions. Several delta storage methods are discussed. Usage statistics show that RCS’s delta storage method is space and time efficient. The paper concludes with a detailed survey of version control tools.

This paper focuses on the version models underlying both commercial systems and research prototypes. It provides an overview and classification of different versioning paradigms. Furthermore, it defines and relates fundamental concepts such as revisions, variants, configurations, and changes. In particular, we focus on intensional versioning, i.e., construction of versions based on configuration rules. Finally,we provide an overview of systems whichhave had significant impact on the development of the SCM discipline, and classify them according to a detailed taxonomy

Abstract-Software configuration management (SCM) is an emerging discipline. An important aspect of realizing SCM is the task of maintaining the configurations of evolving software systems. In this paper, we provide an approach to resolving some ofthe conceptual and technical problems in maintaining configurations of evolving software systems. The approach provides a formal basis for existing notions of system architecture. The formal properties of this view of configurations provide the underpinnings for a rigorous notion of system integrity, and mechanisms to control the evolution of configurations. This approach is embodied in a language, NuMIL, to describe software system configurations, and a prototype environment to maintain software system configurations. We believe that the approach and the prototype environment offer a firm base to maintain software system configurations and, therefore, to implement SCM. Index Terms-Configuration, module and subsystem families, module and subsystem interfaces, software configuration maintenance system, upward compatibility. I.

A rich variety of version models for software configuration management (SCM) has been proposed over the years, and understanding of the basic concepts and their interrelations has been growing accordingly.

Despite recent advances in software configuration management (SCM), constructing consistent configurations of large and complex versioned software products still remains a challenge. We provide an overview of existing approaches which address this problem. These approaches are compared by means of a taxonomy which is based on an analogy to deductive databases: construction of a configuration corresponds to evaluation of a query against a versioned database with stored version selection rules.

. 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 model of a hypertext document which takes into account the perspective of its permanent change. Hypertext documents are modelled by two kinds of nodes in an AND/OR graph. The model forms a basis for building a configuration. Keywords: hypertext document, hypertext document model, version, configuration. 1 Introduction Version control has been identified as one of the critical research areas in the hypertext field [8]. It is important especially for hypertext documents published on the web. Methods of support to versioning hypertext systems have been subject of intensive research f...

Software configuration management (SCM) seeks to control the evolution of software systems. In this pa-per, we introduce a new object-oriented model of SCM that is based on the earlier research results of the SAGA project. The model is, we believe, more gen-eral and comprehensive than previous models and uses clasaes to define different kinds of SCM entities, meth-ods to define the operations applicable to the entities, and inheritance to denote generalization relationships between the classes. The paper presents the principal classes in the model, describes their structure and func-tionality, and explains their roles in the representation of SCM systems. 1

Integration of configuration management (CM) tools into software development environments raises the need for CM models to interoperate through a unified CM model. We present the version set model, where versions, components, and aggregates are grouped into sets according to their features, using feature logic as a formal base to denote sets and operations and deduce consistency. Version sets generalize well-known CM concepts such as components, repositories, workspaces, aggregates, or configurations. Arbitrary revision/variant combinations of components and aggregates are modeled in a uniform and orthogonal way. We show how the concepts of four central configuration management models---the checkin/ checkout model, the change set model, the composition model, and the long transaction model--- are encompassed and extended by the version set model, making it a unified basis for modeling, realizing and integrating configuration management tasks. Finally, some conditions for efficient real...

Abstract not found

This paper presents the role and the evolution of Software Engineering Environment(SEE) and Computer Aided Software Engineering Environments (CASE Environments) in large software development and maintenance. We emphasize the drawbacks of the current state of the art, advocating improved structural and behavioral modeling and the introduction of team support to meet software engineering requirements: what we need is a Process centered SEE its trigger mechanism with its data model to solve some team support problems. Key-words: CASE; Software engineering environments, process modeling; programming in the large; active software database; product modeling; 1