Architectural Diagram
The Architectural Diagram shows the major components of the system and how they connect. Required in Chapter III as a figure.
Architectural Diagram
What this section does
A single figure showing the major components of the system - client devices, servers, databases, external services - and how they connect.
Sample architecture (Sample Bakery Shop)
Drawing rules
| Rule | Why |
|---|---|
| Group internal components | Trust boundary visible at a glance |
| Label every arrow | Reviewer knows the protocol |
| Show backup destination | Demonstrates recovery awareness |
| Show external services | Maps dependencies |
| Keep it on one page | Prints legibly when bound |
What to include
| Layer | Examples |
|---|---|
| Client devices | Tablet, desktop |
| Web server | Apache + PHP, nginx + Node, etc. |
| Database | MySQL, Postgres |
| External | SMS gateway, email, payment, identity |
| Backup | External drive, off-site copy |
| Network | LAN, Internet, VPN |
Caption + prose
Figure 3.1 presents the architectural diagram of the proposed system. Counter tablets and the owner's desktop connect over the local network to the Apache + PHP web server, which mediates all reads and writes to the MySQL database. The SMS notification service is invoked over HTTPS and delivers messages to customers via the public mobile network. A backup process snapshots the database nightly to an external drive.
Panel defense checklist
- [ ] Diagram includes all major components.
- [ ] Arrows show direction and protocol.
- [ ] External services clearly marked.
- [ ] Backup destination shown.
- [ ] Diagram captioned as Figure 3.1 (or per your numbering convention).
- [ ] Diagram references the components named in Operational Feasibility.
- [ ] Diagram readable when printed in black and white.
Mentor’s tip: One clear diagram showing every component, every arrow labelled with its protocol, internal trust boundary marked, backup included. Caption it Figure 3.1 and add a paragraph describing the flow.
Discussion
Loading…