Chapter 8


An architecture practice exists to define and evolve the architecture of the system it oversees. Over the last few chapters, we’ve discussed how to manage a system’s evolution via a change process that starts from a motivation, moves on to a conceptual approach, and then produces a detailed design. Along the way, we’ve described how visions, standards, principles, catalogs, dictionaries, and more help support these practices. In short, an architecture practice produces a lot of information.

But how do you get that information into the hands of your colleagues, partners, and others? Not all of it should go to everyone, of course—we want to get the right information to the right people. While we’re at it, we should get ...

Get Effective Software Architecture: Building Better Software Faster now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.