solid principles of object oriented design

to your immediate friends. For Ood, it is also explained in the following ways: a software entity should interact with as few interactions as possible with other entities. Each software unit has only minimal knowledge of the other units, and is limited to the software units that are closely related to the unit.The purpose of the Dimitri law is to reduce the coupling between classes. Since each class minimizes its reliance on other classes, it is easy to make the functional modules of the system

other objects as possible and not talk to strangers.The English shorthand is: LoD. The Dimitri Law can be simply said: Talk is only to your immediate friends. For Ood, it is also explained in the following ways: a software entity should interact with as few interactions as possible with other entities. Each software unit has only minimal knowledge of the other units, and is limited to the software units that are closely related to the unit.The purpose of the Dimitri law is to reduce the couplin

example in the textbook, in the end, in order to bond these beautiful codes together, the layers become increasingly thick until they become sleepy. C language itself is considered a good example of thin gluing layer. UNIX and object-oriented languages Since the middle of the 1980 s, new languages have claimed to provide direct support for object-

Object-oriented three basic characteristics and five basic principles (1) Three basic characteristics: encapsulation, inheritance, polymorphism Encapsulation:Refers to the abstraction of objective things into classes, and each class protects its own data and methods. A class can put its own data and methods only to allow trusted classes or objects to operate

, "I don't need a lot of things!" Uncle Schopenhauer once said: "Just as a country that does not need or needs very little to import goods, is the luckiest country, likewise, if a person is abundant and rich and does not need to seek amusement from outside of himself, then this person is the luckiest person." because imported goods make the country expensive, rely on others, but also bring danger, create trouble. "Lao Tzu said:" Tone deaf deaf, colored blind, gallop the field is crazy. Chuang Tz

added by the user. As the demand changes, users may need to add new behaviors or actions. It doesn't matter. Users only need to implement the common interface. It can be said that the principle of dependency inversion is an object-oriented foundation. This principle guides us to use class polymorphism, and then we get the ability to bind at runtime. This capability is one of our most valuable

respond to the same message. Polymorphism consists of parameterized polymorphism and inclusion polymorphism. Polymorphism language has the advantage of flexibility, abstraction, behavior sharing and code sharing, which solves the problem of application function with the same name. The function of virtual function in C + + is mainly to realize the mechanism of polymorphism. In terms of polymorphism, in short, a pointer to the parent type points to an instance of its child class, and then invokes

Ten principles of Object Oriented Software development (turn two) When you define the parameters of a method, be sure to make them extensible. For example, the following line of code is not extensible: Public Function PlaceOrder (slastname As String, Sfirstname as String, saddress as String) To invoke this method you must pass these 3 parameters. But if you

Object-oriented basics: OO Basics Understanding Implementation Method Encapsulation Encapsulate objective things into abstract classes, and classes can only allow trusted classes or object operations for their own data and methods to hide untrusted information. Inheritance You can use all the functions of an existing cl

. The principle of single responsibility can be regarded as the extension of low coupling, cohesion in object-oriented principle, defining responsibility as the cause of change, in order to improve cohesion to reduce the cause of change.Open closure principle (open-closed principle): Software entities should be extensible and non-modifiable. That is, open to the extension, to modify the closed.Liskov substi

class.Use:Dependencies between modules occur through abstraction, and there is no direct dependency between classes, and their dependencies are generated through interfaces or abstract classes.To put it simply: interface-oriented (interface or abstract class) programming, or for abstract programming.Example code:Five, the system has higher flexibility: the principle of interface isolationEnglish name: Interfacesegregation Principle (ISP)The first def

abstract paradigm. abstraction can be divided into many layers, from very general to very special, and objects may be at no matter what abstraction level. In addition, objects that are different from each other but are associated with each other can form an Abstract: they can be processed as objects of the same class only if they are similar. PrinciplesThe main principles of object-

1. Single Duty: A class, only need to do one thing 2. Development closure: A class that should be extensible and non-modifiable 3. Dependency inversion: A class that should not be strongly dependent on another class. Each class is replaceable for another class. 4. Configure: Use the configuration as much as possible, not hard-coded. 5. Interface-Oriented programming: Only care about the interface, do not need to care about the implementation.From for

Five basic principles:Single Duty principle (Single-resposibility Principle): A class, it is best to do only one thing, only a change that causes it. The principle of single responsibility can be regarded as the extension of low coupling, cohesion in object-oriented principle, defining responsibility as the cause of change, in order to improve cohesion to reduce the cause of change.Open closure principle (O

I. Single RESPONSIBILITYA class should be a set of highly correlated functions, the encapsulation of dataTwo. Opening and closing principleObjects (classes, modules, functions, etc.) in the software should be open for expansion and closed for modification.Explanation: During the software life cycle, because of changes, upgrade maintenance and other reasons need to modify the old code, this time may break the old code has been tested, so should try to expand to modify the code, rather than by mod

country expensive, rely on others, but also bring danger, create trouble. "Lao Tzu said:" Tone deaf deaf, colored blind, gallop the field is crazy. Chuang Tzu said: "Fall limb, deposed clever, I lost me." Confucius said "amending", Mencius said "reflexive and sincere", Zeng Zi said "a day provinces", Zen "Ming Xin", "Wang Yangming" to "conscience", from the pursuit of the external things confused, can really take care of the inner heart. So please refactor yourself according to the "interface i

coupling (Low coupling)Loosely coupled as a principle of evaluation system design, the responsibility lies in: Reduce dependencies between classes and classes Change the impact of a class to other classes to minimize Higher reusability Polymorphic (polymorphism)In an inherited system, a different invocation is produced at run time using the same design-time definitionProtected changes

The first five principles are about class design. They are: SRP, single responsibility principle, a class should have only one reason for change.OCP, open and closed principle, you should be able to expand the behavior of a class without modifying the original class.LSP, liskov replacement principle, the derived class must be self-compatible with its base class.Dip: the principle of dependency inversion de