Many software development and management methods are founded on a basic assumption – that constructing software is rather like building a bridge or a house. Once we’ve “done the design”, actually generating the software ought to be a completely predictable, relatively low-skilled process. However four decades of failure to achieve this vision might suggest that we should revisit
\nthe assumption.<\/p>\n
In a paper entitled “The New Methodology”<\/a> Martin Fowler, the guru of object-oriented development, suggests a couple of reasons why this might be.<\/p>\n My article answers Martin’s, suggesting a couple of other considerations, and whether we have to completely abandon the physical construction analogy as a result.<\/p>\n","protected":false},"excerpt":{"rendered":" Many software development and management methods are founded on a basic assumption – that constructing software is rather like building a bridge or a house. Once we’ve “done the design”, actually generating the software ought to be a completely predictable, … Continue reading