D6.4.2-3 User Interface for the Writer part (release 3)

[ferhaterata]

This is an issue of the task T6.4 User Interfaces Implementation (OBEO + SOGETI + UNIT + KOCSISTEM)

This task is about providing all the graphical user interfaces allowing the user to interact with the Knowledge Base content, and fix synchronization issues between documentation and models. For the Writer part: o To help preventing errors of ergonomics (based on lessons from past development of TopiWriter), ergonomics guidelines will have to be defined for the Writer part. The result of this work will be captured under an Ergonomics Guidelines document (D6.4.1). o Definition of the evaluation procedures for Task T6.8 (based on deliverables from WP1). o Implementation of the User Interfaces (D6.4.2-x) allowing the user to use all the features provided by the Knowledge Base (see WP4):

• Fix the consistency issues detected by the Model Checker (T4.4)
• Compare the current version of the document with a previous one thanks to the Semantic Comparison engine (T4.6) For the Bi-directional synchronisation capabilities of the Knowledge Base (see T4.9): an implementation of all UI parts integrated to the Eclipse platform, allowing the user to update models or documentation directly inside his IDE (D6.4.3-x). The following features are considered as the minimal sets of UI parts required for ModelWriter Use Cases: o Provide actions (quick-fixes) allowing the user to fix synchronization issues, whether by updating the models or the documentation o Provide UI mechanism (such as quick-outlines and hyperlink detectors) to navigate easily from model elements to the related documentation parts o Provide views (existing views like the Eclipse "Problem" view may be populated) allowing to get all the synchronization issues between documentation and models o Provide views allowing the user to determine which model elements have not yet been documented o Provide views allowing to get all the differences between models as defined in the documentation and models actually used by the development team The implementation of these UI Parts will be contributed to the open-source Intent project. Additional UI features, such as integration bridges with existing modelling tools (e.g. standard EMF tooling or Obeo Designer) allowing to see synchronization issues directly inside modellers may be provided, if the Use Cases analysis prove that this is a must-have feature. The implementation of these UI Parts will be contributed to the open-source Intent project.

[ylussaud]

This is part of the release:

https://github.com/ModelWriter/Source/tree/ITEA_RELEASE_1

[m-challenger]

Yvan, you closed the 3rd release of deliverable. It seems that you need to close D6.4.3-2 deliverable instead.

[ylussaud]

Yes my bad.

[ylussaud]

The third release source code is tagged here: https://github.com/ModelWriter/Source/tree/ITEA_RELEASE_3

It can be build using maven issuing the following command at the root of the repository:

mvn clean verify

The build is ran in a continuous integration fashion using travis:

https://travis-ci.org/ModelWriter/Source

And finally binaries can be found on the ModelWriter web site (http://modelwriter.eu/download) in order to be installer into Eclipse:

https://s3-eu-west-1.amazonaws.com/modelwriter-releases/ITEA_RELEASE_3/repository/ https://s3-eu-west-1.amazonaws.com/modelwriter-releases/ITEA_RELEASE_3/repository_gpl/