Start with the lowest level modules and work toward
the top.
Use a "test harness" or "driver" to test and debug the
results at any given level.
Problem: will we be able to integrate the final
pieces to satisfy the ultimate requirements? - This is why
bottom-up is not considered to be a good design technique,
but it is very useful and fine for implementation.
Advantage: we are always working with concrete,
real data.
Generally not recommended as a design methodology,
but is good for implementation.
Last Modified -
Thursday, 23-Aug-2007 12:00:48 EDT