Context
We are convinced that (graphical) modeling is a cooperative and explorative process done by domain experts. However, several studies identified an insufficient collaboration support of graphical modeling tools. Therefore, we develop a new collaboration approach for graphical modeling tools that is based on the persistence of sequential edit operations (also called operation-based approach). We aim to enable both synchronous as well as asynchronous collaboration and improve the comprehensibility of evolving models.

Problem
In the context of synchronous collaboration it can happen that two or more users make changes within the same area of a graphical model. This might lead to visually interfering edit operations, e.g., Alice edits the value of a property Prop1 while Bob moves BlockA which contains Prop1. Also semantically conflicting edit operations, such as Bob deletes BlockA instead of moving it, can have a negative impact to the user experience.

We assume that the negative impact of those interfering edit operations can be avoided be implicitly create a temporary branch that delays interfering edit operations of other users.

Tasks

• Systematically identify different types of be interfering edit operations
• Develop an algorithm to detect interfering edit operations
• Implement a solution that uses your algorithm and is able to temporary delay other users edit operations.
• Conduct a user study that evaluates the impact of your approach on the user experience.

Related Work

• Enhancing Collaborative Modeling
  Summary of the vision of our new modeling approach.
• An Operation-based Versioning Approach for Synchronous and Asynchronous Collaboration in Graphical Modeling Tools.
  Developed operation-based versioning approach.
• An Introduction to Model Versioning
  Introduction in model versioning.
• Event Sourcing
  Data persistence pattern that we use for versioning purposes.
• A Domain-Specific Language and Interactive User Interface for Model-Driven Engineering of Technology Roadmaps
  Graphical roadmapping tool developed by our institute that we extend with our collaboration approach.

Contact

Jakob Pietron

Context
We are convinced that (graphical) modeling is a cooperative and explorative process done by domain experts. However, several studies identified an insufficient collaboration support of graphical modeling tools. Therefore, we develop a new collaboration approach for graphical modeling tools that is based on the persistence of sequential edit operations (also called operation-based approach). We aim to enable both synchronous as well as asynchronous collaboration and improve the comprehensibility of evolving models.

Problem
At the present stage of our research we persist every kind of edit operation a user has performed to alter the model and present the result in a simple directed acyclic graph (DAG). We are able to filter the edit history by the type of operation or the target of an operation. However, we can not formulate more advanced queries. For instance: "Show only refactoring operations performed by Alice during the last two weeks within this area of the model."

Tasks

• Develop or extend query language (QL) covers the following dimensions:
  • Syntax, e.g., type of element
  • Semantic, e.g., fulfilment of a requirement
  • Meta information, e.g., time or user
  • Edit operations, e.g., type of edit operation
• QL should be interactive and should provide live feedback.
• Conduct a user study to evaluate the user experience of your implementation.

Related Work

• Enhancing Collaborative Modeling
  Summary of the vision of our new modeling approach.
• An Introduction to Model Versioning
  Introduction in model versioning.
• Event Sourcing
  Data persistence pattern that we use for versioning purposes.
• A Domain-Specific Language and Interactive User Interface for Model-Driven Engineering of Technology Roadmaps
  Graphical roadmapping tool developed by our institute that we extend with our collaboration approach.

Contact

Jakob Pietron