Software Design Pattern

A software design pattern is the description of the generally accepted 'best practice' method or technique, for solving particular common problems in software engineering.

---

Why do we use design patterns

By identifying and formalizing a method or task, code becomes more understandable by others, who recognize the terms used, and structure of the code.
These patterns help to solve many common problems in computer programming of all languages.

Once a design pattern becomes popular, it would have stood the test of many great minds, and in it's acceptance becomes coinsidered "best practice".

Categorization

There are many popular design patterns. Below are some of the most popular, grouped by category.

Behavioral Patterns Blackboard Chain of responsibility Command Interpreter Iterator Mediator Memento Null object Observer or Publish/Subscribe Servant Specification State Strategy Template Method Visitor	Concurrency Patterns Active Object Balking Messaging design pattern Double-checked locking Event-based asynchronous Guarded suspension Lock Monitor object Reactor Read-write lock Scheduler Thread pool Thread-specific storage
Creational Patterns Abstract factory Builder Factory method Lazy initialization Multiton Object pool Prototype Singleton	Structural Patterns Adapter / Wrapper / Translator Bridge Composite Decorator Facade Front Controller Flyweight Proxy Module

↑ Return to Top

---

See Also

Link to domain parent articles and related articles in TechNet Wiki.

• Design Patterns

↑ Return to Top

---

Community Resources

These are the external links, including links to Microsoft and TechNet sites that are non-Wiki

• Design Patterns: Solidify Your C# Application Architecture with Design Patterns

↑ Return to Top

---

References section

Use this section if you pulled source material and ideas from other sites, blogs, or forums. Make sure you have permission from authors to use their material.

• Software Patterns & Practices

↑ Return to Top