Difference between revisions of "Software design pattern"
Karl Jones (Talk | contribs) (→External links) |
Karl Jones (Talk | contribs) (→See also) |
||
| Line 21: | Line 21: | ||
== See also == | == See also == | ||
| + | * [[Abstraction principle]] | ||
| + | * [[Algorithmic skeleton]] | ||
| + | * [[Anti-pattern]] | ||
| + | * [[Architectural pattern]] | ||
| + | * [[Debugging patterns]] | ||
* [[Design pattern]] | * [[Design pattern]] | ||
| + | * [[Distributed design patterns]] | ||
| + | * [[Double-chance function]] | ||
| + | * [[Enterprise Architecture framework]] | ||
| + | * [[GRASP (object-oriented design)]] | ||
| + | * [[Helper class]] | ||
| + | * [[Interaction design pattern]] | ||
| + | * [[List of software development philosophies]] | ||
| + | * [[List of software engineering topics]] | ||
* [[Model-view-controller]] | * [[Model-view-controller]] | ||
* [[Object-oriented programming]] | * [[Object-oriented programming]] | ||
| Line 27: | Line 40: | ||
* [[Pattern]] | * [[Pattern]] | ||
* [[Pattern language]] | * [[Pattern language]] | ||
| + | * [[Pattern theory]] | ||
| + | * [[Pedagogical patterns]] | ||
| + | * [[Portland Pattern Repository]] | ||
| + | * [[Refactoring]] | ||
| + | * [[Software development methodology]] | ||
* [[Software engineering]] | * [[Software engineering]] | ||
* [[Structure]] | * [[Structure]] | ||
Revision as of 06:53, 27 May 2016
In software engineering, a design pattern is a general reusable solution to a commonly occurring problem within a given context in software design.
Contents
Description
A design pattern is a description or template for how to solve a problem that can be used in many different situations.
Patterns are formalized best practices that the programmer can use to solve common problems when designing an application or system.
Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.
Patterns that imply object-orientation or, more generally, mutable state, are not as applicable in functional programming languages.
Not a finished design
A design pattern is not a finished design that can be transformed directly into source code or machine code.
Design patterns in other fields
The concept of design patterns originated in architecture, and subsequently spread to other fields.
See also
- Abstraction principle
- Algorithmic skeleton
- Anti-pattern
- Architectural pattern
- Debugging patterns
- Design pattern
- Distributed design patterns
- Double-chance function
- Enterprise Architecture framework
- GRASP (object-oriented design)
- Helper class
- Interaction design pattern
- List of software development philosophies
- List of software engineering topics
- Model-view-controller
- Object-oriented programming
- Observer pattern
- Pattern
- Pattern language
- Pattern theory
- Pedagogical patterns
- Portland Pattern Repository
- Refactoring
- Software development methodology
- Software engineering
- Structure
External links
- Software design pattern @ Wikipedia
