CSC/ECE 517 Fall 2009/wiki3 13 b5: Difference between revisions
Jump to navigation
Jump to search
Chump Chief (talk | contribs) m (→Sources) |
Chump Chief (talk | contribs) |
||
| Line 8: | Line 8: | ||
== Motivation == | == Motivation == | ||
The Principle of Explicit Interfaces refers to the attempt to ensure that relationships between separate modules are easily found and understood. This is important when considering making a change to the code base. It allows the programmer to quickly see what other modules his work might impact, preventing unintended side effects. | |||
== Application == | == Application == | ||
Revision as of 09:06, 18 November 2009
Principle of Explicit Interfaces
Definition
The Principle of Explicit Interfaces is proposed by Bertrand Meyer in his book Object-Oriented Software Construction. It states
Whenever two modules A and B communicate, this must be obvious from the text of A or B or both.
Motivation
The Principle of Explicit Interfaces refers to the attempt to ensure that relationships between separate modules are easily found and understood. This is important when considering making a change to the code base. It allows the programmer to quickly see what other modules his work might impact, preventing unintended side effects.
Application
External Links
Sources
- Meyer, Bertrand. Object-Oriented Software Construction, 2nd edition p50. ISE Inc., Santa Barbara, CA, 1997.