
Initial Development ◾ 225
14.4.1 Bottom-Up Implementation
Bottom-up implementation is a process that is driven by the desire to minimize the
number of testing stubs for unit tests, because they represent an extra expense and
delay in the project. e programmers are guided by the dependency graph. First
they implement the bottom classes that do not have any suppliers, and then they
implement their clients, the clients of the clients, and so forth. In the dependency
graphs without cycles, all suppliers can be written before the clients, so there is no
need for writing any stubs.
Figure 14.5 contains the dependency graph that corresponds to t