Differences between versions of UML diagrams
Proceedings of the 9th European software engineering conference held jointly with 11th ACM SIGSOFT international symposium on Foundations of software engineering
Refactoring-Aware Configuration Management for Object-Oriented Programs
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Reconciling software configuration management and product data management
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Collaborative software engineering on large-scale models: requirements and experience in ModelBus
Proceedings of the 2008 ACM symposium on Applied computing
Matching class diagrams: with estimated costs towards the exact solution?
Proceedings of the 2008 international workshop on Comparison and versioning of software models
Towards software configuration management for unified models
Proceedings of the 2008 international workshop on Comparison and versioning of software models
Operation-based conflict detection
Proceedings of the 1st International Workshop on Model Comparison in Practice
| Hi-index | 0.00 |
Various types of diagrams are used to represent the design of software systems. During the design phase, versions of a diagram may be created like other design documents and source code, and it is necessary to manage them efficiently. However, traditional configuration management systems and some object-oriented database management systems that provide object versioning are not suitable for managing versions of a diagram. In this paper, we propose an efficient version model of software diagrams. This model reflects the common characteristics and structure of software diagrams, and revisions of a diagram are managed by operation delta and object visibility. A merge model for versions of a diagram is also presented at the end of this paper.