Operations in instances of Components

[RonnyPutz]

Hi

In my current high level component diagrams, I had to use multiple instances of one component, to visualize a data flow.
For this I created a new instance of the original component by dropping it on the diagram and selected "add as instance". I created data flows etc and everything worked fine.
I also wanted to create a sequence diagram, trying to explain the call sequencens. There I figured out that in the messages I can select operations, I have created in the original component. But these methods are not available in the instances of the component.
Shouldnt the methods be also avialable there?

If I drop the component into the sequence diagram and add it there as lifeline. The methods are available.
Means:
- an instance created in a component diagram, does not support the methods in sequence diagram.
- an instance created in a sequence diagram, does support the methods in sequence diagram.

This sounds odd to me. I am using EA 15.2

[Richard Freggi]

Don't use component diagrams to visualized data flow.  That's not what they are for.
Study interaction diagrams.  This forum has a few posts about good books to learn UML.

[Paolo F Cantoni]

Don't use component diagrams to visualized data flow.  That's not what they are for.
Study interaction diagrams.  This forum has a few posts about good books to learn UML.

Wot 'e sed!

Plus, when you need multiple copies of an item on a diagram, use Virtual Connector Ends (VCEs).  Post available on the forum, also.

Paolo

[Modesto Vega]

Don't use component diagrams to visualized data flow.  That's not what they are for.
Study interaction diagrams.  This forum has a few posts about good books to learn UML.

It depends on what these flows represent. If they represent Information Flows, I don't see much of a problem using them in a high-level component diagram, they are certainly a permitted relationship between components.

Interaction diagrams are great but not sure I will call them a high level diagram.

[qwerty]

He's talking about SDs where instances of components are used. Not so sure about this, but I use SDs only for class instances, not for component instances.

q.

[Geert Bellekens]

He's talking about SDs where instances of components are used. Not so sure about this, but I use SDs only for class instances, not for component instances.

q.

That shouldn't be an argument, since a Component is a specialization of Class.

Geert

[RonnyPutz]

Hi

Thanks for the hints.
Simple said - what I wanted to represent is the relation / information between 2 instances of the same servie, which i drafted as component.


>That shouldn't be an argument, since a Component is a specialization of Class.
I also agree to that. And that was exactly also my assumption, that a intance of a coponent behaves like an instance of a class. Means I would assume i see all the methods of the parent.

Regards