{"id":813,"date":"2026-02-25T10:25:06","date_gmt":"2026-02-25T10:25:06","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/"},"modified":"2026-02-25T10:25:06","modified_gmt":"2026-02-25T10:25:06","slug":"dfd-to-uml-mapping-patterns","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/","title":{"rendered":"DFD-to-UML Translation Patterns"},"content":{"rendered":"<p>Most textbooks present DFD-to-UML mapping as a direct, one-to-one conversion. That\u2019s a simplification. In real-world systems, the mapping is far more nuanced\u2014driven not by rules alone, but by intent, context, and the underlying architecture.<\/p>\n<p>Over 20 years of modeling across financial systems, healthcare platforms, and e-commerce engines has taught me this: you can&#8217;t force a DFD process into a UML use case if the process is a data transformation with no user-driven goal. The mapping must reflect purpose, not just syntax.<\/p>\n<p>This chapter offers a disciplined, experience-based guide to converting DFD components into UML constructs. You\u2019ll learn how to preserve business meaning while translating between paradigms\u2014avoiding the trap of over-engineering simple flows or losing critical data lineage.<\/p>\n<p>By the end, you\u2019ll have actionable rules, real examples, and validation strategies to ensure your models remain consistent, understandable, and operationally sound.<\/p>\n<h2>Core Mapping Principles<\/h2>\n<p>Mapping DFD to UML isn&#8217;t about visual equivalence. It&#8217;s about semantic alignment. The goal is to preserve intent: what the system does, who it serves, and how data changes over time.<\/p>\n<p>Start by asking: Is this process driven by a user goal, or is it an automated data transformation? The answer determines whether to map to a use case or a system operation.<\/p>\n<p>Here\u2019s the foundational rule: <strong>mapping is driven by behavior, not structure<\/strong>. A DFD process that performs a payroll calculation shouldn\u2019t become a use case unless it\u2019s initiated by a human action\u2014like a manager approving a batch run.<\/p>\n<h3>Mapping by Intent, Not Form<\/h3>\n<p>Consider a process labeled &#8220;Validate Customer Credentials.&#8221; If it\u2019s triggered by a login request from a user, map it to a use case: <em>Authenticate User<\/em>. But if it\u2019s called by a nightly batch job with no external trigger, it\u2019s not a use case\u2014it\u2019s a system operation, best modeled as an internal activity or method.<\/p>\n<p>Always ask:<\/p>\n<ul>\n<li>Is there a human or system actor initiating the process?<\/li>\n<li>Does it result in a visible outcome for a stakeholder?<\/li>\n<li>Is it part of a business workflow or a background data task?<\/li>\n<\/ul>\n<p>If the answer is yes to the first two, treat it as a use case. If not, model it as an operation within a class or an activity.<\/p>\n<h2>Systematic Mapping Rules<\/h2>\n<p>Use the following rules as a starting point, but adjust based on context. They\u2019re not rigid laws\u2014they\u2019re guidelines to help you think, not dictate.<\/p>\n<h3>DFD Process \u2192 UML Use Case<\/h3>\n<p>Map only when the process represents a user-initiated, goal-oriented interaction. The process name should reflect a distinct outcome.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>DFD Process:<\/strong> &#8220;Generate Monthly Invoice&#8221;<\/li>\n<li><strong>UML Use Case:<\/strong> <em>Generate Monthly Invoice<\/em><\/li>\n<\/ul>\n<p>But if the process is &#8220;Calculate Tax on Invoice&#8221; without a user trigger, it\u2019s not a use case. It\u2019s an internal method.<\/p>\n<h3>Data Store \u2192 UML Class<\/h3>\n<p>Map data stores to classes when they represent persistent, structured data with attributes and relationships.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>DFD Data Store:<\/strong> &#8220;Customer Database&#8221;<\/li>\n<li><strong>UML Class:<\/strong> <em>Customer<\/em> with attributes like <em>customerId<\/em>, <em>name<\/em>, <em>email<\/em><\/li>\n<\/ul>\n<p>But if the data store is a temporary file used for sorting, model it as a transient object or a data structure in an activity, not a full-fledged class.<\/p>\n<h3>Data Flow \u2192 UML Message or Attribute<\/h3>\n<p>Data flows into or out of a process map to messages or attributes depending on context.<\/p>\n<p>When a flow is part of a sequence between actors and systems, map it to a message in a sequence diagram.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>DFD Data Flow:<\/strong> &#8220;Invoice Data&#8221; \u2192 &#8220;Generate Monthly Invoice&#8221;<\/li>\n<li><strong>UML:<\/strong> A message labeled <em>sendInvoiceData<\/em> from <em>Invoice Generator<\/em> to <em>Customer<\/em><\/li>\n<\/ul>\n<p>If the flow is a field passed into a method (e.g., &#8220;customerID&#8221; from a UI form), map it as a method parameter.<\/p>\n<h2>Worked Example: Order Processing System<\/h2>\n<p>Consider a simple DFD Level 1 for an order processing system:<\/p>\n<ul>\n<li><strong>Process:<\/strong> &#8220;Validate Order&#8221;<\/li>\n<li><strong>Data Flow In:<\/strong> &#8220;Order Details&#8221;, &#8220;Customer ID&#8221;<\/li>\n<li><strong>Data Flow Out:<\/strong> &#8220;Valid Order&#8221;, &#8220;Error Message&#8221;<\/li>\n<li><strong>Data Store:<\/strong> &#8220;Order History&#8221;<\/li>\n<\/ul>\n<p>Here\u2019s how to convert this to UML:<\/p>\n<ul>\n<li><strong>Process &#8220;Validate Order&#8221;<\/strong> \u2192 <em>Validate Order<\/em> use case (user-initiated)<\/li>\n<li><strong>Data Store &#8220;Order History&#8221;<\/strong> \u2192 <em>Order<\/em> class with attributes: <em>orderId, date, status, customerId<\/em><\/li>\n<li><strong>Flow &#8220;Order Details&#8221; \u2192 Process<\/strong> \u2192 <em>validateOrder(Order)<\/em> method parameter<\/li>\n<li><strong>Flow &#8220;Valid Order&#8221; \u2192 Customer<\/strong> \u2192 <em>sendOrderConfirmation()<\/em> message in sequence diagram<\/li>\n<\/ul>\n<p>This preserves both the functional intent and data lineage.<\/p>\n<h2>Common Mapping Pitfalls<\/h2>\n<p>Mistakes here are not just technical\u2014they undermine trust with stakeholders and create maintenance debt.<\/p>\n<h3>Pitfall 1: Forcing Every Process into a Use Case<\/h3>\n<p>Not every process is a use case. A process like &#8220;Update Inventory Count&#8221; that runs automatically after delivery is not a use case. It\u2019s a system operation.<\/p>\n<p>Overuse of use cases leads to bloated diagrams and confusion. A use case should represent a business goal, not a technical step.<\/p>\n<h3>Pitfall 2: Ignoring Context in Data Store Translation<\/h3>\n<p>Mapping a temporary file like &#8220;Temp Order Queue&#8221; to a UML class like <em>OrderQueue<\/em> gives it undue permanence.<\/p>\n<p>Instead, model it as a data structure in an activity diagram, or a transient component in a component diagram.<\/p>\n<h3>Pitfall 3: Misinterpreting Data Flows as Messages<\/h3>\n<p>Not all data flows are messages. A flow from &#8220;Customer DB&#8221; to &#8220;Generate Invoice&#8221; is data retrieval, not a message exchange.<\/p>\n<p>Use a <em>data flow<\/em> notation in an activity diagram, not a message in a sequence diagram.<\/p>\n<h2>Validation Strategies<\/h2>\n<p>After mapping, validate with three checks:<\/p>\n<ol>\n<li><strong>Traceability:<\/strong> Can every DFD process be traced to a corresponding UML element? If not, reconsider intent.<\/li>\n<li><strong>Actor Consistency:<\/strong> Does every use case have a clear actor? If a process has no actor, it\u2019s likely not a use case.<\/li>\n<li><strong>Data Flow Integrity:<\/strong> Are input\/output data flows represented as parameters, messages, or data objects? Ensure consistency.<\/li>\n<\/ol>\n<p>Use tools like Visual Paradigm to automate traceability and cross-check. Set up validation rules to flag misaligned mappings.<\/p>\n<p>Tip: Run a \u201cbusiness stakeholder review\u201d of the UML model. If a non-technical person can\u2019t understand the purpose of a use case or class, you\u2019ve likely misrepresented the DFD.<\/p>\n<h2>When Not to Convert<\/h2>\n<p>Not every DFD needs a UML translation. Sometimes, the DFD is sufficient.<\/p>\n<p>Use DFD when:<\/p>\n<ul>\n<li>The system is highly data-centric (e.g., billing, audit, reporting).<\/li>\n<li>Stakeholders are more comfortable with data movement than object behavior.<\/li>\n<li>The goal is to document end-to-end data lineage, not object collaboration.<\/li>\n<\/ul>\n<p>Convert to UML when:<\/p>\n<ul>\n<li>Behavioral complexity (state, timing, interaction) is key.<\/li>\n<li>Code generation or microservices design is planned.<\/li>\n<li>Team is trained in object modeling and needs detailed design.<\/li>\n<\/ul>\n<p>Remember: <strong>mapping is not mandatory\u2014it\u2019s strategic<\/strong>.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I convert a DFD process that has no actor into a UML use case?<\/h3>\n<p>Don\u2019t. If the process has no external trigger or user goal, it\u2019s not a use case. Model it as an internal operation within a class or an activity in a UML activity diagram.<\/p>\n<h3>Can I convert a data store with multiple entities into a single UML class?<\/h3>\n<p>No. If the data store contains multiple related entities (e.g., &#8220;Customer&#8221;, &#8220;Order&#8221;, &#8220;Payment&#8221;), map each to a separate UML class. Use a class diagram to show relationships between them.<\/p>\n<h3>What if my data flow involves multiple data elements?<\/h3>\n<p>Break the flow into individual attributes or data objects. In UML, use a <em>DataObject<\/em> or a parameter list in a method. In sequence diagrams, represent each element as a separate message or part of a single message.<\/p>\n<h3>Why does my UML model feel larger than the DFD?<\/h3>\n<p>Because UML captures behavior, state, and relationships that DFD omits. This is expected. The goal is not to mirror DFD structure, but to preserve its intent with richer semantics.<\/p>\n<h3>Can I use both DFD and UML in the same project?<\/h3>\n<p>Absolutely. Many projects use DFD for requirements and audit visibility, then use UML for design and implementation. Just ensure traceability and consistency between models.<\/p>\n<h3>How do I avoid over-engineering when converting?<\/h3>\n<p>Apply the \u201cbusiness goal\u201d test. If a UML element doesn\u2019t serve a clear stakeholder need, simplify it. Use activity or component diagrams to avoid unnecessary class definitions.<\/p>\n<p>When done right, DFD-to-UML mapping becomes a bridge\u2014not a barrier. It allows you to move from functional clarity to behavioral precision, without losing sight of the data that powers everything.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most textbooks present DFD-to-UML mapping as a direct, one-to-one conversion. That\u2019s a simplification. In real [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":811,"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-813","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>DFD to UML Mapping: Practical Translation Patterns<\/title>\n<meta name=\"description\" content=\"Master DFD to UML mapping with proven translation rules, real-world examples, and common pitfalls. Learn how to convert data flow to UML models accurately and efficiently.\" \/>\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\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DFD to UML Mapping: Practical Translation Patterns\" \/>\n<meta property=\"og:description\" content=\"Master DFD to UML mapping with proven translation rules, real-world examples, and common pitfalls. Learn how to convert data flow to UML models accurately and efficiently.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills\u65e5\u672c\u8a9e\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\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\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/\",\"name\":\"DFD to UML Mapping: Practical Translation Patterns\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:25:06+00:00\",\"description\":\"Master DFD to UML mapping with proven translation rules, real-world examples, and common pitfalls. Learn how to convert data flow to UML models accurately and efficiently.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data Flow Diagrams vs. UML: When to Use Each\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Hybrid Modeling Strategies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"DFD-to-UML Translation Patterns\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DFD to UML Mapping: Practical Translation Patterns","description":"Master DFD to UML mapping with proven translation rules, real-world examples, and common pitfalls. Learn how to convert data flow to UML models accurately and efficiently.","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\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/","og_locale":"ja_JP","og_type":"article","og_title":"DFD to UML Mapping: Practical Translation Patterns","og_description":"Master DFD to UML mapping with proven translation rules, real-world examples, and common pitfalls. Learn how to convert data flow to UML models accurately and efficiently.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"7\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/","name":"DFD to UML Mapping: Practical Translation Patterns","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:25:06+00:00","description":"Master DFD to UML mapping with proven translation rules, real-world examples, and common pitfalls. Learn how to convert data flow to UML models accurately and efficiently.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/dfd-to-uml-mapping-patterns\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Data Flow Diagrams vs. UML: When to Use Each","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/"},{"@type":"ListItem","position":3,"name":"Hybrid Modeling Strategies","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/hybrid-dfd-uml-modeling\/"},{"@type":"ListItem","position":4,"name":"DFD-to-UML Translation Patterns"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website","url":"https:\/\/skills.visual-paradigm.com\/ja\/","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","url":"https:\/\/skills.visual-paradigm.com\/ja\/","logo":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills\u65e5\u672c\u8a9e"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/813","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/813\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/811"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=813"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=813"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}