Contracts: specifying behavioral compositions in object-oriented systems
OOPSLA/ECOOP '90 Proceedings of the European conference on object-oriented programming on Object-oriented programming systems, languages, and applications
A Layered Architecture for Uniform Version Management
IEEE Transactions on Software Engineering
SOFA/DCUP: Architecture for Component Trading and Dynamic Updating
CDS '98 Proceedings of the International Conference on Configurable Distributed Systems
Towards a Versioning Model for Component-based Software Assembly
ICSM '03 Proceedings of the International Conference on Software Maintenance
Component evolution and versioning state of the art
ACM SIGSOFT Software Engineering Notes
IEEE Transactions on Software Engineering
ACM SIGSOFT Software Engineering Notes
| Hi-index | 0.00 |
Component-based systems provide a better reuse of software components, greater flexibility, scalability and higher quality of services. Component development generally takes place due to the process of creating and propagating changes in requirement definitions, system designs, program source code, documentation and test data. As a result, multiple versions of constituent components come into existence. Thus, there is a need to keep the track of multiple versions of same component. To handle multiple versions of constituent components, a version-control tool named as Visual Version Control Tool (VVCT), for the management of life-cycle evolution of component, is developed. The developed tool satisfies all the conditions required for version control in component-based systems. The parameters required for uniform version management as well as component frameworks are also satisfied by the developed tool. To monitor and control the versioning system, an example model is tested along with the set of proposed metrics. This paper also incorporates issues like component configuration, component evolution, component framework, component version tree and version-control metrics.