Provide a model organisation for Papyrus

[cecilebraun]

@UweSteinkeFromSiemens provides a model structure to do collaborative work with Papyrus see
https://github.com/openETCS/modeling/tree/master/ModelSpace

[UweSteinkeFromSiemens]

The task is to prepare a model and file structure for collaborative modelling in WP3. The model structure is given by the SysML model "WP3-TaskForce-Architecture" at https://github.com/openETCS/modeling/tree/master/model. Exactly for this model the structure shall be prepared and stored at https://github.com/openETCS/modeling/tree/master/ModelSpace/SysML. The structure shall be expandable in parallel to the growing model.

Please take as an advice what I did already for Scade Suite with the following capabilities:

• Each of the subblocks of "WP3-TaskForce-Architecture" has its own submodel and subproject, so that it can be assigned to exactly one person for modelling without unneccessarily affecting others.
• Integration models and projects are prepared for the stepwise integration of the submodels.
• Type definitions to be shared between several submodels reside in separate models and can be included as libs into each submodel where needed.
• The "ETCS Language" type definitions (subset 026-7, 026-8) are available in libs and can be used for modelling.
• Several basic types (for length, speed, acceleration, gradient, ...) for consistent internal usage in the models have been defined additionally.
• Each subproject is based upon the same project template and sets all required options.

Cooperation between different persons on the model structure requires the exclusive assignment of a submodel to only one person at time. Since github does not have this capability, it requires manual care between the participants until the tool chain has solved it.

A similar approach should be used for SysML modelling too.

[UweSteinkeFromSiemens]

The collaborative model and file structure for SysML should rely onto the openETCS tool chain with the requirements management and data dictionary integrated.

[MatthieuPERIN]

Solution proposed during the WP3 meeting on 2014.02.26 @ Munich:

• A document with precise process to create and modify the SysML document will be provided (@MatthieuPERIN)
• A test run will be held base on this document and the first WP3 action on core function (@MatthieuPERIN & @astante)

[MatthieuPERIN]

The test have not proving to be successful on WP3.

The document is under formatting and completion, a draft is present in the modeling repository.

[MatthieuPERIN]

On going, new issue found (see openETCS/modeling#35)