Need OpenETCS perspectives in Papyrus

[MariellePetitDoche]

According discussion during SysML training, specific perspectives for the project in papyrus will be useful to develop a model in SysML following a common, methodology.

Objective: limit the number of elements (diagrams, nodes, links,...) which can be used to define the model.

At the beginning at least one perspective can be defined based on description of D2.4 (https://github.com/openETCS/requirements/blob/master/D2.4/D2_4.pdf).

[JonasHelming]

should this become part of openETCS or Papyrus?
@MatthieuPERIN

[MatthieuPERIN]

I think that wiil be provided as a part of OpenETCS toolchain, as this perspective may be probably very "ETCS" related.

[JonasHelming]

to make this clear, @MariellePetitDoche : I think you are talking about some kind of filter or profile for Papyrus, right?
@MatthieuPERIN : Could you point us to some documentation, how this is done in papyrus?

[MariellePetitDoche]

Yes, I am talking on filter on menu on papyrus and on the palette in papyrus.

But I agree that concern only the papyrus included in the openETCS tool.

(It is too early for me to speak on other items of the openETCS toolchain)

[cecilebraun]

From Scrum meeting 11.02.2014

• Reduce the available diagram
• Reduce the palette choice
• Define the behavioral constraints from D2.4
• find a way to add these constraints

[cecilebraun]

From scrum meeting 27.02.2014.
@MatthieuPERIN proposes to work on it

[MatthieuPERIN]

Actual talk with Papyrus dev team shows that limiting palette is quite difficult in Papyrus Kepler (improved in Luna using viewpoints) but we can:

• Add a custom part in the palette for our "Open ETCS modelling elements"
• Choose to hide by default the classic Papyrus palette to only shows the Open ETCS related elements (topic to be investigate)
• Hide everything in the palette for the diagram that should not be used.

I am still trying to improve the solution.