Home › IT zone › UML zone › UML Parsing Analysis zone › Tutorial: the UML Parsing Analysis recipe(s) ›
"0th order" UML Parsing Analysis: source text in UML text boxes as cosmetic "parsing container", no Relationships.
[book] Submitted by webel on Mon, 12/01/2009 - 17:49
One can naively "associate" or "relate" source text very loosely with UMLTM model elements by copying the source text as snippets (such as sentences) into UML text boxes - which are NOT true model elements) - and placing the text boxes near or amongst model elements in UML diagrams:
This can read quite well, a bit like a colourful book or poster, however it is extremely limited because:
- The source text snippets are NOT stored in the model repository (the UML tools store the text box data in XML extensions, which is also true of UML notes, whereas the Comment is a true model element).
- In most UML tools one can't even draw a handle (dashed line) from a text box to indicate a "relationship" to a model element (with a UML note one can at least draw a handle to a model element).
- A unique source text snippet in a UML text box or UML note can't appear robustly in more than one diagram, you have to copy and paste, and changes/edits to the original snippet won't propagate.
- The indicated "relationship" between the source text snippets and model elements can't be traced at all in the model !
Although one can make some pretty diagrams this way, in terms of information technology the approach it is next to useless, so I call this approach "0th order UMLTM Parsing Analysis". Old example diagrams and models employing this technique are indicated in this site by the following "note node" (which can be traced to many other examples):
Don't use UML text boxes and/or UML notes as containers for parsed source text snippets ! You need at least the Comment as a container for the parsed text snippets.
- Login to post comments
Zones
- IT zone
- UML zone
- Galleries meta-index: overview of all UML and SysML gallery groups
- UML metaclasses and metamodel overview
- UML Parsing Analysis zone
- Galleries index: UML Parsing Analysis examples
- Tutorial: the UML Parsing Analysis recipe(s)
- "0th order" UML Parsing Analysis: source text in UML text boxes as cosmetic "parsing container", no Relationships.
- "1st order" UML Parsing Analysis: stereotyped Comment as a simple source text container related to UML model elements by "handles"
- "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
- External: MagicDraw UML eSchool: UML Parsing Analysis tutorial trail
- Examples
- Gallery: UML Parsing Analysis demonstration: Wikipedia Shapes (from 2009)
- UML Parsing Analysis: notes and reusable policies
- Gallery: UML Parsing Analysis: miscellaneous examples and supplementary diagrams
- UML tools zone
- SysML zone
- UML: notes
- Galleries index: some miscellaneous (and curious) UML galleries
- Tutorial: some UML modelling and diagramming tips, tricks, and best practices
- Tutorial: the UML2 Component as a logical and graphical «wrapper» (MagicDraw-centric)
- UML for Software Development
- Towards Executable UML
- Animated and simulated UML
- Java zone
- XML zone
- Drupal CMS zone
- OMG zone
- C++ zone
- Eclipse zone
- Netbeans IDE zone
- Puredata synthesis zone
- Shibboleth zone
- Tools and Tips
- UML zone




















