Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: DanG83616 on May 13, 2008, 03:59:28 am
-
I'm trying to treat components as sort of super classes. Components offer the concepts necessary to create software ICs as Brad Cox envisioned so many decades ago but I cannot get it to work. I can create a component (IC), add ports (pins), specify the supported or required interfaces (analogous to TTL, CMOS, rise-times, impedence, ...). I can put components into components just like creating macro cells. These things can be represented in class diagrams but with too much detail. All this is exciting and seems right on the cusp of real power.
BUT, when I put components into components the link between object and classifier is lost. Changes to the classifier don't affect the instance. When I make a composite out of a component, I lose the ports in the composite diagram. I cannot show the connection between the parent's ports and the internal component's ports. I'm frustrated because it seems like such a powerful construct but I cannot make it work.
Has anyone had better luck? Am I trying to do something the hard way?
Thanks, Dang
P.S. - I didn't do a very good job of phrase this rant in the form of a question. Sorry.
-
The "show owned/inherited" box in Embedded Elements dialog is what I should have been using. The inherited ports show up just like you would expect.
-
Thanks for closing the loop on this Dang. It will make life easier for the rest of us. I had not seen this either.