One of the endless challenges for a large corporate software engineering organization is to develop an effective process for handling <A HREF="http://www.cioinsight.com/article2/0,1540,2036364,00.asp?kc=CMCIOEMLP102406CMS3">the steady stream of small changes, fixes and enhancements</A> that seem to accumulate around installed software, both custom developed and Commercial of the Shelf--no matter how good it is initially. The problem for the engineering managers, however, is that each change generally requires considerable impact analysis before it is made, and considerable testing after it has been implemented but before the new "version" of the software goes into production. This "engineering process" effort can easily dwarf the core engineering resource requirements as each small change includes all the aforementioned associated "overhead."