CSC/ECE 517 Fall 2009/wiki2 11 zv: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Overview= | |||
Before starting off with design patterns for Ruby we need to define what a design pattern is, Design patterns can be described as "a general reusable solution to a commonly occurring problem in software design." [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29] | Before starting off with design patterns for Ruby we need to define what a design pattern is, Design patterns can be described as "a general reusable solution to a commonly occurring problem in software design." [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29] | ||
The idea of design patterns is to not to reinvent the wheel but to solve the current problems by using solutions that have worked in the past. | The idea of design patterns is to not to reinvent the wheel but to solve the current problems by using solutions that have worked in the past. | ||
Revision as of 05:05, 7 October 2009
Overview
Before starting off with design patterns for Ruby we need to define what a design pattern is, Design patterns can be described as "a general reusable solution to a commonly occurring problem in software design." [1] The idea of design patterns is to not to reinvent the wheel but to solve the current problems by using solutions that have worked in the past. A design pattern names, abstracts, and identifies the key aspects of a common design structure that make it useful for creating a reusable object-oriented design. It helps to identify the classes and instances and the way they collaborate with each other to form a solution to a pronblem. Design patterns c an be classified into 3 parts Creational, Structural, Behavioral (See if we can give links for these.)