Difference between revisions of "Software design pattern"
Karl Jones (Talk | contribs) (etc) |
Karl Jones (Talk | contribs) (→See also) |
||
| Line 21: | Line 21: | ||
== See also == | == See also == | ||
| + | * [[Design pattern]] | ||
* [[Object-oriented programming]] | * [[Object-oriented programming]] | ||
* [[Pattern]] | * [[Pattern]] | ||
* [[Software engineering]] | * [[Software engineering]] | ||
* [[Structure]] | * [[Structure]] | ||
| + | |||
== External links == | == External links == | ||
* [https://en.wikipedia.org/wiki/Software_design_pattern Software design pattern] @ Wikipedia | * [https://en.wikipedia.org/wiki/Software_design_pattern Software design pattern] @ Wikipedia | ||
Revision as of 06:29, 1 September 2015
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
External links
- Software design pattern @ Wikipedia
