{"id":628,"date":"2026-02-25T10:21:31","date_gmt":"2026-02-25T10:21:31","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/"},"modified":"2026-02-25T10:21:31","modified_gmt":"2026-02-25T10:21:31","slug":"dfd-level-progression","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/","title":{"rendered":"No Logical Progression Between DFD Levels"},"content":{"rendered":"<p>Imagine a system where a user submits a form, and the data flows through a series of steps. On the Level 0 DFD, you see one process: \u201cProcess Order.\u201d At Level 1, you expect to see a breakdown of that single step\u2014validating inputs, checking inventory, and creating a record. But what if Level 1 shows \u201cSend Email,\u201d \u201cUpdate Dashboard,\u201d and \u201cLog Error\u201d\u2014none of which are part of the original order process?<\/p>\n<p>This mismatch is a classic symptom of poor DFD level progression. The decomposition doesn\u2019t reflect the parent process; instead, it introduces unrelated actions. This breaks the logical flow and makes the model unreliable for analysis, design, or communication.<\/p>\n<p>Over 20 years guiding teams through complex data modeling, I\u2019ve seen this repeated across industries\u2014finance, logistics, healthcare\u2014where a misaligned decomposition leads to misdirected development, missed data requirements, and stakeholder confusion. The fix isn\u2019t about better tools. It\u2019s about disciplined, traceable DFD decomposition.<\/p>\n<p>This chapter walks you through what a proper progression from Level 0 to Level 1 should look like, how to identify flawed decompositions, and a tested technique to verify that every process on a parent diagram is fully and correctly decomposed.<\/p>\n<h2>What a Proper DFD Level Progression Should Look Like<\/h2>\n<p>Every process on a higher-level DFD must be decomposed into child processes that refine, not replace, its function. The child diagram should explain how the parent process actually works\u2014without introducing new, unrelated responsibilities.<\/p>\n<p>Consider the Level 0 process: <strong>\u201cProcess Order\u201d<\/strong>. This is a high-level abstraction. The correct decomposition at Level 1 should reveal the internal logic\u2014what actually happens when an order is processed.<\/p>\n<p>Here\u2019s how it should look:<\/p>\n<ul>\n<li><strong>Validate Order Inputs<\/strong> \u2013 Check if all required fields are present and conform to format.<\/li>\n<li><strong>Check Inventory Availability<\/strong> \u2013 Query stock levels for each item.<\/li>\n<li><strong>Create Order Record<\/strong> \u2013 Store the order in the database with status \u201cPending\u201d.<\/li>\n<li><strong>Trigger Payment Processing<\/strong> \u2013 Pass order data to the payment module.<\/li>\n<\/ul>\n<p>Each of these child processes directly contributes to the outcome of \u201cProcess Order.\u201d There are no gaps, no magic, no side effects. This is clean DFD decomposition alignment.<\/p>\n<p>Now contrast it with a common trap:<\/p>\n<ul>\n<li><strong>Update Customer Dashboard<\/strong><\/li>\n<li><strong>Send Confirmation Email<\/strong><\/li>\n<li><strong>Log Error<\/strong> (if any)<\/li>\n<li><strong>Process Order<\/strong> (repeated as a sub-process)<\/li>\n<\/ul>\n<p>Here, \u201cUpdate Customer Dashboard\u201d and \u201cSend Confirmation Email\u201d are not part of order processing\u2014they are follow-up actions, often part of a different process like \u201cNotify Customer.\u201d Introducing them here breaks the <strong>parent-child DFD relationship<\/strong>.<\/p>\n<h2>How to Catch Misaligned Decompositions<\/h2>\n<p>Don\u2019t rely on intuition. Use a structured cross-check method to ensure that every process in a parent diagram is properly decomposed.<\/p>\n<p>Here\u2019s a simple, field-tested technique I\u2019ve used in audits and design reviews:<\/p>\n<ol>\n<li><strong>List all processes on the parent diagram<\/strong>\u2014no exceptions. For Level 0, this is often just 1\u20133 processes.<\/li>\n<li><strong>For each process<\/strong>, go to its corresponding child diagram (e.g., Level 1 for Level 0).<\/li>\n<li><strong>Verify that every function<\/strong> in the parent process is represented by one or more processes in the child.<\/li>\n<li><strong>Check for orphans<\/strong>\u2014any processes in the child that have no traceable link to the parent.<\/li>\n<li><strong>Confirm no new responsibilities<\/strong> appear in the child that weren\u2019t implied in the parent.<\/li>\n<\/ol>\n<p>This is not just about matching names. It\u2019s about functional coherence. If the parent says \u201cProcess Order,\u201d the child should break down what that process actually does\u2014not what happens after.<\/p>\n<h3>Example: Correct vs Incorrect DFD Level Progression<\/h3>\n<p>Let\u2019s compare two Level 1 views of \u201cProcess Order.\u201d<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Parent Process<\/th>\n<th>Correct Child Processes (Aligned)<\/th>\n<th>Incorrect Child Processes (Misaligned)<\/th>\n<\/tr>\n<tr>\n<td>Process Order<\/td>\n<td>Validate Inputs<br \/>Check Inventory<br \/>Create Order Record<br \/>Trigger Payment<\/td>\n<td>Send Email<br \/>Update Dashboard<br \/>Log Error<br \/>Process Order<\/td>\n<\/tr>\n<tr>\n<td>Process Order<\/td>\n<td>\u2714 All functions are parts of order processing<\/td>\n<td>\u2716 Email and dashboard updates are external to order processing<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The second example introduces processes that are not decomposition steps\u2014they are side effects. This breaks the <strong>DFD decomposition alignment<\/strong> principle and creates a misleading model.<\/p>\n<h2>Why Some Decompositions Fail<\/h2>\n<p>Even when teams mean well, certain patterns undermine DFD level progression:<\/p>\n<ul>\n<li><strong>Confusing action verbs<\/strong> \u2013 Using \u201cUpdate\u201d or \u201cSend\u201d as process names often indicates that the process is about side effects, not data transformation.<\/li>\n<li><strong>Introducing external actors too early<\/strong> \u2013 If a child diagram shows \u201cSend Email to Customer,\u201d but the parent process doesn\u2019t mention customers, the flow is disconnected.<\/li>\n<li><strong>Splitting unrelated functions<\/strong> \u2013 Breaking \u201cProcess Order\u201d into \u201cCreate Record\u201d and \u201cNotify Customer\u201d without a shared context creates two independent processes.<\/li>\n<li><strong>Reusing a process name<\/strong> \u2013 \u201cProcess Order\u201d used in a different context (e.g., a reporting process) can cause confusion if not clearly separated.<\/li>\n<\/ul>\n<p>These are not trivial. They create a fragmented mental model. When stakeholders see different meanings for the same process name, trust in the DFD erodes.<\/p>\n<h2>Practical Tips to Maintain Logical Progression<\/h2>\n<p>Here\u2019s how to keep your DFDs aligned and meaningful:<\/p>\n<ol>\n<li><strong>Use process names that reflect transformation<\/strong> \u2013 Replace \u201cSend Email\u201d with \u201cGenerate and Dispatch Confirmation.\u201d The verb should describe data change.<\/li>\n<li><strong>Define a process contract<\/strong> \u2013 For each process, write a short statement: \u201cThis process transforms input X into output Y.\u201d If you can\u2019t, the process may be too broad or misaligned.<\/li>\n<li><strong>Apply the \u201cSo what?\u201d test<\/strong> \u2013 Ask: \u201cWhy does this process exist?\u201d If the answer isn\u2019t tied to the parent process\u2019s purpose, reconsider its place.<\/li>\n<li><strong>Map each child process back to the parent<\/strong> \u2013 Use a simple traceability table to track which parent process each child contributes to.<\/li>\n<li><strong>Use modeling tools with validation<\/strong> \u2013 Diagrams in Visual Paradigm or similar can flag orphan processes or missing flows during review.<\/li>\n<\/ol>\n<p>These practices aren\u2019t just about correctness\u2014they\u2019re about creating a model that people can actually use. A DFD with proper <strong>linking level 0 and level 1 DFD<\/strong> relationships becomes a living guide, not a static diagram.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What happens if I decompose a process but miss a key function?<\/h3>\n<p>Missing functions create blind spots. In development, that function might be forgotten, leading to bugs or data loss. In audits, the flow appears incomplete. Always cross-check child processes against the parent\u2019s purpose.<\/p>\n<h3>Can a parent process have multiple child diagrams?<\/h3>\n<p>Yes\u2014but only if they represent different logical parts of the same process. For example, \u201cProcess Order\u201d might have one child diagram for validation and another for payment processing. Ensure the decomposition is cohesive, not scattered.<\/p>\n<h3>Is it okay to have a child process that doesn\u2019t directly feed into the parent?<\/h3>\n<p>No. Every child process must be functionally part of achieving the parent\u2019s outcome. If it\u2019s not, it\u2019s either a separate process or an orphan\u2014both of which break DFD integrity.<\/p>\n<h3>How do I know when decomposition is complete?<\/h3>\n<p>When all child processes are small enough to be easily testable and maintainable. A rule of thumb: if a process does more than one clear transformation (e.g., \u201cvalidate,\u201d \u201ccalculate,\u201d \u201cstore\u201d), it should be split.<\/p>\n<h3>Do I need to decompose every process in a DFD?<\/h3>\n<p>Only if it\u2019s complex or critical. For low-risk processes, a high-level description may suffice. But if the process affects data integrity, compliance, or performance, decomposition is essential. Use risk-based judgment.<\/p>\n<h3>Can a single process at Level 0 map to multiple processes at Level 1?<\/h3>\n<p>Yes\u2014this is normal and expected. A complex process must be broken into logical steps. The key is that each step must contribute directly to the outcome of the parent process. No side effects.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Imagine a system where a user submits a form, and the data flows through a series of steps. On the Level 0 DFD, you see one process: \u201cProcess Order.\u201d At Level 1, you expect to see a breakdown of that single step\u2014validating inputs, checking inventory, and creating a record. But what if Level 1 shows [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":627,"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-628","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>DFD Level Progression: Avoiding Breaks in Logical Flow<\/title>\n<meta name=\"description\" content=\"Ensure proper DFD level progression with clear linking between Level 0 and Level 1 DFDs. Learn how to align decomposition and avoid orphan processes for accurate, maintainable data flow modeling.\" \/>\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\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DFD Level Progression: Avoiding Breaks in Logical Flow\" \/>\n<meta property=\"og:description\" content=\"Ensure proper DFD level progression with clear linking between Level 0 and Level 1 DFDs. Learn how to align decomposition and avoid orphan processes for accurate, maintainable data flow modeling.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/\",\"name\":\"DFD Level Progression: Avoiding Breaks in Logical Flow\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:21:31+00:00\",\"description\":\"Ensure proper DFD level progression with clear linking between Level 0 and Level 1 DFDs. Learn how to align decomposition and avoid orphan processes for accurate, maintainable data flow modeling.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common DFD Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Leveling and Decomposition Errors\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"No Logical Progression Between DFD Levels\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DFD Level Progression: Avoiding Breaks in Logical Flow","description":"Ensure proper DFD level progression with clear linking between Level 0 and Level 1 DFDs. Learn how to align decomposition and avoid orphan processes for accurate, maintainable data flow modeling.","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\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/","og_locale":"pl_PL","og_type":"article","og_title":"DFD Level Progression: Avoiding Breaks in Logical Flow","og_description":"Ensure proper DFD level progression with clear linking between Level 0 and Level 1 DFDs. Learn how to align decomposition and avoid orphan processes for accurate, maintainable data flow modeling.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/","name":"DFD Level Progression: Avoiding Breaks in Logical Flow","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:21:31+00:00","description":"Ensure proper DFD level progression with clear linking between Level 0 and Level 1 DFDs. Learn how to align decomposition and avoid orphan processes for accurate, maintainable data flow modeling.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-level-progression\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Common DFD Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Leveling and Decomposition Errors","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/"},{"@type":"ListItem","position":4,"name":"No Logical Progression Between DFD Levels"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/628","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/628\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/627"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=628"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=628"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}