Standard object oriented (OO) design facilitates organizing the classes in a modular fashion during the design stage. However, this doesn't necessarily mean that the modularity is preserved in the later stages of the software development cycle. For example, during implementation, a casual use of friends in classes can re-introduce dependencies. We describe the design of a tool that detects such dependencies and aids in learning the design of classes in OO programs where the interdependencies in the classes are minimized.