Icon class icon_class far fa-sticky-note icon_class_computed far fa-sticky-note Note kind NAMING POLICY Policy level STRONG UML keywords Behavior Activity Classifier Keywords UML SysML Note however: Webel Best Practice: The name of a «testCase» Behavior may be verbose and may use natural language, but should always start with a Capital letter. Please be mindful of these: Webel Best Practice: SysML: Naming: You may include Block, ValueType, and Signal names in the names of Behaviors (such as Activities) as long as this does not undermine the principles of functional analysis and allocation. SysML: Naming: Including Block, ValueType, and Signal names in the names of Behaviors (such as Activities) can sometimes undermine purist functional allocation (because it may presuppose the element of the physical solution that carries out the function). Relates to Figure 14.7 Composite State with two States Figure 15-4: Behavior Allocation Satisfying Requirements and the Satisfy relationship Refrigerant cycle Activity allocation Related notes Related notes (backlinks) [MODELLING, NAMING, TIP]{STRONG} Webel: SysML: "Really long human friendly element names with spaces make my diagrams easier to read". Dr Darren says "No they don't! Prefer code-like naming (or anonymous for typed elements) wherever possible. Use custom tagged values for other names!" [ANTI-PATTERN, CAVEAT, MODELLING, NAMING, WARNING]{INFORMATIVE} SysML: Naming: You may include Block, ValueType, and Signal names in the names of Behaviors (such as Activities) as long as this does not undermine the principles of functional analysis and allocation. [ANTI-PATTERN, CAVEAT, MODELLING, NAMING, WARNING]{INFORMATIVE} SysML: Naming: Including Block, ValueType, and Signal names in the names of Behaviors (such as Activities) can sometimes undermine purist functional allocation (because it may presuppose the element of the physical solution that carries out the function). [CONVENTION, NAMING, POLICY] The name of a «testCase» Behavior may be verbose and may use natural language, but should always start with a Capital letter. [NAMING, POLICY, WARNING]{STRICT} DO NOT use Connector names that are identical to the names of the Associations that type them! [NAMING, POLICY, WARNING]{STRICT} DO NOT use Property names that are identical to the names of the Classifier (Class, DataType, Block, ValueType) that type them! [NAMING, POLICY]{STRICT} DO NOT use spaces in Property names or Class/Block names! If you want to communicate familiar names of elements within an organisation use a custom stereotype and tagged values (such as 'aka')! [NAMING, POLICY]{STRICT} When using acronyms in names of Classifiers either treat them as a word 'TlaLikeThis' or suffix with an underscore 'TLA_LikeThis', except at the end of the name 'LikeThisTLA' is admissable. [NAMING, POLICY]{STRONG} Use 'UpperCamelCase' (a.k.a. PascalCase) names for Classifiers such as UML Classes and SysML Blocks) to avoid confusion with 'lowerCase' Property names [see however special naming conventions for acronyms and SysML contract and flow Blocks] [NAMING, POLICY]{STRONG} Prefer anonymous Actions, or if they must be named, prefer code-like 'lowerCamelCase' or completely 'lower case' (if you do absolutely insist on having spaces in action names, but please no other punctuation). Related snippets (extracts) Visit also Visit also (backlinks) Flags Book traversal links for Prefer 'UpperCamelCase' (a.k.a. PascalCase) names for Behaviors such as Activities intended for use in CallBehaviorActions, or at least use a 'Capital first letter'; avoid 'all lower case' (as it leads to confusion with lower case Action names) Previous Up Next
