Software Architecture: The Hard Parts
1: Architect products; evolve from projects to products. Architecting products is more efficient than just designing point solutions to projects and focuses the team on its customers. Principle 2: Focus on quality attributes, not on functional requirements. Quality attribute requirements drive the architecture. Principle 3: Delay design decisions u
... See morePierre Pureur • Continuous Architecture in Practice: Software Architecture in the Age of Agility and DevOps (Addison-Wesley Signature Series (Vernon))
The engineering practices in continuous delivery address the factors that slow down software releases, and those practices should be considered axiomatic for evolutionary architecture to be successful.
Rebecca Parsons • Building Evolutionary Architectures: Support Constant Change
A corollary of Conway’s Law is that an organization’s structures themselves can be constrained by the architectures that they designed many years earlier. And without intentional action, it’s a Catch-22. “We cannot solve our problems with the same level of thinking we used when we created them,” Einstein said. An example of this antipattern is a mi
... See moreJonathan Smart • Sooner Safer Happier: Antipatterns and Patterns for Business Agility
Decisions at all stages of the life cycle—from architectural design to coding and implementation and testing—affect system quality. Therefore, quality is not completely a function of an architectural design. But that’s where it starts.