Home › IT zone › UML zone › UML Parsing Analysis zone › UML Parsing Analysis: notes and reusable policies ›

UML: MagicDraw UML: the "parasitic" «wrapper» Component strategy (whereby a "logical" Component does not "steal" ownership of a graphically contained element) is known to work in at least MagicDraw UML; it may not work in all UML2 tools.

[note] Submitted by webel on Sat, 20/12/2008 - 05:27
Used in
"2nd Order" UML Parsing Analysis: use a «wrapper» Component as a container for the source text, and relate it to model elements using a Relationship
Gallery: UML Parsing Analysis example: Wikipedia particle physics (from 2005)
Gallery: UML Parsing Analysis example: Wikipedia mathematics article (from 2005)
UML Parsing Analysis zone
7.3.45 Realization (from Dependencies)
Gallery: UML2 metaclass examples (MagicDraw UML eSchool versions, 2007-2008)
8.3.4 ComponentRealization (from BasicComponents)
CASE Study: a UML Parsing Analysis of UML2 Specification metaclasses, using «wrapper» Components as relatable parsing containers
Gallery: HOWTO use a UML2 Component as a graphical and/or logical «wrapper»
Physical ownership vs. logical grouping in MagicDraw UML
Examples of «wrapper» Components
Tutorial: the UML2 Component as a logical and graphical «wrapper» (MagicDraw-centric)
Related notes
UML: TIP: MagicDraw UML: DO NOT use reverse-engineered Components (like Class.java) as «wrapper» Components
UML: TIP: MagicDraw UML: unlike Package and Model, a Component does not always "steal ownership" of graphically contained elements.
UML: TIP: MagicDraw UML: wrap every major Class in a logical «wrapper» Component of the same name.
[book] Submitted by webel on Tue, 16/12/2008 - 14:54
Unified Modeling Language
OMG Systems Modeling Language
Java Get Powered
PHP
Powered by MySQL
Powered by Drupal
Lunarpages.com Web Hosting