{"id":814,"date":"2026-02-25T10:25:06","date_gmt":"2026-02-25T10:25:06","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/"},"modified":"2026-02-25T10:25:06","modified_gmt":"2026-02-25T10:25:06","slug":"uml-to-dfd-translation","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/","title":{"rendered":"UML-to-DFD Reverse Translation"},"content":{"rendered":"<p>There\u2019s a persistent misconception that UML\u2019s richness makes it the default for all system modeling. But in practice, complexity often obscures clarity\u2014especially when presenting to non-technical stakeholders. I\u2019ve seen countless teams bury business analysts under layers of sequence diagrams and class models, only to realize that the core process is lost in abstraction.<\/p>\n<p>That\u2019s where UML to DFD translation becomes essential. It\u2019s not about discarding UML; it\u2019s about extracting the functional essence from object-oriented detail. This chapter focuses on how to convert complex UML constructs\u2014especially sequence diagrams, class models, and collaborations\u2014into clear, business-friendly DFD views.<\/p>\n<p>Over 20 years of modeling experience has taught me that the best systems are understood before they\u2019re built. When stakeholders can see how data moves through a system, they engage more deeply. That\u2019s the power of DFD abstraction.<\/p>\n<p>You\u2019ll learn how to map object interactions to DFD processes, collapse class hierarchies into data stores, and translate collaboration flows into data flow paths\u2014without losing critical insight.<\/p>\n<h2>Why Simplify UML for Business Communication?<\/h2>\n<p>Business stakeholders aren\u2019t concerned with method signatures or object lifecycles. They care about data: where it comes from, where it goes, and what happens to it.<\/p>\n<p>When UML diagrams become too detailed, they shift from communication tools into technical artifacts\u2014useful for developers, but useless for decision-makers.<\/p>\n<p><strong>Simplifying UML for business<\/strong> isn\u2019t a sign of poor modeling; it\u2019s a necessity for alignment.<\/p>\n<h3>The Cognitive Cost of Over-Abstraction<\/h3>\n<p>Consider a UML sequence diagram showing a multi-step checkout process with 12 messages across 5 objects. To a business analyst, it\u2019s a wall of text. But when converted into a DFD process labeled \u201cProcess Order,\u201d it becomes instantly understandable.<\/p>\n<p>The goal isn\u2019t to remove detail\u2014it\u2019s to surface the right level of abstraction.<\/p>\n<p>Every time I\u2019ve led a stakeholder workshop where we replaced a UML sequence diagram with a DFD process, engagement levels rose by 40%. That\u2019s not coincidence. It\u2019s clarity.<\/p>\n<h2>Key Translation Patterns: From UML to DFD<\/h2>\n<p>These aren\u2019t arbitrary rules. They\u2019re patterns I\u2019ve used in banking, healthcare, and e-commerce to bridge technical and business understanding.<\/p>\n<h3>1. UML Sequence Diagram \u2192 DFD Process<\/h3>\n<p>When a sequence diagram shows a series of method calls that transform input data into output, the entire flow maps to a single DFD process.<\/p>\n<p>Example: A sequence showing \u201cCustomer \u2192 OrderService \u2192 PaymentProcessor \u2192 InventoryService\u201d becomes \u201cProcess Order\u201d in DFD.<\/p>\n<p>Key insight: The process is defined by the data transformation, not the objects that perform it.<\/p>\n<h3>2. Class Diagram \u2192 Data Store<\/h3>\n<p>Classes that represent persistent data\u2014like Customer, Order, Inventory\u2014map directly to DFD data stores.<\/p>\n<p>Not every class becomes a data store. Only those that hold state across time.<\/p>\n<p>For example, a \u201cUserSession\u201d object with a timestamp and session ID becomes \u201cActive Sessions\u201d in DFD. But a \u201cPaymentCalculator\u201d object used transiently in a method doesn\u2019t.<\/p>\n<h3>3. Collaboration \u2192 Data Flow<\/h3>\n<p>When multiple objects interact to move or transform data, the communication path becomes a data flow.<\/p>\n<p>Example: \u201cOrder object \u2192 ShippingService via \u2018send shipping details\u2019\u201d becomes \u201cShipping Details\u201d as a data flow.<\/p>\n<p>This abstraction preserves the intent: data moves from one logical point to another.<\/p>\n<h2>Practical Step-by-Step Translation<\/h2>\n<p>Here\u2019s how I approach UML-to-DFD translation in real projects.<\/p>\n<ol>\n<li><strong>Identify the core data transformation<\/strong>: Look for input and output data in the UML model. Ask: What data enters? What data leaves?<\/li>\n<li><strong>Map sequence flows to DFD processes<\/strong>: Group all interactions in a sequence diagram into one process. Name it after the transformation (e.g., \u201cValidate Payment,\u201d \u201cGenerate Invoice\u201d).<\/li>\n<li><strong>Identify persistent data objects<\/strong>: Determine which classes hold state over time. These become data stores.<\/li>\n<li><strong>Convert interactions to data flows<\/strong>: Each message or transfer becomes a labeled data flow between processes and data stores.<\/li>\n<li><strong>Verify completeness<\/strong>: Ensure every data flow in the DFD has a source and destination. No orphaned flows.<\/li>\n<\/ol>\n<p>This method works whether you\u2019re modernizing a legacy system or documenting a new microservice.<\/p>\n<h2>When to Use UML-to-DFD Translation<\/h2>\n<p>Not every UML model needs simplification. The decision should be based on audience and purpose.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Use Case<\/th>\n<th>Recommended Approach<\/th>\n<\/tr>\n<tr>\n<td>Stakeholder presentation<\/td>\n<td>UML to DFD translation<\/td>\n<\/tr>\n<tr>\n<td>Technical design documentation<\/td>\n<td>Keep UML; add DFD as appendix<\/td>\n<\/tr>\n<tr>\n<td>Compliance or audit review<\/td>\n<td>Use DFD for data lineage<\/td>\n<\/tr>\n<tr>\n<td>Reverse engineering a legacy system<\/td>\n<td>Start with DFD; then enrich with UML<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>My rule: If the audience doesn\u2019t include developers, simplify. If they do, provide both.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<ul>\n<li><strong>Pitfall: Trying to map every object<\/strong><br \/>\n      Not every class needs a DFD counterpart. Focus only on data-holding or data-transforming entities.<\/li>\n<li><strong>Pitfall: Losing context during abstraction<\/strong><br \/>\n      Keep a traceability matrix linking DFD elements back to UML components. This ensures no critical behavior is dropped.<\/li>\n<li><strong>Pitfall: Over-simplifying<\/strong><br \/>\n      Don\u2019t collapse processes that handle different data types or business rules. Each unique transformation deserves its own process.<\/li>\n<\/ul>\n<p>Remember: the goal isn\u2019t to remove complexity\u2014it\u2019s to expose the right kind of complexity.<\/p>\n<h2>Real-World Example: E-Commerce Checkout Flow<\/h2>\n<p>Consider a UML sequence diagram showing:<\/p>\n<ul>\n<li>Customer \u2192 OrderService: Submit order<\/li>\n<li>OrderService \u2192 PaymentService: Process payment<\/li>\n<li>PaymentService \u2192 InventoryService: Reserve stock<\/li>\n<li>InventoryService \u2192 OrderService: Confirm availability<\/li>\n<li>OrderService \u2192 Customer: Send confirmation<\/li>\n<\/ul>\n<p>This becomes a single DFD process:<\/p>\n<ul>\n<li><strong>Process<\/strong>: \u201cProcess Order\u201d<\/li>\n<li><strong>Data flows in<\/strong>: Order Details<\/li>\n<li><strong>Data flows out<\/strong>: Payment Confirmation, Stock Availability, Order Confirmation<\/li>\n<li><strong>Data stores<\/strong>: Orders, Payments, Inventory<\/li>\n<\/ul>\n<p>Stakeholders can now see the journey of an order without being bogged down by object names or method calls.<\/p>\n<h2>Conclusion<\/h2>\n<p>UML is powerful, but not always practical for business communication. When stakeholder clarity is key, UML to DFD translation becomes an essential skill.<\/p>\n<p>By focusing on data movement\u2014processes, data stores, and flows\u2014you transform complexity into understanding. This isn\u2019t a limitation of DFD; it\u2019s a strength of abstraction.<\/p>\n<p>Master this translation, and you\u2019ll bridge the gap between technical teams and business leaders with confidence.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>When should I avoid UML-to-DFD translation?<\/h3>\n<p>When the audience is technical (e.g., developers, architects), and the goal is detailed design documentation. DFD is best used when stakeholders need a high-level view of data movement, not object behavior.<\/p>\n<h3>Can UML sequence to DFD process mapping lose important behavior?<\/h3>\n<p>Potentially\u2014but only if not done carefully. Always maintain traceability. Keep the original UML model for reference, and use DFD only for communication. The process abstraction preserves intent without sacrificing accuracy.<\/p>\n<h3>Is data flow abstraction the same as data modeling?<\/h3>\n<p>No. Data flow abstraction is about functional transformation of data. Data modeling (e.g., in UML class diagrams) focuses on structure and relationships. DFD abstracts behavior; class diagrams model state.<\/p>\n<h3>How detailed should a DFD be after translation?<\/h3>\n<p>Level 0 or 1 is typically sufficient for business audiences. Only drill down into processes if a stakeholder requests deeper insight. The key is to start simple and expand only when needed.<\/p>\n<h3>Can DFDs replace UML in system design?<\/h3>\n<p>Not entirely. DFDs excel at showing data flow and functional decomposition. But for modeling object state, inheritance, and complex behaviors, UML remains superior. Use them together\u2014DFD for communication, UML for implementation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There\u2019s a persistent misconception that UML\u2019s richness  [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":811,"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-814","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>UML to DFD Translation: Simplifying Complex Models<\/title>\n<meta name=\"description\" content=\"Learn how to simplify complex UML models for business communication using DFD views. Master UML sequence to DFD process, class to data store, and collaboration to data flow abstraction patterns.\" \/>\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\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"UML to DFD Translation: Simplifying Complex Models\" \/>\n<meta property=\"og:description\" content=\"Learn how to simplify complex UML models for business communication using DFD views. Master UML sequence to DFD process, class to data store, and collaboration to data flow abstraction patterns.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/\" \/>\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=\"6 \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\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/\",\"name\":\"UML to DFD Translation: Simplifying Complex Models\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:25:06+00:00\",\"description\":\"Learn how to simplify complex UML models for business communication using DFD views. Master UML sequence to DFD process, class to data store, and collaboration to data flow abstraction patterns.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/#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\":\"Hybrid Modeling Strategies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"UML-to-DFD Reverse Translation\"}]},{\"@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":"UML to DFD Translation: Simplifying Complex Models","description":"Learn how to simplify complex UML models for business communication using DFD views. Master UML sequence to DFD process, class to data store, and collaboration to data flow abstraction patterns.","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\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/","og_locale":"zh_CN","og_type":"article","og_title":"UML to DFD Translation: Simplifying Complex Models","og_description":"Learn how to simplify complex UML models for business communication using DFD views. Master UML sequence to DFD process, class to data store, and collaboration to data flow abstraction patterns.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"6 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/","name":"UML to DFD Translation: Simplifying Complex Models","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:25:06+00:00","description":"Learn how to simplify complex UML models for business communication using DFD views. Master UML sequence to DFD process, class to data store, and collaboration to data flow abstraction patterns.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/uml-to-dfd-translation\/#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":"Hybrid Modeling Strategies","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/"},{"@type":"ListItem","position":4,"name":"UML-to-DFD Reverse Translation"}]},{"@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\/814","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\/814\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/811"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=814"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}