UML (Unified Modeling Language) is a universal modeling language in the field of software engineering. It is designed to provide a standard way to visualize the design of a system by allowing the programmer to visually see what is required for the software you are working on. Many people believe that UML is not important to learn that it is simply just a time consuming task, and in some cases that is true, but while UML can be time consuming, it can. help more people understand the essence of a program that is being created. It allows everyone to be on the same page about what the end goal is and the means to achieve it. There are two types of UML diagrams are structural diagrams and diagrams Behavioral diagrams consist of diagrams such as class diagrams, component diagrams, and behavioral diagrams consisting of diagrams such as activity diagrams, communication diagrams, and timing diagrams show the composition of the software, while behavioral diagrams show what the software is doing. software step by step. Above is an example of a class diagram. It consists of three sections. The upper section contains the Class Name, it is necessary if we are talking about a classifier or an object. The central section contains the class Attributes. Attributes describe the variables of the class. This will tell you what type of data it is and whether it is public or private variables. This (↑) is an example of a component diagram. Shows the components that work together to create a system. The diagram names the objects, indicates the order and shows the steps to reach the next component. This diagram in particular shows the water cycle. This shows that he/she is constantly going… middle of the paper… he/she knows exactly what should happen step by step. It allows for a much simpler thought process. Another type of behavior diagram along with activity diagrams would be a sequence diagram. Sequence diagrams focus on the interactions that occur in the system. They show how objects communicate with other objects to perform a function. This diagram shows the system for creating a new event on a calendar and announcing it. This is generally what happens whenever you use something like Google Calendar to schedule something or other. First the form is requested and displayed, then it is filled in and the date is checked to verify its validity. If the date is valid, the event will be added to the schedule and an email alert will be sent. This type of diagram helps the reader understand which object is working with which other object and how it is doing so.