"Essentials and models of Software Design" (2)

Chapter 2 encapsulation changes

 

2.1Design Patterns

Here I will explain: the center of the arrow target; the target of the exercise shooting (see the http://zidian.teachercn.com/gu/Word_5649.html)

 

The design pattern is the best explanation of the Thought of "encapsulation change. Whether it isCreate mode, structure model, or behavior modelIn the final analysis, they are all looking for possible "changes" in the software and then encapsulating these changes in an abstract way ....... The most important thing about encapsulation changes is to discover changes, or look for changes.

The purpose of the Creation Mode is to encapsulate changes in object creation.

Structural mode, which focuses on the combination of objects.

The behavior mode focuses on the behavior of objects. This type of mode needs to abstract the changed behavior and achieve the scalability of the entire architecture through encapsulation.

 

2.2 how to encapsulate changes

Here, I will only list the titles of each chapter.

2.2.1 encapsulate changes in user requests

2.2.2 encapsulate changes in object Creation

2.2.3 EncapsulationAlgorithmImplementation changes

 

2.3 dependency Injection

Dependency exists outside the module, and object creation is required. We need to use related technologies to inject external dependencies into the module. This is the so-called "dependency injection)