Skip to content
Matthias Bohlen

iSAQB® CPSA Advanced Level Workshop

Documenting software architecture

Create software architecture documentation, communicate it effectively, keep it easy to maintain. A two-day intensive workshop with Matthias Bohlen (20 CP for iSAQB® CPSA-A).

days
2
credit points
20
people max.
12
language
DE / EN
Book your seat ↓

Create software architecture documentation, communicate it effectively, keep it easy to maintain.

What it's about

In this workshop you learn a skill that matters a great deal for a project's success: documenting software architecture appropriately, so your audience likes to read it and you, as its authors, spend little effort maintaining it.

As an architect, you design an appropriate, traceable solution for your system. Do you also want different stakeholders to understand and value your documentation? Do you want developers to implement the solution correctly, and your design decisions to be reliably followed? In this workshop you learn the techniques that get you there.

iSAQB accredited training

Accredited training for the iSAQB® Certified Professional for Software Architecture, Advanced Level (CPSA-A). It counts for 20 credit points (20 methodical).

Content

  1. 01

    PurposeWhy document architecture?

  2. 02

    ReadersHow to talk to your readers first

  3. 03

    DecisionsHow to record decisions

  4. 04

    Architecture viewsWhich architecture views you need and how to document them

  5. 05

    InterfacesWhat makes a good interface description

  6. 06

    MethodHow documentation fits into a methodical approach and into your process models

  7. 07

    StructureHow good architecture documentation is structured so that people read it

  8. 08

    Templates and checklistsProven templates and checklists you can use right away

  9. 09

    ToolsTools to create and maintain documentation

  10. 10

    ReviewHow to evaluate documentation in a review, or have it evaluated

Who it's for

Software architects and developers who design or evolve systems. You should have experience in IT projects or product development. You don't need to know any particular technology or programming language to understand and take part. UML helps, but isn't required.

Prerequisites

Experience in IT projects or product development. No particular technology or programming language. UML helps, but isn't required.

Option: an agent day after the training

In the training you learn what makes good architecture documentation. On an optional agent day after it, you and your AI agent learn to create, review and maintain it together, on one example system all day.

You decide what the documentation is for. Your agent recovers decisions from emails and tickets and interviews you where the rationale is missing. It derives views from the code, reports where documentation and code disagree, and reviews your documentation from the perspective of different readers. You leave knowing which documentation work you can delegate, with documentation your coding agents understand and follow.

The day runs online or in person. To add it, ask your training partner, or get in touch with me for an in-house training.

Delivery

A balanced mix of talks and hands-on exercises. With my guidance, you learn in the group how to document your software architecture effectively and keep it easy to maintain later.

Online

Since 2020 I've also taught ADOC online, with Zoom (or Microsoft Teams if need be) as the video platform and Miro as an online whiteboard. I've built a fully equipped video studio with professional broadcast hardware for it.

Book your seat

AustriaAlbion AcademySee dates ↗GermanyAlbion AcademySee dates ↗SwitzerlandtecnovySee dates ↗

In-house for your company? Call +49 170 772 8545 or email mbohlen@mbohlen.de.