Every example below is a complete architecture documentation of a real system, written along the same twelve-part arc42 structure. Different domains, different scales, different technologies — one structure, so you can read any two of them against each other.
Looking for short, section-sized illustrations instead? Those live with the template documentation at docs.arc42.org.
Demonstration
Sample System
A placeholder, here to show what a tile and a documentation look like.
Show every part of the site's structure with one example in place.
- One directory per system
- Markdown as the canonical source
- Twelve sections, always
- Jekyll
- Liquid
- SCSS
13 files · 0 users · never shipped
Customer relationship management
MaMa-CRM
Customer contact handling for mass-market campaigns.
Absorb a new mandator or campaign — new data structures, new file formats — without changing code.
- Persistence generated from a UML model
- DSLs for CSV and fixed-record formats
- Rule engine for campaign process control
- Images on the filesystem, not the database
- Java
- Hibernate
- Oracle
- JBoss
- Drools
- ANTLR
7–10 developers · 2–4 week iterations · ~15 months
No example matches that filter.