Difference between revisions of "DesignPatterns"
From Suhrid.net Wiki
Jump to navigationJump to search (→Intro) |
|||
| Line 8: | Line 8: | ||
** Determining how abstract or how concrete a class should be. | ** Determining how abstract or how concrete a class should be. | ||
** Specifying interfaces of classes, architectures, and binary components. | ** Specifying interfaces of classes, architectures, and binary components. | ||
| + | ** Designing for change. | ||
Revision as of 15:41, 27 November 2011
Intro
- A design pattern systematically names, explains, and evaluates an important and recurring design problem and its solution.
- Patterns support reuse of software architecture and design.
- They give software engineers a vocabulary with which to describe their designs.
- Patterns solve design problems such as:
- Finding appropriate classes to solve a problem.
- Determining how abstract or how concrete a class should be.
- Specifying interfaces of classes, architectures, and binary components.
- Designing for change.
