Resolving requirements conflicts with computer-supported negotiation
Requirements engineering
Flexible conflict detection and management in collaborative applications
Proceedings of the 10th annual ACM symposium on User interface software and technology
Representing Design Dependencies in an Issue-Based Style
IEEE Software
WHAT MAKES A GOOD DESIGN QUESTION?
ACM SIGCHI Bulletin
Traceability in viewpoint merging: a model management perspective
TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
Collaboration in Software Engineering: A Roadmap
FOSE '07 2007 Future of Software Engineering
Towards a Belief-Theoretic Model for Collaborative Conceptual Model Development
HICSS '08 Proceedings of the Proceedings of the 41st Annual Hawaii International Conference on System Sciences
Managing Model Conflicts in Distributed Development
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
Human-Computer Interaction
Operation-based conflict detection and resolution
CVSM '09 Proceedings of the 2009 ICSE Workshop on Comparison and Versioning of Software Models
Rationale-based Unified Software Engineering Model
Rationale-based Unified Software Engineering Model
Agile Model-Driven Development in Practice
IEEE Software
Proceedings of the 15th annual conference on Genetic and evolutionary computation
Natural modeling: retrospective and perspectives an anthropological point of view
Proceedings of the 2012 Extreme Modeling Workshop
Negotiated grammar transformation
Proceedings of the 2012 Extreme Modeling Workshop
| Hi-index | 0.00 |
Models are important artifacts in the software development life-cycle and are often the result of a collaborative activity of multiple developers. When multiple developers modify the same model, conflicts can occur and need to be resolved by merging. Existing approaches for model merging require developers to solve all conflicts before committing. The later a developer commits the higher the probability for even more conflicts. This forces the developers to solve every conflict as soon as possible and without consulting the other developer. However, we claim that developers often need to discuss their choice of conflict resolution with another developer in case of a complex conflict, since a conflict also expresses differences in opinion about the model. In this paper we propose to allow developers to postpone a decision of a modeling conflict. We present an approach to make conflicts part of the model and represent them as first-level entities based on issue modeling from the field of Rationale Management. This facilitates the possibility for collaborative conflict resolution and merging. Furthermore, it allows for a complete batch merge instead of interactive merging, where all conflicts are added to the model and then resolved later. To substantiate our claim that developers favor to discuss complex conflicts we conducted a case study.