Designing configuration management facilities for dynamically bound systems

Schmerl, Bradley; Marlin, Chris D.

doi:10.1007/3-540-60578-9_7

Cited by 3 publications

(3 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Up to now, the relations to SCM have not been investigated thoroughly. Only recently have a few approaches been proposed that apply version-selection techniques from SCM to dynamic configuration [Warren and Sommerville 1995;Schmerl and Marlin 1995]. However, elaborating on this topic goes beyond the scope of this article.…”

Section: Conceptual Framework For Intensional Versioningmentioning

confidence: 99%

Version models for software configuration management

1998

View full text Add to dashboard Cite

After more than 20 years of research and practice in software configuration management (SCM), constructing consistent configurations of versioned software products still remains a challenge. This article focuses on the version models underlying both commercial systems and research prototypes. It provides an overview and classification of different versioning paradigms and defines and relates fundamental concepts such as revisions, variants, configurations, and changes. In particular, we focus on intensional versioning, that is, construction of versions based on configuration rules. Finally, we provide an overview of systems that have had significant impact on the development of the SCM discipline and classify them according to a detailed taxonomy.

show abstract

Section: Conceptual Framework For Intensional Versioningmentioning

confidence: 99%

Version models for software configuration management

1998

View full text Add to dashboard Cite

show abstract

“…SCM systems generally provide poor support for treating several items at once. This includes lack of support for manipulating and identifying permanent variants [33], change propagation across several versions at once [36], or consistency checking in abstract (ambiguous) configurations [47].…”

Section: Unified Scm Modelmentioning

confidence: 99%

Unified versioning through feature logic

Zeller

Snelting

1997

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

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.

show abstract

“…Our research focusses on providing configuration management facilities which address the problems associated with the construction of DCS; these problems include the selection of components dynamically and the need to evaluate consistency on-the-fly, which can no longer be guaranteed statically. In [21], these were identified as configuration management problems.…”

Section: Introductionmentioning

confidence: 99%

Consistency issues in partially bound dynamically composed systems

Schmerl

Marlin

Proceedings of 1996 Australian Software Engineering Conference

View full text Add to dashboard Cite

Dynamically composed systems are able to incorporate new components as they execute. Therefore, configurations of these systems are not fully elaborated until at least the time that they are executed, and they are perhaps newer fully elaborated. Such incomplete configurations are termed partially bound configurations. Although partially bound, it is still important to be able to analyse these configumtions to ascertain whether they meet certain assumptions about their composition. We are endeavouring to provide such support for the construction of dynamically composed systems through the application of configuration management concepts. One way in which these concepts can be applied in this domain is to explicitly state such assumptions and hence be able to validate partially bound configurations against these assumptions; in this way, inconsistencies can be reported as soon as they arise. This paper explores some of the issues involved in providing this kind of consistency mechanism for dynamically composed systems. In particular, the paper discusses consistency issues which arise in the context of systems where the generic structure of the system configuration is known, but the decision about which particular components comprise the configuration is deferred until execution.

show abstract

Designing configuration management facilities for dynamically bound systems

Cited by 3 publications

References 12 publications

Version models for software configuration management

Version models for software configuration management

Unified versioning through feature logic

Consistency issues in partially bound dynamically composed systems

Contact Info

Product

Resources

About