Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » Defining Component interactions in Sequence Diagram(Messages according to an Interface)
Defining Component interactions in Sequence Diagram [message #1462343] Wed, 05 November 2014 13:27 Go to next message
Grischa Liebel is currently offline Grischa LiebelFriend
Messages: 14
Registered: October 2014
Junior Member
Hi again,

I'd like to draw a sequence diagram specifying the interaction between component instances.
E.g. I have a collaboration with two instances c0 and c1 of two component (i.e. properties c0 and c1 of type Component0 and Component1).
Additionally, Component1 is realising an interface I0 and Component0 is using it.

Now if I draw two lifelines I can specify that they represent c0 and c1.
However, if I draw a Message from c0 to c1, I can't use any operations that are specified in the Interface I0. If I create a new operation, I can't assign it to interface I0.

Is there a way to do this? Should there be one, or am thinking wrongly here?

Cheers,
Grischa
Re: Defining Component interactions in Sequence Diagram [message #1479218 is a reply to message #1462343] Wed, 19 November 2014 08:55 Go to previous messageGo to next message
Grischa Liebel is currently offline Grischa LiebelFriend
Messages: 14
Registered: October 2014
Junior Member
No one has an idea regarding this?
Re: Defining Component interactions in Sequence Diagram [message #1482206 is a reply to message #1479218] Fri, 21 November 2014 15:34 Go to previous messageGo to next message
Camille Letavernier is currently offline Camille LetavernierFriend
Messages: 926
Registered: February 2011
Senior Member
Hi Grischa,

I don't really understand your issue, especially this part:

Quote:
I can't use any operations that are specified in the Interface I0. If I create a new operation, I can't assign it to interface I0.


What do you mean "use any operations"? You can specify that an Operation is the Signature of a message. You may need to use the "Advanced" tab of the properties view to manipulate the "signature" property of the message.

Does this help?

Camille


Camille Letavernier
Re: Defining Component interactions in Sequence Diagram [message #1486766 is a reply to message #1482206] Tue, 25 November 2014 09:18 Go to previous messageGo to next message
Grischa Liebel is currently offline Grischa LiebelFriend
Messages: 14
Registered: October 2014
Junior Member
Hi Camille,

my idea was to define a component diagram according to the attached image (compDiag.png). Then, I want to define two properties c0 and c1 of type Component0 and Component1. These, I would then like to use in a sequence diagram and define an interaction based on the interface I defined in the component diagram.
However, Papyrus knows only the operations that Component1 owns, not the ones that it realises through an interface. I.e. in sequenceDiag.png, I can't choose op() from the existing operations. For that, I would have to use a property of type IProvides instead.
Is this intended?
Re: Defining Component interactions in Sequence Diagram [message #1488313 is a reply to message #1486766] Wed, 26 November 2014 13:55 Go to previous message
Christian Damus is currently offline Christian DamusFriend
Messages: 1207
Registered: July 2009
Location: Canada
Senior Member

Hi,

Component0 can also inherit operations from supertypes
(generalizations), but realized interfaces are not supertypes and their
features are not inherited. A classifier realizing an interface is
responsible for providing some appropriate realizations of the
interface's features, and the form that such realizations take is a
semantic variation point (I think). FWIW, I recall some version of the
UML specification giving an example of a model in a Java-based system
in which interface properties are realized in a class by getter and
setter operations.

HTH,

Christian

On 2014-11-25 09:18:42 +0000, Grischa Liebel said:

> Hi Camille,
>
> my idea was to define a component diagram according to the attached
> image (compDiag.png). Then, I want to define two properties c0 and c1
> of type Component0 and Component1. These, I would then like to use in a
> sequence diagram and define an interaction based on the interface I
> defined in the component diagram.
> However, Papyrus knows only the operations that Component1 owns, not
> the ones that it realises through an interface. I.e. in
> sequenceDiag.png, I can't choose op() from the existing operations. For
> that, I would have to use a property of type IProvides instead.
> Is this intended?
> <image>
> <image>
Previous Topic:Add decorators to UML view
Next Topic:Java Code Generation Plug-in
Goto Forum:
  


Current Time: Wed Aug 05 17:14:04 GMT 2020

Powered by FUDForum. Page generated in 0.02366 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top