{"id":818,"date":"2026-02-25T10:25:08","date_gmt":"2026-02-25T10:25:08","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/"},"modified":"2026-02-25T10:25:08","modified_gmt":"2026-02-25T10:25:08","slug":"architecture-dfd-uml-hybrid","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/","title":{"rendered":"Architecture Definition: UML Package + DFD Overlay"},"content":{"rendered":"<p>Never assume that a single diagram type can capture both the structure and flow of a system. The most common mistake in architecture definition is treating structure and data movement as separate concerns, leading to misaligned teams, incomplete requirements, and expensive rework.<\/p>\n<p>This is why the UML package with data flow overlay pattern exists\u2014not as a compromise, but as a deliberate, high-leverage strategy to unify two essential perspectives.<\/p>\n<p>Over 20 years of modeling experience have taught me: system architecture fails not because of poor tools, but when stakeholders speak in different languages. The UML package provides the structural vocabulary; the DFD overlay supplies the behavioral transparency. Together, they form a single, coherent picture that even business analysts and compliance officers can understand.<\/p>\n<p>In this chapter, you\u2019ll learn how to build this dual-layer view using Visual Paradigm layout strategies, how to align the two notations without creating redundancy, and why this approach is ideal for architecture reviews and stakeholder communication.<\/p>\n<h2>Why Combine UML Packages with DFD Overlays?<\/h2>\n<p>UML packages organize system components by responsibility, domain, or technical layer. They define *what* exists and *how* it\u2019s grouped.<\/p>\n<p>But architecture isn\u2019t just about containers\u2014it\u2019s about movement. Data flows through those packages. Without visibility into how data moves across boundaries, you risk designing isolated components that can\u2019t coordinate.<\/p>\n<p>This is where the DFD overlay shines. It inserts data flow transparency directly onto the UML package diagram, showing incoming and outgoing data, transformation points, and data stores.<\/p>\n<p>Think of it like a city map: UML packages are the neighborhoods, while the DFD overlay shows the traffic patterns, road closures, and delivery routes.<\/p>\n<p>For any system where data integrity and flow are critical\u2014banking, healthcare, logistics\u2014the hybrid view is not optional. It\u2019s the only way to ensure both technical and business stakeholders see the same system.<\/p>\n<h3>When to Use This Hybrid Approach<\/h3>\n<ul>\n<li><strong>Architecture review meetings<\/strong>: Present a single diagram that shows structure and flow simultaneously.<\/li>\n<li><strong>Stakeholder onboarding<\/strong>: Business leads understand the \u201cwhy\u201d of data movement without diving into class methods.<\/li>\n<li><strong>Regulatory or compliance documentation<\/strong>: Auditors need to trace data lineage\u2014this pattern makes it visible.<\/li>\n<li><strong>System modernization<\/strong>: Map existing DFDs onto new UML packages to align legacy and modern architecture.<\/li>\n<\/ul>\n<p>This pattern is not about duplication. It\u2019s about integration.<\/p>\n<h2>Step-by-Step: Building the UML Package + DFD Overlay<\/h2>\n<p>Here\u2019s how to structure the hybrid diagram in practice\u2014specifically in Visual Paradigm.<\/p>\n<h3>Step 1: Define UML Packages by Domain or Layer<\/h3>\n<p>Start with a standard UML package diagram. Group components by business domain (e.g., Order Management, Payment Processing) or technical layer (e.g., Presentation, Business Logic, Data Access).<\/p>\n<p>Use clear, concise package names. Avoid \u201cModule 1\u201d or \u201cComponent A.\u201d Each package should represent a cohesive responsibility.<\/p>\n<h3>Step 2: Add DFD Elements as Overlay Annotations<\/h3>\n<p>Do not replace the UML elements. Instead, overlay the DFD flow using annotations:<\/p>\n<ul>\n<li>Draw <strong>data flows<\/strong> from external entities into package boundaries. Label them with the data type (e.g., \u201cOrder Request\u201d)<\/li>\n<li>Use a <strong>dashed arrow<\/strong> to represent data movement across packages<\/li>\n<li>Add a <strong>data store icon<\/strong> inside a package if it contains persistent data (e.g., \u201cOrder History DB\u201d)<\/li>\n<li>Label <strong>processes<\/strong> with a small circle or rectangle in the middle of the package, annotated with the function (e.g., \u201cValidate Order\u201d)<\/li>\n<\/ul>\n<p>Use a different color (e.g., blue) for DFD elements to distinguish them from UML structure.<\/p>\n<h3>Step 3: Align Data Flow with Package Boundaries<\/h3>\n<p>Ensure that all data flows enter or exit through the package boundary. If a data flow appears to pass through a package without interacting with its internal elements, reevaluate the structure.<\/p>\n<p>For example: if a \u201cCustomer Data\u201d flow enters the \u201cBilling\u201d package but no class handles it, the package design is incomplete.<\/p>\n<p>Use this to reveal missing components, redundant flows, or unhandled data paths.<\/p>\n<h3>Step 4: Use Visual Paradigm Layout Strategies<\/h3>\n<p>Visual Paradigm supports dual-view layouts for this exact purpose. Use the following settings:<\/p>\n<ul>\n<li><strong>Diagram Layout<\/strong>: Use \u201cTree Layout\u201d or \u201cLayered Layout\u201d to keep packages visually aligned<\/li>\n<li><strong>Grouping<\/strong>: Use \u201cPackage Grouping\u201d to cluster related domains (e.g., all payment-related packages)<\/li>\n<li><strong>Overlay Layer<\/strong>: Use \u201cAnnotation Layer\u201d to draw DFD elements without interfering with UML structure<\/li>\n<li><strong>Color Coding<\/strong>: Use blue for data flows, red for external entities, green for data stores<\/li>\n<\/ul>\n<p>Enable \u201cAuto-Layout\u201d for clean presentation. Then export as high-resolution image or PDF for reports and presentations.<\/p>\n<h2>Real-World Example: E-Commerce Checkout Flow<\/h2>\n<p>Consider a checkout process with three key UML packages: <em>Order Validation<\/em>, <em>Payment Processing<\/em>, and <em>Inventory Management<\/em>.<\/p>\n<p>Now overlay the DFD:<\/p>\n<ul>\n<li><strong>External Entity<\/strong>: \u201cCustomer\u201d sends \u201cCheckout Request\u201d to <em>Order Validation<\/em><\/li>\n<li><strong>Data Flow<\/strong>: \u201cOrder Data\u201d moves from <em>Order Validation<\/em> to <em>Payment Processing<\/em><\/li>\n<li><strong>Data Store<\/strong>: \u201cPayment Confirmation\u201d is stored in <em>Payment Processing<\/em><\/li>\n<li><strong>Data Flow<\/strong>: \u201cPayment Approved\u201d triggers <em>Inventory Management<\/em> to reserve stock<\/li>\n<li><strong>External Entity<\/strong>: \u201cLogistics System\u201d receives \u201cShipment Ready\u201d data<\/li>\n<\/ul>\n<p>Now you have a single diagram that shows:<\/p>\n<ul>\n<li>Which component owns which data<\/li>\n<li>Where data is stored<\/li>\n<li>How data moves across boundaries<\/li>\n<li>Which team is responsible for each flow<\/li>\n<\/ul>\n<p>This is not a \u201cnice-to-have.\u201d This is how you prevent data silos.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with the right pattern, the hybrid view can fail if misapplied.<\/p>\n<h3>Pitfall 1: Overloading the Diagram<\/h3>\n<p>Don\u2019t try to include every single data flow. Focus on critical paths\u2014those that affect business rules, compliance, or performance.<\/p>\n<p>Use the <strong>80\/20 rule<\/strong>: map the 20% of flows that cover 80% of the system\u2019s risk.<\/p>\n<h3>Pitfall 2: Confusing Data Flow with Control Flow<\/h3>\n<p>Don\u2019t use DFD flows to represent service calls or API triggers. DFD only models data. If you\u2019re modeling message sequences, use UML sequence diagrams instead.<\/p>\n<p>Keep the domains separate: data flow is for data, message flow is for behavior.<\/p>\n<h3>Pitfall 3: Misaligned Naming Conventions<\/h3>\n<p>Ensure that data flow names (e.g., \u201cCustomer ID\u201d) match the actual attributes in UML classes.<\/p>\n<p>Use consistent naming: \u201cOrder ID\u201d in DFD should be \u201corderId\u201d in the UML class. Avoid synonyms like \u201cOrder Number\u201d or \u201cID\u201d without mapping.<\/p>\n<h3>Pitfall 4: Ignoring the Review Process<\/h3>\n<p>Never present this diagram in isolation. Pair it with a brief narrative: \u201cThis diagram shows how customer data flows from input to confirmation, with oversight by the Payment Processing team.\u201d<\/p>\n<p>Use it as a discussion trigger, not a standalone artifact.<\/p>\n<h2>When Not to Use This Pattern<\/h2>\n<p>Not every system needs a dual-view. Consider these cases where simpler models suffice:<\/p>\n<ul>\n<li><strong>Small, single-team systems<\/strong>: If no external dependencies or compliance needs, a clean UML package diagram may be enough.<\/li>\n<li><strong>Highly real-time systems<\/strong>: Timing and state transitions are better modeled in UML state machines or sequence diagrams.<\/li>\n<li><strong>Legacy systems with no documentation<\/strong>: Start with DFD-only to reverse engineer, then add UML packages later.<\/li>\n<\/ul>\n<p>Use the hybrid pattern when you need to answer: \u201cWho owns this data? How does it move? Where is it stored?\u201d<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can I use this pattern in Visual Paradigm with other UML diagrams?<\/h3>\n<p>Yes. Use the UML package with data flow overlay as a top-level architecture diagram. Reference it in detailed UML diagrams (e.g., sequence, component) for deeper technical context.<\/p>\n<h3>How do I keep the DFD overlay and UML structure synchronized?<\/h3>\n<p>Use traceability links in Visual Paradigm. Each DFD process should link to the UML class or operation that handles it. Update one, and the other should reflect changes.<\/p>\n<h3>Is this method suitable for agile teams?<\/h3>\n<p>Absolutely. Use it in sprint planning to define data boundaries and flow. Update it incrementally as features evolve. It\u2019s lightweight yet powerful.<\/p>\n<h3>What if stakeholders don\u2019t understand DFD?<\/h3>\n<p>Start with a simplified version: use only data flow lines and labels. Add icons for data stores and external entities. Avoid complex notation\u2014focus on clarity.<\/p>\n<h3>Can I generate code from this hybrid diagram?<\/h3>\n<p>Only the UML components can be used for code generation. The DFD overlay is for documentation and analysis. However, the data flows can inform entity mapping and API contract design.<\/p>\n<p>Use this hybrid approach to bridge the gap between architecture and execution. When you show the system\u2019s structure and data flow in one view, you\u2019re not just modeling\u2014it\u2019s understanding.<\/p>\n<p>The right architecture isn\u2019t about perfection. It\u2019s about clarity. And clarity begins with showing both the what and the how.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Never assume that a single diagram type can capture bot [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":816,"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-818","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>Architecture DFD UML Hybrid: Dual-View System Design<\/title>\n<meta name=\"description\" content=\"Master the UML package with data flow overlay pattern for architecture reviews. Combine system structure and data flow transparency to simplify complex system analysis and improve stakeholder alignment.\" \/>\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\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Architecture DFD UML Hybrid: Dual-View System Design\" \/>\n<meta property=\"og:description\" content=\"Master the UML package with data flow overlay pattern for architecture reviews. Combine system structure and data flow transparency to simplify complex system analysis and improve stakeholder alignment.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/\",\"name\":\"Architecture DFD UML Hybrid: Dual-View System Design\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:25:08+00:00\",\"description\":\"Master the UML package with data flow overlay pattern for architecture reviews. Combine system structure and data flow transparency to simplify complex system analysis and improve stakeholder alignment.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data Flow Diagrams vs. UML: When to Use Each\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Practical Implementation Patterns\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Architecture Definition: UML Package + DFD Overlay\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Architecture DFD UML Hybrid: Dual-View System Design","description":"Master the UML package with data flow overlay pattern for architecture reviews. Combine system structure and data flow transparency to simplify complex system analysis and improve stakeholder alignment.","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\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/","og_locale":"zh_CN","og_type":"article","og_title":"Architecture DFD UML Hybrid: Dual-View System Design","og_description":"Master the UML package with data flow overlay pattern for architecture reviews. Combine system structure and data flow transparency to simplify complex system analysis and improve stakeholder alignment.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"7 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/","name":"Architecture DFD UML Hybrid: Dual-View System Design","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:25:08+00:00","description":"Master the UML package with data flow overlay pattern for architecture reviews. Combine system structure and data flow transparency to simplify complex system analysis and improve stakeholder alignment.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/architecture-dfd-uml-hybrid\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"Data Flow Diagrams vs. UML: When to Use Each","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/"},{"@type":"ListItem","position":3,"name":"Practical Implementation Patterns","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/practical-implementation-patterns\/"},{"@type":"ListItem","position":4,"name":"Architecture Definition: UML Package + DFD Overlay"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/818","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/818\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/816"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=818"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=818"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}