User Tools

Site Tools


principles:information_expert

Information Expert (IE)

Variants and Alternative Names

  • Expert
  • Tell Don't Ask
  • Do It Myself

Context

Definition

Assign a responsibility to this module which has the largest subset of the required information.

Description

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.

Rationale

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).

Origin

Craig Larman: Applying UML and Patterns – An Introduction to Object-Oriented Analysis and Design and Iterative Development

Evidence

Relations to Other Principles

Generalizations

  • Low Coupling Adhering to the information expert principle leads to low coupling as there is less need to communicate with other modules to get the necessary information.
  • High Cohesion Adhering to information expert also means that a module only has responsibilities which belong together. So this increases cohesion.

Specializations

Contrary Principles

Complementary Principles

Principle Collections

OOD Principle Language
General Principles Modularization Principles
KISS DRY GP MP IE LC HC
GRASP
Principles Information Expert High Cohesion Low Coupling
Non-Principles Controller Creator Indirection Polymorphism Protected Variation Pure Fabrication

Example

Description Status

Further Reading

principles/information_expert.txt · Last modified: 2021-02-01 23:47 by 95.216.157.202