This part settles what people actually mean when they say architecture documentation.

• The purpose and goals of documentation, seen from each stakeholder's angle
• Where it ends and requirements, user and operations documentation begin
• Notations from UML to the informal sketch, and when each one holds
• Matching documentation effort to the development process in use

This part builds the process by which documentation is planned and maintained across a team.

• Identifying target groups and goals before the first page exists
• Setting structure, roles and artifacts for shared maintenance
• Comparing and selecting arc42, C4 and ISO/IEC 42010 as templates
• Identifying application scenarios for GenAI in documentation

The largest part of the curriculum, with as much exercise time as teaching time.

• Building block, runtime and deployment views, and who reads each of them
• Architecture Decision Records carrying the decision and the options rejected
• Cross-cutting concepts, constraints, quality goals and technical risks
• Keeping the individual parts of a document set consistent with each other

This part answers what documentation is actually written and maintained with.

• Analog and digital tools, modeling tools and complete tool chains
• Defining requirements on tools and artifacts before anything is selected
• Docs-as-Code with PlantUML and versioning next to the source code
• Applying GenAI tools in support of architecture documentation

Here you draw the line between a documentation review and an architecture review.

• Checking whether documentation is fit for purpose rather than complete
• Content assessment against formal assessment, each with its own goals
• Writing your own checklists and question catalogues for reviews
• Taking the author, reviewer and facilitator roles in a review

To close, real documentation is on the table rather than another method.

• Real and representative case studies of documented software architectures
• arc42 by Example, which the curriculum names as an example
• Explaining the advantages and disadvantages of the documentation shown