• 액티비티다이어그램 • 컴포넌트다이어그램 • 배치다이어그램 • 상태다이어그램 • 타이밍다이어그램 다음의 UML 이외의다이어그램도지원함: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 : To control control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML 언어참조가이드 (1.2021.2) 1 / 407 1.2 참여자 (participant) 선언 1 시퀀스다이어그램 as 키워드를이용하여참여자의이름을변경할수있다.

• 액티비티다이어그램 • 컴포넌트다이어그램 • 배치다이어그램 • 상태다이어그램 • 타이밍다이어그램 다음의 UML 이외의다이어그램도지원함: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 : To control control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML 언어참조가이드 (1.2021.2) 1 / 390 1.2 참여자 (participant) 선언 1 시퀀스다이어그램 as 키워드를이용하여참여자의이름을변경할수있다.

객체다이어그램 • 액티비티다이어그램 • 컴포넌트다이어그램 • 배치다이어그램 • 상태다이어그램 • 타이밍다이어그램 다음의 UML 이외의다이어그램도지원함: • JSON Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 : To control control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML 언어참조가이드 (1.2021.1) 1 / 385 1.2 참여자 (participant) 선언 1 시퀀스다이어그램 as 키워드를이용하여참여자의이름을변경할수있다.

• 액티비티다이어그램 • 컴포넌트다이어그램 • 배치다이어그램 • 상태다이어그램 • 타이밍다이어그램 다음의 UML 이외의다이어그램도지원함: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification 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 collections Collections 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 1.2 참여자 (participant) 선언 1

컴포넌트다이어그램 • 상태다이어그램 • 객체다이어그램 • Deployment diagram • Timing diagram 다음의 UML 이외의다이어그램도지원함: • JSON Data • Wireframe graphical interface • Archimate diagram • Specification and Description Language (SDL) actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 : To control control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML 언어참조가이드 (1.2020.23) 1 / 306 1.2 참여자 (participant) 선언 1 시퀀스다이어그램 as 키워드를이용하여참여자의이름을변경할수있다.

컴포넌트다이어그램 • 상태다이어그램 • 객체다이어그램 • Deployment diagram • Timing diagram 다음의 UML 이외의다이어그램도지원함: • JSON Data • Wireframe graphical interface • Archimate diagram • Specification and Description Language (SDL) actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 : To control control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML 언어참조가이드 (1.2020.22) 1 / 294 1.2 참여자 (participant) 선언 1 시퀀스다이어그램 as 키워드를이용하여참여자의이름을변경할수있다.

for loops use a concept called ”iterators” to handle iterating over different kinds of ranges/collections. Iterators will be discussed in more detail later. • for 반복문은 4 까지만 실행됩니다. 마지막 값을포함시키는 방법으로 1 structs (e.g. struct Foo;) might be used when implementing a trait on some type but don’ t have any data that you want to store in the value itself. – 다음 슬라이드에서는 필드 이름이 덜 중요할 때 사용할 수 있는 튜플구조체를 소개합니다. • they must be Sync. Interior mutability is possible through a Mutex, atomic or similar. Thread-local data can be created with the macro std::thread_local. 10.5 타입별칭 타입 별칭은 다른 타입의 이름을 생성합니다. 두 타입은 서로 바꿔서

for loops use a concept called ”iterators” to handle iterating over different kinds of ranges/collections. Iterators will be discussed in more detail later. • for 반복문은 4 까지만 실행됩니다. 마지막 값을포함시키는 방법으로 1 structs (e.g. struct Foo;) might be used when implementing a trait on some type but don’ t have any data that you want to store in the value itself. – 다음 슬라이드에서는 필드 이름이 덜 중요할 때 사용할 수 있는 튜플구조체를 소개합니다. • they must be Sync. Interior mutability is possible through a Mutex, atomic or similar. Thread-local data can be created with the macro std::thread_local. 10.5 타입별칭 타입 별칭은 다른 타입의 이름을 생성합니다. 두 타입은 서로 바꿔서

entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML 언어참조가이드 methods. Note that the syntax is highly flexible about type/name order. @startuml class Dummy { String data void methods() } class Flight { flightNumber : Integer departureTime : Date } @enduml You can use the corresponding item: Character Icon for field Icon for method Visibility - private # protected ~ package private + public @startuml class Dummy { -field1 #field2 ~method1() +method2() } @enduml

entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml PlantUML 언어참조가이드 methods. Note that the syntax is highly flexible about type/name order. @startuml class Dummy { String data void methods() } class Flight { flightNumber : Integer departureTime : Date } @enduml You can use the corresponding item: Character Icon for field Icon for method Visibility - private # protected ~ package private + public @startuml class Dummy { -field1 #field2 ~method1() +method2() } @enduml