An Abridged Guide to the Unified Modelling Language 2
This collection of pages present an abridged combination of The UML User Guide and The UML Reference Manual books, taking an 80-20 approach to The UML (80% of designs can be described using 20% of the UML). Refer to the published books for an in-depth understanding of The UML.
Start with the introduction page below and navigate sequentially, or jump direct to one of the sections:
What is a model? Why we model. UML, Architecture and SDLC. Systems, models and views.
The UML has three main concepts: things, relationships and diagrams.
Structural things, behavioural things, grouping things and annotation things
Dependencies, associations, generalisations and realisations.
Thirteen diagram types in two main classes: structural and behavioural diagrams.
Specifications, adornments, common divisions and extensibility mechanisms.
Architectural views and UML views.
Use case scenarios, logical designs, process interactions, development & implementation and physical deployment views.
Structural classification, dynamic behaviour, physical layout, model management.
Class diagrams, internal structure diagrams, collaboration diagrams, component diagrams and use case diagrams.
Class diagram, activity diagrams, sequence diagrams and communication diagrams.
Package diagrams and profiles.
Graphs (drawing), vertices (things) and arcs (relationships).
Class, object, composite structure, component, deployment, artifact and package diagrams.
The UML’s behavioural diagrams document the dynamic aspects of a system.
It’s only through using The UML that you gain experience of it and become proficient in it.
You can model 80% of most problems using 20% of the UML.
Visio is a very common modelling tool. Visio has its own stencils, but others are available.
Draw.IO (aka Diagrams.net) provides excellent browser-based and desktop alternative to Visio.
Quickly describe UML diagrams in text and PlantUML will convert them into diagrams.