Why Architects’ Diagrams Look Great: Essential UML Tool Recommendations

Diagram Quality Criteria

Accuracy

Content expressed without error

No ambiguity

Conforms to standards and specifications

Clarity

Clear structural hierarchy

Moderate information density

Key points instantly recognizable

Readability

Comfortable colour scheme

Reasonable layout

Clear annotations

Conformance

Follows UML (or team) conventions

Correct symbol usage

Consistent naming

Common Architecture Diagram Types

Logical Architecture – shows system functional partitioning; typical symbols: rectangles, arrows

Technical Architecture – shows technical components; typical symbols: boxes, connectors

Deployment Architecture – shows deployment relationships; typical symbols: servers, network icons

Sequence Diagram – shows interaction order; typical symbols: swimlanes, arrows

Flowchart – shows business processes; typical symbols: diamonds, rectangles

UML Basics

UML = Unified Modeling Language, the standard modelling language for architects.

Common UML Diagrams

1. Use Case Diagram

┌─────────────────────────────┐
│      网上购物系统            │
│                             │
│   ┌─────┐                 │
│   │下单 │ ← 用户          │
│   └─────┘                 │
│                             │
│   ┌─────┐                 │
│   │支付 │ ← 用户          │
│   └─────┘                 │
│                             │
│   ┌─────┐                 │
│   │发货 │ ← 商家          │
│   └─────┘                 │
└─────────────────────────────┘

2. Class Diagram

┌───────────────────────┐
│        User            │
├───────────────────────┤
│ - userId: Long        │
│ - username: String   │
│ - password: String   │
├───────────────────────┤
│ + login()             │
│ + logout()            │
│ + updateInfo()        │
└───────────────────────┘

3. Sequence Diagram

用户        前端        后端        数据库
 │           │          │           │
 │──请求登录─→│          │           │
 │           │──调用API→│           │
 │           │          │──查询──→│
 │           │          │←─结果───│
 │           │←─返回───│           │
 │←─登录成功─│          │           │

4. Component Diagram

┌─────────┐     ┌─────────┐
│  前端   │────→│ API网关 │
└─────────┘     └────┬────┘
                │
          ┌──────┼──────┐
          │      │      │
        ┌────▼─┐┌──▼──┐┌─▼────┐
        │用户服务││订单服务││商品服务│
        └──────┘└─────┘└──────┘

Tool Recommendations

Online Collaborative Tools

ProcessOn

Online use, no installation required

Rich template library

Supports collaborative editing

Free tier available

Advanced features require payment; offline unavailable

Suitable for team collaboration and rapid diagram creation

Draw.io (diagrams.net)

Completely free, no watermarks

Supports both local and online usage

Feature‑rich

Interface can be complex; collaboration features are weaker

Suitable for personal use and quick prototyping

Professional Design‑Oriented Tool

Visio

High professionalism and strong UML support

Widely recognised in enterprises

Windows‑only, paid software; collaboration features are weak

Suitable for enterprise environments and formal UML modelling

Code‑Based Tools

PlantUML

Generates diagrams from textual descriptions

Version‑control friendly and fully free

Automation‑friendly

Learning curve; UI less polished than GUI tools

Typical usage example:

@startuml
Alice -> Bob: 请求
Bob --> Alice: 响应
@enduml

Mermaid

Code‑generated diagrams, Markdown‑friendly

Native support in GitHub and GitLab

Limited style customisation

Suitable for technical documentation and blogs

Cloud‑Native Specialized Tools

Cloudcraft

Focuses on AWS architecture diagrams

Auto‑generates 3D visualisations

Rich AWS element library

Supports only AWS; free tier limited

Suitable for AWS‑centric cloud designs

Lucidchart

Team collaboration, rich template library

Integrates with many services

Requires payment; depends on online access

Suitable for enterprise collaboration

Diagram Creation Techniques

Layout Tips

Arrange from top‑to‑bottom, left‑to‑right; place important elements in the upper‑left

Group related elements together and use colours to distinguish groups

Leave whitespace; avoid overcrowding and keep spacing between elements

Colour Tips

Maintain consistency: same type of elements share the same colour; limit colours to five

Use meaning: green for success/normal, red for error/danger, blue for main flow

Annotation Tips

Clear annotations: appropriate font size, avoid covering other elements

Accurate annotations: use standard terminology and arrows to indicate direction

Diagram Creation Process

Define purpose

Identify audience, message, and usage scenario

Gather information

List system components, relationships, and data flows

Sketch layout

Draft a rough sketch to clarify structure before polishing

Refine & beautify

Adjust layout, choose colours, add annotations

Review

Self‑check, obtain peer review, then deliver