The Unified Extensional Versioning Model

Abstract

Abstract. Versioning of components in a system is a well-researched field where various adequate techniques have already been established. In this paper, we look at how versioning can be extended to cover also the structural aspects of a system. There exist two basic techniques for versioning -intentional and extensional -and we propose a unified extensional versioning model for versioning of both components and structure in the same way. The unified model is described in detail and three different policies that can be implemented on top of the general model are exemplified/illustrated by three prototype tools constructed by the authors. The model is analysed with respect to the number of versions and configurations it generates and has to manage. Finally, the unified extensional model is compared to more traditional intentional models on some important parameters. The conclusions are that the unified model is indeed viable. It not only provides the functionality offered by the intentional model with respect to flexibility during development and management of combinatoric complexity, but also offers a framework for management of configurations that enables systems to provide much more advanced support than is commonly available.

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

“…The principles of the tree-based COOP/Orm framework [12] include the sharing of unchanged tree nodes among versions and change propagation. Unified Extensional Versioning Model [13] supports fine-grained versioning for a tree-structured document by composite/atomic nodes and links. Each atomic node is represented by a text file.…”

“…Recognizing that importance, researchers have proposed several models and tools for version control of fine-grained program entities [11][12][13][14]. Those approaches, however, do not scale well because they generally rely on total versioning [16], which requires to store all versions of any entity for its own version history.…”

Object-Oriented Design Frameworks: Formal Specification and Some Implementation Issues

“…Typically, in a development process, we would implement the changes on all the objects we want, collect the versions of objects we want in a baseline and derive the frameworks from the baselined object versions. In such a case, experience for similar cases [2] shows that the number of derived entities does not necessarily grow rapidly.…”

“…In our approach, we define OOD frameworks and objects/classes in terms of a basic entity that we call a specification framework, or just a framework, for short. 2 A framework ¦ is defined in the context of first-order logic with identity. It is composed of a signature ¦ (containing sort symbols, function declarations and relation declarations), and a finite or recursive set of ¦-axioms.…”

Um controle de versões refinado e flexível para artefatos de software

“…Para fornecer o controle de versões refinado, foi claramente definido um modelo para o controle de versões refinado, chamado Unified Extensional Versioning Model (UEVM). Apesar deste modelo ter sido apresentado anteriormente (ASKLUND et al, 1999), Asklund o apresentou com correções e atualizações, principalmente no que diz respeitoà propagação de versões e preocupações adicionais com as características que permitem ao modelo de versões não sofrer a explosão combinatória (ASKLUND, 2002).…”