观察者模式4dsign ptterns.pptVIP

* * * * * * * * * * * * * * * * * * * * * * Design patterns must be described using consistent format (Gamma). Each pattern is divided into these sections according to the presented template. Pattern name and classification Intent A statement of a problem which describes intent, that is the goals and objectives it wants to reach within given contexts and force. -Motivation - A scenario that illustrates a design problem and how the class and object structures in the pattern solve the problem. Applicability - The situations in which the problem and its solution seem to recur, and for which the solution is desirable. It can be thought of as the initial configuration of a system before the pattern is applied to it. Structure - A graphical representation of the classes in the pattern using notation based on the Object Modeling technique. Participants - Collaborations - How the partic… Consequences - of applying the pattern, both good and bad, and other problems and patterns that may arise from the new context. It describes the postconditions and side-effects of the pattern. Implementation - What pitfalls, hints, or techniques should you be aware of when implementing the patterns? What are language-specific issues? Related patterns - What design patterns are closely related to this one? What are important differences? With which other patterns should this one be used? * * Much of the initial patterns focus in the software community has been on design patterns. The patterns in the [GoF] book are object-oriented design patterns. However, there are many other kinds of software patterns besides design patterns. For example, Martin Fowler has written a book of Analysis Patterns. Patterns cover all aspects of software engineering including: development organization, software process, project planning, requirements engineering, and software configuration, management (just to name a few). Presently however, design patterns still seem to be the most popular (though organizat