. . . . . . 3 3.2. Component oriented frameworks - an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3. Benefits of component oriented frameworks for for web development. . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Wicket vs the other component oriented frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1. Hiding or disabling a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . 4 3.2. Component oriented frameworks - an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.3. Benefits of component oriented frameworks for for web development. . . . . . . . . . . . . . . . . . . . . . . . 5 3.4. Wicket vs the other component oriented frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1. Hiding or disabling a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . 3 3.2. Component oriented frameworks - an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3. Benefits of component oriented frameworks for for web development. . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Wicket vs the other component oriented frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1. Hiding or disabling a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . 3 3.2. Component oriented frameworks - an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.3. Benefits of component oriented frameworks for for web development. . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Wicket vs the other component oriented frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1. Hiding or disabling a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2023.11) PlantUML is a component that allows to quickly write : • Sequence diagram • Usecase diagram • Class diagram • Object diagram • Activity diagram • Component diagram • Deployment diagram hidden or removed later, because hide and remove command will consider the name a $tag instead of a component name. To later remove such elements they must have an alias or must be tagged. @startuml class SYNTAX) PlantUML Language Reference Guide (1.2023.11) 155 / 550 7 COMPONENT DIAGRAM 7 Component Diagram Component Diagram: A component diagram is a type of structural diagram used in UML (Uni- fied Modeling

Let’s have few examples. Advantages of PlantUML: • Simplicity: With PlantUML, you can create component diagrams using simple and intuitive text-based de- scriptions, eliminating the need for complex ключевое слово component для объявления компонента. Вы можете объявить алиас с помощью ключевого слова as. Этот алиас может быть использован позже, при объявлении связей. @startuml [First component] [Another [Another component] as Comp2 component Comp3 component [Last\ncomponent] as Comp4 @enduml 7.2 Интерфейсы Для обозначения интерфейса используется символ () (потому что он выглядит как круг). Также возможно

(Version 1.2021.2) PlantUML is a component that allows to quickly write : • Sequence diagram • Usecase diagram • Class diagram • Object diagram • Activity diagram • Component diagram • Deployment diagram 125 / 415 7 COMPONENT DIAGRAM 7 Component Diagram Let’s have few examples. 7.1 Components Components must be bracketed. You can also use the component keyword to define a component. And you can define alias will be used later, when defining relations. @startuml [First component] [Another component] as Comp2 component Comp3 component [Last\ncomponent] as Comp4 @enduml 7.2 Interfaces Interface can be

uns ein paar Beispiele an. Advantages of PlantUML: • Simplicity: With PlantUML, you can create component diagrams using simple and intuitive text- based descriptions, eliminating the need for complex drawing Komponenten Komponenten werden mittels eckiger Klammern definiert. Alternativ kann das Schlüsselwort component verwendet werden, um eine Komponente zu definieren. Mittels Schlüsselwort as lassen sich Aliase verwendet werden, wenn Beziehungen definiert werden. @startuml [First component] [Another component] as Comp2 component Comp3 component [Last\ncomponent] as Comp4 @enduml 7.2 Schnittstellen Schnittstellen

Let’s have few examples. Advantages of PlantUML: • Simplicity: With PlantUML, you can create component diagrams using simple and intuitive text- based descriptions, eliminating the need for complex drawing reservada component para definir un componente. Y puedes definir un alias, usando la palabra reservada as. Este alias será usado más adelante, cuando definamos relaciones. @startuml [First component] [Another [Another component] as Comp2 component Comp3 component [Last\ncomponent] as Comp4 @enduml 7.2 Interfaces Puedes definir una interfaz usando el símbolo () (porque esto luce como un circulo). Puedes usar

hidden or removed later, because hide and remove command will consider the name a $tag instead of a component name. To later remove such elements they must have an alias or must be tagged. @startuml class Let’s have few examples. Advantages of PlantUML: • Simplicity: With PlantUML, you can create component diagrams using simple and intuitive text- based descriptions, eliminating the need for complex drawing 컴포넌트는반드시대괄호 [] 로둘러싸여야한다. 컨퍼넌트를정의할때 component 키워드도사용할수있다. as 키워드를이용해서별명을정의할수도있다. 이별명은뒤에서관계를정의할때사용된다. @startuml [First component] [Another component] as Comp2 component Comp3 component [Last\ncomponent] as Comp4