> For the complete documentation index, see [llms.txt](https://docs.yemreak.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yemreak.com/contents/d61c27fc.md). # Diyagramlar ```sh 1. STATE MACHINE / STATE TRANSMISSION [Initial] → [Processing] → [Decision?] → [Success/Fail] │ │ │ │ │ ├─ Yes → [Next State] │ │ └─ No → [Alternative] │ │ └─ Error → [Error State] → [Recovery] → [Retry] Pattern: State'ler arası geçişler, transition kuralları, terminal state'ler Kullanım: Workflow, process modeling, UI state management --- 2. BOX DIAGRAM (Black Box / White Box) Black Box: ┌─────────────┐ ┌────────────┐ │ INPUT │ → [???] → │ OUTPUT │ └─────────────┘ └────────────┘ Internal mechanism görünmez White Box: ┌─────────────┐ ┌────────┐ │ INPUT │ → [Step 1] → [Step 2] → [Step 3] → │ OUTPUT │ └─────────────┘ └────────┘ Internal mechanism görünür Pattern: Abstraction level seçimi, detay gizleme/gösterme Kullanım: API design, system decomposition, debugging --- 3. FLOW CHART START │ ▼ [Process A] │ ├─ Condition? ──Yes──→ [Process B] │ │ └─ No │ │ │ ▼ ▼ [Process C] [Process D] │ │ └─────────┬───────────┘ ▼ END Pattern: Sequential flow, conditional branching, merge points Kullanım: Algorithm design, business process, decision logic --- 4. DECISION TREE [Root Decision] / \ [Criteria A?] [Criteria B?] / \ / \ [Yes] [No] [Yes] [No] │ │ │ │ [Action 1] [Action 2] [Action 3] [Action 4] Pattern: Hierarchical decisions, criteria-based branching Kullanım: Classification, rule-based systems, diagnostic --- 5. FEEDBACK LOOP Positive (Reinforcing): [Action] → [Result] → [More Action] → [More Result] ─┐ │ └─ (loop) Negative (Balancing): [Action] → [Result] → [Correction] → [Balanced] ─┐ │ └─ (stabilize) Pattern: Circular causality, self-regulation, system dynamics Kullanım: Control systems, learning loops, market dynamics --- 6. CAUSAL LOOP DIAGRAM ┌─────────┐ │ A │ └────┬────┘ │ + ▼ ┌─────────┐ │ B │ └────┬────┘ │ + ▼ ┌─────────┐ │ C │ └────┬────┘ │ - └───────┐ │ └─ (negative feedback) Pattern: Causal chains, feedback polarity (+/-), delays Kullanım: Systems thinking, root cause analysis, leverage points --- 7. HIERARCHY / TREE STRUCTURE [Level 1: Root] │ ┌────────────────┼────────────────┐ │ │ │ [Level 2: A] [Level 2: B] [Level 2: C] │ │ │ ┌───┴───┐ ┌───┴───┐ ┌───┴───┐ │ │ │ │ │ │ [L3:1] [L3:2] [L3:3] [L3:4] [L3:5] [L3:6] Pattern: Parent-child relationships, depth levels, breadth Kullanım: Organization charts, taxonomy, file systems, DOM --- 8. PROCESS PIPELINE Input → [Stage 1] → [Stage 2] → [Stage 3] → [Stage 4] → Output │ │ │ │ [Filter] [Transform] [Validate] [Enrich] Pattern: Sequential stages, data transformation, pipeline stages Kullanım: Data processing, build pipelines, request handling --- 9. LAYERED ARCHITECTURE ┌─────────────────────────────────────┐ │ Layer 4: Presentation │ ├─────────────────────────────────────┤ │ Layer 3: Business Logic │ ├─────────────────────────────────────┤ │ Layer 2: Data Access │ ├─────────────────────────────────────┤ │ Layer 1: Infrastructure │ └─────────────────────────────────────┘ Pattern: Separation of concerns, abstraction layers, dependency direction Kullanım: Software architecture, OSI model, neural networks --- 10. NETWORK / GRAPH [A] ─────── [B] │ │ │ │ [C] ─────── [D] │ │ │ │ [E] ─────── [F] Pattern: Nodes, edges, connections, graph topology Kullanım: Social networks, dependency graphs, knowledge graphs --- 11. MATRIX / GRID Col1 Col2 Col3 Row1 [A1] [A2] [A3] Row2 [B1] [B2] [B3] Row3 [C1] [C2] [C3] Pattern: Two-dimensional organization, row/column relationships Kullanım: Feature matrices, decision matrices, data tables --- 12. VENN DIAGRAM ┌─────────┐ │ A │ │ ┌───┐ │ │ │ A∩B│ │ │ └───┘ │ │ B │ └─────────┘ Pattern: Set relationships, intersection, union, complement Kullanım: Category overlap, feature sets, user segments --- 13. TIMELINE / SEQUENCE Time: T1 ────→ T2 ────→ T3 ────→ T4 │ │ │ │ [Event1] [Event2] [Event3] [Event4] Pattern: Temporal ordering, before/after, dependencies Kullanım: Project planning, event sequences, history --- 14. INPUT-OUTPUT TRANSFORMATION Input ──→ [Transformation Function] ──→ Output │ │ │ │ └─ Side Effects ───────────────────────┘ Pattern: Function mapping, side effects, pure vs impure Kullanım: Function design, API contracts, data pipelines --- 15. CONTAINER / SCOPE ┌─────────────────────────┐ │ Outer Container │ │ ┌─────────────────┐ │ │ │ Inner Container │ │ │ │ ┌───────────┐ │ │ │ │ │ Element │ │ │ │ │ └───────────┘ │ │ │ └─────────────────┘ │ └─────────────────────────┘ Pattern: Nesting, scope boundaries, containment hierarchy Kullanım: Component composition, namespace, context --- PATTERN: Her model bir abstraction level seçer ve belirli bir görünüm sağlar. CONSTRAINT: Model seçimi soruya bağlıdır — state geçişleri için state machine, hiyerarşi için tree, zaman için timeline. ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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.yemreak.com/contents/d61c27fc.md?ask= ``` 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.