Martin Fowler

Introduction

The role of software architecture in the practice of building software systems has been long debated. At most organisations you will find some sort of “Architecture” function, often under the banner of “Enterprise Architecture”. This is usually a centralised team with the valid and well-meaning aim of ensuring that all software built adheres to industry and company standards, uses patterns and technologies that are the right fit for the problem, is optimised for the problem space, will scale as required, and avoids any unnecessary duplication. Indeed, it is essential that all of these facets are considered when building any valuable software within any domain and at any meaningful scale.

Typically, this architecture function undertakes the architectural design work for all system changes, often (but not always) in isolation from the development teams that will ultimately implement the solution. These designs, once complete, are then handed over to the

To read the full article click on the 'post' link at the top.