The Community for Technology Leaders
Green Image
<p>Version management is a key part of software configuration management. A big variety of version models has been realized in both commercial systems and research prototypes. These version models differ with respect to the objects put under version control (files, directories, entities, objects), the organization of versions (version graphs versus multidimensional version spaces), the granularity of versioning (whole software products versus individual components), emphasis on states versus emphasis on changes (state- versus change-based versioning), rules for version selection, etc. We present a <it>uniform version model</it>—and its support architecture—for software configuration management. Unlike other unification approaches, such as UML for object-oriented modeling, we do not assemble all the concepts having been introduced in previous systems. Instead, we define a base model that is built on a small number of concepts. Specific version models may be expressed in terms of this base model. Our approach to uniform version management is distinguished by its underlying <it>layered architecture</it>. Unlike the main stream of software configuration management systems, our <it>instrumentable version engine</it> is completely orthogonal to the data model used for representing software objects and their relationships. In addition, we introduce version rules at the bottom of the layered architecture and employ them as a uniform mechanism for expressing different version models. This contrasts to the main stream solution, where a specific version model—usually version graphs—is deeply built into the system and version rules are dependent on this model.</p>
Version model, version rules, software configuration management, software architecture, software repositories

B. Westfechtel, B. Munch and R. Conradi, "A Layered Architecture for Uniform Version Management," in IEEE Transactions on Software Engineering, vol. 27, no. , pp. 1111-1133, 2001.
86 ms
(Ver 3.3 (11022016))