Papyrus integration plug-in with PRO-R proxy listnener

[cecilebraun]

No description provided.

[MatthieuPERIN]

@cecilebraun is this issue not a duplication of issue #349 ?

[cecilebraun]

For me, @MatthieuPERIN This is the follow up of #349

[MatthieuPERIN]

Work as started.
@jastram , @BerndHekele and @janWelte info and help is needed !

Remarks for the actual solution:

• Actually the link in ProR is static (not updated when linked SysML element is modified or deleted),
• Link with a block not working,

Now some questions on what have to be done:

• The proxy element is to be created when an SysML element is drag and drop from Papyrus to ProR, right ?
• What kind of proxy element have to be created: Requirements ? Comments ?
• Where do they have to be created: attached/inside the referenced element ? in a specific place ?
• As the link is static, how is manage the life-cycle of the proxy element ?
• Did the element has to be linked to ProR target (hyperlink, so on) ?

[jastram]

@MatthieuPERIN,

First, have you seen the specification? It's located here. You need to open it with openETCS, with the Essentials installed (for rich text rendering).

The proxy element is to be created when an SysML element is drag and drop from Papyrus to ProR, right?

Yes. Right now, the traceability plug-in handles the drop operation. Currently, it creates a proxy element in ProR. This means, within ProR, you see a link, and the content of the linked SysML element is shown inside ProR.

What kind of proxy element have to be created: Requirements ? Comments ?

The Problem: The link is currently only shown on the ProR side, not the Papyrus side. the goal of this effort is to make the link visible in Papyrus as well. To this end, a SysML requirement has to be created in Papyrus.

Where do they have to be created: attached/inside the referenced element ? in a specific place ?

The spec proposes to create a SysML requirement and to create an association between the linked element and that requirement.

As the link is static, how is manage the life-cycle of the proxy element ?

We propose this in two steps: First, only handle proxy element creation as a "proof of concept". Once this works, we have to decide whether we want synchronization in one or both directions.

Did the element has to be linked to ProR target (hyperlink, so on) ?

No, at least not initially. Having access to the ID of the corresponding ProR target would already be a huge help.

[janWelte]

@MatthieuPERIN,

Michael has already given you the main answers and I'm happy to present you the proff of concept objectives as defined in the specifications in person.

I just want to add one small point to the following point:

What kind of proxy element have to be created: Requirements ? Comments ?

The proxy element should be a SysML requirement associated to the SysML model element.
In addition a comment (providing the tag needed for SCADE traceability) shall be added to the SysML element.

[MatthieuPERIN]

Ok thanks for information !