On Tue, Apr 12, 2005 at 08:36:34PM -0700, Stewart Stremler wrote:
Top down means you analyze the program from it's highest functions/behaviors and deconstruct. Bottom up means you identify the critical low-level functions and write them first, letting the program shape up around them. Either approach done purely and without any admixture of the other leads to disaster.
Best to combine them and write out-in, if that makes any sense.
I usually design from a top-down point of view, while I build/architect mostly bottom-up. I don't know how you could do pure bottom-up and have something functional, nor do I see how you end up with more than a giant work around using pure top-down.
-- "If you can't imitate him, don't copy him." --Yogi Bera -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
