1
Uml Process / Re: Component/ports/interface + Comp. internals Mo
« on: June 28, 2006, 01:56:06 pm »
Hi again,
OK, hangs head, shakes it foolishly. I -though- I went through all of these options, well a month ago or so. Hmmmm, I am using a newer version (6.1.798 ), maybe thats my story : - ).
Yes, in fact, you can drop the Component described by the Composition Diagram onto the Composition Diagram. It then could be the "frame" for attaching the port and interface elements....So I have not tested an XMI export/import, but it seems reasonable - Thoughts?
Next issue...Recommendations for documenting systems level interfaces.
The Interface Lollipops do not have property sheets. On the other hand, the Interface element found on the Composite menu, a Class with an <<interface sterotype>> can be fully documented, and it can be associated with the Lollipop.
What is valid UML / best practice for documenting interfaces presented as Lollipops?
Thanks again!
OK, hangs head, shakes it foolishly. I -though- I went through all of these options, well a month ago or so. Hmmmm, I am using a newer version (6.1.798 ), maybe thats my story : - ).
Yes, in fact, you can drop the Component described by the Composition Diagram onto the Composition Diagram. It then could be the "frame" for attaching the port and interface elements....So I have not tested an XMI export/import, but it seems reasonable - Thoughts?
Next issue...Recommendations for documenting systems level interfaces.
The Interface Lollipops do not have property sheets. On the other hand, the Interface element found on the Composite menu, a Class with an <<interface sterotype>> can be fully documented, and it can be associated with the Lollipop.
What is valid UML / best practice for documenting interfaces presented as Lollipops?
Thanks again!