CSC/ECE 517 Fall 2007/wiki3 7 cl: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 15: | Line 15: | ||
===Principle of Explicit Interfaces === | ===Principle of Explicit Interfaces === | ||
The principle of explicit interfaces states that whenever two modules A and B communicate, this must be | |||
obvious from the text of A or B or both. | |||
====Example of Principle of Explicit Interfaces ==== | ====Example of Principle of Explicit Interfaces ==== |
Revision as of 22:03, 16 November 2007
Bertrand Meyer is a prominent author in o-o design. He has developed a set of principles, many of which are embodied in the Eiffel language. Consider the principles of small interfaces, explicit interfaces, the uniform-access principle, the self-documentation principle, and the single-choice principle. What are good examples of each? Do other languages besides Eiffel support them? Is it difficult to follow these principles in certain o-o languages?
Bertrand Meyer's Set of Principles
Bertrand Meyer is the developer of the Eiffel programming language. As a developer, Dr. Meyer participates in the evolution of the Eiffel method and language which includes a set of principles that he developed. Some of the more important principles are the principle of small interfaces, explicit interfaces, the uniform-access principle, the self-documentation principle, and the single-choice principle.
Principle of Small Interfaces
The principle of small interfaces, also known as weak coupling, states that if any two modules communicate at all, they should exchange as little information as possible.
Example of Principle of Small Interfaces
Principle of Explicit Interfaces
The principle of explicit interfaces states that whenever two modules A and B communicate, this must be obvious from the text of A or B or both.