Unified versioning through feature logic

Abstract

Software Configuration Management (SCM) suffers from tight coupling between SCM versioning models and the imposed SCM processes. In order to adapt SCM tools to SCM processes, rather than vice versa, we propose a unified versioning model, the version set model. Version sets denote versions, components, and configurations by feature terms, that is, boolean terms over (feature: value)-attributions. Through feature logic, we deduce consistency of abstract configurations as well as features of derived components and describe how features propagate in the SCM process; using feature implications, we integrate change-oriented and version-oriented SCM models. We have implemented the version set model in a SCM system called ICE for Incremental Configuration Environment. ICE is based on a featured file system (FFS), where version sets are accessed as virtual files and directories. Using the well-known C Preprocessor representation, users can view and edit multiple versions simultaneously, while still only the differences between versions are stored. It turns out that all major SCM models can be realized and integrated efficiently on top of the FFS, demonstrating the flexible and unifying nature of the version set model.

Version models for software configuration management

“…Now we have gained a sufficient level of understanding to classify these approaches. Initial attempts to develop a uniform model have been undertaken [Zeller 1995;Zeller and Snelting 1997]. Furthermore, the recent evolution of SCM systems shows that their underlying version models are converging to an increasing extent.…”

“…In Zeller [1995] and Zeller and Snelting [1997], feature logic is used to realize the checkout/checkin model, the composition model, the long transaction model, and the change set model as introduced by Feiler [1991a] (see also Section 7.1).…”

Operation-Based, Fine-Grained Version Control Model for Tree-Based Representation

“…There exists version control models that are change-based ( [36][37][38]). That is, in change-based models, the changes are first-class entities with unique identifiers that are used to compose the system at different time.…”

Faculty Fellowship in Support of Tolerating Intrusions through Secure System Reconfiguration

“…van software architectures [11], or legal databases [29]), orJy a limited amount of support is available. A third reason is that existing CM systems are based on certain vinderlying assumptior\s; if new approaches are developed that are in conflict with some of these assumptions (e.g., the approach based on feature logic [53]), little help is available to implement them.…”