{"id":1139,"date":"2026-02-25T10:36:44","date_gmt":"2026-02-25T10:36:44","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/"},"modified":"2026-02-25T10:36:44","modified_gmt":"2026-02-25T10:36:44","slug":"process-decomposition-dfd","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/","title":{"rendered":"Principles of Process Decomposition"},"content":{"rendered":"<p>Most modeling teams waste hours chasing inconsistencies because they treat process decomposition as a mechanical task\u2014breaking down a system into smaller parts without first clarifying intent. The real issue isn\u2019t complexity; it\u2019s ambiguity in purpose. I\u2019ve seen teams decompose a single \u201cProcess 3\u201d into seven sub-processes, only to discover that none of them actually produce a distinct output or satisfy a clear input requirement. That\u2019s not decomposition\u2014it\u2019s over-engineering.<\/p>\n<p>The shift that eliminates this waste is simple: think in terms of **functional decomposition**, not just structural breakdown. Every sub-process must answer one question: what unique transformation does it perform on its inputs to generate a measurable output? If it can\u2019t, it either isn\u2019t a process, or it\u2019s part of a larger function that needs redefining. This mindset is the foundation of accurate DFD modeling.<\/p>\n<p>This chapter teaches you how to apply this principle with precision. You\u2019ll learn how to identify processes that are truly atomic, how to define unambiguous input-output relationships, and how to avoid the common pitfalls of over-decomposition and under-decomposition. By the end, you\u2019ll have a reliable, repeatable method for breaking down complex systems\u2014without losing traceability or introducing contradictions.<\/p>\n<h2>Foundations of Functional Decomposition<\/h2>\n<h3>What Makes a Process \u201cAtomic\u201d?<\/h3>\n<p>Atomic processes are the smallest units of transformation in a DFD. They can\u2019t be meaningfully broken down further without losing their functional integrity.<\/p>\n<p>Ask yourself: can this process be described in a single, clear action verb phrase (e.g., \u201cvalidate user credentials\u201d or \u201ccalculate tax\u201d) that results in a distinct data output?<\/p>\n<p>If yes, it\u2019s atomic. If no, it likely involves multiple actions and should be split into logical sub-processes.<\/p>\n<h3>Key Indicators of Non-Atomic Processes<\/h3>\n<ul>\n<li>Requires multiple input data flows but produces only one output.<\/li>\n<li>Contains conditional logic (e.g., \u201cif-then\u201d) but doesn\u2019t separate branching into distinct processes.<\/li>\n<li>Relies on internal decision-making not reflected in the data flows.<\/li>\n<li>Named with vague or compound verbs (e.g., \u201cprocess and update\u201d or \u201chandle payment and notify\u201d).<\/li>\n<\/ul>\n<h3>Practical Rule: One Output, One Transformation<\/h3>\n<p>Every atomic process must have exactly one output, even if it\u2019s a complex data structure. This ensures clarity, traceability, and alignment with the principle of functional decomposition.<\/p>\n<p>If a process generates multiple distinct outputs (e.g., a report and a confirmation), they should be separated into two atomic processes unless they are functionally inseparable (e.g., a batch of output is generated as a single unit).<\/p>\n<h2>Identifying Processes: A Systematic Approach<\/h2>\n<h3>Step 1: Start with the Parent Process<\/h3>\n<p>Begin by reviewing the parent process. What is its purpose? What data does it consume, and what new data does it produce?<\/p>\n<p>Then ask: \u201cWhat specific action transforms this input into that output?\u201d The answer is your candidate for a sub-process.<\/p>\n<h3>Step 2: Apply the Input-Output Test<\/h3>\n<p>For each candidate process, verify the following:<\/p>\n<ul>\n<li>Does it consume at least one input from the parent process?<\/li>\n<li>Does it generate at least one output that becomes part of the parent\u2019s output?<\/li>\n<li>Is the transformation logically complete and independent of other processes?<\/li>\n<\/ul>\n<p>If any test fails, the process is not atomic and should be re-evaluated or split.<\/p>\n<h3>Step 3: Name with Action Verbs<\/h3>\n<p>Use active, precise verbs. Avoid nouns or passive phrasing.<\/p>\n<p>Incorrect: \u201cPayment processing\u201d \u2192 Too broad, lacks action.<\/p>\n<p>Correct: \u201cValidate payment details\u201d \u2192 Clear, measurable.<\/p>\n<h3>Step 4: Check for Duplicates and Overlap<\/h3>\n<p>Compare all sub-processes. Do any perform the same transformation on the same inputs? If so, they\u2019re redundant and should be merged.<\/p>\n<p>Are there gaps in data flow? If an input is consumed but no output is produced, the process is incomplete.<\/p>\n<h2>Avoiding Common Pitfalls in System Breakdown DFD<\/h2>\n<h3>Over-Decomposition: When More Isn\u2019t Better<\/h3>\n<p>Breaking a process into more than five sub-processes often indicates over-decomposition. Ask: \u201cCould this be a single decision point, or are we treating control logic as process logic?\u201d<\/p>\n<p>For example, splitting \u201cvalidate input\u201d into \u201ccheck format,\u201d \u201cverify length,\u201d and \u201ccompare to rules\u201d is unnecessary unless each step produces a distinct intermediate output.<\/p>\n<h3>Under-Decomposition: The Hidden Logic Trap<\/h3>\n<p>One of the most frequent errors I\u2019ve seen is combining distinct transformations into a single process labeled \u201cprocess data.\u201d This hides critical logic and makes balancing and validation nearly impossible.<\/p>\n<p>Every decision point requires a process. If data changes based on a condition (e.g., \u201cif valid, proceed; if invalid, return error\u201d), then the decision and both outcomes must be modeled as separate processes.<\/p>\n<h3>Table: Signs of Over- or Under-Decomposition<\/h3>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Issue<\/th>\n<th>Signs<\/th>\n<th>Fix<\/th>\n<\/tr>\n<tr>\n<td>Over-Decomposition<\/td>\n<td>More than 5 sub-processes for one parent; similar-sounding names; shared inputs but no outputs.<\/td>\n<td>Group small, related transformations; ensure each sub-process has a unique output.<\/td>\n<\/tr>\n<tr>\n<td>Under-Decomposition<\/td>\n<td>One process handles multiple logic paths; no clear output from decision-making.<\/td>\n<td>Break into separate processes for each branch; model decisions as processes.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Ensuring Data Flow Integrity in Decomposition<\/h2>\n<h3>Use the \u201cInput-Output\u201d Filter<\/h3>\n<p>Before finalizing any DFD level, apply this filter:<\/p>\n<ol>\n<li>Every input to a sub-process must come from a parent output or a data store.<\/li>\n<li>Every output from a sub-process must be used by a parent output, another sub-process, or a data store.<\/li>\n<li>Do not introduce data flows that aren\u2019t traceable from the parent.<\/li>\n<\/ol>\n<p>Violations here indicate either missing decomposition or incorrect data flow design.<\/p>\n<h3>Traceability Through the Data Dictionary<\/h3>\n<p>Each process name and data flow must be defined in the data dictionary. This ensures consistency across levels.<\/p>\n<p>Example:<\/p>\n<pre><code>Process: Validate User Credentials\nInputs: User ID, Password (from Login Request)\nOutputs: Validated User Record, Error Message (if invalid)\nData Store: User Database (read only)<\/code><\/pre>\n<p>Without a data dictionary, even small naming changes can break traceability.<\/p>\n<h2>Best Practices for Sustainable DFD Modeling<\/h2>\n<h3>Checklist: Validating Process Decomposition<\/h3>\n<ul>\n<li>Each sub-process has a single, well-defined output.<\/li>\n<li>All inputs are derived from parent outputs or data stores.<\/li>\n<li>No process produces output without consuming input.<\/li>\n<li>All process names use active verbs and are unique.<\/li>\n<li>Decision-making is modeled as a process, not implied in flow lines.<\/li>\n<\/ul>\n<h3>Practical Tip: Use Process Labels Consistently<\/h3>\n<p>Always number processes hierarchically (e.g., 2.1, 2.2). This makes it easy to trace their origin and validate consistency across levels.<\/p>\n<h3>Remember: Decomposition Is Not Simplification<\/h3>\n<p>Decomposition isn\u2019t about making a model smaller\u2014it\u2019s about making it more transparent. The goal is not fewer boxes, but clearer logic.<\/p>\n<p>Each sub-process should be understandable on its own. If you can\u2019t explain it in a sentence or two without referencing other processes, it\u2019s not decomposed properly.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know when I\u2019ve decomposed enough?<\/h3>\n<p>When each sub-process performs one distinct transformation, consumes defined inputs, and generates a measurable output. If the process name includes \u201cand\u201d or \u201cthen,\u201d it\u2019s not atomic. Stop when you can describe the function in one sentence using an active verb.<\/p>\n<h3>Can I break down a data store into processes?<\/h3>\n<p>No. Data stores represent persistent information, not transformations. However, operations on data stores (e.g., \u201cread user profile,\u201d \u201cupdate record\u201d) are processes and should be modeled as such.<\/p>\n<h3>What if two processes produce the same output?<\/h3>\n<p>This is acceptable only if both processes are independent and serve different purposes. But if the output is functionally identical, they should be merged into one process unless there\u2019s a clear reason for separation (e.g., different data sources).<\/p>\n<h3>How do I handle conditional logic in process decomposition?<\/h3>\n<p>Model each decision outcome as a separate process. For example, \u201cif valid \u2192 approve; if invalid \u2192 reject\u201d should be two processes: \u201cValidate Application\u201d and \u201cReject Application.\u201d The decision itself is not a process but triggers the output.<\/p>\n<h3>Should I use the same name for a parent and child process?<\/h3>\n<p>No. Avoid naming conflicts. Use descriptive hierarchy: e.g., \u201cProcess 2.1: Validate ID\u201d instead of \u201cProcess 1: Validate ID.\u201d This prevents confusion and supports traceability.<\/p>\n<h3>What\u2019s the difference between functional decomposition and structural decomposition?<\/h3>\n<p>Functional decomposition focuses on *what* the system does\u2014breaking it into processes by function. Structural decomposition focuses on *how* it\u2019s built (e.g., components, modules). DFD modeling is functional decomposition. The focus is always on data transformation, not physical components.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most modeling teams waste hours chasing inconsistencies because they treat process decomposition as a mechanical task\u2014breaking down a system into smaller parts without first clarifying intent. The real issue isn\u2019t complexity; it\u2019s ambiguity in purpose. I\u2019ve seen teams decompose a single \u201cProcess 3\u201d into seven sub-processes, only to discover that none of them actually produce [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1138,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1139","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Process Decomposition DFD<\/title>\n<meta name=\"description\" content=\"Master process decomposition in DFD with expert techniques for identifying atomic processes and defining clear input-output relationships. Ideal for systems analysts and IT professionals.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Process Decomposition DFD\" \/>\n<meta property=\"og:description\" content=\"Master process decomposition in DFD with expert techniques for identifying atomic processes and defining clear input-output relationships. Ideal for systems analysts and IT professionals.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/\",\"name\":\"Process Decomposition DFD\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:36:44+00:00\",\"description\":\"Master process decomposition in DFD with expert techniques for identifying atomic processes and defining clear input-output relationships. Ideal for systems analysts and IT professionals.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering Data Flow Diagram Levels and Balancing\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Techniques for DFD Leveling\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Principles of Process Decomposition\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Process Decomposition DFD","description":"Master process decomposition in DFD with expert techniques for identifying atomic processes and defining clear input-output relationships. Ideal for systems analysts and IT professionals.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/","og_locale":"de_DE","og_type":"article","og_title":"Process Decomposition DFD","og_description":"Master process decomposition in DFD with expert techniques for identifying atomic processes and defining clear input-output relationships. Ideal for systems analysts and IT professionals.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"7\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/","name":"Process Decomposition DFD","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:36:44+00:00","description":"Master process decomposition in DFD with expert techniques for identifying atomic processes and defining clear input-output relationships. Ideal for systems analysts and IT professionals.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/process-decomposition-dfd\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"Mastering Data Flow Diagram Levels and Balancing","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/"},{"@type":"ListItem","position":3,"name":"Techniques for DFD Leveling","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/"},{"@type":"ListItem","position":4,"name":"Principles of Process Decomposition"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1139","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1139\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1138"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1139"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}