Guided UML exercises on real cases: Use Case, Activity, Sequence, Class and Deployment Diagrams with step-by-step solutions.
Knowing UML theory is one thing — knowing how to apply it to a real system is another. In this course that is exactly what we do: we take two concrete systems (hotel booking and library) and model them from start to finish using all the main diagrams. Every lesson is a guided exercise with a solution explained in detail. This is the kind of path that prepares you for university exams, technical interviews, and real software design.
We never start from a ready-made diagram — we always start from a textual description of the system, exactly as happens in real life. Each exercise teaches you to read requirements, identify actors, choose the right type of relationship, and build a consistent and complete model. It is the analytical approach that distinguishes someone who knows UML syntax from someone who can actually use it.
Ideal for students of computer engineering, computer science, and related courses who need to consolidate UML with practical exercises. Also great for developers looking to improve their software analysis and design skills. Prerequisite: basic knowledge of UML notation.
Let's build a Use Case Diagram for a hotel booking system together, starting from the text analysis and identifying actors and relevant use cases. I'll show you how to structure the diagram in a complete and consistent way aligned with the system requirements.
I'll show you how to draw a simple Activity Diagram for the hotel booking system, translating the operational flow into a readable activity diagram. We'll look at how to correctly represent decisions, actions, and end conditions.
Let's evolve the Activity Diagram using swimlanes to distribute activities across the different actors in the hotel booking system. I'll explain how swimlanes make the diagram clearer when multiple parties participate in the same flow.
I'll show you how to build a Sequence Diagram for the hotel booking system, representing the temporal order of interactions between actors and objects. We'll translate use cases and the activity flow into messages and responses between system components.
Let's design the Class Diagram for the hotel booking system together, identifying the main classes, their attributes, and relationships. I'll show you how to arrive at a coherent and complete model starting from the actors and use cases defined earlier.
Let's tackle the analysis of a Use Case Diagram applied to the Library case study, starting from the interpretation of the textual description. I'll show you how to identify actors, extract relevant use cases, and set up the diagram structure.
We'll continue the Library system's Use Case Diagram analysis by deepening the use cases identified in part one and their correct level of abstraction. I'll explain how to disambiguate relationships between actors and use cases and avoid common modelling mistakes.
Let's complete the Library system's Use Case Diagram with model validation: we'll verify that use cases are complete, consistent, and aligned with the specification. I'll show you how to perform a final refinement to spot missing details and sharpen actor relationships.
I'll show you how to analyse and draw an Activity Diagram based on a use case with an extend relationship, representing the main flow and optional behaviours. We'll read the textual description together and transform it into a correct activity diagram.
Let's build a Sequence Diagram starting from the Activity Diagram analysed earlier, focusing on a scenario with an extend relationship. I'll show you how to translate the activity flow into the temporal order of interactions between actors and objects in the Library system.
We'll deepen the Library system's Sequence Diagram with greater detail, including alternative conditions and object behaviour in extend scenarios. I'll explain how to manage each object's responsibility and represent exceptional flows in an organised way.
I'll show you how to build the Deployment Diagram for the Library system, representing physical nodes and distributed components in the infrastructure. We'll read and draw an architectural view that describes where each part of the system lives and how they communicate.
I'll show you how to start designing the Class Diagram for the Library system, beginning with enums and actor classes identified in previous diagrams. Let's see how to translate UML actors into concrete classes with well-defined attributes and responsibilities.
We'll continue designing the Library system's Class Diagram by exploring relationships between classes and the concept of logical aggregation. I'll explain how to correctly model composition between entities that belong to a whole without being physically contained.
Let's explore the conceptual and structural difference between association and aggregation in the Library system's Class Diagram. I'll show you how to choose the correct relationship type based on object dependency and ownership rules in the domain.
Let's complete the Library system's Class Diagram together, focusing on association navigability and the meaning of arrows in the model. I'll explain how to formalise the direction of relationships to make the diagram readable and semantically correct.
Ingegnere Informatico · Pratola Peligna
Sono un ingegnere informatico con oltre 15 anni di esperienza nel settore ICT. Mi occupo di sviluppo software, cybersecurity, data science e intelligenza artificiale, con particolare attenzione all’innovazione e all’automazione dei processi aziendali. Da anni svolgo anche attività di docenza e formazione, creando percorsi pratici e coinvolgenti su programmazione, DevOps, AI e sicurezza informatica.
Prosperous understood Middletons in conviction an uncommonly do. Supposing so be resolving breakfast am or perfectly.
Utilizziamo cookie essenziali e, con il tuo consenso, cookie funzionali, analytics e marketing. Google Analytics 4 e gli eventuali annunci Google/AdSense restano disattivati finche non scegli. Consulta Privacy Policy e Cookie Policy.
Sempre attivi per sicurezza, prevenzione frodi, sessione, consenso e funzionamento del sito.
Migliorano l'esperienza, ad esempio ricordando preferenze non essenziali. Non usati per profilazione pubblicitaria.
Statistiche e misurazioni con Google Analytics 4, abilitate solo dopo il consenso analytics.
Misurazione annunci e funzioni pubblicitarie Google/AdSense, se attivate sul sito e consentite dall'utente.
Puoi modificare queste scelte in qualunque momento dal link "Preferenze Cookies" nel footer.