diagram-types

draw.io supports UML diagrams by providing specific notation rules and minimal XML examples for Class, Sequence, State, Activity, Component, Deployment, and Use Case diagrams. You can use these implementation examples to accurately represent system interactions and structures within the draw.io editor.

The difference between a C4 Model and a UML component diagram is scope: C4 provides contextual architecture levels from system to container, while UML component diagrams detail specific module interfaces and dependencies. This reference helps distinguish use cases to ensure accurate visual representation.

For BPMN 2.0 and ER diagrams, notation rules dictate specific shapes, symbols, and styling conventions for elements like events, gateways, entities, and relationships. This reference details these standards to ensure your process and data visualizations maintain structural accuracy.

Yes, you can use this reference to draw Kubernetes and cloud architecture diagrams. It includes specific notation guidance and draw.io implementation examples for mapping container orchestration topologies and cloud infrastructure components accurately.

You should use a swimlane diagram instead of a standard flowchart when you need to visually categorize process steps by department, role, or system. This reference explains selection criteria to distinguish when specific visualization formats best fit your process documentation needs.