grokking object oriented design interview pdf

I. Design Principles1. Dependency inversion principle (DIP) High-level modules (stability) should not depend on low-level modules (changes), both of which should depend on abstraction.Abstract (stable) should not depend on implementation details (changes), and implementation details should depend on abstraction. 2. Open and closed principle (OCP) Class modules should be extensible, but cannot be modified; open to extensions and closed to changes

by the program, the value of the inside does not know when will be overwritten If you pass a class, struct, and so on, the parameters and return values are passed through some space in memory.The reference is converted into a pointer operation.Constructor: The same as the class name, no return value, implementation of the class member initialization. It is best to initialize the initial value list, and if the function body is initialized, the data member has completed the default initialization

One, the distinction of the concept Some people confuse object-oriented database design (i.e. database schema) with object-oriented database management system (OODBMS) theory. In fact, the former is a database user-defined database mode of thinking, the latter is the idea o

package, it will affect all classes in the package, but it will not affect other packages. Package coupling principle No-ring dependency principle (Acyclic Dependencies Principle, ADP) The package dependency does not allow loops. Stable-Dependencies Principle, SDP) Dependency in a stable direction Stable-abstractions principle (SAP) The abstraction level of the package should be consistent with its stability. Old ti

C # overview of the object-oriented design model (1): Face-to-Face Design Model and mongo.zip Lecture content: this training course introduces the basic concepts and principles of object-oriented

For Java programmers, mastering object-oriented design theory and some design patterns is an essential skill. To start programming without learning a theory is similar to learning a language without studying the alphabet. There's a lot of object-

clause 32: Make sure your pubilc inherits the is-a relationship of plastic mold Make sure public inheritance models "Is-a" one of the most important rules for –c++ (OOP) object-oriented programming is that public inheritance (open inheritance) means "is-a" (a) relationship. – If you make class D ("derived") Inherit class B ("Base") as public, you tell the compiler that each

define a large number of access methods in the public interface. A large number of access methods means that the relevant data and behavior are not centrally stored. (15) Be more careful with classes that contain too much communication behavior. P31 Another manifestation of this problem is the creation of many get and set functions in the public interface of the classes in your application. (16) In an application composed of an object-

Object-oriented design principles are at the heart of oops programming, but most of the Java programmers I've seen are enthusiastic about design patterns like Singleton (singleton), Decorator (adorner), OBSERVER (Observer), Instead of focusing enough attention on learning object