This post has already been read 2396 times!
Design Pattern History
The term “design pattern” was originally coined in the field of architecture. Christopher Alexander, in his 1977 work, “A Pattern Language: Towns/Building/Construction,” describes common issues of architectural design and explains how new, effective designs can be created through the aggregation of existing, well-known patterns. Alexander’s concepts translate well into software development, where it’s long been desirable to construct solutions from previously existing components.
All design patterns have several common characteristics: a name, a problem statement, and a solution.
• The name of a design pattern is important, because it allows you to instantly communicate the intent of your code with other programmers—at least programmers familiar with patterns—without going into too much detail.
• The problem is the domain where the pattern can be applied.
• The solution describes the implementation of the pattern.
I attach here one part of my code made in PHP.
Code Source - php_patterns-master.zip