Master UML Deployment and Activity Diagrams: A Practical Guide with B2C Example

1. Review of Previous Chapter

Previously we covered three UML diagram types: sequence diagram, component diagram, and state diagram.

2. Abstract

The focus of this article is on UML activity diagrams and deployment diagrams.

3. Chapter Outline

Review of previous chapter

Abstract

Chapter content

Deployment diagram and activity diagram

Chapter summary

Series progress

Preview of next chapter

4. Deployment Diagram

Definition

A deployment diagram describes how components are deployed onto nodes (hardware or software environments) and shows the system’s runtime structure.

Basic Elements

Node : the execution environment, which can be a software platform (e.g., operating system) or hardware resource.

Node instance : a specific instance of a node, denoted with an underline and colon.

Component container : a node may contain other nodes or components.

Relationships between nodes :

Unidirectional dependency

Bidirectional dependency

Communication

Example: Simple B2C System

The diagram shows a B2C system with nodes such as Browser, Registration System, Member Management, Procurement System, Publishing System, and Payment System, illustrating how each component interacts with the database and each other.

Summary of Deployment Diagram

Deployment diagrams are essential for visualizing where components run and how they are connected, providing a clear picture of the system’s runtime architecture.

5. Activity Diagram

Purpose

Activity diagrams describe dynamic behavior, showing the flow of control from one activity to another. They are similar to flowcharts but have distinct semantics.

Elements

Action state : represented by a rounded rectangle, atomic, non‑interruptible, and always leads to another state.

Activity state : composed of multiple action states or sub‑activities, non‑atomic, can have entry/exit actions and internal transitions.

Relationships

Control flow: arrows indicating transition direction.

Branch: decision points splitting into multiple paths.

Merge: converging multiple paths into one.

Swimlane: partitions activities by responsible actors or objects.

Object flow: shows how objects are used or produced by actions.

Examples

Illustrations depict action states, activity states, control flow, branching, merging, swimlanes, and object flows, reinforcing the concepts.

Summary of Activity Diagram

The section concludes with a B2C e‑commerce example, demonstrating how activity diagrams can model the product management workflow for members and sellers.

6. Chapter Summary

Deployment diagrams describe component placement on nodes, while activity diagrams model dynamic behavior and workflow. Both are fundamental UML tools for system analysis and design.

7. Next Chapter Preview

The upcoming article will discuss other UML diagram types and further analyze B2C system modules using appropriate modeling techniques.