tailieunhanh - Lecture Object-oriented software engineering - Chapter 6: Using design patterns

The main contents of this chapter include all of the following: Introduction to patterns, the abstraction? Occurrence pattern, the general hierarchy pattern, the player? Role pattern, the singleton pattern, the observer pattern, the delegation pattern, the adapter pattern,. Inviting you refer. | Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 6: Using Design Patterns Introduction to Patterns The recurring aspects of designs are called design patterns. A pattern is the outline of a reusable solution to a general problem encountered in a particular context Many of them have been systematically documented for all software developers to use A good pattern should Be as general as possible Contain a solution that has been proven to effectively solve the problem in the indicated context. Studying patterns is an effective way to learn from the experience of others © Lethbridge/Laganière 2005 Pattern description Context: The general situation in which the pattern applies Problem: A short sentence or two raising the main difficulty. Forces: The issues or concerns to consider when solving the problem Solution: The recommended way to solve the problem in the given context. ‘to balance the forces’ Antipatterns: (Optional) Solutions . | Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 6: Using Design Patterns Introduction to Patterns The recurring aspects of designs are called design patterns. A pattern is the outline of a reusable solution to a general problem encountered in a particular context Many of them have been systematically documented for all software developers to use A good pattern should Be as general as possible Contain a solution that has been proven to effectively solve the problem in the indicated context. Studying patterns is an effective way to learn from the experience of others © Lethbridge/Laganière 2005 Pattern description Context: The general situation in which the pattern applies Problem: A short sentence or two raising the main difficulty. Forces: The issues or concerns to consider when solving the problem Solution: The recommended way to solve the problem in the given context. ‘to balance the forces’ Antipatterns: (Optional) Solutions that are inferior or do not work in this context. Related patterns: (Optional) Patterns that are similar to this pattern. References: Who developed or inspired the pattern. © Lethbridge/Laganière 2005 The Abstraction-Occurrence Pattern Context: Often in a domain model you find a set of related objects (occurrences). The members of such a set share common information but also differ from each other in important ways. Problem: What is the best way to represent such sets of occurrences in a class diagram? Forces: You want to represent the members of each set of occurrences without duplicating the common information © Lethbridge/Laganière 2005 Abstraction-Occurrence Solution: © Lethbridge/Laganière 2005 Abstraction-Occurrence Antipatterns: © Lethbridge/Laganière 2005 Abstraction-Occurrence Square variant © Lethbridge/Laganière 2005 The General Hierarchy Pattern Context: Objects in a hierarchy can have one or more objects above them (superiors), and one or more .