The Way of the Software Architect – the first allegory
Posted by robkraft on April 9, 2012
– The architect’s way
This story illustrates the necessity of the architect to understand more than technology. Indeed, for every person involved in a software development project, the goal of your tasks is not to provide an esoteric best answer. In the role of a software architect, your goal is to recommend the best architecture. But every person in an organization has many roles, and one role shared by every person is to help solve business problems quickly and efficiently. Often, the business goals trump the goals of the software architecture. Business goals include: getting to market early, pleasing a specific client, pleasing a specific CEO, developing a secure solution, developing a prototype solution; development a solution inexpensively that is good enough; allowing a junior developer to learn through trial and error by developing a solution; developing a solution merely to learn a new technology; developing a solution to test out a new technology before using it in more important projects. All this and more. A software architect needs to help a business solve business problems first, and worry about purity of architecture second.