A good architecture only works if other people understand it, agree with it, and can build on it. Much of an architect's job is therefore communication: recording why decisions were made, showing how a system fits together, and guiding teams toward a shared direction. This final module covers the habits that make an architecture last.
You'll start with architecture decision records for capturing the reasoning behind important choices, then learn the C4 model for drawing clear diagrams at different levels of detail. After that you'll look at how to write a technical design document, and finish with how to lead and influence a team when you don't hold the authority of a manager.
Once you've finished the modules, move on to Projects to put what you've learned into practice.
The idea behind architecture decision records and how to use them to document design decisions and the reasons for them.
The four levels of the C4 model (context, container, component, and code) and when to use each one to describe a system.
A walkthrough of writing a technical design document, using a currency converter microservice as the example.
How to build influence through relationships and value rather than a title, a key skill for architects who lead without direct authority.