On Jan 2, 2004, at 11:54 AM, Ray Hooker wrote:
The point is that complex design is more often evolutionary and involves a
lot of discovery. The old style rigid approach where the "requirements" are
documented, delivered to the programming team who then takes months (or
years) to finally deliver to the end user a result which is usually
inadequate and needs several more evolutions to make it right.
In my experience business apps are more evolutionary in the grand scheme of things, while traditional engineering tasks are more requirements based. With a typical business application the client more than likely has only a fuzzy idea of what he/she needs, hence the difficulty in coming up with requirements. On the other hand, if you're trying to send a lander to mars, there's lots of nice rigid requirements like not crashing into the Sun, landing on the surface without breaking anything, etc.
-------------------------------- Michael Czeiszperger czei at webperformanceinc dot com Web Performance, Inc. 919-845-7601
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
