Assign a responsibility to this module which has the largest subset of the required information.
Each module has a set of responsibilities. Subsystems have specific tasks, packages group several related classes, classes have methods and attributes, and so on. So there is a kind of mapping between modules and responsibilities. This mapping is good when the information which is necessary to fulfill the given task is present in the given module so there is no need to acquire all this information.
When this principle is not adhered to, then a module has a responsibility for which it is lacking some information. So in order to fulfill the task the module has to first acquire the needed information by invoking other modules. This increases the dependencies between the modules (which may lead toripple effects).
Craig Larman: Applying UML and Patterns – An Introduction to Object-Oriented Analysis and Design and Iterative Development
Craig Larman describes how to assign responsibilities to classes using the following principles and patterns:
He calls GRASP “patterns of general principles in assigning responsibilities”1). Some of these are really patterns but others are principles. The latter are links in the above list.