GOTCHA: UML Component «subsystem» vs non-normative SysML «subsystem»

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
14:01: UseCases in SysML
Topic level
AUXILIARY
UML keywords
Component
«Subsystem»
UseCase
UseCase::subject
SysML keywords
«subsystem»
Block
Slide kind
hybrid diagram
UML Profile Diagram
This slide concerns a subtle matter you could encounter in the MagicDraw SysML Plugin or Magic Cyber-Systems Engineer ® (Cameo Systems Modeler®) tools. Although the UML Component is not supported by SysML, it is present in the tools, and there is a UML-specific «Subsystem» stereotype for Component, which one could confuse for the non-normative SysML «subsystem» stereotype for Blocks:
Click on the image to view it full size
Up next
15:01: The Allocate relationship and functional analysis
Notes
[CAPABILITY, FEATURE, TOOL] MagicDraw/Cameo: Supports embedding of one or more Diagrams in another via the Diagram Overview feature. Awesome!
[ASSERTION, TOOL] SysML: The «system», «subsystem», «external», «domain» and «system context» keywords are for "user defined" block Stereotypes (they are not part of core SysML); they are supported in MagicDraw/Cameo as Non-Normative Extensions.
[ASSERTION, TIP] The «Subsystem» stereotype for UML Components has nothing to do with the non-normative SysML «subsystem» stereotype for Blocks
[CAPABILITY, TIP, TOOL] MagicDraw/Cameo: You can easily create your own extensions of Block to act as subjects of UseCases. The tool knows how to handle the rectangular ‘subject’ notation on Use Case Diagrams
Snippets (quotes/extracts)
Visit also
Visit also (backlinks)
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.
SysMLv1: A common misunderstanding: Just because a UseCase symbol appears inside the rectangle of a subject Classifier does NOT mean that it is owned by that Classifier and can only have that one Classifier as 'subject', and it does not imply ownership!
SysMLv1: "Should" the 'subject' of a top-level UseCase be a System or (a particular) SystemContext? Answer: Which one would you like to be correct!? [WITH EXTERNAL LINKS]
SysMLv1: MagicDraw/Cameo: Having a SystemContext as the 'subject' of each main UseCase plays nicely with the feature for automated creation of usage-level allocation swimlanes in SysML Activity Diagrams for part properties. But it's not the only way.
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)
Useful "user-defined" stereotypes for Blocks: «system context», «system», «subsystem», «external», «domain»