UML

UML — Unified Modeling Language is a standard object-oriented modeling language, adopted by the OMG (Object Management Group) consortium as a formal standard in November 1997. It’s the result of the merger of three previous methodologies — the Booch Method, OMT (James Rumbaugh’s Object Modeling Technique) and Objectory (Ivar Jacobson’s) — carried out by the three creators, the Three Amigos, at Rational Software between 1995 and 1997.

How it works #

UML defines a set of standard diagrams for visually representing the structure and behaviour of a software system. Version 1.1 (1997) offered nine of them, organised in two families: structural (class diagram, object diagram, component diagram, deployment diagram) and behavioural (use case, sequence, collaboration, statechart, activity). The current version, UML 2.5, offers thirteen — but the core of the most-used types has remained stable.

What it’s for today #

For years UML was the universal language of enterprise architectural documentation. Today its adoption is more selective: it lives on in public-administration technical specifications, in ISO certification projects, and in academic contexts where teaching object-oriented modeling is part of the curriculum. For new software projects the space has been eroded by freer diagrams (Mermaid, draw.io, architecture decision records in markdown) that carry its spirit without the formal syntax.

What sets it apart from alternative languages #

Unlike Mermaid or the C4 Model (more informal and suited to developer-to-developer communication), UML is a formal standard: every symbol has a precise semantics defined by the OMG specifications, every diagram is unambiguously interpretable. This formality is its strength in contexts where a common language between organisations is needed — public tenders, certifications — and its limitation when a small team wants to communicate quickly.