Software architecture is a lot of different things to different people, however most definitions agree that it deals with the major components or structures, their relationships and interactions. It encompasses the major (read hard to change) decisions and their rationale and every system has an architecture (even if it is a default one)
While agreeing on what software architecture is – is one thing. Getting there (i.e. building one) is another thing altogether. There is very little guidance on how one can go about building/developing an architecture for a software project. The SPAMMED framework (dare I say methodology? J) was developed to help fill this gap. SPAMMED is not a new thing invented out of thin-air, but rather a synthesis of several existing approaches and methods combined and integrated into something, I believe, is greater than the sum of its parts.
A note on real-world uses of this process – I have employed major parts of this process in previous projects I architected and this is the prime process I use on project I architect these days.
OK, so what is SPAMMED already… well:
On the next few posts(among other things) I’ll try to delve in more detail to each of the steps that make the SPAMMED process I will then follow this with guidance on integrating the process with the rest of the (waterfall/iterative/agile/plan based) development life cycle
Subscribe to RSS headline updates from:
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.
© Copyright 2005-2013, Arnon Rotem-Gal-Oz
DirectionalRedux theme by John Forsythe and Jon Stovall