http://blog.8thlight.com/uncle-bob/2011/09/30/Screaming-Architecture.html
Every software architects should remind himself of this once in a while! If we cannot make a direct and straightforward link between the functional documentation and the technical documentation, we are doing it wrong. If it takes more than 5 min. to find where a business rule is implemented in the code, we are doing it wrong. It’s easy to lose sight of the forest, but that is part of our duty and responsibility.
Imagine that you are looking at the blueprints of a building. This document, prepared by an architect, tells you the plans for the building. What do these plans tell you? [...]
Just as the plans for a house or a library scream about the use cases of those buildings, so should the architecture of a software application scream about the use cases of the application.
Architectures are not (or should not) be about frameworks. [...]
