Software design thinking: software should be able to increase or decrease

After many "frameworks" are designed, You need to carry the burden of the entire framework. This is not good.

The software should be able to remove unnecessary functions from the user's choice. A good software design should be able to increase or decrease.

In this sense, the. net dll encapsulation mode is not as good as the Java class + jar zip package mode. A dll is a large package and may contain many classes that are not usable. As an object-oriented encapsulation mode, it makes sense to refine it to the class. Assume that yourProgramIf you only use a framework class, you only need to include the class file of the class, then include the reference of the class itself, and so on.

For example, a subclass requires the relevant base class and the class to which it is used.

If programmers of this type follow the more standardized object-oriented principles, it is foreseeable that it will not be useful at all.Code.

Therefore, there is hope to streamline the software capacity.

It can be reduced, indicating that the software is well modularized and it is not difficult to increase.