Book a Demo

Author Topic: Doubts with Composite, Ports and so on  (Read 4481 times)

Ronaldo Juliatto

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
Doubts with Composite, Ports and so on
« on: June 28, 2007, 04:05:36 am »
Hi all

I am trying to use a Component Diagram to model the architecture of a software item. I would like to do it with a Composite Component Diagram, as I don't think that the internals of the software item should be visible all the time. I wanted to be able to hide them and be able also to structure the related documentation in a better way. So, I guessed that the Composite Component Diagram would suit.

The problem is that I am not managing to reach some kind of understanding or know-how regarding to the way that the boundaries are related from the parent diagram to the child one. This is simple if I do it all in the same diagram, but as the number of levels get higher, the diagram gets too cluttered.

For example, if I have a port with an exposed interface at the parent component, which is delegated to and internal level, how do I represent this in the child diagram? How do I keep consistency from the parent component to the child ones, if they are in different diagrams?

I think that this seems to be a very basic question and I realize that I may be missing something. However, I have bee struggling with this for some time and would appreciate very much any kind of help.

Thanks in advance

Ronaldo Juliatto



thomaskilian

  • Guest
Re: Doubts with Composite, Ports and so on
« Reply #1 on: June 28, 2007, 09:32:30 am »
I think there are some threads here dealing with that. Try a search.

However, you can use embdedded elements (required and provided interfaces) inside embedded components. Now you can delegate internal interfaces to/from external interfaces.

Ronaldo Juliatto

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
Re: Doubts with Composite, Ports and so on
« Reply #2 on: June 29, 2007, 04:42:03 am »
Thanks, Thomas, for your answer

However, I think I couldn't express myself well.
Surely I can use exposed interfaces in embedded components and certainly I can delegate internal interfaces to/from external ones. That is ok.

The problem arises when I am using Composite. How do I represent the EXTERNAL exposed interfaces in the CHILD diagram? If I represent everything in a single diagram that is easy. But when I create a composite diagram, which leads to a child diagram of the embedded elements, I don't know what is the correct way to represent the boundaries of the external component without copying it.

I hope I could be clearer.

Thanks a lot.

Ronaldo Juliatto

thomaskilian

  • Guest
Re: Doubts with Composite, Ports and so on
« Reply #3 on: June 29, 2007, 05:43:39 am »
You could simply place the parent in the composite diagram and make it the right (big) size. Then you put the embedded elements inside.