Catch-61 of PHP object-oriented analysis and design_PHP Tutorial

You do not have to strictly adhere to these principles, and there are no religious penalties for violating them. But you should think of these principles as alarm bells. If one of them is violated, the alarm bell will sound. ----- Arthur J.Riel

(1) All data should be hidden inside the class.

(2) Users of a class must rely on the shared interface of the class, but a class cannot rely on its users.

(3) Minimize the messages in the class protocol.

(4) Implement the most basic public interface that all classes understand [for example, copy operations (deep copy and shallow copy), equality judgment, correct output content, parsing from ASCII description, etc.].

(5) Do not put implementation details (such as placing private functions with shared code) into the public interface of the class.

If two methods of a class have a common code, then you can create a private function that prevents this common code.

(6) Do not disturb the public interface of a class with things that users cannot use or are not interested in.

(7) There should be zero coupling between classes, or only exported coupling relationships. That is, one class either has nothing to do with another class, or it only uses operations in the public interface of another class.

(8) Classes should only represent one key abstraction.

All classes in the package should be jointly closed for changes in properties of the same class. If a change affects a package, it will affect all classes in the package, but will not have any impact on other packages.

(9) Centralize relevant data and behaviors.

Designers should pay attention to objects that obtain data from other objects through operations such as get. This type of behavior implies that this empirical principle is violated.

(10) Put irrelevant information in another class (that is, the behavior of not communicating with each other).

Dependencies towards stability.

(11) Make sure that the abstract concept you model is a class, not just the role played by an object.

(12) Distribute system functions as uniformly as possible in the horizontal direction, that is: according to the design, top-level classes should share work uniformly.

(13) Do not create omnipotent classes/objects in your system. Be especially careful with classes whose names include Driver, Manager, System, and Susystem.

Plan an interface rather than implement an interface.

• Total 4 pages:
• Previous page
• 1
• 2
• 3
• 4
• Next page

http://www.bkjia.com/PHPjc/364011.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/364011.htmlTechArticleYou do not have to strictly adhere to these principles, and there will be no religious penalties for violating them. But you should think of these principles as alarm bells. If one of them is violated, the alarm bell will sound. ...