Software Architecture for Developers Quotes

“Any narrative should complement the diagram rather than explain it.”
― Simon Brown, Software Architecture for Developers: Volume 2 - Visualise, document and explore your software architecture

“All joking aside, these diagrams do suffer from one or more of the following problems:
• Notation (e.g. colour coding, shapes, etc) is not explained or is inconsistent. • The purpose and meaning of elements is ambiguous.
• Relationships between elements are missing or ambiguous.
• Generic terms such as “business logic” are used.
• Technology choices (or options, if doing up front design) are omitted. • Levels of abstraction are mixed.
• Too much or too little detail.
• No context or a logical starting point.”
― Simon Brown, Software Architecture for Developers: Volume 2 - Visualise, document and explore your software architecture

“colour coding to decipher. Can you work out what the colour coding means? Is it related to input vs output functions? Or perhaps it’s business vs infrastructure? Existing vs new? Buy vs build? Or maybe different people simply had different colour pens! Who knows.”
― Simon Brown, Software Architecture for Developers: Volume 2 - Visualise, document and explore your software architecture

“unlike the building industry, the software development industry lacks a standard, consistent way to think about, describe and visually communicate software architecture”
― Simon Brown, Software Architecture for Developers: Volume 2 - Visualise, document and explore your software architecture