Webel Parsing Analysis: A "focus" Parsing Analysis Diagram (PAD) for one or more Snippets SHOULD always show the /member tagged value of every Snippet.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
DISPLAY
MODELLING
POLICY
Policy level
STRONG
Specification keywords
SysML-1.6
SysML-1.7
UML keywords
Diagram
Keywords
Compare with:
Webel Parsing Analysis: An "index" Parsing Analysis Diagram (PAD) showing a collection of Snippets may optionally (but need not always) show the /member tagged value of each Snippet.
Webel Parsing Analysis: If you wish to show a «snippet» comment symbol (with its body text) in a presentation diagram (that is NOT a «pa» diagram) remove the '/member' tagged value from display so the only visible tagged value is 'source'.
Relates to
Focus PAD for the Snippet 'The quick brown fox jumps over the lazy dog'
Focus PAD for the Snippet ''an English-language pangram — a sentence that contains all of the letters of the English alphabet'
PAD for eliciting the letters of an English-language pangram
REFERENCE CARD: Webel Parsing Analysis for SysML1.x: Snippet Customizations
Related notes
[ASSERTION]{STRICT} In Webel Parsing Analysis elicited model elements MUST eventually be moved out of the 'source' (or '0-source') Package/Model zone and under a main project Package/Model area. (Use the owner display option to check.)
[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 Parsing Analysis «pa» diagrams are NOT intended as final presentation diagrams! They serve merely to traceably elicit model elements, which may then be shown in other (typically much tidier) presentation diagrams elsewhere.
[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, POLICY, TOOL]{STRICT} Webel Parsing Analysis: As StateMachine Diagrams are always owned by an element that is not eventually under the Source Input Zone they should not be used as «pa» diagrams. Elicit States instead via the /member section of the specification dialog.
[POLICY]{STRICT} Webel Parsing Analysis: Create a top-level 'source' or '0-source' Package/Model SEPARATE from your project model. All source «document» elements and «snippet» extracts and «pa» diagrams MUST be ultimately owned by that top-level Package/Model as ancestor!
[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.
[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.
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)