entity • database • collections • queue @startuml participant Participant as Foo actor Actor as Foo1 boundary Boundary as Foo2 control Control as Foo3 entity Entity as Foo4 database Database as Foo5 actor Foo -> Foo2 : To boundary Foo -> Foo3 : To control Foo -> Foo4 : To entity Foo -> Foo5 : To database Foo -> Foo6 : To collections Foo -> Foo7: To queue @enduml PlantUML Language Reference Guide (1 11) 52 / 550 2.10 Changing arrows direction 2 USE CASE DIAGRAM @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

participante: • actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 Foo1 -> Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml Se puede renombrar un participante usando la palabra reservada as. Guía de Referencia Cambio de dirección de las flechas 2 DIAGRAMA DE CASOS DE USO @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

verwenden: • actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 Foo1 -> Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml Teilnehmer können mittels as umbenannt werden. PlantUML Sprachreferenz (1.2023.11) 2 / Anwendungsfälle mit den << und >> Symbolen hinzugefügt werden . @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

entity • database • collections • queue @startuml participant Participant as Foo actor Actor as Foo1 boundary Boundary as Foo2 control Control as Foo3 entity Entity as Foo4 database Database as Foo5 actor Foo -> Foo2 : To boundary Foo -> Foo3 : To control Foo -> Foo4 : To entity Foo -> Foo5 : To database Foo -> Foo6 : To collections Foo -> Foo7: To queue @enduml PlantUML 언어참조가이드 (1.2023.11) 2 / 551 PlantUML 언어참조가이드 (1.2023.11) 52 / 551 2.10 화살표방향변경 2 유즈케이스다이어그램 @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

entity（实体） • database（数据库） • collections（集合） • queue（队列） @startuml participant Participant as Foo actor Actor as Foo1 boundary Boundary as Foo2 control Control as Foo3 entity Entity as Foo4 database Database actor Foo -> Foo2 : To boundary Foo -> Foo3 : To control Foo -> Foo4 : To entity Foo -> Foo5 : To database Foo -> Foo6 : To collections Foo -> Foo7: To queue @enduml 使用 as 关键字重命名参与者。 你也可以改变演员或参与者的背景颜色。 来定义角色或者用例的构造类型。 PlantUML 语言参考指引 (1.2023.11) 49 / 538 2.10 改变箭头方向 2 用例图 @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

participant: • actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 Foo1 -> Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML Language Reference Guide (1.2019.4) 1 / 166 1.2 Declaring participant 1 SEQUENCE stereotypes while defining actors and use cases using << and >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

participant: • actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 Foo1 -> Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML Language Reference Guide (1.2019.3) 1 / 158 1.2 Declaring participant 1 SEQUENCE stereotypes while defining actors and use cases using << and >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

declare a participant: • actor • boundary • control • entity • database @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML Language Reference Guide (1.2019.1) 1 / 147 1.2 Declaring participant 1 SEQUENCE DIAGRAM stereotypes while defining actors and use cases using << and >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

participant: • actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 Foo1 -> Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML Language Reference Guide (1.2019.2) 1 / 159 1.2 Declaring participant 1 SEQUENCE stereotypes while defining actors and use cases using << and >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

참여자선언에다른키워드를사용할수있다. • actor • boundary • control • entity • database @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML 언어참조가이드 (1.2019.4) 1 / 165 1.2 참여자선언 1 시퀀스다이어그램 다른이름을이용하여참여자의이름을변경할수있다. 또한, 참여자 (actor stereotypes while defining actors and use cases using << and >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User