Home › IT zone › UML zone › UML Parsing Analysis zone › UML Parsing Analysis: notes and reusable policies ›
UML Parsing Analysis: [subject, predicate, object] represented here by an Association with "directional" name (only) between Classes.
[note] Submitted by webel on Mon, 12/01/2009 - 10:12
- 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)
- Examples
- Gallery: UML Parsing Analysis demonstration: Wikipedia Shapes (from 2009)
- UML Parsing Analysis: notes and reusable policies
- TIP: the full benefit of UML Parsing Analysis can only be obtained through the physical and cognitive act of analysis and interpretation of text as an associative, graphical, UML model, not in just studying someone else's UML interpretation.
- The term 'UML Parsing Analysis' is not a trademark or an official OMG technology (whereas 'UML' is an OMG trademark).
- UML Parsing Analysis: 0th order: free text containers, no traceable relationship or binding between UML model elements and "parsed" source text, visual association only.
- UML Parsing Analysis: 1st Order: "physical" containment (ownership) of Comment by Package, Model, or Component.
- UML Parsing Analysis: 1st Order: uses Comments containing source text snippets with loose handle binding to UML analysis elements.
- UML Parsing Analysis: 2nd Order: DirectedRelationship (Dependency, Realization, ComponentRealization, Generalization) used to carry parsed text source snippet.
- UML Parsing Analysis: 2nd Order: «wrapper» Component used as (relatable) container for «source» text.
- UML Parsing Analysis: Each source text "wrapper" Component is hyperlinked to at least a dedicated "focus" class diagram, and possibly also to other UML diagram types.
- UML Parsing Analysis: InstanceSpecifications in "object diagrams" used to illustrate interpretation and/or understanding of «source» text.
- UML Parsing Analysis: STUB(S) ONLY, INCOMPLETE (NOT STABLE OR CONVERGED) !
- UML Parsing Analysis: [subject, predicate, object] represented here by an Association with "directional" name (only) between Classes.
- UML Parsing Analysis: example: note use of «stereotype» to indicate container of «editorial» text annotation.
- UML Parsing Analysis: example: note use of «stereotype» to indicate container of «source» text snippet.
- UML Parsing Analysis: example: there is more than one «source» of parsed and analysed text snippets indicated by different stereotypes.
- UML Parsing Analysis: no explicit binding of model elements to source text is shown.
- UML Parsing Analysis: old example, does not have clear binding of UML analysis elements to a "relatable parsing container" element with source text.
- UML Parsing Analysis: prefer indicate «editorial» remark with a «stereotype», to distinguish it from the «source» text; additionally also use a style (like italic font or background color) bound to the «stereotype».
- UML Parsing Analysis: prefer use a «stereotype» to indicate the parsed and analysed «source» text.
- UML Parsing Analysis: prefer use only one sentence of source text per "parsing container" ! Motto: "divide and conquer" !
- UML Parsing Analysis: the container Element of every «source» text snippet and «editorial» remark should be clearly stereotyped in the model, even if that «stereotype» is not displayed in every diagram !
- 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.
- 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



















