Slim ABP DDD Good 逑 context

Context Description

There is a very important concept in domain-driven design, called defining context. The purpose is to make a restrictive statement of the scope of the current activity, all analysis, verification, conclusion, only in the context of the specified definition, it is meaningful to explore their rationality, once beyond this context, to discuss his rationality and correctness, is directly irrelevant.

The application of the DDD domain-driven design is to better analyze the knowledge, relationships and processes of the business in nature. The final output is not necessarily exactly the same as the customer's needs. Because the customer is able to complete the work skillfully, but few people can summarize their own business knowledge, and the rationality of business process to make in-depth analysis and evaluation. Enterprise Personnel post configuration, personnel quality, the use of information tools, determines the majority of business processes, has a certain irrationality, but still can operate normally. With the development of enterprises, many business processes of irrationality began to play a role, will let enterprises into the mire, struggling. The starting point of all development enterprise applications should be to find out what the business should be, and then realize it by developing information tools as support, so that the business process returns to its reasonable state. This is my understanding of the development of enterprise applications and the choice of domain-driven design to develop enterprise applications, that is, the context of DDD.

Solve the problem of business analysis and design, the next is the problem of technology landing, and then the good design can not be achieved, it becomes an armchair. The method of domain-driven design is not widely adopted, it is because of its high quality requirements for developers, a lot of knowledge can not be copied, only by experience. Software development process from the production line, into the creation of art, the management and cooperation of the large team put forward higher requirements. Uphill is so hard, but it has to be challenged. At first, I used the traditional method of demand analysis, three-layer architecture technology development and production enterprise material tracking management software, according to the needs of customers to do, wait until the on-line to understand, this is not what customers need. There are problems with the methods and ideas of demand analysis. Then adopt Apworks frame, based on the idea of ddd Field drive design, re-analyze and design software, solve the problem of demand analysis and function design, but encountered the problem of technology landing, now terminated. The ABP framework was later discovered, analyzed and researched, and found to be a perfect solution for all the problems previously encountered that led to the difficulty of landing the technology.

DDD is a good prescription for symptomatic, ABP is a good medicine, can solve the problem? No way. There is also a very important step, the method of taking medicine, only to take this step also solved, can be repaired to the attainment. The next series of blogs will be based on the development of purchasing management module, introduce the business analysis method of domain driven design, and use ABP framework to support the output of business analysis, and finally realize a fantastic purchasing management module.

Slim ABP DDD Good 逑 context