role names on association ends [message #1378] |
Thu, 23 June 2016 15:16 |
Felix Prüter
Messages: 28 Registered: June 2016 Location: Berlin
|
Junior Member |
|
|
Hello,
I assume that all names on associations on the diagrams are role names.
If true, all these names should have a sigular or plural ending corresponding the related multiplicity.
e.g.
SpotLocation --> PositioningNetElement: 1 netElement
LinearLocation --> PositioningNetElement: 1..* netElements
ComposuitionNetElement --> ElementPartCollection: 0..* elementCollections
Kind regards
Felix
SIGNON Deutschland GmbH
--
Felix Prüter
SIGNON Deutschland GmbH
|
|
|
Re: role names on association ends [message #1386 is a reply to message #1378] |
Mon, 27 June 2016 10:54 |
christian.rahmig
Messages: 465 Registered: January 2016
|
Senior Member |
|
|
Dear Felix,
Am 23.06.2016 um 18:18 schrieb Felix Prüter:
> Hello,
> I assume that all names on associations on the diagrams are
> role names.
> If true, all these names should have a sigular or plural
> ending corresponding the related multiplicity.
> e.g.
> SpotLocation --> PositioningNetElement: 1 netElement
> LinearLocation --> PositioningNetElement: 1..* netElements
> ComposuitionNetElement --> ElementPartCollection: 0..*
> elementCollections
> [...]
Your assumption is correct. And we should keep it the same in the all
the diagrams. However, in railML3 UML, the role name always describes
one instance. For the XSD export, this results then in sth like this:
<linearLocation>
<netElement ref="..." />
<netElement ref="..." />
</linearLocation>
Here, netElement is the UML role name.
Best regards
Christian
--
Christian Rahmig
railML.infrastructure coordinator
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|