Chapter 11Describe the Architecture
Software architecture documentation has a reputation for being notoriously awful. It takes time away from writing code. It always seems to be out of date. It’s usually written in some proprietary binary file format that you can’t edit. And on top of all that, nobody reads it anyway! It’s no wonder some people call software architecture descriptions SAD!
Bad architecture descriptions make us sad. Great architecture descriptions give our team clarity of vision. Great architecture descriptions are a planning asset, a communication aide, and a collaboration tool. They improve the quality of the software we build ...
Get Design It! 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.
