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

Distributed con guration management is intended to support the activities of projects that span multiple sites. NUCM is a testbed that we are developing to help us explore the issues of distributed con guration management. NUCM separates con guration management repositories (i.e., the stores for versions of artifacts) from con guration management policies (i.e., the procedures by which the versions are manipulated) by providing a generic model of a distributed repository and an associated programmatic interface. This paper describes the model and the interface, presents an initial repository distribution mechanism, and sketches how NUCM can be used to implement two, rather di erent, con guration management policies, namely checkin/check-out and change sets.

The gulf between the user and the developer perspectives lead to diculties in producing successful software systems. Users are focused on the problem domain, where the system's features are the primary concern. Developers are focused on the solution domain, where the system's life-cycle artifacts are key. Presently, there is little understanding of how to narrow this gulf.

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.

Recent work on software processes has produced a considerable amount of detailed information which renders the software life cycle more explicit by describing it as an enactable software process model. This article presents TEMPO: a software process modeling strategy based on Adele: a software con guration management kernel. The facilities for describing and enacting software process models are highlighted. TEMPO is an object oriented process model. Each software process is modeled as an object which encapsulates (role concept) the operations around a set of resources required to carry out a speci c software development activity. Each software activity provides workspace in which the developers work by calling operations on processes. On this way a software development environment may consist of a set of workspace working together by coordinating their activities. This paper concludes with an overview of the TEMPO implementation on top of Adele.

Abstract not found

After years using of Adele [3], a con guration management system, it became apparent that it lacks activity-related concepts and mechanisms like work environment control, user coordination and synchronization, method and tool control, etc. It was also clear that considerable work is required toadpat a Software Engineering Environment (SEE) to user requirements. Using this experience, Adele 2 has been implemented toprovide a general support for de ning and managing dynamic aspects of a SEE and facilitate the building of new SEE's. This paper describes, using an example (work space control), the concepts and mechanisms involved. We show how close integration of an activity manager with a software engineering database ful lls the basic requirements and how a high level task manager coupled toacon guration manager can be developed. Key words CASE; software development process; team coordination; programmingin-the-large; software engineering environment; process model; process control; groupware mechanisms.

This paper reports our experiences gained in designing, implementing, and experimenting with technologies for improved support for cooperative work in our configuration management (CM) system. The aim of the work has been to find a set of mechanisms supporting cooperation in a range of situations, from planning and scheduling long-lasting CM activities, to resolving access conflicts between users. Although our tools are tailored for our home-grown environment, the general approach should be applicable also to other CM systems or usage domains. The emphasis of this paper is on flexible mechanisms to solve access conflicts without enforcing only one way of working.