head first object oriented analysis and design

inheritance in the design, first assume that you have made a mistake. If you do not make a mistake, try to prove it. (56) as long as inheritance is used in object-oriented design, I have two questions: (1) is the derived class a special type of the thing it inherits? (2) is the base class part of the derived class? (5

frameworks rather than reusable components when creating an inheritance hierarchy. (55) If you use multiple inheritance in the design, first assume that you have made a mistake. If you do not make a mistake, try to prove it. (56) as long as inheritance is used in object-oriented design, I have two questions: (1) i

not change operations into classes. Question any class whose name is a verb or a derived Automatic Word, especially a class with only one meaningful action. Consider whether the meaningful behavior should be migrated to an existing or undiscovered class.(21) We often introduce a proxy class when creating an analysis model for an application. In the design phase, we often find that many agents are useless a

system domain.(20) Do not turn the operation into a class. Question any class whose name is a verb or a derived automatic word, especially one that has only a meaningful behavior. Consider whether the meaningful behavior should be migrated to a class that already exists or has not yet been discovered.(21) We often introduce proxy classes when creating an application's analysis model. In the design phase, w

. If you do not make a mistake, try to prove it.(56) as long as inheritance is used in object-oriented design, I have two questions: (1) is the derived class a special type of the thing it inherits? (2) is the base class part of the derived class?(57) If you find multiple inheritance relationships in an object-

information in another class (that is, non-communication behavior ).Dependency in a stable direction.(11) make sure that the abstract concept you are modeling for is a class, not just the role played by an object.(12) distribution of system functions in the horizontal direction as much as possible, that is, the top-level classes should share work in a unified manner according to the design.(13) do not crea

access methods defined in the public interface. A large number of access methods means that the relevant data and behavior are not centrally stored. (15) Be cautious about classes that contain too many non-communicating behaviors. Another manifestation of this problem is that many get and set functions are created in the public interface of the class in your application. (16) In an application that is composed of an object-

From http://www.cnblogs.com/kid-li/ I have been working for three years. To tell the truth, I have never studied Object-Oriented Programming well. I just learned some perceptual knowledge and some so-called theories. I am reading a book "head first object-oriented

Design class---> Design class is the abstraction of one or more objects in a system implementation.---> Design classes have been mapped directly to the implementation code, so the design class relies on the implementation language. On the other hand, the design class origina