Design complexity measurement and testing
Communications of the ACM
Version models for software configuration management
ACM Computing Surveys (CSUR)
Versions and workspaces in Microsoft repository
SIGMOD '99 Proceedings of the 1999 ACM SIGMOD international conference on Management of data
Application of cluster algorithms for batching of pro~posed software changes
Journal of Software Maintenance: Research and Practice
Journal of the ACM (JACM)
UML distilled (2nd ed.): a brief guide to the standard object modeling language
UML distilled (2nd ed.): a brief guide to the standard object modeling language
Agile Software Development: Principles, Patterns, and Practices
Agile Software Development: Principles, Patterns, and Practices
Challenges of component-based development
Journal of Systems and Software
Software release management for component-based software
Software—Practice & Experience
The Impact Analysis Task in Software Maintenance: A Model and a Case Study
ICSM '94 Proceedings of the International Conference on Software Maintenance
Software Change Impacts - An Evolving Perspective
ICSM '02 Proceedings of the International Conference on Software Maintenance (ICSM'02)
Simulation: The Practice of Model Development and Use
Simulation: The Practice of Model Development and Use
Component evolution and versioning state of the art
ACM SIGSOFT Software Engineering Notes
Model driven generation and testing of object-relational mappings
Journal of Systems and Software
Using dependency models to manage complex software architecture
OOPSLA '05 Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
IEEE Transactions on Software Engineering
Hi-index | 0.00 |
As much component-based software is developed, a software configuration management (SCM) tool for component-based software is necessary. In this paper, we propose a version management mechanism for impact analysis while components are upgraded. We separately version the components and interfaces based on a Component-Interface Dependency Matrix (CIDM), and analyze impacts according to their dependency relationship. The result of our simulation shows that CIDM is capable of managing large numbers of components without impedance mismatch. In addition, in a well-designed software system, using CIDM to analyze impacts can save resources in the software development phase.