Icon class icon_class far fa-sticky-note icon_class_computed far fa-sticky-note Note kind ASSERTION TOOL Specification keywords SysML-1.6 SysMLv1.x keywords «system» «subsystem» «external» «domain» «system context» Keywords non-normative MagicDraw SysML Cameo Systems Modeler Relates to Figure D.4 - Establishing the Context of the Hybrid SUV System using a User-Defined Context Diagram Figure D.13 - Acceleration Requirement Relationships Figure D.17 - Internal Structure of Hybrid SUV Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram) Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram) [ANNOTATED] Package, Model, or SysML Block as UseCase owner GOTCHA: UML Component «subsystem» vs non-normative SysML «subsystem» Useful "user-defined" stereotypes for Blocks: «system context», «system», «subsystem», «external», «domain» IBD: Context for SimpleDomesticInverterAirCon IBD: Context for SimpleDomesticInverterAirCon - detailed Webel SE: pragmatic tool-friendly functional analysis: 2-level drill-down from a single Use Case via a «scenario» Activity with allocation to «logical» subsystems first then crossing to the «design» Blocks zone. Related notes Related notes (backlinks) [ASSERTION, TIP] The «Subsystem» stereotype for UML Components has nothing to do with the non-normative SysML «subsystem» stereotype for Blocks [ISSUE] It's not clear that the «domain» block 'AutomotiveDomain' is the best choice of owner for BDD Figure D.16, the «system» block 'Hybrid SUV' might be better. Related snippets (extracts) [SysML-1.6] The «system» and «external» stereotypes are user defined, not specified in SysML, but help the modeler to identify the system of interest relative to its environment. Visit also Visit also (backlinks) Flags
