{"id":631,"date":"2026-02-25T10:21:32","date_gmt":"2026-02-25T10:21:32","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/"},"modified":"2026-02-25T10:21:32","modified_gmt":"2026-02-25T10:21:32","slug":"dfd-process-numbering-fixed-hierarchies","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/","title":{"rendered":"Incorrect Process Numbering and Broken Hierarchies"},"content":{"rendered":"<p>When I first encountered a team that had numbered their processes as 1, 3, and 7 across Level 1, I knew the model was already leaking logic. Numbering isn&#8217;t just about order\u2014it\u2019s about signaling hierarchy, enabling traceability, and ensuring that every process has a clear parent. Arbitrary IDs create confusion, especially in larger systems where context is already fragile.<\/p>\n<p>Many analysts treat process numbering as an afterthought, not realizing that inconsistent or broken DFD hierarchy numbering undermines every other best practice. The real issue isn\u2019t the number itself\u2014it\u2019s what it fails to communicate: the relationship between parent and child diagrams.<\/p>\n<p>By the end of this chapter, you\u2019ll understand a simple, scalable numbering convention that enforces logical decomposition. You\u2019ll see how consistent DFD IDs save time in reviews, reduce miscommunication, and make it easy to validate that each process is properly broken down.<\/p>\n<h2>Why Numbering Matters More Than You Think<\/h2>\n<p>Process numbering isn&#8217;t about aesthetics. It\u2019s about structure.<\/p>\n<p>A single rule governs every DFD: the parent process must be decomposed into processes that are numbered with a hierarchy that reflects their position in the model.<\/p>\n<p>If your Level 1 processes are labeled 4, 8, and 12, you\u2019ve already lost the reader. You&#8217;re not just making the diagram hard to follow\u2014you\u2019re breaking the most fundamental principle of DFD leveling.<\/p>\n<h3>The Hidden Cost of Arbitrary Numbering<\/h3>\n<p>Let\u2019s be clear: skipping numbers or using non-sequential ID schemes doesn&#8217;t make your diagram more &#8222;flexible.&#8220; It makes it harder to maintain, validate, and explain.<\/p>\n<p>Imagine a stakeholder asking, \u201cWhere did the customer data come from?\u201d You can&#8217;t answer because the flow originated in a process labeled \u201cStep 5,\u201d but in the parent diagram, it\u2019s represented as \u201cProcess C.\u201d That disconnect happens when numbering doesn\u2019t reflect hierarchy.<\/p>\n<p>Here\u2019s what I\u2019ve seen in real projects: a Level 1 process labeled \u201c3.1\u201d while another is \u201c3.11.\u201d No one noticed that it wasn\u2019t a typo\u2014it was a broken numbering scheme. This isn\u2019t just messy; it\u2019s a red flag for poor modeling discipline.<\/p>\n<h2>A Simple, Effective Numbering Convention<\/h2>\n<p>Use a clear, hierarchical numbering system\u2014like 1.1, 1.2, 2.1, 2.2\u2014that mirrors how your processes are decomposed.<\/p>\n<p>When a process is decomposed into sub-processes, the child IDs must begin with the parent&#8217;s ID followed by a decimal and a unique digit.<\/p>\n<p>For example:<\/p>\n<ul>\n<li>Level 0: Process 1.0 (e.g., \u201cProcess Customer Order\u201d)<\/li>\n<li>Level 1: 1.1 (Validate Order), 1.2 (Check Inventory), 1.3 (Confirm Payment)<\/li>\n<li>Level 2: 1.1.1 (Check Order Form), 1.1.2 (Verify Customer ID), etc.<\/li>\n<\/ul>\n<p>This structure gives every process a unique, traceable ID and makes it instantly clear which processes are children of which.<\/p>\n<h3>Why This Works in Practice<\/h3>\n<p>I\u2019ve used this method on projects with over 50 processes. The first time I applied it, a junior analyst asked, \u201cWait, how do I know which process to look at when I see 2.4?\u201d That question went from confusion to clarity in seconds. The numbering answered it.<\/p>\n<p>It also makes validation easier. When reviewing a diagram, you can quickly check whether each parent process has a logically ordered set of children. If you see 3.1, 3.3, and 3.5, you suspect a missing 3.2 or 3.4\u2014something worth investigating.<\/p>\n<h2>Common Mistakes in DFD Process Numbering<\/h2>\n<p>Even experienced analysts make these errors. Here\u2019s what to watch for:<\/p>\n<h3>Skipping Levels or Numbers<\/h3>\n<p>Using 1, 2, 4, 5 instead of 1, 2, 3, 4 creates gaps that don\u2019t signal structure\u2014they signal oversight.<\/p>\n<p>Example: A process labeled \u201c2.1\u201d has no \u201c2.0\u201d parent. That\u2019s a red flag. The correct hierarchy should be 2.0 \u2192 2.1, 2.2, etc.<\/p>\n<h3>Mixing Numbering Schemes<\/h3>\n<p>Some teams use \u201cProcess 3\u201d for Level 1 and \u201c3.1\u201d for Level 2. That\u2019s inconsistent. Use the same format across all levels.<\/p>\n<p>Stick to decimals: 1.1, 1.2, 2.1, etc. It keeps things predictable and scalable.<\/p>\n<h3>Reusing IDs Across Diagrams<\/h3>\n<p>Don\u2019t reuse \u201c3.1\u201d in a different branch of the DFD. That invites confusion and breaks traceability.<\/p>\n<p>Each ID should be unique within the model, even if it appears in a different subtree.<\/p>\n<h2>Before and After: A Real Example<\/h2>\n<p>Consider this flawed scenario:<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Level<\/th>\n<th>Process ID<\/th>\n<th>Name<\/th>\n<th>Issue<\/th>\n<\/tr>\n<tr>\n<td>1<\/td>\n<td>5<\/td>\n<td>Process Order<\/td>\n<td>Arbitrary ID\u2014no hierarchy<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>5.1<\/td>\n<td>Validate Details<\/td>\n<td>Child of 5, but 5 has no parent<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>7.1<\/td>\n<td>Check Inventory<\/td>\n<td>Disconnected from main flow<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Now the corrected version:<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Level<\/th>\n<th>Process ID<\/th>\n<th>Name<\/th>\n<th>Corrected ID<\/th>\n<\/tr>\n<tr>\n<td>0<\/td>\n<td>1.0<\/td>\n<td>Process Customer Order<\/td>\n<td>Root process<\/td>\n<\/tr>\n<tr>\n<td>1<\/td>\n<td>1.1<\/td>\n<td>Validate Order<\/td>\n<td>Child of 1.0<\/td>\n<\/tr>\n<tr>\n<td>1<\/td>\n<td>1.2<\/td>\n<td>Check Inventory<\/td>\n<td>Child of 1.0<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>1.1.1<\/td>\n<td>Verify Customer Info<\/td>\n<td>Child of 1.1<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>1.1.2<\/td>\n<td>Check Order Form<\/td>\n<td>Child of 1.1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Notice the clarity? Each process has a unique, hierarchical ID. There\u2019s no guesswork.<\/p>\n<h2>Checklist: Ensuring Clean DFD Process Numbering<\/h2>\n<p>Use this checklist before finalizing any DFD model:<\/p>\n<ul>\n<li>Every process has a unique ID that reflects its hierarchical position.<\/li>\n<li>Child process IDs begin with the parent\u2019s ID followed by a decimal and a digit.<\/li>\n<li>Numbering is sequential and does not skip values.<\/li>\n<li>Same ID is never reused across different branches of the model.<\/li>\n<li>Modeling tools enforce consistent IDs where available.<\/li>\n<li>Reviewers check for hierarchy breaks in every diagram.<\/li>\n<\/ul>\n<p>Apply this to every level. It takes minutes to implement\u2014but the impact lasts for years.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Should I use 1.1, 1.1.1, or 1.1.1.1 for deep decomposition?<\/h3>\n<p>Use up to three decimal places. Beyond that, the IDs become unwieldy and hard to read. If you need more depth, consider breaking the process into a separate diagram or splitting it into higher-level functions.<\/p>\n<h3>Can I mix Roman numerals and Arabic numerals in DFD numbering?<\/h3>\n<p>No. Stick to one system. Roman numerals (e.g., I.1, I.2) may look formal but disrupt consistency and are harder to validate. Use Arabic numerals with decimals for clarity and scalability.<\/p>\n<h3>What if my process is named \u201cProcess 1,\u201d but the ID is \u201c1.1\u201d?<\/h3>\n<p>That\u2019s acceptable, as long as the ID reflects its hierarchical position. The name can be descriptive (\u201cValidate Order\u201d), but the ID must signal its place in the model.<\/p>\n<h3>Do all levels need to be numbered the same way?<\/h3>\n<p>Yes. Uniformity in numbering across levels is critical. Don\u2019t switch between \u201cStep 1,\u201d \u201c1.1,\u201d and \u201cProcess A\u201d \u2014 it breaks consistency and confuses readers.<\/p>\n<h3>How do I handle processes that are not directly decomposed but still needed?<\/h3>\n<p>If a process isn\u2019t decomposed, it should be at the highest level (e.g., Level 0 or Level 1). Do not create child processes just to assign a number. If decomposition is needed, ensure the numbering reflects that.<\/p>\n<h3>Can I rename a process without changing its ID?<\/h3>\n<p>Yes. The ID is a structural identifier, not a name. Renaming the process is fine as long as the ID remains consistent. Always document changes in a revision log.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I first encountered a team that had numbered their processes as 1, 3, and 7 across Level 1, I knew the model was already leaking logic. Numbering isn&#8217;t just about order\u2014it\u2019s about signaling hierarchy, enabling traceability, and ensuring that every process has a clear parent. Arbitrary IDs create confusion, especially in larger systems where [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":627,"menu_order":3,"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-631","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 Process Numbering: Fix Broken Hierarchies<\/title>\n<meta name=\"description\" content=\"Master DFD process numbering to ensure clean hierarchy, consistent IDs, and easy review. Learn how to avoid broken DFD level numbering and enforce logical decomposition.\" \/>\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\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DFD Process Numbering: Fix Broken Hierarchies\" \/>\n<meta property=\"og:description\" content=\"Master DFD process numbering to ensure clean hierarchy, consistent IDs, and easy review. Learn how to avoid broken DFD level numbering and enforce logical decomposition.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/\" \/>\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=\"5\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\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/\",\"name\":\"DFD Process Numbering: Fix Broken Hierarchies\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:21:32+00:00\",\"description\":\"Master DFD process numbering to ensure clean hierarchy, consistent IDs, and easy review. Learn how to avoid broken DFD level numbering and enforce logical decomposition.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common DFD Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Leveling and Decomposition Errors\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Incorrect Process Numbering and Broken Hierarchies\"}]},{\"@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":"DFD Process Numbering: Fix Broken Hierarchies","description":"Master DFD process numbering to ensure clean hierarchy, consistent IDs, and easy review. Learn how to avoid broken DFD level numbering and enforce logical decomposition.","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\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/","og_locale":"de_DE","og_type":"article","og_title":"DFD Process Numbering: Fix Broken Hierarchies","og_description":"Master DFD process numbering to ensure clean hierarchy, consistent IDs, and easy review. Learn how to avoid broken DFD level numbering and enforce logical decomposition.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"5\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/","name":"DFD Process Numbering: Fix Broken Hierarchies","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:21:32+00:00","description":"Master DFD process numbering to ensure clean hierarchy, consistent IDs, and easy review. Learn how to avoid broken DFD level numbering and enforce logical decomposition.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-process-numbering-fixed-hierarchies\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"Common DFD Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Leveling and Decomposition Errors","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/"},{"@type":"ListItem","position":4,"name":"Incorrect Process Numbering and Broken Hierarchies"}]},{"@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\/631","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\/631\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/627"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=631"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=631"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}