Frequently Asked Questions
What is a Deployment Diagram?
A Deployment Diagram is a UML structural diagram showing where software components physically run. Key elements: Nodes (3D box — hardware like Web Server, Database Server, Client Laptop, Mobile Phone), Artifacts (rectangles — deployed software like WebApp.war or app.apk), Communication Paths (lines between nodes labeled with protocol like HTTPS, TCP/IP, JDBC). Deployment Diagrams answer "how is this system physically deployed?"
When should I include a Deployment Diagram in my capstone?
Include when: (1) Your system is web-based (client browser + web server + database server). (2) Your system spans multiple devices (mobile app + backend API + database). (3) You integrate with cloud services (AWS, Azure, Firebase). (4) Your panel asks "how is this deployed?" Skip for local-only desktop apps where everything runs on a single laptop — a Deployment Diagram for a single node adds no insight.
What is the difference between Deployment Diagram and Component Diagram?
Component Diagram shows WHAT software components exist and how they connect logically. Deployment Diagram shows WHERE each component physically runs (which server, laptop, mobile device). Most capstones with web/cloud deployment include BOTH: Component for logical architecture, Deployment for physical topology with concrete hardware names.
What is a node and what is an artifact?
A node (3D cube/box) is a physical or virtual hardware unit — Server, Cloud VM, Mobile Device, IoT Sensor. An artifact (rectangle, optionally with a document icon) is a deployable file — WebApp.war, app.apk, database.sql, model.pkl. Artifacts are PLACED inside nodes. One node can contain multiple artifacts (e.g., the Web Server node contains both the WebApp.war and the auth-microservice.jar).
Should I label communication paths with protocols?
Yes — it tells the panel HOW nodes talk to each other. Common labels: HTTPS (web-to-server), JDBC (web-to-database), TCP/IP (generic network), MQTT (IoT), gRPC (microservices), AMQP (message queues). This information directly impacts security and performance discussion in Chapter 5. Unlabeled lines force the panel to guess.
What free tool should I use to draw a Deployment Diagram?
draw.io / diagrams.net — free, web-based, has UML Deployment shapes (3D node box, artifact rectangle, communication path). Lucidchart Free — prettier. Visual Paradigm Community — full UML support with auto-layout. PlantUML — text-based, version-controllable. AWS/Azure architecture-specific tools (Cloudcraft, Azure Architecture) for cloud capstones. Start with draw.io.
How often is this Deployment Diagram collection updated?
New Deployment Diagrams are added regularly, especially for cloud-deployed capstones (AWS, Azure, Firebase, Vercel). Existing diagrams are revised when UML 2.5.x notation updates. Last refreshed: May 2026.