Data dictionary user workflow

This page proposes a user workflows for data dictionary.

(Rejected) Using registered packages for data dictionary

Pros:

Each time the plugin is built, a transformation in produced to update other models.

Issues:

• Each time someone modifies the data dictionary, a plugin has to be build and the workspace updated.

• The data dictionary should not be part of the toolchain because it is workspace specific.

• Users want fast feedback for their changes.

Proposed solution:

Using a local eclipse update site that can be stored within the user project.

This update site is part of the user git repository. It allows for local updates of user workspace and reviews of changes without pushing the git repository. A user can also pull the git repository and update his workspace using this local update site.

The user workflow

Automatisable steps:

• Updating the data dictionary plugin.

• Pushing the local update site.

• Updating workspace (load the new plugin).

Issues

• Conflicts may arise, they are similar to conflicts with other models.

• The git repository may bloat up because we store binaries.

(Accepted) Using imported user packages

Using imported packages is simpler. The only constraint here is to save all models before modifying a registered package, otherwise modifications will be discarded.

The workflow

The workflow is easy to follow, but conflicts can arise. For conflict resolution we propose EMFCompare which allows for comparing and merging EMF models.

Conflict resolution