{"id":624,"date":"2026-02-25T10:21:30","date_gmt":"2026-02-25T10:21:30","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/"},"modified":"2026-02-25T10:21:30","modified_gmt":"2026-02-25T10:21:30","slug":"logical-vs-physical-dfd","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/","title":{"rendered":"Modeling Physical Architecture Instead of Logical Data Flow"},"content":{"rendered":"<p>One of the most frequent missteps I\u2019ve seen in data flow modeling isn\u2019t about notation or structure\u2014it\u2019s about perspective.<\/p>\n<p>When a DFD shows microservices, servers, or network hops, it\u2019s no longer a logical model. It\u2019s a physical architecture sketch, masquerading as a data flow diagram.<\/p>\n<p>That distinction isn\u2019t academic. A logical DFD captures the <strong>what happens to the data<\/strong>, not where it runs. A physical DFD, by contrast, defines <strong>where<\/strong> the logic lives\u2014something that belongs in a different kind of diagram.<\/p>\n<p>My experience has taught me that teams who conflate the two end up with models that confuse stakeholders and mislead developers. The data flow becomes entangled with deployment decisions, making it hard to reason about transformations and risks.<\/p>\n<p>This chapter shows you how to untangle logic from infrastructure. You\u2019ll learn when to use each view, how to keep them separate, and why mixing them destroys clarity. I\u2019ll also share how Visual Paradigm supports both views without blurring the lines.<\/p>\n<h2>Understanding the Core Difference<\/h2>\n<h3>What Is a Logical DFD?<\/h3>\n<p>A logical DFD focuses on business processes, their inputs, outputs, and transformations\u2014without regard to technical implementation.<\/p>\n<p>It answers: <em>What\u2019s being done to the data?<\/em><\/p>\n<p>Examples: \u201cVerify customer identity,\u201d \u201cCalculate tax,\u201d \u201cGenerate invoice.\u201d<\/p>\n<p>These are abstract actions that could be performed in any system, regardless of technology.<\/p>\n<h3>What Is a Physical DFD?<\/h3>\n<p>A physical DFD maps processes to real-world components: servers, databases, queues, or services.<\/p>\n<p>It answers: <em>Where is this logic actually running?<\/em><\/p>\n<p>Examples: \u201cCustomer service microservice,\u201d \u201cAWS Lambda function,\u201d \u201cSQL Server database.\u201d<\/p>\n<p>This is architecture-level detail\u2014crucial for deployment, monitoring, or performance tuning.<\/p>\n<h3>Why Mixing Them Is a Critical Error<\/h3>\n<p>When you draw a server in your logical DFD, you\u2019re forcing the model to carry technical baggage. The process \u201cGenerate Invoice\u201d now becomes \u201cInvoice Generator Service (Node.js, hosted on AWS),\u201d which distracts from the core transformation.<\/p>\n<p>Business stakeholders can\u2019t engage with this. Developers get trapped in implementation details too early.<\/p>\n<p>Worse, these diagrams become fragile. A change in deployment architecture\u2014like moving from a monolith to a microservices setup\u2014breaks the model, even if the logic hasn\u2019t changed.<\/p>\n<h2>When to Use Each View<\/h2>\n<h3>Use Logical DFDs When:<\/h3>\n<ul>\n<li>Building a requirements model with business analysts<\/li>\n<li>Designing workflows independent of technology<\/li>\n<li>Onboarding stakeholders unfamiliar with infrastructure<\/li>\n<li>Documenting high-level business processes<\/li>\n<\/ul>\n<h3>Use Physical DFDs When:<\/h3>\n<ul>\n<li>Planning deployment architecture<\/li>\n<li>Designing system integration or API boundaries<\/li>\n<li>Validating performance, scalability, or security constraints<\/li>\n<li>Preparing technical documentation for DevOps or SRE teams<\/li>\n<\/ul>\n<p>They serve different purposes. One is for logic. The other is for infrastructure.<\/p>\n<h2>How to Keep Them Separate<\/h2>\n<h3>Step 1: Start with the Logical View<\/h3>\n<p>Begin every DFD project with a purely logical model. Focus on:<\/p>\n<ul>\n<li>Business processes (verb + object, e.g., \u201cProcess Order\u201d)<\/li>\n<li>Data flows that reflect business events (e.g., \u201cOrder Details\u201d)<\/li>\n<li>Data stores that represent business records (e.g., \u201cCustomer Database\u201d)<\/li>\n<li>External entities as real-world roles (e.g., \u201cCustomer,\u201d \u201cPayment Gateway\u201d)<\/li>\n<\/ul>\n<p>Do not name processes \u201cService A\u201d or \u201cMicroservice B.\u201d<\/p>\n<h3>Step 2: Add Physical Implementation Later<\/h3>\n<p>Once the logical flow is validated, you can create a physical DFD from the same model.<\/p>\n<p>Each logical process becomes a physical component:<\/p>\n<ul>\n<li>\u201cGenerate Invoice\u201d \u2192 \u201cInvoice Service (Node.js, Docker)\u201d<\/li>\n<li>\u201cVerify Payment\u201d \u2192 \u201cPayment Validator (Python, AWS Lambda)\u201d<\/li>\n<\/ul>\n<p>This way, you preserve the original intent while adding deployment context.<\/p>\n<h3>Step 3: Use Visual Paradigm to Maintain Both Views<\/h3>\n<p>Visual Paradigm lets you model both views in the same project without mixing them.<\/p>\n<p>Here\u2019s how:<\/p>\n<ul>\n<li>Create a <strong>Logical DFD<\/strong> in a dedicated workspace.<\/li>\n<li>Create a <strong>Physical DFD<\/strong> in a separate view.<\/li>\n<li>Use <strong>model links<\/strong> to connect logical processes to physical components.<\/li>\n<li>Apply <strong>view filters<\/strong> to show only logical or physical elements.<\/li>\n<li>Use <strong>diagram templates<\/strong> to standardize symbol sets and labeling.<\/li>\n<\/ul>\n<p>This keeps your models clean, traceable, and reusable.<\/p>\n<h2>Common Mistakes to Avoid<\/h2>\n<h3>Mistake 1: Calling a Physical Diagram a \u201cProcess\u201d<\/h3>\n<p>\u201cCustomer Service Queue\u201d is a physical structure. In a logical DFD, it should be \u201cProcess Customer Requests.\u201d<\/p>\n<p>Change the label. Strip out infrastructure.<\/p>\n<h3>Mistake 2: Drawing Network Paths in the DFD<\/h3>\n<p>Lines should represent data movement, not network hops.<\/p>\n<p>If a line crosses a firewall or traverses a cluster, that\u2019s a deployment diagram issue\u2014*not* a flow diagram one.<\/p>\n<h3>Mistake 3: Using Microservice Names as Process Names<\/h3>\n<p>\u201cOrderService v2.1\u201d is not a process. \u201cProcess Order\u201d is.<\/p>\n<p>Keep the name business-meaningful, even if the implementation changes.<\/p>\n<h2>Practical Guidelines<\/h2>\n<p>Use this checklist when reviewing a DFD:<\/p>\n<ul>\n<li>Are all process names verbs that reflect business actions?<\/li>\n<li>Do any process names include server names, frameworks, or deployment platforms?<\/li>\n<li>Are data stores named after databases or services?<\/li>\n<li>Do any data flows include technical terms like \u201cAPI,\u201d \u201cREST,\u201d or \u201cKafka\u201d?<\/li>\n<li>Could a non-technical stakeholder understand this model?<\/li>\n<\/ul>\n<p>If more than one answer is \u201cyes,\u201d you\u2019re likely modeling physically instead of logically.<\/p>\n<h2>Comparison: Logical vs Physical DFD<\/h2>\n<table>\n<tbody>\n<tr>\n<th>Aspect<\/th>\n<th>Logical DFD<\/th>\n<th>Physical DFD<\/th>\n<\/tr>\n<tr>\n<td>Focus<\/td>\n<td>Business processes &amp; data transformations<\/td>\n<td>Technical implementation &amp; deployment<\/td>\n<\/tr>\n<tr>\n<td>Process Examples<\/td>\n<td>Verify Identity, Calculate Tax<\/td>\n<td>Auth Service (Java, Tomcat)<\/td>\n<\/tr>\n<tr>\n<td>Data Flow Names<\/td>\n<td>Customer Data, Order Summary<\/td>\n<td>Order JSON (via REST API)<\/td>\n<\/tr>\n<tr>\n<td>Use Case<\/td>\n<td>Requirements analysis, stakeholder alignment<\/td>\n<td>Deployment planning, system integration<\/td>\n<\/tr>\n<tr>\n<td>Change Resistance<\/td>\n<td>High \u2013 logic remains stable<\/td>\n<td>Low \u2013 infrastructure changes often<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Final Advice: Let the Model Reflect the Purpose<\/h2>\n<p>I\u2019ve seen teams spend hours refining a DFD that shows Kubernetes pods, only to realize it was supposed to capture business logic. The time lost is not just in rework\u2014it\u2019s in miscommunication.<\/p>\n<p>Always ask: <em>Who is this diagram for?<\/em><\/p>\n<p>If it&#8217;s for business decision-makers, keep it logical. If it&#8217;s for engineers, you can build a physical counterpart.<\/p>\n<p>Never assume that a DFD must include infrastructure. <strong>Separate the what from the where.<\/strong><\/p>\n<p>When you do, your data flow becomes a true reflection of logic\u2014not a shadow of deployment.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the main difference between logical and physical DFD?<\/h3>\n<p>Logical DFDs focus on what happens to data\u2014abstract business processes and transformations. Physical DFDs show where those processes run, including infrastructure components like servers, services, and databases.<\/p>\n<h3>Can I use the same DFD for both business and technical teams?<\/h3>\n<p>No. A single DFD cannot serve both audiences well. Use a logical DFD for business stakeholders and a separate physical DFD for technical teams. Keep them aligned but distinct.<\/p>\n<h3>Should I draw microservices in my logical DFD?<\/h3>\n<p>No. Microservices are deployment artifacts. In a logical DFD, they should be represented as abstract processes like \u201cProcess Payment\u201d or \u201cValidate User.\u201d<\/p>\n<h3>How do I convert a logical DFD to a physical one?<\/h3>\n<p>Map each logical process to one or more physical components. Use model links in tools like Visual Paradigm to associate them. Update process names to include technical details, and replace abstract data stores with real databases or queues.<\/p>\n<h3>Why not just model everything in one diagram for complete traceability?<\/h3>\n<p>Because it sacrifices clarity. Mixing logic and implementation creates confusion, especially during changes. Keep views separate\u2014traceability can be handled via model links, not by merging views.<\/p>\n<h3>When should I use a physical DFD instead of a logical one?<\/h3>\n<p>Use a physical DFD when designing system deployment, defining API boundaries, or explaining integration points. Use logical DFDs during requirements gathering, process modeling, or system design discussions.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the most frequent missteps I\u2019ve seen in data flow modeling isn\u2019t about notation or structure\u2014it\u2019s about perspective. When a DFD shows microservices, servers, or network hops, it\u2019s no longer a logical model. It\u2019s a physical architecture sketch, masquerading as a data flow diagram. That distinction isn\u2019t academic. A logical DFD captures the what [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":621,"menu_order":2,"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-624","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>Logical vs Physical DFD: Avoid Architecture Confusion<\/title>\n<meta name=\"description\" content=\"Learn how to separate logical data flow from physical architecture in DFDs. Master the distinction between what happens to data and where it runs to avoid common modeling errors.\" \/>\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\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Logical vs Physical DFD: Avoid Architecture Confusion\" \/>\n<meta property=\"og:description\" content=\"Learn how to separate logical data flow from physical architecture in DFDs. Master the distinction between what happens to data and where it runs to avoid common modeling errors.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/\",\"name\":\"Logical vs Physical DFD: Avoid Architecture Confusion\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:21:30+00:00\",\"description\":\"Learn how to separate logical data flow from physical architecture in DFDs. Master the distinction between what happens to data and where it runs to avoid common modeling errors.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common DFD Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Scope and Boundary Mistakes\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Modeling Physical Architecture Instead of Logical Data Flow\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Logical vs Physical DFD: Avoid Architecture Confusion","description":"Learn how to separate logical data flow from physical architecture in DFDs. Master the distinction between what happens to data and where it runs to avoid common modeling errors.","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\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/","og_locale":"id_ID","og_type":"article","og_title":"Logical vs Physical DFD: Avoid Architecture Confusion","og_description":"Learn how to separate logical data flow from physical architecture in DFDs. Master the distinction between what happens to data and where it runs to avoid common modeling errors.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"6 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/","name":"Logical vs Physical DFD: Avoid Architecture Confusion","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:21:30+00:00","description":"Learn how to separate logical data flow from physical architecture in DFDs. Master the distinction between what happens to data and where it runs to avoid common modeling errors.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/logical-vs-physical-dfd\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"Common DFD Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Scope and Boundary Mistakes","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-scope-mistakes\/"},{"@type":"ListItem","position":4,"name":"Modeling Physical Architecture Instead of Logical Data Flow"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/624","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/624\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/621"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=624"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=624"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}