architecture-format-core

Architecture Document Structure (Core)

[!NOTE] This is the CORE template for architecture documents. For sections 3–10 in full, with example templates and JSON samples, load architecture-format-extended. Figures in any section follow mermaid-authoring-guidelines; load it before the first figure.

Your architecture must contain the following sections:

---

1. Task Description

Link to TASK and brief summary of requirements.

---

2. Functional Architecture

Description of the system in terms of functions it performs.

2.1. Functional Components

For each functional component describe:

Component Name: [Example, "User Management"]

Purpose: [Why this component is needed]

Functions:

• Function 1: [Description]
  • Input: [what accepts]
  • Output: [what returns]
  • Related Use Cases: [UC-01, UC-03]

Dependencies:

• Depends on which other components
• Which components depend on it

2.2. Functional Components Figure (optional)

Draw a figure only when §2.1 states relations that a reader would otherwise hold in memory; otherwise leave this subsection out. Before the figure, load mermaid-authoring-guidelines: its Step 0 picks the form, and its rules draw the figure. A Mermaid figure takes this block:

**Figure [N].** [Title] — [one sentence: what the figure shows of §2.1].

```mermaid
[the settings line of the kind, then the figure]
```

[Legend: the notation this figure uses, one item per encoding.]

---

3. System Architecture

Description of the system in terms of physical/logical components.

3.1. Architectural Style

Which architectural pattern is used:

• Monolith
• Microservices
• Layered Architecture
• Event-driven
• Etc.

Justification: [Why this style was chosen]

3.2. System Components

For each system component describe:

Component Name: [Example, "User Service"]

Type: [Backend service / Frontend / Database / Message Queue / etc.]

Purpose: [Why needed]

Implemented Functions: [Links to functions from functional architecture]