Icon class icon_class far fa-sticky-note icon_class_computed far fa-sticky-note Note kind CAVEAT Policy level OPTION Keywords Webel Best Practice model query table query report generation report extraction Relates to Related notes [NAMING, POLICY]{STRONG} Prefer anonymous Actions, or if they must be named, prefer 'lowerCamelCase' or completely 'lower case' (if you do absolutely insist on having spaces in action names, but please no other punctuation). [NAMING, POLICY]{STRICT} SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase Related notes (backlinks) [MODELLING, NAMING, POLICY]{RECOMMENDED} Webel Parsing Analysis: An anonymous Element may be collected as a /member of a Snippet (it is not important whether collected elements list with a clear name under /member, only that they are traceably elicited). [DISPLAY, MODELLING, NAMING, STYLE]{OPTION} UML/SysML: In Internal Block Diagrams: If you have a Port with a name that indicates a unique role AND and if there is an ItemFlow on a Connector that implies or suggests the Type of the Port, consider hiding the Type on the Port symbol. [ASSERTION, MODELLING, NAMING, TIP]{STRICT} Webel: SysML: DO NOT sacrifice modelling naming conventions for the mere sake of carrying organisation-specific names! Instead use tagged values of custom stereotypes as metadata to carry alternative names in parallel with systematic model element names. [NAMING, POLICY, STYLE] "Trust the Port or Pin Type!" - Often the name of the Type of an anonymous Port or Pin is completely sufficient to indicate its role, unless a clear indication of its direction or unique role is required. [DISPLAY, MODELLING, NAMING, STYLE]{TIP} UML/SysML: In Internal Block Diagrams: Consider hiding the name of a named Port or Property in a Diagram if its Type is sufficient to indicate its role. [NAMING, POLICY, STYLE]{STRONG} "Trust the Type!" - Often the name of the Type of an anonymous Property or instance-level element is completely sufficient to indicate its role - unless multiple Properties of the same Type have different roles! Related snippets (extracts) Visit also Visit also (backlinks) Flags Book traversal links for If you are using model queries (such as table and report extraction) you may not always be able to use anonymous Property names and anonymous instance level element names Previous Up Next
