User Tools

Site Tools


principles:tell_don_t_ask_information_expert

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
principles:tell_don_t_ask_information_expert [2014-10-09 12:27]
157.193.8.23 [Caveats] Typo
principles:tell_don_t_ask_information_expert [2016-08-16 20:37]
216.84.89.16 [Evidence]
Line 41: Line 41:
 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:​ripple effects]]). 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:​ripple effects]]).
  
 +Furthermore adhering to this principle distributes responsibilities among several classes instead of having one central [[anti-patterns:​god object]] which uses other objects simply as dumb data containers.
 ===== Strategies ===== ===== Strategies =====
  
Line 65: Line 65:
 /*  * [[wiki:​Examined]]*/​ /*  * [[wiki:​Examined]]*/​
  
-[[wiki:​Accepted]]:​ This principle is prominently described in Craig Larman'​s book //​Applying ​UMl and Patterns//.+[[wiki:​Accepted]]:​ This principle is prominently described in Craig Larman'​s book //​Applying ​UML and Patterns//.
  
 /*  * [[wiki:​Questioned]]*/​ /*  * [[wiki:​Questioned]]*/​
principles/tell_don_t_ask_information_expert.txt · Last modified: 2016-08-16 20:37 by 216.84.89.16