solid principles of object oriented design

. 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-

3 basic elements of object-oriented: encapsulation, inheritance, polymorphism Object-oriented 5 basic design principles: single Duty principle (Single-resposibility Principle) Its core idea is: A class, it is best to do only one t

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

derived class. p103(53) Do not confuse the optional inclusion with the need for inheritance. Modeling an optional inclusion into a class where inheritance can lead to flooding. p108(54) When creating an inheritance hierarchy, try creating a reusable framework, rather than a reusable component. p112(55) If you use multiple inheritance in your design, let's say you made a mistake. If you don't make a mistake, you need to try to prove it. P120(56) If yo

number of access methods in public interfaces. A large number of access methods mean that related data and behaviors are not stored in a centralized manner.(15) Be careful with classes that contain too many non-communication behaviors. Another manifestation of this problem is in your application.ProgramMany get and set functions are created in the public interface of the class. (16) In an application composed of an object-

included and associated relationships, select the included relationship. P123 (59)Do not use global data or global functions to note the work of class objects. Class variables or class methods should be used. P140 (60)Object-oriented designers should not allow physical design

number of access methods in public interfaces. A large number of access methods mean that related data and behaviors are not stored in a centralized manner. (15) Be careful with classes that contain too many non-communication behaviors. Another manifestation of this problem is that many get and set functions are created in the public interfaces of classes in your application. (16) In an application composed of an object-

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-oriented design, make sure that no base class is actually a derived class of another base class. (58) in the object-

number of access methods in public interfaces. A large number of access methods mean that related data and behaviors are not stored in a centralized manner.(15) Be careful with classes that contain too many non-communication behaviors. Another manifestation of this problem is in your application.ProgramMany get and set functions are created in the public interface of the class. (16) In an application composed of an object-

access methods in public interfaces. A large number of access methods mean that related data and behaviors are not stored in a centralized manner. (15) Be careful with classes that contain too many non-communication behaviors. Another manifestation of this problem is in your application.ProgramMany get and set functions are created in the public interface of the class. (16) In an application composed of an object-

) is the base class part of the derived class? (57) If you find multiple inheritance relationships in an object-oriented design, make sure that no base class is actually a derived class of another base class. (58) in the object-oriented