<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>uml on toorun.dev</title><link>https://toorun.dev/tags/uml/</link><description>Recent content in uml on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/uml/index.xml" rel="self" type="application/rss+xml"/><item><title>Software Engineering Diagrams: A Practical Guide to Choosing the Right One</title><link>https://toorun.dev/posts/software-engineering-diagrams-practical-guide/</link><pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate><guid>https://toorun.dev/posts/software-engineering-diagrams-practical-guide/</guid><description>Software Engineering Diagrams: A Practical Guide to Choosing the Right One Diagrams make a system easier to discuss before or while it is being built. But a sequence diagram, a state machine, and an architecture diagram answer different questions. Picking the diagram by name alone can create detail without clarity.
Start with the question you need to answer. This guide covers common software, UML, data, and engineering diagrams, when they help, and how they fit together.</description></item></channel></rss>