컴포넌트다이어그램 • 상태다이어그램 • 객체다이어그램 • Deployment diagram • Timing diagram 다음의 UML 이외의다이어그램도지원함: • JSON Data • Wireframe graphical interface • Archimate diagram • Specification and Description Language (SDL) PlantUML 언어참조가이드 (1.2020.23) 49 / 306 3.5 Defining visibility 3 클래스다이어그램 @startuml class Dummy { String data void methods() } class Flight { flightNumber : Integer departureTime : Date } @enduml You can use class User { .. Simple Getter .. + getName() + getAddress() .. Some setter .. + setName() __ private data __ int age -- encrypted -- String password } @enduml 3.8 Notes and stereotypes Stereotypes are

컴포넌트다이어그램 • 상태다이어그램 • 객체다이어그램 • Deployment diagram • Timing diagram 다음의 UML 이외의다이어그램도지원함: • JSON Data • Wireframe graphical interface • Archimate diagram • Specification and Description Language (SDL) PlantUML 언어참조가이드 (1.2020.22) 40 / 294 3.5 Defining visibility 3 클래스다이어그램 @startuml class Dummy { String data void methods() } class Flight { flightNumber : Integer departureTime : Date } @enduml You can use class User { .. Simple Getter .. + getName() + getAddress() .. Some setter .. + setName() __ private data __ int age -- encrypted -- String password } @enduml 3.8 Notes and stereotypes Stereotypes are

• 액티비티다이어그램 • 컴포넌트다이어그램 • 배치다이어그램 • 상태다이어그램 • 타이밍다이어그램 다음의 UML 이외의다이어그램도지원함: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification PlantUML 언어참조가이드 (1.2021.2) 53 / 407 3.5 Defining visibility 3 클래스다이어그램 @startuml class Dummy { String data void methods() } class Flight { flightNumber : Integer departureTime : Date } @enduml You can use class User { .. Simple Getter .. + getName() + getAddress() .. Some setter .. + setName() __ private data __ int age -- encrypted -- String password } @enduml 3.8 Notes and stereotypes Stereotypes are

• 액티비티다이어그램 • 컴포넌트다이어그램 • 배치다이어그램 • 상태다이어그램 • 타이밍다이어그램 다음의 UML 이외의다이어그램도지원함: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification PlantUML 언어참조가이드 (1.2021.2) 53 / 390 3.5 Defining visibility 3 클래스다이어그램 @startuml class Dummy { String data void methods() } class Flight { flightNumber : Integer departureTime : Date } @enduml You can use class User { .. Simple Getter .. + getName() + getAddress() .. Some setter .. + setName() __ private data __ int age -- encrypted -- String password } @enduml 3.8 Notes and stereotypes Stereotypes are

객체다이어그램 • 액티비티다이어그램 • 컴포넌트다이어그램 • 배치다이어그램 • 상태다이어그램 • 타이밍다이어그램 다음의 UML 이외의다이어그램도지원함: • JSON Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification PlantUML 언어참조가이드 (1.2021.1) 53 / 385 3.5 Defining visibility 3 클래스다이어그램 @startuml class Dummy { String data void methods() } class Flight { flightNumber : Integer departureTime : Date } @enduml You can use class User { .. Simple Getter .. + getName() + getAddress() .. Some setter .. + setName() __ private data __ int age -- encrypted -- String password } @enduml 3.8 Notes and stereotypes Stereotypes are

• 액티비티다이어그램 • 컴포넌트다이어그램 • 배치다이어그램 • 상태다이어그램 • 타이밍다이어그램 다음의 UML 이외의다이어그램도지원함: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification #aliceblue;line:blue;line.dotted;text:blue @enduml [Ref. QA-5340 and adapted from QA-6852] 2.18 Display JSON Data on Usecase diagram 2.18.1 Simple example @startuml allowmixing actor Actor usecase Usecase json "size":"Large", "color": ["Red", "Green"] } @enduml PlantUML 언어참조가이드 (1.2023.11) 58 / 551 2.18 Display JSON Data on Usecase diagram 2 유즈케이스다이어그램 [Ref. QA-15481] For another example, see on JSON page. 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 class User { .. Simple Getter .. + getName() + getAddress() .. Some setter .. + setName() __ private data __ int age -- encrypted -- String password } @enduml 3.7 Notes and stereotypes Stereotypes are AbstractList abstract AbstractCollection interface List interface Collection List <|-- AbstractList Collection <|-- AbstractCollection Collection <|- List AbstractCollection <|- AbstractList AbstractList <|--

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 class User { .. Simple Getter .. + getName() + getAddress() .. Some setter .. + setName() __ private data __ int age -- encrypted -- String password } @enduml 3.7 Notes and stereotypes Stereotypes are AbstractList abstract AbstractCollection interface List interface Collection List <|-- AbstractList Collection <|-- AbstractCollection Collection <|- List AbstractCollection <|- AbstractList AbstractList <|--

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 class User { .. Simple Getter .. + getName() + getAddress() .. Some setter .. + setName() __ private data __ int age -- encrypted -- String password } @enduml 3.7 Notes and stereotypes Stereotypes are interface List interface Collection PlantUML 언어참조가이드 (1.2019.1) 37 / 145 3.11 Using non-letters 3 클래스다이어그램 List <|-- AbstractList Collection <|-- AbstractCollection Collection <|- List AbstractCollection

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 class User { .. Simple Getter .. + getName() + getAddress() .. Some setter .. + setName() __ private data __ int age -- encrypted -- String password } @enduml 3.7 Notes and stereotypes Stereotypes are AbstractList abstract AbstractCollection interface List interface Collection List <|-- AbstractList Collection <|-- AbstractCollection Collection <|- List AbstractCollection <|- AbstractList AbstractList <|--