=Paper=
{{Paper
|id=Vol-2019/commitmde_intro
|storemode=property
|title=None
|pdfUrl=https://ceur-ws.org/Vol-2019/commitmde_intro.pdf
|volume=Vol-2019
}}
==None==
https://ceur-ws.org/Vol-2019/commitmde_intro.pdf
COMMitMDE 2017 - 2nd International Workshop
on Collaborative Modelling in MDE
Jan Bosch Sébastien Gérard Dimitris Kolovos
Chalmers University of Technology CEA, LIST University of York
Sweden France UK
Email: jan.bosch@chalmers.se Email: sebastien.gerard@cea.fr Email: dimitris.kolovos@york.ac.uk
Ivano Malavolta Henry Muccini
Vrije Universiteit Amsterdam University of L’Aquila, DISIM Department
The Netherlands Italy
Email: i.malavolta@vu.nl Email: henry.muccini@univaq.it
Abstract—Collaborative modeling is gaining a growing inter- The COMMitMDE workshop had the dual role of investi-
est in both academia and industry. However, several research gating the potential impact of collaborative SE methods and
challenges remain open, including scalability, support for multi- principles [4] into MDE practices, as well as MDE support
user modeling environments, model versioning, migration, com-
parison, merging and conflict management. Recently, scientific to collaborative SE. More specifically, the objective of this
research contributions related to collaborative model-driven soft- workshop was to bring together experts in model-driven and
ware engineering (MDSE) are emerging, each of them focusing collaborative software engineering in order to give evidence
on different and specific aspects of collaboration and modelling. on the ongoing research and development on this topic. Such
Still, many of these studies are scattered across multiple research a high-level objective can be decomposed into the following
areas such as software engineering, model-driven engineering,
model integrated computing, etc. details action points:
COMMitMDE 2017 has brought together researchers and . Report on the state of research and practice on collaborative
practitioners to explore (i) the impact of collaborative SE methods MDE;
and principles on MDE practices and (ii) how MDE methods . Create links among tool vendors, researchers, and practition-
and techniques can support collaborative software engineering ers;
activities. Also, the workshop aimed at assessing the state of
the research and practice on Collaborative MDE, creating new . Identify needs and gaps in the collaborative MDE commu-
synergies between tool vendors, researchers, and practitioners, nity;
informing the community about the new means for collaborative . Inform the community about new means for collaborative
MDE, and identifying needs and research gaps in the collabora- MDE.
tive MDE area. The topics proposed for discussion during the 2nd COMMit-
Index Terms—MDE, collaboration, collaborative MDE
MDE workshop are: collaborative MDE design; requirements
engineering with collaborative MDE; metamodel-level collab-
I. I NTRODUCTION
oration; multi-view collaborative MDE; the role of off-the-
A collaborative Model-Driven Engineering approach [1], shelf VCS/forges in MDE; web-based model editing; collab-
[2] is a method or technique in which: (i) models are first-class orative MDE practices; academic and industrial needs in col-
artefacts that drive both the software development activities laborative MDE; case studies and experience reports; scalable
and the other model-based tasks in the context of a software repositories for collaborative modeling; multi-user modeling
engineering process; (ii) at least one repository exists for man- environments; synchronization mechanisms like models mi-
aging the persistence of the models; (iii) at least one modelling gration and merging; conflicts management; models versioning
tool [3] exists for allowing each stakeholder involved in the and model comparison support.
modelling activities to create, edit, and delete models; (iv) at COMMitMDE 2017 solicited regular research papers with
least one communication means exists for allowing involved a maximum length of 10 pages proposing and discussing
stakeholders to be aware of what the other stakeholders research results or industrial experiences related to collab-
collaborating with them are doing (e.g., chat, social network, orative MDSE, as well as tool demonstration papers with
wiki, asynchronous messaging system, issue tracker); (v) at a maximum length of 4 pages presenting interesting tools
least one collaboration means exists for allowing involved supporting collaborative MDSE. In its second edition the
stakeholders to work on the modelling artifacts collaboratively COMMitMDE workshop received six submissions, of which
(e.g., model versioning systems, model merging mechanisms, five papers were accepted for publication and presentation
systems for model conflict management and visualization). during the workshop. Articles from COMMitMDE 2017 and
ME 2017 (Workshop on Models and Evolution) have been extended to cover concepts such as timeline, branches, forks,
presented in a joint programme. The COMMitMDE 2017 merges, commets and releases. Special attention is given to
website is available on-line1 . a merge conflict where two branches introduce the same
The program of the workshop comprised a full day of transition. A running example on a drone system is developed
activities, which were split into two sessions, summarized all along the paper.
below.
R EFERENCES
II. S ESSION ON C OLLABORATIVE M ODELING [1] M. Franzago, D. Di Ruscio, I. Malavolta, and H. Muccini, “Collabora-
tive Model-Driven Software Engineering: a Classification Framework
The first session comprised three talks. and a Research Map”, IEEE Transactions on Software Engineering,
In their paper, titled Towards Efficient Evaluation of Rule- 10.1109/TSE.2017.2755039, 2017.
based Permissions for Fine-grained Access Control in Collab- [2] D. Di Ruscio, M. Franzago, H. Muccini, and I. Malavolta, “Envisioning
the future of collaborative model-driven software engineering”. In Pro-
orative Modeling, Gabor Bergman, Csaba Debreceni, Istvan ceedings of the 39th International Conference on Software Engineering
Rath and Daniel Varro presented their work related to access Companion (pp. 219-221). IEEE Press, 2017.
control in collaborative modeling environments. A rule-based [3] M. Brambilla, J. Cabot, and M.Wimmer, “Model-driven software engi-
neering in practice”, Morgan & Claypool Publishers, 2012.
approach is used to define fine grained policies. Differently [4] I. Mistrk, J. Grundy, A. v. Hoek, and J. Whitehead, “Collaborative
from previous work, the permission rules evaluation and re- Software Engineering”, Springer Berlin Heidelberg.
processing (in case of changes) is done incrementally, there-
fore scaling to very large models.
In the second paper, titled Feature Model for Collaborative
Modeling Environments, Constantin Masson, Jonathan Corley
and Eugene Syriani presented a feature model for collaborative
systems. Features and key concepts related to collaborative
modeling are collected and organizeding through an informal
analysis of the state of the art. Each concept is discussed
in detail, describing related challenges, issues and relations
among them.
In the last article in the session, titled Supporting
Consensus-based Software Development: A Vision Paper,
Mathieu Lavalle, Guillaume Beaulieu and Michalis Famelis
presented the notion of consensus-based software development
identifying all the dimensions and implication of consensus in
group decision making, as well as required activities and roles,
and challenges of implementing them in practice. Tool support
is also analyzed and mapped to existing requirements.
III. S ESSION ON C ONSISTENCY M ANAGEMENT
The second session comprised three talks. Two of them are
part of the COMMitMDE 2017 programme and are summa-
rized below.
In the first paper, titled Modeling and Enactment Support
for Early Detection of Inconsistencies in Engineering Pro-
cesses, István Dávid, Bart Meyers, Ken Vanherpen, Yentl
Van Tendeloo, Kristof Berx and Hans Vangheluwe, presented
their methodology to support the early detection of model
inconsistencies. Constraints (i.e., rules enconding inconsis-
tency definitions) are specified and evaluated at run-time.
Inconsistencies are caused by attribute values modifications
that bring to violation to rules. Errors are raised in case of
inconsistencies.
The second paper, titled Towards Collaborative Modeling
Using a Concern-Driven Version Control System, Omar Alam,
Vasco Sousa and Eugene Syriani presented an extension to
the CORE (Concern-Oriented REuse) paradigm to support
collaboration through a version control system. CORE is
1 http://cs.gssi.it/commitmde2017/