RCS—a system for version control
Software—Practice & Experience
The Adele configuration manager
Configuration management
ESEC '97/FSE-5 Proceedings of the 6th European SOFTWARE ENGINEERING conference held jointly with the 5th ACM SIGSOFT international symposium on Foundations of software engineering
Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Version models for software configuration management
ACM Computing Surveys (CSUR)
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
A cooperative approach to support software deployment using the software dock
Proceedings of the 21st international conference on Software engineering
The software component market on the internet current status and conditions for growth
ACM SIGSOFT Software Engineering Notes
Introducing Microsoft® .NET
A State-of-the-Art Survey on Software Merging
IEEE Transactions on Software Engineering
ICSR-7 Proceedings of the 7th International Conference on Software Reuse: Methods, Techniques, and Tools
Modelling Systems with Variability using the PROTEUS Configuration Language
Selected papers from the ICSE SCM-4 and SCM-5 Workshops, on Software Configuration Management
New Challenges for Configuration Management
SCM-9 Proceedings of the 9th International Symposium on System Configuration Management
Imposing a Memory Management Discipline on Software Deployment
Proceedings of the 26th International Conference on Software Engineering
Integration of component-based development-deployment support for J2EE middleware
SEM'04 Proceedings of the 4th international conference on Software Engineering and Middleware
Hi-index | 0.00 |
Software systems are increasingly being built by integrating preexisting components developed by different, geographically distributed organizations. Each component typically evolves independently over time, not only in terms of its functionality, but also in terms of its exposed interfaces and dependencies on other components. Given that those other components may also evolve, creating an application by assembling sets of components typically involves managing a complex web of evolving dependencies. Traditional configuration management systems assume a form of centralized control that simply does not suffice in these situations. Needed are new configuration management systems that span multiple organizations, operate in a distributed and decentralized fashion, and help in managing the consistent evolution of independently developed, inter-related sets of components. A critical aspect of these new configuration management systems is that they must respect the different levels of autonomy, privacy, and trust that exist among different organizations. In this paper, we introduce TWICS, an early example of such a new configuration management system. Key aspects of TWICS are that it maintains traditional configuration management functionality to support the development of individual components, but integrates policy-driven deployment functionality to support different organizations in evolving their inter-related components.