Editing Unified Modeling Language (section)

== Diagrams ==
{{UML diagram types}}

UML 2 has many types of diagrams, which are divided into two categories.<ref name=":0" /> Some types represent ''structural'' information, and the rest represent general types of ''behavior'', including a few that represent different aspects of ''interactions''. These diagrams can be categorized hierarchically as shown in the following class diagram:<ref name=":0" />

[[File:UML diagrams overview.svg|class=skin-invert-image|center|600px|Hierarchy of UML 2.2 Diagrams, shown as a [[class diagram]]]]

These diagrams may all contain comments or notes explaining usage, constraint, or intent.

=== Structure diagrams ===
Structure diagrams represent the static aspects of the system. It emphasizes the things that must be present in the system being modeled. Since structure diagrams represent the structure, they are used extensively in documenting the [[software architecture]] of software systems. For example, the [[component diagram]] describes how a software system is split up into components and shows the dependencies among these components.

<gallery class="center skin-invert-image" style="width: initial">
Policy Admin Component Diagram.PNG|[[Component diagram]]
BankAccount1.svg|[[Class diagram]]
</gallery>

=== Behavior diagrams ===
Behavior diagrams represent the dynamic aspect of the system. It emphasizes what must happen in the system being modeled. Since behavior diagrams illustrate the behavior of a system, they are used extensively to describe the functionality of software systems. As an example, the [[activity diagram]] describes the business and operational step-by-step activities of the components in a system.

<gallery class="center skin-invert-image" style="width: initial">
Activity conducting.svg|[[Activity diagram]]
UML Use Case diagram.svg|[[Use case diagram]]
</gallery>

Visual Representation: Staff User → Complaints System: Submit Complaint Complaints System → HR System: Forward Complaint HR System → Department: Assign Complaint Department → Complaints System: Update Resolution Complaints System → Feedback System: Request Feedback Feedback System → Staff User: Provide Feedback Staff User → Feedback System: Submit Feedback. This description can be used to draw a sequence diagram using tools like Lucidchart, Draw.io, or any UML diagram software. The diagram would have actors on the left side, with arrows indicating the sequence of actions and interactions between systems and actors as described. Sequence diagrams should be drawn for each use case to show how different objects interact with each other to achieve the functionality of the use case.