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
In UML/SysMLv1.x Lifelines do not have specific information about the times or time ordering of events (such as Message arrival/sending) of other Lifelines
12:01: Interactions [NOT COVERED] TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
The SysML diagrams Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:01: [BRIEF] SysML Overview Slide kind SysML Package Diagram
Figure D.10 shows the sequence of communication that occurs inside the HybridSUV when the vehicle is started successfully. Source OMG Systems Modeling Language (SysML) 1.6
The “hybridSUV” lifeline represents another interaction which further elaborates what happens inside the “hybridSUV” when the vehicle is started. Source OMG Systems Modeling Language (SysML) 1.6
Figure D.9 shows an interaction that includes events and messages communicated between the driver and vehicle during the starting of the vehicle. Source OMG Systems Modeling Language (SysML) 1.6
CombinedFragments are used to illustrate that steering can take place at the same time as controlling the speed and that controlling speed can be either idling, accelerating/cruising, or braking. Source OMG Systems Modeling Language (SysML) 1.6
To manage the complexity, a hierarchical sequence diagram is used which refers to other interactions that further elaborate the system behavior (“ref StartVehicleBlackBox”). Source OMG Systems Modeling Language (SysML) 1.6
Figure D.7 illustrates the overall system behavior for operating the vehicle in Sequence diagram format. Source OMG Systems Modeling Language (SysML) 1.6
