Mention “UML” to a room of developers and you will get a few groans. The Unified Modeling Language has a reputation, earned in the 2000s, for enormous specifications and diagrams nobody read. But strip away the ceremony and a small core of UML is genuinely, practically useful — a shared visual language for explaining how a system is shaped and how it behaves. You do not need all fourteen official diagram types. You need about four. This guide covers the ones you will actually reach for, what each is good at, and when to draw which.<\/p>\n
Code tells you exactly what a system does but rarely what it means<\/em>. A diagram is lossy on purpose: it throws away detail to make structure and flow obvious at a glance. That is precisely what you want when onboarding a new teammate, designing a feature before writing it, documenting a database, or arguing through a tricky interaction on a whiteboard. A good diagram is the fastest way to get several people to share the same mental model.<\/p>\n An ER diagram models the data<\/strong> in a system: the things you store (entities), their fields (attributes), and how they relate to one another. Each entity becomes a box — Reach for it when<\/strong> you are designing or documenting a database. An ER diagram is the single best way to plan a schema before you write a line of SQL, and the fastest way to understand an unfamiliar database someone hands you. It maps almost directly onto tables, primary keys and foreign keys.<\/p>\n A class diagram is the object-oriented cousin of the ER diagram. Instead of database tables it shows classes<\/strong> — their attributes, their methods, and the relationships between them: inheritance (“a Reach for it when<\/strong> you are designing the object model of an application, explaining how a codebase is organised, or planning how a set of classes will collaborate before you build them. It is the go-to diagram for the static shape of object-oriented code.<\/p>\n Where the first two capture structure<\/em>, a sequence diagram captures behaviour<\/em>: the step-by-step conversation between parts of a system to accomplish one task. Vertical lifelines represent participants (a user, a service, a database), and horizontal arrows show the messages that pass between them, top to bottom, in order — including loops and conditional fragments.<\/p>\n Reach for it when<\/strong> you need to explain or design a specific flow: a login sequence, a payment being processed, an API request travelling through your services. When someone asks “wait, what actually happens when a user clicks buy?”, a sequence diagram is the answer.<\/p>\n A process (or activity) diagram is essentially a sophisticated flowchart: it shows a workflow as a series of steps with decision points, branches and parallel paths. It is less about software internals and more about the business process<\/strong> a system supports — approval workflows, order fulfilment, onboarding.<\/p>\n Reach for it when<\/strong> you are mapping a real-world procedure, aligning with non-technical stakeholders, or working out the branches a feature must handle before you code them. It is the most accessible UML diagram for a mixed audience.<\/p>\n ERPDesk<\/strong> is a clean, fast Windows UML designer for ER, class, process and sequence diagrams, with a searchable shape toolbox and multi-diagram projects. Its standout trick: design a table diagram and generate real SQL DDL<\/strong> (PostgreSQL, MySQL, SQL Server, SQLite) — or paste a 1. Entity-Relationship (ER) diagrams — for data<\/h2>\n
Customer<\/code>, Order<\/code>, Product<\/code> — and lines between them capture relationships and their cardinality: one customer has many orders; an order contains many products; a product belongs to many orders.<\/p>\n2. Class diagrams — for structure<\/h2>\n
SavingsAccount<\/code> is an<\/em> Account<\/code>“), composition (“an Order<\/code> has<\/em> LineItems<\/code>“), and associations.<\/p>\n3. Sequence diagrams — for behaviour over time<\/h2>\n
4. Process \/ activity diagrams — for flow and decisions<\/h2>\n
Which one do I draw?<\/h2>\n
\n\n
\n \nIf you want to show…<\/th>\n Use<\/th>\n<\/tr>\n<\/thead>\n \n What data you store and how it relates<\/td>\n ER diagram<\/strong><\/td>\n<\/tr>\n \n How your classes\/objects are structured<\/td>\n Class diagram<\/strong><\/td>\n<\/tr>\n \n The step-by-step flow of one interaction<\/td>\n Sequence diagram<\/strong><\/td>\n<\/tr>\n \n A business workflow with decisions and branches<\/td>\n Process \/ activity diagram<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n ERPDesk — A Fast UML Designer That Also Speaks SQL<\/h4>\n
CREATE TABLE<\/code> script and watch it become a laid-out diagram. Exports PNG\/SVG\/PDF, round-trips XMI, 100% offline. Free on the Microsoft Store.<\/p>\n