"1st order" UML Parsing Analysis: stereotyped Comment as a simple source text container related to UML model elements by "handles"
An obvious way to indicate that a UML™ model is derived from (or in some way related to) some source text is to place a Comment on a relevant diagram with some "handles" drawn from the Comment to some "related" elements, as shown in the UML™ Parsing Analysis logo:
A handle from a Comment is however not a true UML Relationship, so I describe the Comment used this way as a non-relatable parsing container, because there is no way to trace from the Comment to the model repository elements (in UML tools the handle information is usually stored in additional tool-specific XMI extensions in a saved model project file).
Although limited, this approach is a good place to start experimenting; the Comment - being a true UML model element - can appear in many different diagrams, and changes in the text content in one place (in the Comment symbol in a diagram, or in the actual Comment element in model browser) propagate to other instances of the symbol.
UML™ Parsing Analysis example diagrams in this Webel site that use the Comment-with-handle approach are indicated with the following "note node", which has links to the diagrams it is applied to (open it in another window or tab) :
Here is another example:
This "1st Order UML™ Parsing Analysis" approach using Comments with handles is already quite useful - as illustrated by the many examples on this site - however it is ultimately limited by the fact that a handle is not a UML Element - it is merely a graphical symbol - so there is no way of tracing the "relationship" between a source text snippet and analysis elements in the UML model. Nevertheless, readers and students should definitely cut their teeth on UML™ Parsing Analysis with the Comment strategy first.
- Printer-friendly version
- Login to post comments
Zones
- IT zone
- UML zone
- Galleries meta-index: overview of all UML and SysML gallery groups
- 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
- 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
- Gallery: Tutorial: port-based software engineering with UML and Java
- Towards Executable UML
- Animated and simulated UML
- Java zone
- XML zone
- Drupal CMS zone
- SysML zone
- C++ zone
- Eclipse zone
- In MagicDraw UML, classifier-level sterotypes "show through" on symbols of instance level properties, unless that property has a visible (non-hidden) instance-level stereotype applied.
- Netbeans IDE zone
- Puredata synthesis zone
- Shibboleth zone
- Snippet-driven engineering: a meta-process for documentation-driven software and systems engineering
- Tools and Tips
- UML zone

















InformationFlow

