The use case diagram describes the usage of a system (subject) by its actors (environment) to achieve a goal, that is realized by the subject providing a set of services to selected actors. Source OMG Systems Modeling Language (SysML) 1.7beta1
Actors represent classifier roles that are external to the system that may correspond to users, systems, and or other environmental entities. Source OMG Systems Modeling Language (SysML) 1.7beta1
An Actor specifies a role played by a user or any other system that interacts with the subject. Source Unified Modeling Language 2.5.1
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.
SysMLv1: MagicDraw/Cameo: Automated creation of usage-level allocation swimlanes in SysML Activity Diagrams for part properties of a Block. EXAMPLE: A UseCase scenario within a SystemContext as UseCase ‘subject’.
SysMLv1: UseCase scenario representations: On use of Activity Diagrams with swimlanes and/or Sequence Diagrams (Interactions): Actor or block-based custom «actor» on 1st (typically left) Lifeline/Swimlane, System/Subsystem on 2nd Lifeline/Swimlane
Webel: MBSE: SysMLv1: Prefer a custom «actor» extension of a Block (such as the non-normative External) over UML-style Actor for use as parts in IBDs and on allocation swimlanes. You can also have a Trace from a block-based «actor» to a UML-style Actor.
Webel Parsing Analysis: SysML: Pseudo Semantic Triple: A «pa:triple» may be applied to a uni-directional Association between SysML Blocks and/or Actors.
Webel Parsing Analysis: SysML: Pseudo Semantic Triple: A «pa:triple» may be applied to a Dependency between SysML Blocks and/or Actors or Properties typed by them.
UseCases may have associated Actors, which describe how an instance of the Classifier realizing the UseCase and a user playing one of the roles of the Actor interact. Source Unified Modeling Language 2.5.1
It may also be described indirectly through a Collaboration that uses the UseCase and its Actors as the Classifiers that type its parts. Source Unified Modeling Language 2.5.1
UseCases define the offered Behaviors of the subject without reference to its internal structure. These Behaviors, involving interactions between the Actors and the subject, may result in changes to the state of the subject and communications with its... Source Unified Modeling Language 2.5.1
A UseCase is a kind of BehavioredClassifier that represents a declaration of a set of offered Behaviors. Each UseCase specifies some behavior that a subject can perform in collaboration with one or more Actors. Source Unified Modeling Language 2.5.1
A UseCase may apply to any number of subjects. When a UseCase applies to a subject, it specifies a set of behaviors performed by that subject, which yields an observable result that is of value for Actors or other stakeholders of the subject. Source Unified Modeling Language 2.5.1
Figure D.29 - Requirements and VnV views exposing elements from the model (Package Diagram) Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6: HSUV sample Slide kind SysML Package Diagram
A Stakeholder stereotype can only be applied to UML::Actor or UML::Class which are not a UML::Association. Source OMG Systems Modeling Language (SysML) 1.6
A stakeholder represents a role, group, or individual who has concerns that will be addressed by the View of the model. Source OMG Systems Modeling Language (SysML) 1.6
Figure D.15 - Defining the Automotive Domain (Automotive Domain Breakdown) Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6: HSUV sample Slide kind SysML Block Definition Diagram (BDD)
Figure D.9 - Black Box Interaction for "StartVehicle", referencing White Box Interaction Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6: HSUV sample Slide kind SysML Sequence Diagram UML Sequence Diagram
Figure D.5 - Establishing Top Level Use Cases for the Hybrid SUV Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6: HSUV sample Slide kind SysML UseCase Diagram
The use case diagram for “Drive Vehicle” in Figure D.5 depicts the drive vehicle usage of the vehicle system. The subject (HybridSUV) and the actors (Driver, Registered Owner, Maintainer, Insurance Company, DMV) interact to realize the use case. Source OMG Systems Modeling Language (SysML) 1.6
Figure D.4 - Establishing the Context of the Hybrid SUV System using a User-Defined Context Diagram ARCHIVAL (2023): This content is now considered historical only! Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6: HSUV sample Slide kind SysML Internal Block Diagram (IBD)
