Architecture Diagrams

This is a historical learning note and may contain outdated or incomplete understanding.

1. Business Architecture Diagram

Explains the business process.

Explains which functional modules an application has and which technologies it uses.

1629028613625

Describes the users of the software system and what users can do.
In UML it is usually represented by a use-case diagram.
- Use-Case Diagram.md (related note not yet published)

Describes the functions of the software system, including both business functions (functions provided to users) and system functions (logging, permissions, etc.); it also includes module division and relationships between modules.
In UML it is represented by a class diagram.
- Class Diagram.md

Describes the static organizational structure of software in the development environment.
In UML it is usually represented by component diagrams and package diagrams.
- Component Diagram.md

Used to describe the communication sequence between system software components and data input/output.
In UML it is usually represented by sequence diagrams and flowcharts.
- Sequence Diagram.md
- Flowchart.md

Describes how the software system is deployed on hardware and networks.
- The physical environment may be physical devices such as servers, PCs, and mobile terminals.
- The software environment may be virtual machines, containers, processes, or threads.
In UML it is represented by a deployment diagram.
- Deployment Diagram.md

Chapter 3.1.2 of Software Revolution in the Internet Era - SaaS Architecture Design.pdf.