Integrate Bitwalker Data and Papyrus/SysML

[jastram]

Request from Bernd:

we have need for accessing the defintions of SRS subset 26 sections 7 and 8
from SysML.
We want to build data definitions in Papyrus and Scade System.
We already have a definition of the types in XML and in Scade Suite's
Lustre.

[BerndHekele]

Thanks for the Issue, Michael,

One additional remark: you will find the current files in this location: https://github.com/openETCS/dataDictionary/tree/master/Artifacts

If you are not able to see the repository: please, let me know - I will give you read access.

[jastram]

TODO

• Decide whether this is a direct transformation, or an indirect, via the DataDictionary. Note, according to the timeliness of this issue, this should probably be direct for now, see Document the components and their interaction #202
• Create a Spec (Use the DataDictionary Spec as a template) and validate it with the stakeholders.
• Implement it.
• Integrate it in the Product

[jastram]

@astante offers to help, especially with implementation.

[jastram]

The first design specification is complete, please provide feedback (and update, as you see fit):

https://github.com/openETCS/dataDictionary-Tool-Development/wiki

[cecilebraun]

In what SysML element do we need these data ?

[astante]

I think the best way to make this data available is via creating an Eclipse Plugin that registers a UML Library. This Library can then be imported to a SysML model. It is the same mechanism that allows you to import for example Java or Ecore primitive Types to UML models.

What are the advantages?

• An already existing mechanism would be used
• Such a library could also be used with other SysML modeling tools and allows better reuse of this work

What is needed?

• A plan how the data dictionary can be modeled in UML
• Transformation from XML to UML
• Plugin which registeres the UML library and automatically calls the transformation during build process

For those who are interested how that would look like, in https://github.com/astante/openetcs-sysml-to-b I created a UML library for B primitive types. Instead importing ClassicalBPrimitiveTypes you would import something like OpenETCSDataDictionary.

It would be glad to hear comments about this propsal or other approaches to make the data available to Papyrus.

[jastram]

@astante thank you for the suggestion, which sounds promising. Once we have more information about the mapping from the SRS team, we can check whether your approach is compatible with what they need (I assume it is).

[MatthieuPERIN]

Hi evrybody,

I am not very active right now (working for the SysML formation) but I still keep an eyes on the issues.

I will ask the best "howto" for transforming an XML to an UML Profile to the guys from the Papyrus dev team and I will go back to you !

[cecilebraun]

Alexabder Stante had proposed this specification https://github.com/openETCS/toolchain/wiki/Integration-of-Data-Dictionary-into-Papyrus

The idea is to have an export mechanism of the bitwalker, from the data dictionnary and not a direct link

[BerndHekele]

We need the data definitions being useable inside the m,odelös in SysML. And we need the solution as quick as possible.

Best Regards
Bernd

[cecilebraun]

@BerndHekele, @UweSteinkeFromSiemens In which SysML artifacts do you need the data definition ?

• As Block ?
• As Data type
• Item Flow
• In a polymorphic way ?