Book a Demo

Author Topic: Re-using lollypop interfaces  (Read 2704 times)

andykennelly

  • EA User
  • **
  • Posts: 54
  • Karma: +0/-0
    • View Profile
Re-using lollypop interfaces
« on: April 24, 2013, 06:36:42 am »
I want to represent a component logically as a single entity (with its 2 interfaces) as well as physically across 2 other components (that implement 1 interface each). As part of that, I'm trying to create those interfaces once and re-use them across all components.
i.e. :- Component1 (the logical component) has 2 lollypop interfaces against it. This is (physically) implemented by Component2, which has 1 of the lolly pop interfaces against, and Component3, which has the other. I can maybe show some sort of link/dependency between Component2/Component3 and Component1 to indicate that the former are physical manifestations of the latter. However, I'm stumped how to make the interfaces re-usable (i.e. create them once, "independently" of the components,and then use them against the component elements as appropriate).
The only way I can see to do it is to create lollypop interfaces on their own and then drag them onto diagrams as links using a realize arrow to articulate the relationship with the between interface and component. However, that doesn't look as succint/tidy on a diagram as lollypops.

Should I be using ports? I've tried, but can't drag/drop an "independent" interface onto the port.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Re-using lollypop interfaces
« Reply #1 on: April 24, 2013, 08:57:03 am »
I'd use ports and add required/provided interfaces classified with the appropriate interface. From my experience the best approach.

q.