{"id":793,"date":"2026-02-25T10:24:57","date_gmt":"2026-02-25T10:24:57","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/"},"modified":"2026-02-25T10:24:57","modified_gmt":"2026-02-25T10:24:57","slug":"context-vs-use-case-diagram-boundary-definition","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/","title":{"rendered":"Context Diagrams vs. Use Case Diagrams: Boundary Definition"},"content":{"rendered":"<p>Getting the system boundary right early isn\u2019t just about drawing a box\u2014it\u2019s about setting the stage for every decision that follows. A misaligned boundary leads to scope creep, misaligned expectations, and integration failures. When I\u2019ve seen projects derailed by boundary confusion, it wasn\u2019t due to poor tools, but because the wrong lens was used to define what belongs inside the system.<\/p>\n<p>The most overlooked advantage of choosing the right boundary model is clarity in stakeholder communication. A DFD context diagram focuses on *data exchange*. It shows who sends and receives data, and what flows between systems. This is invaluable when the core challenge is auditing data lineage or ensuring compliance.<\/p>\n<p>Conversely, a UML use case diagram captures *functional goals* tied to actor roles. It answers: \u201cWhat can this user do?\u201d\u2014not \u201cWhat data do they receive?\u201d This works best when the system\u2019s purpose is defined by user-driven actions, especially in interactive or service-oriented environments.<\/p>\n<p>My experience has taught me that the real power lies not in picking one over the other, but in knowing *when* each excels. This chapter helps you see both models side by side\u2014same system, different perspectives\u2014and equips you with a practical framework to decide which boundary model wins for your use case.<\/p>\n<h2>DFD Context Diagram: Data-Centric Boundary Definition<\/h2>\n<p>DFD context diagrams answer: <strong>What data moves across the system boundary?<\/strong><\/p>\n<p>They focus on data flows, not processes or behaviors. The central element is a single process (the system), and external entities represent sources or sinks of data.<\/p>\n<p>For example, in a payment processing system, the context diagram shows that a bank sends transaction data, and a merchant receives confirmation data. The boundary is defined by what data is exchanged\u2014not by what the system does.<\/p>\n<p>This model excels in environments where data security, compliance, and lineage matter\u2014like finance, healthcare, or regulated industries.<\/p>\n<h3>When DFD Context Diagrams Excel<\/h3>\n<ul>\n<li>When the primary concern is <strong>data integrity<\/strong> and audit trails (e.g., SOX, HIPAA).<\/li>\n<li>When external systems are defined by <strong>data formats<\/strong> (e.g., EDI, XML, JSON).<\/li>\n<li>When stakeholders need to understand <strong>who sends what to whom<\/strong> without diving into business logic.<\/li>\n<li>During <strong>integration analysis<\/strong>\u2014where data flow between systems is the key challenge.<\/li>\n<\/ul>\n<h3>Limitations of DFD Context Diagrams<\/h3>\n<ul>\n<li>Does not capture <strong>user goals<\/strong> or system behaviors.<\/li>\n<li>Cannot show conditional logic or state changes.<\/li>\n<li>May obscure functional scope if stakeholders focus only on data, missing underlying intent.<\/li>\n<\/ul>\n<h2>UML Use Case Diagram: Function-Centric Boundary Definition<\/h2>\n<p>UML use case diagrams answer: <strong>What can the system do for whom?<\/strong><\/p>\n<p>They define the system boundary around <strong>functional capabilities<\/strong> tied to actor roles. Actors represent roles (e.g., Customer, Admin), not individuals. Use cases represent discrete functions (e.g., \u201cPlace Order\u201d, \u201cApprove Withdrawal\u201d).<\/p>\n<p>For example, in the same payment system, a customer can \u201cSubmit Payment\u201d, and an admin can \u201cReview Transaction\u201d. The boundary is defined by what users can do\u2014functional scope, not data flow.<\/p>\n<p>This model is ideal when the system\u2019s value is determined by user interaction, workflow automation, or service orchestration.<\/p>\n<h3>When Use Case Diagrams Excel<\/h3>\n<ul>\n<li>When the system is <strong>user-driven<\/strong> (e.g., web apps, mobile apps).<\/li>\n<li>When the goal is to define <strong>functional scope<\/strong> during requirements gathering.<\/li>\n<li>When teams use <strong>agile or user story-driven<\/strong> planning.<\/li>\n<li>When you need to model <strong>conditional behavior<\/strong> (extensions, alternatives) via use case dependencies.<\/li>\n<\/ul>\n<h3>Limitations of Use Case Diagrams<\/h3>\n<ul>\n<li>Does not clarify <strong>how data moves<\/strong>\u2014can lead to ambiguity in integration.<\/li>\n<li>Can become cluttered in complex systems with many actors and overlapping cases.<\/li>\n<li>May miss <strong>data-centric constraints<\/strong> like data volume, format, or lifecycle.<\/li>\n<\/ul>\n<h2>System Boundary Modeling Comparison: DFD vs UML<\/h2>\n<p>To help you choose, here\u2019s a direct comparison of how DFD and UML define the system boundary in practice.<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Aspect<\/th>\n<th>DFD Context Diagram<\/th>\n<th>UML Use Case Diagram<\/th>\n<\/tr>\n<tr>\n<td><strong>Primary Focus<\/strong><\/td>\n<td>Data exchange<\/td>\n<td>Functional goal<\/td>\n<\/tr>\n<tr>\n<td><strong>Boundary Definition<\/strong><\/td>\n<td>Where data enters\/exits the system<\/td>\n<td>What functional capabilities are internal<\/td>\n<\/tr>\n<tr>\n<td><strong>Stakeholder Clarity<\/strong><\/td>\n<td>Best for IT, compliance, integration teams<\/td>\n<td>Best for business analysts, product owners, developers<\/td>\n<\/tr>\n<tr>\n<td><strong>Strengths<\/strong><\/td>\n<td>End-to-end data lineage, auditability<\/td>\n<td>User-centered scope, goal-driven planning<\/td>\n<\/tr>\n<tr>\n<td><strong>Weaknesses<\/strong><\/td>\n<td>Misses user intent, poor for behavior modeling<\/td>\n<td>Doesn\u2019t show data flow, ambiguous in complex integrations<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Real-World Example: Patient Registration System<\/h3>\n<p><strong>DFD Context View:<\/strong> A hospital system receives patient data from a clinic, and sends discharge summaries to a referral service. The boundary is defined by data flows: &#8222;Patient Record&#8221;, &#8222;Discharge Summary&#8221;.<\/p>\n<p><strong>UML Use Case View:<\/strong> The system supports roles: &#8222;Receptionist&#8221;, &#8222;Doctor&#8221;, &#8222;Nurse&#8221;. Use cases include: &#8222;Register Patient&#8221;, &#8222;Assign Bed&#8221;, &#8222;Update Medical Notes&#8221;. The boundary is defined by actions, not data.<\/p>\n<p>Which is better? It depends on your goal. If you\u2019re auditing data sharing under HIPAA, the DFD view is more useful. If you\u2019re defining sprint goals and user stories, the use case diagram wins.<\/p>\n<h2>When Data Exchange vs Functional Boundary Matters<\/h2>\n<p>Here\u2019s a simple decision rule: <strong>If integration is the main concern, use DFD context.<\/strong><\/p>\n<p>The data exchange vs functional boundary distinction is critical in cross-system scenarios. For example, in a supply chain platform, multiple vendors send inventory data. The system&#8217;s boundary must reflect how data is received and processed\u2014not whether a warehouse manager &#8222;updates stock&#8221;.<\/p>\n<p>In one project, a financial services client struggled with compliance because their use case diagrams listed &#8222;Process Transaction&#8221; as a use case. No one knew what data was involved. Switching to a DFD context diagram clarified that the system received ISO 20022 XML messages from banks\u2014immediately triggering audit readiness.<\/p>\n<h3>Key Insight<\/h3>\n<p>Functional boundaries define *what the system does*. Data exchange boundaries define *what it touches*. In complex systems, you often need both\u2014but the <strong>first model you create should match your primary stakeholder<\/strong>.<\/p>\n<h2>Stakeholder Communication Implications<\/h2>\n<p>Use case diagrams are ideal for business stakeholders who think in terms of tasks and goals. They resonate because they mirror how product owners write user stories: \u201cAs a [role], I want to [action] so that [goal].\u201d<\/p>\n<p>DFD context diagrams are more effective for IT, compliance, and integration teams. They speak the language of data flow, not interaction. Saying \u201cThe system receives credit card data from the gateway\u201d is clearer than \u201cThe system performs payment processing.\u201d<\/p>\n<p>When the stakeholder group is mixed, I recommend showing both models early. Use the DFD for integration planning, and the use case for feature breakdown. They\u2019re not competitors\u2014they\u2019re complementary lenses.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>When should I use a DFD context diagram instead of a UML use case diagram?<\/h3>\n<p>Use a DFD context diagram when your primary goal is to define system boundaries based on data exchange\u2014especially in regulated industries, integration projects, or when auditing data lineage. Use a UML use case diagram when the system\u2019s value is defined by user-driven actions, especially in agile environments.<\/p>\n<h3>Can I use both DFD and UML diagrams together for the same system?<\/h3>\n<p>Absolutely. Many successful projects use both: DFD context diagrams for integration and compliance, and UML use case diagrams for feature definition. They serve different purposes and can be linked via cross-referencing or traceability.<\/p>\n<h3>Is a DFD context diagram less detailed than a UML use case diagram?<\/h3>\n<p>No\u2014different. The DFD context diagram is not less detailed; it\u2019s focused on a different dimension. It doesn\u2019t show behavior or user goals, but it excels at showing what data comes from where, which is often more critical in system integration.<\/p>\n<h3>Why do some teams prefer DFD despite its perceived simplicity?<\/h3>\n<p>Because simplicity is not a flaw\u2014it\u2019s a strength. DFDs force clarity on data movement, which is often the root of integration failures. Simplicity helps analysts avoid over-engineering and stay focused on the core data challenges.<\/p>\n<h3>Can a UML use case diagram replace a DFD context diagram?<\/h3>\n<p>Not reliably. While a use case can imply data interaction, it doesn\u2019t model the data flow explicitly. In high-accuracy environments (e.g., banking, healthcare), assuming data flow from a use case can lead to compliance gaps.<\/p>\n<h3>Which is better for legacy system modernization: DFD or UML?<\/h3>\n<p>Start with DFD context diagrams. They reveal the actual data flows in legacy systems, which is critical for migration. Once you understand the data, map it to UML use cases for modernization planning. This two-step approach ensures nothing is missed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Getting the system boundary right early isn\u2019t just about drawing a box\u2014it\u2019s about setting the stage for every decision that follows. A misaligned boundary leads to scope creep, misaligned expectations, and integration failures. When I\u2019ve seen projects derailed by boundary confusion, it wasn\u2019t due to poor tools, but because the wrong lens was used to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":792,"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-793","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>Context vs Use Case Diagram: Boundary Definition<\/title>\n<meta name=\"description\" content=\"Compare DFD context diagrams vs UML use case diagrams for system boundary modeling. Learn when data exchange boundaries beat functional goal boundaries for integration and stakeholder clarity.\" \/>\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\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Context vs Use Case Diagram: Boundary Definition\" \/>\n<meta property=\"og:description\" content=\"Compare DFD context diagrams vs UML use case diagrams for system boundary modeling. Learn when data exchange boundaries beat functional goal boundaries for integration and stakeholder clarity.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/\" \/>\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=\"7 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\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/\",\"name\":\"Context vs Use Case Diagram: Boundary Definition\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:24:57+00:00\",\"description\":\"Compare DFD context diagrams vs UML use case diagrams for system boundary modeling. Learn when data exchange boundaries beat functional goal boundaries for integration and stakeholder clarity.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data Flow Diagrams vs. UML: When to Use Each\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Detailed Diagram Type Comparisons\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Context Diagrams vs. Use Case Diagrams: Boundary Definition\"}]},{\"@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":"Context vs Use Case Diagram: Boundary Definition","description":"Compare DFD context diagrams vs UML use case diagrams for system boundary modeling. Learn when data exchange boundaries beat functional goal boundaries for integration and stakeholder clarity.","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\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/","og_locale":"pl_PL","og_type":"article","og_title":"Context vs Use Case Diagram: Boundary Definition","og_description":"Compare DFD context diagrams vs UML use case diagrams for system boundary modeling. Learn when data exchange boundaries beat functional goal boundaries for integration and stakeholder clarity.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"7 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/","name":"Context vs Use Case Diagram: Boundary Definition","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:24:57+00:00","description":"Compare DFD context diagrams vs UML use case diagrams for system boundary modeling. Learn when data exchange boundaries beat functional goal boundaries for integration and stakeholder clarity.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/context-vs-use-case-diagram-boundary-definition\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Data Flow Diagrams vs. UML: When to Use Each","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/"},{"@type":"ListItem","position":3,"name":"Detailed Diagram Type Comparisons","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-diagram-comparison\/"},{"@type":"ListItem","position":4,"name":"Context Diagrams vs. Use Case Diagrams: Boundary Definition"}]},{"@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\/793","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\/793\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/792"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=793"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=793"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}