|
| Re: Member End in association links in Use Case Diagrams [message #1691476 is a reply to message #1691431] |
Tue, 07 April 2015 13:58   |
|
Hi,
The UML models associations as classifiers that group of two or more
properties that are called its member ends (they are "association
ends"). The association may own these end properties, or the
associated classifiers may own the end properties, or some combination
thereof.
In the particular case of associations between use cases and actors,
the association has to own the ends because use cases and actors cannot
have properties. So, some of the usual controls that you would see for
association ends in, for example, a class diagram are not applicable
here.
This is all just the way UML associations work. There is nothing
specific to Papyrus, here.
Cheers,
Christian
On 2015-04-07 09:07:04 +0000, Quentin Carpentier said:
> I have some new questions, and I still hope someone could help me here.
>
> What are the "member ends" objects at each extremity of an association
> link between an actor and a UseCase ?
> What do they represent ?
>
>
> (I uploaded a picture of the properties of an association link with
> this message...)
>
> <image>
|
|
|
|
| Re: Member End in association links in Use Case Diagrams [message #1691540 is a reply to message #1691491] |
Wed, 08 April 2015 02:12 |
|
I don't know much about SysML. But, it is specified as a profile of
UML, so its associations are UML associations and therefore I would
expect the semantics of member ends to be similar.
Perhaps somebody else in the newsgroup with more knowledge of SysML can
clarify.
Cheers,
Christian
On 2015-04-07 15:20:05 +0000, Quentin Carpentier said:
> Thank you very much.
>
> I work more with SysML than UML, and I had never see any details about
> these member ends...
> Do you know if they still exist in SysML ?
|
|
|
Powered by
FUDForum. Page generated in 6.44333 seconds
] 
Search
Help
Register
Login
Home
