Design Patterns in MVC Describing Design Patterns - unGrid精品分析.ppt

Designing for Change Common causes of redesign: Dependence on specific operations (Chain of Responsibility) (Command) * Designing for Change Common causes of redesign: Dependence on hardware and software platform (Abstract Factory) (Bridge) * Designing for Change Common causes of redesign: Dependence on object implementations or representations  (Abstract Factory) (Bridge) (Memento) (Proxy) * Designing for Change Common causes of redesign: Algorithmic dependences  (Builder) (Iterator) (Strategy) (Template Method) (Visitor) * Designing for Change Common causes of redesign: Tight coupling  (Abstract Factory) (Bridge) (Chain of Responsibilty) (Command) (Facade) (Mediator) (Observer) * Designing for Change Common causes of redesign: Extending functionality by subclassing  (Bridge) (Chain of Responsibilty) (Composite) (Decorator) (Observer) (Strategy) * Designing for Change Common causes of redesign: Inability to alter classes conveniently  (Adapter) (Decorator) (Visitor) * Toolkits A set of related and reusable classes designed to provide useful, general purpose functionality. (C++ iostream, STL)(java.lang/java.util) * Toolkits Toolkits emphasize code reuse The OO equivalent of subroutine libraries * Frameworks A set of cooperating classes that make up a reusable design for a specific class of software. (C++ MFC)(J2EE) * Frameworks The framework dictates the architecture of the application Defines the overall structure, its partitioning into classes and objects, the key responsibilities, and the collaboration patterns * Design Difficulty Levels Applications Toolkits (harder) Frameworks (hardest) * Selecting Design Patterns Consider how design patterns solve design problems Scan intent sections Study how patterns interrelate Study patterns of like purpose * Selecting Design Patterns Examine a cause of redesign Consider what should be variable in the design * Using Design Patterns Read the pattern once through Pay particular attention