1.1 Basic Examples In PlantUML sequence diagrams, the -> sequence denotes a message sent between two participants, which are automatically recognized and do not need to be declared beforehand. Utilize for users at all levels. 2.1 Usecases Use cases are enclosed using between parentheses (because two parentheses looks like an oval). You can also use the usecase keyword to define a usecase. And you MySql --> (Use) @enduml 2.10 Changing arrows direction By default, links between classes have two dashes -- and are vertically oriented. It is possible to use horizontal link by putting a single dash

arrow by using only the first character of the direction (for example, -d- instead of -down-) or the two first characters (-do-). Please note that you should not abuse this functionality : Graphviz gives foo bar ()- foo @enduml 3.26 Changing arrows orientation By default, links between classes have two dashes -- and are vertically oriented. It is possible to use horizontal link by putting a single dash arrow by using only the first character of the direction (for example, -d- instead of -down-) or the two first characters (-do-). Please note that you should not abuse this functionality : Graphviz gives

DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use Let’s have a few examples: 2.1 Usecases Use cases are enclosed using between parentheses (because two parentheses looks like an oval). You can also use the usecase keyword to define a usecase. And you MySql --> (Use) @enduml 2.10 Changing arrows direction By default, links between classes have two dashes -- and are vertically oriented. It is possible to use horizontal link by putting a single dash

DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use Let’s have a few examples: 2.1 Usecases Use cases are enclosed using between parentheses (because two parentheses looks like an oval). You can also use the usecase keyword to define a usecase. And you MySql --> (Use) @enduml 2.10 Changing arrows direction By default, links between classes have two dashes -- and are vertically oriented. It is possible to use horizontal link by putting a single dash

DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use Let’s have a few examples: 2.1 Usecases Use cases are enclosed using between parentheses (because two parentheses looks like an oval). You can also use the usecase keyword to define a usecase. And you MySql --> (Use) @enduml 2.10 Changing arrows direction By default, links between classes have two dashes -- and are vertically oriented. It is possible to use horizontal link by putting a single dash

DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use shadowing false command. 2.1 Usecases Use cases are enclosed using between parentheses (because two parentheses looks like an oval). You can also use the usecase keyword to define a usecase. And you usecase UC3 usecase (Last\nusecase) as UC4 @enduml 2.2 Actors Actor are enclosed using between two points. You can also use the actor keyword to define an actor. And you can define an alias, using

DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use Let's have few examples : 2.1 Usecases Use cases are enclosed using between parentheses (because two parentheses looks like an oval). You can also use the usecase keyword to define a usecase. And you usecase UC3 usecase (Last\nusecase) as UC4 @enduml 2.2 Actors Actor are enclosed using between two points. You can also use the actor keyword to define an actor. And you can define an alias, using

DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use Let's have few examples : 2.1 Usecases Use cases are enclosed using between parentheses (because two parentheses looks like an oval). You can also use the usecase keyword to define a usecase. And you usecase UC3 usecase (Last\nusecase) as UC4 @enduml 2.2 Actors Actor are enclosed using between two points. You can also use the actor keyword to define an actor. And you can define an alias, using

DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use Let's have a few examples: 2.1 Usecases Use cases are enclosed using between parentheses (because two parentheses looks like an oval). You can also use the usecase keyword to define a usecase. And you MySql --> (Use) @enduml 2.10 Changing arrows direction By default, links between classes have two dashes -- and are vertically oriented. It is possible to use horizontal link by putting a single dash

DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use Let's have a few examples: 2.1 Usecases Use cases are enclosed using between parentheses (because two parentheses looks like an oval). You can also use the usecase keyword to define a usecase. And you MySql --> (Use) @enduml 2.10 Changing arrows direction By default, links between classes have two dashes -- and are vertically oriented. It is possible to use horizontal link by putting a single dash