principles:tell_don_t_ask_information_expert
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
principles:tell_don_t_ask_information_expert [2013-03-13 22:26] – PSU christian | principles:tell_don_t_ask_information_expert [2020-10-12 16:38] – old revision restored (2015-06-29 12:02) 159.69.186.191 | ||
---|---|---|---|
Line 11: | Line 11: | ||
/* fill in contexts here: */ | /* fill in contexts here: */ | ||
* [[contexts: | * [[contexts: | ||
+ | * [[contexts: | ||
===== Principle Statement ===== | ===== Principle Statement ===== | ||
Line 20: | Line 20: | ||
===== Description ===== | ===== 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 | + | Each module has a set of responsibilities so there is a kind of mapping between |
+ | Another view on the principle is that responsibility mapping is bad when one module has to ask another module for information (getter invocation), | ||
+ | The following reasoning shows that //Tell don't Ask// and // | ||
+ | |||
+ | * Suppose TdA is adhered to, but IE is neglected. | ||
+ | * When IE is neglected, then there is a module which is not the information expert for its responsibility. | ||
+ | * But then the module has to ask for the information it needs, so TdA is also neglected. | ||
+ | * As this violates the assumption that TdA is adhered to, this means that adhering to TdA also results in adhering to IE. | ||
+ | * Suppose IE is adhered to but TdA is neglected | ||
+ | * When TdA is neglected, then there is a module '' | ||
+ | * But then '' | ||
+ | * As this violates the assumption that IE is adhered to, this means that adhering to IE also results in adhering to TdA. | ||
+ | * So TdA and IE are equivalent views on the same principle. | ||
+ | |||
+ | Despite of its proof-like form this is not a formal proof as there is no formal definition of TdA and IE. Nevertheless TdA and IE can be seen as two views on the same principle. | ||
===== Rationale ===== | ===== 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 to [[glossary: | 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 to [[glossary: | ||
+ | Furthermore adhering to this principle distributes responsibilities among several classes instead of having one central [[anti-patterns: | ||
===== Strategies ===== | ===== Strategies ===== | ||
Line 35: | Line 49: | ||
===== Caveats ===== | ===== Caveats ===== | ||
- | Sometimes assigning responsibilities using IE results in bas solutions (high coupling, low cohesion). This is because IE just focuses on the availability of data. So for example IE would demand domain objects saving themselves to the database. This is bad since it couples the domain objects to the database interface (JDBC, SQL, etc.) and lowers cohesion by adding unrelated responsibilities to the classes. Here it is better to give the task of persisting the domain objects to a separate class.((see Craig Larman: //Applying UML and Patterns – An Introduction to Object-Oriented Analysis and Design and Iterative Development//, | + | Sometimes assigning responsibilities using IE results in bad solutions (high coupling, low cohesion). This is because IE just focuses on the availability of data. So for example IE would demand domain objects saving themselves to the database. This is bad since it couples the domain objects to the database interface (JDBC, SQL, etc.) and lowers cohesion by adding unrelated responsibilities to the classes. Here it is better to give the task of persisting the domain objects to a separate class.((see Craig Larman: //Applying UML and Patterns – An Introduction to Object-Oriented Analysis and Design and Iterative Development//, |
See also section [[#contrary principles]]. | See also section [[#contrary principles]]. | ||
Line 47: | Line 61: | ||
===== Evidence ===== | ===== Evidence ===== | ||
/* Comment out what is not applicable and explain the rest: */ | /* Comment out what is not applicable and explain the rest: */ | ||
- | /* | + | |
- | * [[wiki: | + | /* * [[wiki: |
- | * [[wiki: | + | /* * [[wiki: |
- | | + | |
- | * [[wiki: | + | [[wiki: |
- | */ | + | |
+ | /* * [[wiki: | ||
===== Relations to Other Principles ===== | ===== Relations to Other Principles ===== | ||
Line 78: | Line 94: | ||
- | ===== Example | + | ===== Examples |
===== Description Status ===== | ===== Description Status ===== | ||
/* Choose one of the following and comment out the rest: */ | /* Choose one of the following and comment out the rest: */ | ||
- | [[wiki: | + | /*[[wiki: |
- | /*[[wiki: | + | [[wiki: |
/ | / | ||
Line 93: | Line 109: | ||
* Andrew Hunt and David Thomas: // | * Andrew Hunt and David Thomas: // | ||
+ | ===== Discussion ===== | ||
+ | |||
+ | Discuss this wiki article and the principle on the corresponding [[talk: |
principles/tell_don_t_ask_information_expert.txt · Last modified: 2021-10-18 21:42 by christian