Skip to content
Tagged articles

architecture documentation

7 articles · Page 1 of 1
Code Archaeology
Code Archaeology
Sep 7, 2026 · Fundamentals

Why C4 Starts with System Context Diagrams: A Step-by-Step Guide

This article explains why the C4 model begins with system context diagrams, detailing their purpose, key elements (people, software systems, relationships), notation conventions, and a step-by-step example of creating a context diagram for an online banking system integrating with core banking and email services.

C4 modelarchitecture documentationonline banking example
0 likes · 14 min read
Why C4 Starts with System Context Diagrams: A Step-by-Step Guide
TonyBai
TonyBai
Aug 1, 2026 · R&D Management

Why a Good Design Document Is More Crucial Than Ever in the AI‑Assisted Coding Era

As AI tools increasingly generate code, engineers must still decide when to write a design document, how detailed it should be, and what essential sections to include—project scope, requirements, technical solution, risk, and collaboration trace—to ensure sound decisions and effective reviews.

AI-assisted codingDesign Documentarchitecture documentation
0 likes · 18 min read
Why a Good Design Document Is More Crucial Than Ever in the AI‑Assisted Coding Era
YiSu Grain
YiSu Grain
Jul 16, 2026 · Fundamentals

Why One Architecture Diagram Isn’t Enough? Using the 4+1 View Model to Clarify a System

The article explains that a single diagram cannot capture all concerns of an internet‑hospital system, so architects should employ multiple viewpoints—logical, process, development, physical, and a scenario (+1) view—each tailored to different stakeholder needs and validated together.

4+1 view modelarchitecture documentationsoftware architecture
0 likes · 11 min read
Why One Architecture Diagram Isn’t Enough? Using the 4+1 View Model to Clarify a System
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Jun 30, 2021 · Fundamentals

Who Is Software Architecture Designed For? Exploring 4+1 Views and Documentation

This article examines the purpose of software architecture by identifying its diverse stakeholders, detailing the refinement process, illustrating the 4+1 view model with diagrams, outlining documentation practices, summarizing key takeaways, and previewing the next installment on deployment architecture.

4+1 viewarchitecture documentationsoftware architecture
0 likes · 4 min read
Who Is Software Architecture Designed For? Exploring 4+1 Views and Documentation