Top-down and down-up design (part 2)

Yesterday I wrote about top down approach to design, bottom up is the reverse approach

With this approach we first predict what components on going to be required. Going back to the EchoServer example, the echoServer class depends on a echoConsole module, this means by first designing the echoConsole, we’re taking a bottom up approach.

In this example it doesn’t seem to make much of a difference however when designing a larger system, the difference becomes more apparent.

In addition with larger system you don’t get the immediate feedback on whether the domain objects that you’ve implemented will even be needed. This leads to wastage, requiring deletion of tests and classes(worse is if the developer forgets these classes, yikes!)




Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s