RCS—a system for version control
Software—Practice & Experience
Unified versioning through feature logic
ACM Transactions on Software Engineering and Methodology (TOSEM)
Version models for software configuration management
ACM Computing Surveys (CSUR)
A Testbed for Configuration Management Policy Programming
IEEE Transactions on Software Engineering
A State-of-the-Art Survey on Software Merging
IEEE Transactions on Software Engineering
A Layered Architecture for Uniform Version Management
IEEE Transactions on Software Engineering
Foundations for Software Configuration Management Policies Using Graph Transformations
FASE '00 Proceedings of the Third Internationsl Conference on Fundamental Approaches to Software Engineering: Held as Part of the European Joint Conferences on the Theory and Practice of Software, ETAPS 2000
Improving Cooperation Support in the EPOS CM System
EWSPT '98 Proceedings of the 6th European Workshop on Software Process Technology
Change Sets Versus Change Packages: Comparing Implementations of Change-Based SCM
ICSE '97 Proceedings of the SCM-7 Workshop on System Configuration Management
The Unified Extensional Versioning Model
SCM-9 Proceedings of the 9th International Symposium on System Configuration Management
Defining and supporting concurrent engineering policies in SCM
SCM'01/SCM'03 Proceedings of the 2001 ICSE Workshops on SCM 2001, and SCM 2003 conference on Software configuration management
An Experimental, Pluggable Infrastructure for Modular Configuration Management Policy Composition
Proceedings of the 26th International Conference on Software Engineering
MOD2-SCM: A model-driven product line for software configuration management systems
Information and Software Technology
| Hi-index | 0.00 |
A configuration management policy specifies the procedures through which a user evolves artifacts stored in a configuration management system. Different configuration management systems typically use different policies, and new policies continue to be developed. A problem in the development of these new policies is that existing policies (and their implementations) typically cannot be reused. As a basis for a future solution, this paper presents a new configuration management system architecture that focuses on modularly specified policies. In particular, policies consist of a set of constraint modules, which enforce the desired repository structure, and a set of action modules, which govern the desired user interaction. New policies can be developed by combining relevant existing modules from existing policies with new modules that specify the unique aspects of the new policy. We demonstrate how several quite different configuration management policies can be effectively constructed this way.