In some slides some Comments in UML/SysML diagrams are verbosely marked with the stereotype keyword «webel» to distinguish them from «snippet» domain source document text extracts.
Webel Parsing Analysis: Q: "Instead of using a Snippet, can't I just use a Requirement and Trace to achieve the same thing?" A: No! The Snippet is far more powerful and fit for purpose.
In the Webel Parsing Analysis recipe you are not obliged to map every single part of a Snippet's text extract to a UML or SysML model, just traceably elicit model elements of immediate or anticipated interest to your task or goal.
In Webel Parsing Analysis tutorials, Wikipedia pages are often used as a placeholder source to represent authoritative domain source documents from which text extract "snippets" are sourced, and from which SysML model elements are traceably elicited.
Overview of major Package Diagrams for the optical telescopes model Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model Section Slide kind hybrid diagram SysML Package Diagram
AplanaticGregorianReflector - finer image flow model Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model Section Slide kind SysML Internal Block Diagram (IBD)
AplanaticGregorianReflector - finer light flow model Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model Section Slide kind SysML Internal Block Diagram (IBD)
Webel Parsing Analysis diagrams do their job once - namely traceable elicitation of model elements - and are then only kept as a reference! The elicited model elements are then used elsewhere in the final model.
