Icon class icon_class far fa-sticky-note icon_class_computed far fa-sticky-note Note kind GOTCHA TOOL WARNING Specification keywords SysML-1.6 SysML-1.7 UML-2.5.1 UML keywords UseCase UseCase::subject MagicDraw:useCaseModel Keywords MagicDraw UML MagicDraw SysML Cameo Systems Modeler vendor-specific Webel Best Practice Relates to Figure D.5 - Establishing Top Level Use Cases for the Hybrid SUV Figure D.6 - Establishing Operational Use Cases for Drive the Vehicle UseCases - UML subject vs SysML Block Package, Model, or SysML Block as UseCase owner Related notes Related notes (backlinks) [DISPLAY, MODELLING, NAMING, NAVIGATION, POLICY, SETTINGS, STYLE, TIP, TOOL]{INFORMATIVE} Webel: SysMLv1: Overview of annotated Diagram Slides and Note pages related to general high level SysML modelling principles (some specific to MagicDraw/Cameo). Recommended reading for all Webel SysML/MBSE course attendees. [MODELLING]{INFORMATIVE} Webel: SysMLv1: Overview of annotated Diagram Slides and Note pages related to UseCases and their combination with a System (of interest), SystemContext, and drill-down to scenario Sequence Diagrams (Interactions) and Activity Diagrams. [CONVENTION, MODELLING, TIP] Webel: SysML for MBSE: The frequent recommendation that each UseCase have at least one "primary" scenario is a very useful and highly recommended CONVENTION (only). But it is not actually enforced by the SysML1.7 or UML2.5.1 metamodels or specifications. Related snippets (extracts) Visit also Visit also (backlinks) Flags
