- Short answer
-
Please don’t fill in everything. Document only what your stakeholders need (you should ask them, one-by-one).
- Longer answer
-
Everything you document will potentially require maintenance effort in the future. With every piece of documentation, you’re effectively piling up maintenance debt - and in parallel creating some information value…
Please only document things, facts and reasons that you or your stakeholders consider important enough to justify written documentation.
Prefer to learn arc42 hands-on?
Practical architecture training, most classes taught by Peter Hruschka and Gernot Starke — the people who created arc42 and maintain this FAQ (dates with other trainers say so) — and solid preparation for iSAQB certifications.
Next dates
- 15–17 Sep 2026 DE Req4Arc · Frankfurt/Maingetting your requirements right
- 29 Sep–1 Oct 2026 EN Mastering SW Architectures · onlineperfect preparation for iSAQB CPSA-Foundation certification · with Wolfgang Reimesch
- 27–28 Oct 2026 DE ADOC · Züricharchitecture documentation · with Gernot Starke
- 24–26 Nov 2026 DE IMPROVE · Hamburgevolve and maintain systems · with Carola Lilienthal & Gernot Starke
- 1–4 Dec 2026 DE Mastering SW Architectures · Münchenperfect preparation for iSAQB CPSA-Foundation certification
- 23–25 Feb 2027 EN Mastering SW Architectures · onlineperfect preparation for iSAQB CPSA-Foundation certification · with Wolfgang Reimesch
- 2–5 Mar 2027 DE Mastering SW Architectures · Münchenperfect preparation for iSAQB CPSA-Foundation certification
- 9–11 Mar 2027 DE Req4Arc · Münchengetting your requirements right
All courses and dates: trainings.arc42.org · as of 25 Aug 2026