# Dizayn Patternlar

Dasturiy ta'minotni ishlab chiqishda qo'llaniladigan patternlar,  dastur tuzish davomida muntazam ravishda uchraydigan muammolarga yechim topishda qo'llaniladi. Ushbu qonun - qoidalar faqat **OOP(Obyektga Yo'naltirilgan Dasturlash)** uchun amal qiladi. Ya'ni qoidalarni **Funksional Dasturlash**ga qo'llash yaramaydi.

Dizayn Patternlar - dasturchi uchun muhim qurollardan biri hisoblanadi. Dasturchi injinerlarning, dizayn patternlarni qanday tashkil qilingani va uning aynan qaysi muammoni yecha olishligini bilishligi, patternlarni qanday sinflar, metodlar va maydonlardan tashkil etilganini eslab qolishdan ko'ra avzalroqdir. Chunki patternlarni yaratilishi(Implementatsiyasi), berilgan muammoga ko'ra tashkil etiladi.

Dizayn Patternlar bo'limida, Gang of Four(GoF) mualliflari tomonidan yaratilingan  [Design Patterns - Elements of Reusable Object-Oriented Software](https://amzn.to/1WjWC1U) kitobida sanab o'tilgan patternlar to'g'risida so'z boradi.

Dizayn Patternlari maqsadiga ko'ra 3 turga bo'linadi:

* **Creational**
* **Structural**
* **Behavioral**

### **Creational dizayn patternlar oilasi**

1. Factory Method
2. Abstract Factory
3. Builder
4. Prototype
5. Singleton

### **Structural design patternlar oilasi**

1. Adapter
2. Bridge
3. Composite
4. Decorator
5. Façade
6. Flyweight
7. Proxy

### **Behavioral design patternlar oilasi**

1. Chain of Responsibility
2. Command
3. Interpreter
4. Iterator
5. Mediator
6. Memento
7. Observer
8. State
9. Strategy
10. Visitor
11. Template Method

Ko'rib turganingizdek jami 23 ta asosiy dizayn patternlari mavjud. Suxbatlarimiz davomida bularning barchasini Alloh qodir qilgancha  yoritib borishga harakat qilamiz


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dot-net.uz/c-.net/.net-dasturchi/clean-architecture/design-pattern.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.