http://www.codingthearchitecture.com/2006/02/17/simplicity.html As an architect, you'll undoubtedly be called upon to make decisions about how a particular requirement should be fulfilled. Remember, you bring together the appropriate balance between functional and non-functional requirements to produce what the ... en Simon Brown Mon, 30 Oct 2006 19:35:55 GMT Pebble (http://pebble.sourceforge.net) http://backend.userland.com/rss http://www.codingthearchitecture.com/2006/02/17/simplicity.html#comment1162236955000 a simple solution as you described is'nt as fun to develop as a complex solution. The developers and purhaps your self could easily choose the complex solution to get a challange.<br /> <br /> :) Arne http://www.codingthearchitecture.com/2006/02/17/simplicity.html#comments http://www.codingthearchitecture.com/2006/02/17/simplicity.html#comment1162236955000 Mon, 30 Oct 2006 19:35:55 GMT http://www.codingthearchitecture.com/2006/02/17/simplicity.html#comment1140446545958 <p> Simplicity is, of course, subjective. The argument presented <i>seems</i> to be balanced but is this merely because we're projecting our own expectations and experience? What would my dad make of a form asking him to "re-register for the new site"? Dunno. But a phone call to a relative may well be involved... </p> <p> Naturally you know that when you say "much simpler" you implicitly add "with respect to all the requirements I'm balancing". Beware what the development team and business analysts are implicitly adding - they may not see your solution as "much simpler"! </p> <p> Finding that appropriate balance of requirements requires that an appropriate weight be given to each viewpoint. Additionally, the social role of an architect requires that appropriate language be used for each. </p> kseal http://www.codingthearchitecture.com/2006/02/17/simplicity.html#comments http://www.codingthearchitecture.com/2006/02/17/simplicity.html#comment1140446545958 Mon, 20 Feb 2006 14:42:25 GMT