Unified Modeling Language (UML) is the standard tool for creating “blueprints” of software. Using UML, you can visualize, specify, design, and document artifacts of software systems. UML examples are suitable for modeling any system: from enterprise-wide information systems to distributed web applications and even embedded real-time systems. This is a very expressive language, allowing you to view the system from all points of view, relevant to its development and subsequent deployment. UML is a language for visualizing, specifying, constructing, and documenting artifacts of software systems. The language consists of a dictionary and rules that allow you to combine the words included in it and get meaningful constructions.
In the Unified Modeling Language example that we present, you can find ideas on how to deal with your own assignment. If you need to complete a task on a similar topic, the sample will greatly help you. Reading through the example is necessary to understand the issue. In any case, the following sample will be helpful.
UML: Overview and Examples
Unified Modeling Language (UML) was developed in the end of the 20th century as the general tool of representing object-oriented terms and diagramming methods during the process of system development. The issue at that time was that every developer represented system development processes using personal notation and nobody could remember and know every single way of representation.
Over time, UML has been modified, being adjusted to new techniques and standards. Now it consists of two major groups of diagrams: behavioral and structural. The first focuses attention on the behavior of models and classes, while structural is about the overall foundation and structure of the system and its processes.
For better understanding of UML, I would like to present you some simple diagrams.
The first is an activity diagram that shows the actions necessary to be performed in order to achieve some goal. Here is an activity diagram for creating an essay. It is simple and encompasses general points when writing it.
Actually, UML is a very simple tool, not just when being observed, but also when being developed. For you, to understand what is what, I will list and explain some concepts. First of all, it is necessary to specify its type. As we know there are only two types of UML diagrams. Since this diagram is about process behavior, it is of the behavioral type.
In the activity diagram, there are rectangles that signify actions necessary to be taken. The rhombus is for decision-making: usually there is a question in it, and two arrows coming out of it – for “yes” and for “no.” As you see, after making a plan for future works goes the question of whether each point in the plan was described, and there are two ways: if no, then it is necessary to search for information and make some notes. And if all points are already written, it is revision time. Simple enough. And the two circles are for the beginning and the end of the diagram.
As you see, there is nothing complicated: you just describe the situation or process in the algorithmic way through this type of notation (using rectangles, rhombuses, and circles).
Let’s observe other examples of another type of diagram – structural.
Below you can see a class diagram. The purpose of this diagram is to describe objects and their interactions within the system.
In this particular diagram, a course management system is proposed. There are student, professor, and course administrator objects (actors), and course schedule, topic, and course entities. Every object has its properties (attributes) and functions.
The administrator of the course is able to manage information about student, professor, course, and topic, and can assign professor to course and can make a course schedule.
“Managing” means creation, modification, and removal procedures.
All these actions and interactions are better to be viewed on the use case diagram where every actor can perform specific actions. So, have a look at the diagram below.
The use case diagram makes clearer who can do this or that action.
Dennis, Alan, Wixom, Barbara Haley, & Tegarden, David. (2015). Systems Analysis
and Design (5th ed.). John Wiley & Sons.