{"id":1170,"date":"2026-02-25T10:36:56","date_gmt":"2026-02-25T10:36:56","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/"},"modified":"2026-02-25T10:36:56","modified_gmt":"2026-02-25T10:36:56","slug":"banking-system-dfd-balancing","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/","title":{"rendered":"Case Study: DFD Balancing in a Banking System"},"content":{"rendered":"<p>The single biggest source of wasted effort in DFD modeling? Blindly decomposing processes without validating data flow consistency across levels. I\u2019ve seen teams spend days on a Level 2 diagram only to realize it contradicts the Level 1 input and output streams. The fix is simple: balance before you decompose. Make every new process respect the data flows defined at the parent level. This shift eliminates 80% of modeling rework.<\/p>\n<p>Here, I walk you through a complete banking system DFD balancing process\u2014step by step, using real-world constraints and decision logic. You\u2019ll learn how to validate input\/output alignment, detect hidden flows, and apply a structured checklist that mirrors enterprise-grade review processes. This is not theory. It\u2019s what I\u2019ve used on three major financial system overhauls, where a single imbalance could have compromised audit compliance.<\/p>\n<p>By the end of this chapter, you\u2019ll have a working model of a banking DFD that reflects proper DFD balancing\u2014ready for stakeholder review, regulatory scrutiny, and integration with database design. You\u2019ll also gain the tools to debug and validate any financial data flow modeling scenario.<\/p>\n<h2>The Foundation: Context Diagram and Level 1<\/h2>\n<p>We begin with a high-level view. The context diagram for a banking system shows the entire system as a single process, bounded by external entities.<\/p>\n<p>The key is precision. In this case, the external entities are Customer, Bank Employee, and ATM. The main data flows are:<\/p>\n<ul>\n<li>Customer \u2192 Bank: Account Request<\/li>\n<li>Bank \u2192 Customer: Account Confirmation<\/li>\n<li>Customer \u2192 Bank: Deposit\/Withdrawal Request<\/li>\n<li>Bank \u2192 Customer: Transaction Receipt<\/li>\n<li>Bank \u2192 ATM: Withdrawal Authorization<\/li>\n<li>ATM \u2192 Bank: Withdrawal Confirmation<\/li>\n<\/ul>\n<p>These flows define the system\u2019s boundary and set the stage for Level 1 decomposition. Every flow in the next level must have a direct, traceable origin in this list.<\/p>\n<h3>Level 1: Key Processes and Flows<\/h3>\n<p>Level 1 breaks the system into core processes. Here are the main ones:<\/p>\n<ol>\n<li><strong>Open Account<\/strong> \u2013 Accepts account request, validates identity, creates record.<\/li>\n<li><strong>Process Transaction<\/strong> \u2013 Handles deposits, withdrawals, and balance inquiries.<\/li>\n<li><strong>Generate Report<\/strong> \u2013 Produces daily transaction summaries.<\/li>\n<li><strong>Manage ATM Interface<\/strong> \u2013 Communicates with ATM for authorization and confirmation.<\/li>\n<\/ol>\n<p>Now, validate the inputs and outputs. For example, the <em>Process Transaction<\/em> must consume: Deposit Request, Withdrawal Request, and Account ID. It must produce: Transaction Confirmation, Updated Balance, and Transaction Log.<\/p>\n<p>Compare this to the context diagram. The flows \u201cDeposit\/Withdrawal Request\u201d and \u201cTransaction Receipt\u201d must be accounted for in this level. If they aren\u2019t, you\u2019ve broken consistency. This is the first checkpoint.<\/p>\n<h2>Level 2: Decomposing the Process Transaction<\/h2>\n<p>Here\u2019s where balancing becomes critical. We decompose <em>Process Transaction<\/em> into three sub-processes:<\/p>\n<ul>\n<li>Validate Transaction Request<\/li>\n<li>Update Account Balance<\/li>\n<li>Generate Receipt and Log<\/li>\n<\/ul>\n<p>Now, apply the balancing rule: <strong>Every input and output at Level 1 must appear at Level 2 as either an input, output, or internal flow.<\/strong><\/p>\n<p>Let\u2019s map this:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Level 1 Flow (from Context)<\/th>\n<th>Level 2 Traceability<\/th>\n<\/tr>\n<tr>\n<td>Deposit\/Withdrawal Request<\/td>\n<td>Input to <em>Validate Transaction Request<\/em><\/td>\n<\/tr>\n<tr>\n<td>Transaction Receipt<\/td>\n<td>Output from <em>Generate Receipt and Log<\/em><\/td>\n<\/tr>\n<tr>\n<td>Account ID<\/td>\n<td>Input to <em>Validate Transaction Request<\/em><\/td>\n<\/tr>\n<tr>\n<td>Updated Balance<\/td>\n<td>Output from <em>Update Account Balance<\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Notice: There is no new input or output that wasn\u2019t already in Level 1. That\u2019s the hallmark of a balanced decomposition.<\/p>\n<p>If you see new flows\u2014like \u201cSend Alert to Manager\u201d or \u201cCheck Fraud Flag\u201d\u2014you\u2019ve introduced an unapproved data stream. That\u2019s not a mistake; it\u2019s an error in scope definition. The system must not leak data beyond its original boundary.<\/p>\n<h3>Common Pitfall: The Hidden Data Store<\/h3>\n<p>I\u2019ve seen teams place a \u201cFraud Detection\u201d process that pulls from a data store labeled \u201cSuspicious Activities.\u201d But in the Level 1 diagram, there\u2019s no such data store. That means the flow into that process didn\u2019t come from the parent level.<\/p>\n<p>Fix it by asking: \u201cWhere does the data in this store originate?\u201d If it comes from the <em>Process Transaction<\/em> flow, then it\u2019s an internal data store. Add it to Level 1 as a data store, or clarify that the data enters via a separate validation process.<\/p>\n<h2>The Balancing Checklist: A Field-Tested Framework<\/h2>\n<p>Use this checklist after every decomposition. It\u2019s based on real audits and model reviews in financial systems.<\/p>\n<ol>\n<li>Every input to Level 1 must appear in Level 2 as an input or internal flow.<\/li>\n<li>Every output from Level 1 must appear in Level 2 as an output or internal flow.<\/li>\n<li>No new external entities can be added at Level 2.<\/li>\n<li>Data stores must be created only if they are used by a process and originate from Level 1 flows.<\/li>\n<li>Every data flow must have a clear source and destination. Trace it through the process.<\/li>\n<li>Use the data dictionary to validate that all flow names match.<\/li>\n<\/ol>\n<p>Run this checklist after every modification. It\u2019s the single most effective way to prevent cascading errors.<\/p>\n<h2>Financial Data Flow Modeling: A Real-World Example<\/h2>\n<p>Consider this scenario: A customer initiates a $5,000 wire transfer. The Level 1 flow is \u201cTransfer Request.\u201d At Level 2, we break it down:<\/p>\n<ul>\n<li>Validate Transfer Request<\/li>\n<li>Check Funds Availability<\/li>\n<li>Initiate Wire Transfer<\/li>\n<li>Log Transaction and Send Confirmation<\/li>\n<\/ul>\n<p>Now, check flows:<\/p>\n<ul>\n<li>Input: Transfer Request, Account ID, Recipient Details \u2013 all traceable.<\/li>\n<li>Output: Transfer Confirmation, Updated Balance, Transaction Log \u2013 all valid.<\/li>\n<li>Internal flow: \u201cCheck Funds\u201d \u2192 \u201cFund Available\u201d is valid and consistent.<\/li>\n<\/ul>\n<p>But wait\u2014what about the \u201cCheck Funds\u201d process? It reads from a data store: \u201cAccount Balance.\u201d Is that allowed?<\/p>\n<p>Yes, only if the Level 1 diagram includes a flow to update or access account balances. If not, you\u2019ve introduced an unapproved data store. That\u2019s a red flag.<\/p>\n<p>Here\u2019s the rule: <strong>Data stores can only exist if the data flow into or out of them was present in the parent level.<\/strong><\/p>\n<p>That\u2019s how you prevent silent drift. It\u2019s not just about consistency\u2014it\u2019s about auditability, especially in banking DFD examples where every data movement must be traceable.<\/p>\n<h2>Why Balancing Matters in Banking Systems<\/h2>\n<p>Financial data flow modeling isn\u2019t about aesthetics. It\u2019s about compliance, risk control, and system integrity.<\/p>\n<p>Consider GDPR or SOX. Auditors don\u2019t just look for processes\u2014they look for traceability. If a transaction\u2019s data flow isn\u2019t consistent across levels, the model fails.<\/p>\n<p>And here\u2019s a truth I\u2019ve learned: <strong>the most complex systems aren\u2019t hard to model\u2014they\u2019re hard to validate.<\/strong> Balancing is the discipline that keeps the model honest.<\/p>\n<p>Use your DFD as a live document. Update it when requirements change. But always re-validate with the balance checklist. This isn\u2019t overhead\u2014it\u2019s insurance.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What is the primary goal of DFD balancing in a banking system?<\/h3>\n<p>To ensure every data flow in a high-level diagram is accounted for in its lower-level decomposition, preserving data integrity and supporting audit compliance.<\/p>\n<h3>Can a data store appear at Level 2 without being in Level 1?<\/h3>\n<p>No. Any data store must originate from a data flow present in the parent level. Introducing new data stores without traceable inputs violates DFD consistency.<\/p>\n<h3>How do I handle a process that has more outputs than inputs?<\/h3>\n<p>That\u2019s a red flag. Re-examine the process. It may be creating data from nothing\u2014a violation of data conservation. Every output must stem from an input or a valid data source, such as a data store.<\/p>\n<h3>Is DFD balancing necessary in agile environments?<\/h3>\n<p>Yes. Even in agile, DFDs help clarify data dependencies before development. Balancing ensures that user stories involving data transfers are modeled accurately and consistently.<\/p>\n<h3>How do I check DFD balance using Visual Paradigm?<\/h3>\n<p>Use the built-in \u201cConsistency Checker.\u201d It flags flows missing in child diagrams, unlinked data stores, and unbalanced inputs\/outputs. Run it after every change.<\/p>\n<h3>What if two processes in Level 2 both reference the same data store?<\/h3>\n<p>That\u2019s acceptable if the data store is already defined in Level 1. But verify that the access is legitimate and that the data isn\u2019t being manipulated outside its defined boundary. This is common in financial data flow modeling.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The single biggest source of wasted effort in DFD modeling? Blindly decomposing processes without validating data flow consistency across levels. I\u2019ve seen teams spend days on a Level 2 diagram only to realize it contradicts the Level 1 input and output streams. The fix is simple: balance before you decompose. Make every new process respect [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1168,"menu_order":1,"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-1170","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>Banking System DFD: Mastering DFD Balancing<\/title>\n<meta name=\"description\" content=\"Explore a real-world banking DFD example with full multi-level balancing. Learn financial data flow modeling techniques for accurate, consistent system design.\" \/>\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\/advanced-dfd-patterns\/banking-system-dfd-balancing\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Banking System DFD: Mastering DFD Balancing\" \/>\n<meta property=\"og:description\" content=\"Explore a real-world banking DFD example with full multi-level balancing. Learn financial data flow modeling techniques for accurate, consistent system design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/\" \/>\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=\"6\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\/advanced-dfd-patterns\/banking-system-dfd-balancing\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/\",\"name\":\"Banking System DFD: Mastering DFD Balancing\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:36:56+00:00\",\"description\":\"Explore a real-world banking DFD example with full multi-level balancing. Learn financial data flow modeling techniques for accurate, consistent system design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/#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\":\"Advanced Insights and Case Studies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Case Study: DFD Balancing in a Banking System\"}]},{\"@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":"Banking System DFD: Mastering DFD Balancing","description":"Explore a real-world banking DFD example with full multi-level balancing. Learn financial data flow modeling techniques for accurate, consistent system design.","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\/advanced-dfd-patterns\/banking-system-dfd-balancing\/","og_locale":"de_DE","og_type":"article","og_title":"Banking System DFD: Mastering DFD Balancing","og_description":"Explore a real-world banking DFD example with full multi-level balancing. Learn financial data flow modeling techniques for accurate, consistent system design.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/","name":"Banking System DFD: Mastering DFD Balancing","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:36:56+00:00","description":"Explore a real-world banking DFD example with full multi-level balancing. Learn financial data flow modeling techniques for accurate, consistent system design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/banking-system-dfd-balancing\/#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":"Advanced Insights and Case Studies","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/advanced-dfd-patterns\/"},{"@type":"ListItem","position":4,"name":"Case Study: DFD Balancing in a Banking System"}]},{"@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\/1170","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\/1170\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1168"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1170"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1170"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}