Difference between revisions of "DesignPatterns"
From Suhrid.net Wiki
Jump to navigationJump to search (→Intro) |
(→Intro) |
||
| Line 3: | Line 3: | ||
* A design pattern systematically names, explains, and evaluates an important and recurring design problem and its solution. | * A design pattern systematically names, explains, and evaluates an important and recurring design problem and its solution. | ||
* They capture the intent behind a design by identifying objects, collaborations, and distributions of responsibilities. | * They capture the intent behind a design by identifying objects, collaborations, and distributions of responsibilities. | ||
| + | ** They capture static and dynamic structures of successful solutions to problems. | ||
* Patterns support reuse of software architecture and design. | * Patterns support reuse of software architecture and design. | ||
* They give software engineers a vocabulary with which to describe their designs. | * They give software engineers a vocabulary with which to describe their designs. | ||
Revision as of 08:40, 17 December 2011
Intro
- A design pattern systematically names, explains, and evaluates an important and recurring design problem and its solution.
- They capture the intent behind a design by identifying objects, collaborations, and distributions of responsibilities.
- They capture static and dynamic structures of successful solutions to problems.
- 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.
- Patterns are not code-reuse they are experience reuse !
