Responsibility Assignment and abstract responsibilities

• The core of software design is Responsibility Assignment and responsibility abstraction.
• Responsibility Assignment and abstract responsibilities are involved at all levels of software design. At the upper level, both the architectural hierarchy and the partition belong to the Responsibility Assignment. At the bottom layer, how to define classes and functions belong to the Responsibility Assignment.
• The essence of the design pattern is that it separates many responsibilities from the old design scheme and helps solve the problem of strong functional coupling of the old system.
• Some accusations are easy to find, such as the definition of responsibility for layers, partitions, and classes, because it is a natural responsibility at the functional level; however, some responsibilities cannot be confirmed, for example, it is difficult to process the duties separated by the design pattern because it belongsAlgorithmType of unnatural responsibilities.
• Responsibility Assignment is not static. Different people may have different understandings in different periods; for example, at the beginning, we didn't realize that we should extract the process-related responsibilities from the project into a workflow system, but gradually figured out that we should use the workflow to control the process in the Process of failure.