dependent module

A particular module might be harder to reuse and/or test because dependent modules must be included.

Any change in a module which would force dependent modules to change were closely tracked and documented.

Therefore changing the way the second module produces data (location, type, timing) will lead to changing the dependent module.

List all dependent modules (portable executables)

The main reasons to create such mockups is to be able to test one part of a software system (a unit) without having to use dependent modules.

Type 2 or setter injection, in which the dependent module exposes a setter method that the framework uses to inject the dependency.

Most problematic from a software design point of view is the tight coupling of the mutually dependent modules which reduces or makes impossible the separate re-use of a single module.