Where did the idea of design patterns come from, who decided what is and isn't a pattern and gave them their names? Is there an official organisation that defines them, or do they exist through some community consensus?
Wikipedia has a good list. http://en.wikipedia.org/wiki/Design_pattern_(computer_science)
Most are by community consensus (that community being of people who have read design patterns or code complete :/)
There's no definitive list. Patterns are discovered, not invented, so there's no organization that can say "this is a pattern" and "this is not a pattern". Even if there were one, it wouldn't be useful for anybody.
Despite that, the "famous" patterns are the ones described in Design Patterns, or the GOF book.
Most people would point to the "Gang of Four" (Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides) who wrote the book Design Patterns: Elements of Reusable Object-Oriented Software. There is no real definitive list as useful design patterns are certainly being discovered all the time.
There is a canonical book: Gamma, Helm, Johnson, Vlissides: "Dessign Patterns - Elements of Reusable Object-Oriented Software" which started it all. It contains 23 patterns.
I think there's a basic "life cycle of a design pattern"
- Author writes about design pattern in a book.
- Book becomes well read, possibly best seller
- Design pattern enters public conscious, gains mindshare.
- Design pattern gets used. It works well. design pattern gets more mindshare
- Design pattern becomes panacea, gets over-used.
- Different Author writes "Design Pattern Considered Harmful"
- Design pattern becomes Anti Pattern
- Different Author becomes famous, writes book full of new design patterns...
There is no definitive list - for there to be one would most likely require some authority to declare whether a pattern is a pattern or just a ... something else.
Some patterns make sense only in a subset of languages - the canonical GOF book concentrates on Java (or is it C++? The book's on my desk at the office) and some of the patterns described aren't very relevant in, for example, Ruby or VB6. And vice versa of course.
This is a good list of patterns (from the Patterns of Enterprise Application Architecture book):
Short answer: No.
Long answer: Since if someone designs something, and it tends to be reused by others a new "design pattern" will be just created ( or discovered?? )
Actually the number of design patterns in existing applications might be enormous, but none has classified them yet.
I would add the the previous links these two:
I would say that the Union of the list in the Gang of Four book and Fowler's Patterns of Enterprise Arhitecture will give you 99% of what you would ever need to know.
The idea of Design Patterns was coined by Christopher Alexander, while writing about architectural patterns within buildings and towns. Similarly, patterns have emerged as engineers have gained more experience with object oriented design methodologies.
There is not one official consortium that defines what is a pattern and what is not a pattern. However, patterns typically have a long lifecycle before they are generally accepted. The development community is beginning to participate in things like PLOP (Pattern Languages of Programs) and their yearly conference: 2008 Conference, which focus on pattern authors and enthusiasts to discuss the subject of patterns and new pattern development.
There can't be a definitive list. Ever.
If you see some solutions to a problem that -- to you -- have a pattern that can be articulated, you've discovered a design pattern. You can always continue doing this.
Every clever, new solution could be the genesis for a similar solution which shares a common pattern. Patterns are something you use to summarize and capture a cool solution to a problem.
The human brain can find patterns in almost anything. It's a thing we do without thinking about it.