Chapter 2 Organizational Mode
Object-oriented programming basic elements are classes. However, if there is no more meaning of the relationship between other classes that make up the solution, a single class is not much significant. Each mode usually describes a set of classes and emphasizes the relationships and interactions between them. Therefore, the mode converts a large number of classes into a more easily managed mode set.
How can I understand the meaning of all modes? The relationship between the project is the key to the problem.
Architecture mode represents the infrastructure structure structure of the software system. It provides a set of predefined subsystems to specify their duties and include rules and guidelines used to organize their relationships. The design mode provides an architecture that optimizes subsystems or components of the software system or the relationship between each other. It describes the structure that is often reused in communication components to solve the general design problems in a particular context. Implementation mode is a lower level of mode specific to a particular platform. Implementation mode describes how to use the functionality of the given platform to implement some aspects of the component or the relationship between them.
Four mechanisms that help browse patterns: relationship. The relationship between patterns helps identify patterns closely related to the modes used (such as the controller of Model-View-Controller) used. Cluster. The cluster will be combined with a common topic range (such as web represented). Abstract level. The abstraction level enables you to describe the concept (such as an architecture session) in a manner that is consistent with the detailed level of the discussion. Viewpoint. The point of view helps to select vocabulary related to the group's specific role (such as the infrastructure group).
