CSC/ECE 517 Fall 2009/wiki2 12 01: Difference between revisions
Jump to navigation
Jump to search
Suryaramana (talk | contribs) No edit summary |
|||
| Line 1: | Line 1: | ||
Problem Statement | |||
Patterns are often classified into creational, structural, and behavioral categories. However, this leaves a large number of patterns in each group, with no easy way of remembering all of them. What classifications and strategies have been developed to help programmers remember patterns, so that they can apply them at opportune moments? | |||
== Design Patterns == | == Design Patterns == | ||
A design pattern in software engineering can be described as a reusable solution template to a frequently occurring software design problem. | A design pattern in software engineering can be described as a reusable solution template to a frequently occurring software design problem. | ||
== Classification of Design Patterns == | == Classification of Design Patterns == | ||
Revision as of 19:24, 9 October 2009
Problem Statement
Patterns are often classified into creational, structural, and behavioral categories. However, this leaves a large number of patterns in each group, with no easy way of remembering all of them. What classifications and strategies have been developed to help programmers remember patterns, so that they can apply them at opportune moments?
Design Patterns
A design pattern in software engineering can be described as a reusable solution template to a frequently occurring software design problem.
Classification of Design Patterns
Design patterns can be classified along the following schemes
- Purpose - Scope - Functionality - Structural Principles - Granularity