Some entities are known by more than one name, and sometimes the primary human-friendly name does not match a desired code-friendly element naming pattern.

It's important in such tutorial trails to use real-world examples wherever possible; there's nothing more real than the world of Roald Dahl:

Wikipedia: 'The BFG (short for The Big Friendly Giant) is a 1982 children's book written by British novelist Roald Dahl and illustrated by Quentin Blake.'

Wikipedia: 'The start of the book begins with an eight-year-old orphan girl named Sophie lying in bed ...'

Wikipedia: 'When he sets Sophie down, she begins to plead for her life, believing that the giant will eat her. The giant laughs and explains that most giants do eat human beings (which he pronounces as "human beans") ..'

Wikipedia: 'The giant then says that he will not eat her as he is the Big Friendly Giant, or BFG for short.'

Click on the image to view it full size

Tagged values for the «pa:term» stereotype keyword have been used to capture overloaded naming.

A code-friendly "French-style" ([util{vin rouge}]) post-adjectival naming pattern has been used for the block Giant_big_friendly, which has tagged values acronym = "BFG" and realName = "The Big Friendly Giant". For the sake of demonstration here he's also been given id = "G01" because he's the first giant mentioned.

It seems that a Human is also known as aka = "human bean". The human Sophie has been given id = "H01", since she's the first human bean ... sorry, human ... mentioned.

If you want to customise «pa:term» for your organisation, simply extend and adapt it or replace it completely.

Note also how some of the elicited members such as the Operation befriends(humanBeanFriend:Human) have been marked as «pa:implied».

Up next

«pa:triple»: Pseudo semantic triples (c.f. RDF/S and OWL)

Notes

[MODELLING, NAMING, POLICY]{STRICT} Webel Parsing Analysis: The name of a Parsing Analysis Diagram (PAD) may be drawn from a focus Snippet OR may simply indicate a topic of interest to the analysis

[DISPLAY, STYLE, TIP]{SUGGESTED} Webel Parsing Analysis: If the dashed-line "anchors" from your «snippet» ElementGroup symbols to elicited elements make a «pa» Parsing Analysis Diagram (PAD) too hard to read, try making them light grey using symbol properties.

[TIP]{EDITORIAL} In Webel Parsing Analysis every Package, Model, or Diagram used to perform Parsing Analysis MUST have the stereotype keyword «pa» applied, and MUST live under a top-level Model or Package 'source' separate from the rest of the project model.

[POLICY, STYLE]{STRICT} Webel «pa» Parsing Analysis Diagrams (PADs) are "scratchpads" used to elicit model elements traceably from text Snippets (extracts from source Documents). While BDDs are a good initial choice, most types of SysML diagram can be used as a «pa» diagram.

[MODELLING, NAMING, POLICY]{STRICT} Webel Parsing Analysis: Acronym: PAD = Parsing Analysis Diagram (may be nearly any diagram type, except those types that must be owned by an elicited model element)

[MODELLING, NAVIGATION, PATTERN, TIP, TOOL]{STRONG} Webel: UML/SysML: Navigation: ALWAYS offer a way out of a diagram (usually up a hierarchy, but possibly across) using a navigable symbol (linked to a diagram) and/or a diagram symbol. Avoid "cul-de-sacs"! [But beware of shared package cross-dependencies]

[TOOL]{INFORMATIVE} In MagicDraw/Cameo the dashed line symbol from a UML Comment or SysMLv1.x ElementGroup to an annotatedElement is called an 'anchor'.