{"id":800,"date":"2026-02-25T10:25:00","date_gmt":"2026-02-25T10:25:00","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/"},"modified":"2026-02-25T10:25:00","modified_gmt":"2026-02-25T10:25:00","slug":"data-vs-object-modeling-decision","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/","title":{"rendered":"Primary Decision Factors: Data vs. Object Focus"},"content":{"rendered":"<p>At the heart of every system design lies a fundamental question: do we start by tracing data as it moves through a system, or by modeling the objects that act upon it? The moment you begin analyzing a business process, this decision shapes how clearly you\u2019ll communicate with stakeholders, how well you\u2019ll manage complexity, and how maintainable your design will become.<\/p>\n<p>Too often, teams default to UML out of habit, even when the problem is fundamentally about data movement. I\u2019ve seen this happen repeatedly\u2014business analysts drawing class diagrams for a batch reporting system, only to find that stakeholders can\u2019t read them. Conversely, I\u2019ve seen DFDs used to model user interactions in an e-commerce platform, leading to ambiguous flows and missed state transitions.<\/p>\n<p>This chapter cuts through the noise. Based on two decades of working with teams across finance, healthcare, and software development, I\u2019ll show you how to choose between data flow modeling and object modeling\u2014not based on preference, but on the actual nature of the system you\u2019re building.<\/p>\n<h2>Core Decision Framework: Data Flow vs. Object Collaboration<\/h2>\n<p>When a system\u2019s behavior is defined by how data moves, transforms, and persists, DFD is your best friend. When it\u2019s defined by how objects interact, change state, and manage identity, UML wins.<\/p>\n<h3>Ask These 3 Questions to Decide<\/h3>\n<ol>\n<li><strong>Is the primary goal to document data lineage and transformation?<\/strong> If yes, DFD is likely better. Think batch processing, regulatory reporting, audit trails.<\/li>\n<li><strong>Do objects have complex lifecycles, state changes, or interactions across multiple services?<\/strong> If yes, UML is the clearer choice. Think session management, order fulfillment, clinical workflows.<\/li>\n<li><strong>Are stakeholders mostly non-technical (e.g., business analysts, auditors, operations)?<\/strong> If yes, DFD\u2019s visual clarity often trumps UML\u2019s detail.<\/li>\n<\/ol>\n<p>This framework isn\u2019t about one notation being \u201cbetter.\u201d It\u2019s about matching the method to the problem. Let\u2019s explore real-world scenarios.<\/p>\n<h3>When Data Movement Dominates: DFD Wins<\/h3>\n<p>Consider a healthcare claims processing system. Each claim flows through multiple stages: submission \u2192 validation \u2192 eligibility check \u2192 adjudication \u2192 payment. The data moves through predefined steps, with each process transforming the claim in a deterministic way.<\/p>\n<p>Modeling this as a DFD Level 1 reveals the exact data flows, decision points, and store locations\u2014critical for compliance with HIPAA and audit verification. A UML use case diagram might show \u201cProcess Claim,\u201d but it doesn\u2019t capture how the data changes at each step.<\/p>\n<p>Use DFD when:<\/p>\n<ul>\n<li>You\u2019re modeling end-to-end data lineage for compliance or auditing.<\/li>\n<li>Your system is batch-based or event-driven with little stateful object interaction.<\/li>\n<li>Stakeholders need a clear picture of where data comes from and where it goes.<\/li>\n<\/ul>\n<h3>When Object Behavior Is Central: UML Wins<\/h3>\n<p>Now imagine an e-commerce platform. A user adds a product to their cart, logs in, applies a coupon, and checks out. The <strong>cart object<\/strong> persists across sessions, changes state (incomplete \u2192 checkout \u2192 paid \u2192 shipped), and interacts with payment, inventory, and shipping services.<\/p>\n<p>Modeling this in UML using sequence and state diagrams reveals object lifecycles, message timing, and error recovery logic. A DFD might show \u201cprocess order,\u201d but it can\u2019t show how the cart object retains state or how the user\u2019s session impacts order status.<\/p>\n<p>Use UML when:<\/p>\n<ul>\n<li>You need to model state transitions, message sequences, or object collaboration.<\/li>\n<li>The system involves user sessions, real-time updates, or distributed microservices.<\/li>\n<li>Developers will use the model to generate code or define API contracts.<\/li>\n<\/ul>\n<h2>Decision Tree: How to Choose in Practice<\/h2>\n<p>Use this flow to guide your notation choice:<\/p>\n<ol>\n<li><strong>Start with the data flow.<\/strong> Ask: \u201cWhat data changes, and how?\u201d If the answer is clear and hierarchical (e.g., \u201cclaim data is validated, then processed\u201d), DFD is ideal.<\/li>\n<li><strong>Then assess object complexity.<\/strong> Ask: \u201cDo these objects need to maintain state, interact across time, or inherit behaviors?\u201d If yes, UML is required.<\/li>\n<li><strong>Check stakeholder needs.<\/strong> If business users are the primary audience, DFD\u2019s simplicity often wins. If developers are the target, UML\u2019s precision is essential.<\/li>\n<li><strong>Consider scale and lifecycle.<\/strong> For legacy systems or large batch processes, DFD is easier to reverse-engineer. For modern, evolving systems, UML supports change better.<\/li>\n<\/ol>\n<h3>Real-World Examples<\/h3>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Project Type<\/th>\n<th>Recommended Notation<\/th>\n<th>Why<\/th>\n<\/tr>\n<tr>\n<td>Payroll processing system<\/td>\n<td>DFD<\/td>\n<td>Clear data transformation: employee data \u2192 payroll rules \u2192 payment.<\/td>\n<\/tr>\n<tr>\n<td>Online banking dashboard<\/td>\n<td>UML (Sequence + State)<\/td>\n<td>User session, balance state, transaction history\u2014objects with state.<\/td>\n<\/tr>\n<tr>\n<td>Supply chain inventory tracking<\/td>\n<td>DFD<\/td>\n<td>Material flow, batch status, warehouse transfers.<\/td>\n<\/tr>\n<tr>\n<td>Healthcare patient monitoring<\/td>\n<td>UML (State + Sequence)<\/td>\n<td>Patient vitals change over time; alerts trigger object actions.<\/td>\n<\/tr>\n<tr>\n<td>Regulatory reporting (SOX, PCI-DSS)<\/td>\n<td>DFD<\/td>\n<td>End-to-end data traceability is required for audit.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These aren\u2019t rigid rules. In hybrid systems, you can use both\u2014DFD for high-level data flows, UML for detailed object behavior. But never use one when the other is clearly better suited.<\/p>\n<h2>When to Model Data Flow vs Objects<\/h2>\n<p>Here\u2019s how to apply the decision in real projects:<\/p>\n<h3>Use DFD When:<\/h3>\n<ul>\n<li>You need to prove that data flows from source to destination without loss or alteration.<\/li>\n<li>Compliance requires a clear audit trail (e.g., financials, healthcare).<\/li>\n<li>You&#8217;re analyzing a legacy system with no object-oriented structure.<\/li>\n<li>The problem is procedural: \u201cHow does this data move through the system?\u201d<\/li>\n<\/ul>\n<h3>Use UML When:<\/h3>\n<ul>\n<li>The system must maintain state across interactions (e.g., e-commerce carts, user sessions).<\/li>\n<li>Multiple objects collaborate through message passing (e.g., microservices, real-time systems).<\/li>\n<li>Code generation or API design is part of the workflow.<\/li>\n<li>You\u2019re modeling user journeys with multiple state changes.<\/li>\n<\/ul>\n<p>Remember: DFD is about transformation. UML is about identity and behavior.<\/p>\n<h2>Common Pitfalls to Avoid<\/h2>\n<ul>\n<li><strong>Overusing UML for simple flows.<\/strong> Don\u2019t draw a class diagram when a DFD would be clearer. Over-complexity confuses stakeholders and adds no value.<\/li>\n<li><strong>Using DFD for stateful systems.<\/strong> You can\u2019t model \u201ccart is empty\u201d or \u201corder is pending\u201d in a DFD\u2014those are object states, best modeled in UML.<\/li>\n<li><strong>Ignoring stakeholder context.<\/strong> Never assume a business user can read a UML sequence diagram. Start with DFD, then refine for technical teams.<\/li>\n<li><strong>Forcing one notation on all phases.<\/strong> Use DFD in requirements; UML in design. Each serves its purpose at the right time.<\/li>\n<\/ul>\n<h2>Frequently Asked Questions<\/h2>\n<h3>When should I use DFD instead of UML?<\/h3>\n<p>Use DFD when the system is dominated by data movement, transformation, and lineage\u2014such as batch processing, compliance reporting, or legacy system analysis. DFD excels at showing what data moves where and how it changes.<\/p>\n<h3>Can I use both DFD and UML in the same project?<\/h3>\n<p>Absolutely. Use DFD for high-level data flows (e.g., context diagram) and UML for detailed object behavior (e.g., sequence diagrams). This is called hybrid modeling. The key is consistency: ensure processes map to use cases, data stores to classes, and flows to messages.<\/p>\n<h3>Is DFD outdated for modern systems?<\/h3>\n<p>No. DFD is not outdated. It\u2019s still ideal for systems where data integrity and movement are critical\u2014such as finance, supply chain, and healthcare. Modern systems may use UML for implementation, but DFD remains valuable for analysis and compliance.<\/p>\n<h3>Why do business analysts prefer DFD?<\/h3>\n<p>Because it\u2019s visual, intuitive, and focused on what matters to them: data inputs, outputs, and transformations. A DFD doesn\u2019t require object-oriented thinking. It\u2019s a natural fit for stakeholders who need to understand how data moves through a system without getting bogged down in behavior or state.<\/p>\n<h3>When should I avoid UML?<\/h3>\n<p>Avoid UML when your system is purely functional or transactional with no persistent state. If your team is not trained in UML, or stakeholders can\u2019t interpret sequence\/state diagrams, DFD is a better choice. Also avoid it when simplicity and clarity are more important than detailed object interaction.<\/p>\n<h3>How do I transition from DFD to UML?<\/h3>\n<p>Start with the DFD context diagram. Map each process to a use case. Map data stores to classes. Map data flows to messages or attributes. Use tools like Visual Paradigm to maintain traceability. The goal is not to replace DFD, but to enrich it with object behavior where needed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>At the heart of every system design lies a fundamental question: do we start by tracing data as it moves throu [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":799,"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-800","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>Data vs Object Modeling Decision<\/title>\n<meta name=\"description\" content=\"Make the right choice between DFD and UML by focusing on data flow vs object behavior. Learn when to use each for system modeling based on project complexity and stakeholder needs.\" \/>\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\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Data vs Object Modeling Decision\" \/>\n<meta property=\"og:description\" content=\"Make the right choice between DFD and UML by focusing on data flow vs object behavior. Learn when to use each for system modeling based on project complexity and stakeholder needs.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/\" \/>\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\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/\",\"name\":\"Data vs Object Modeling Decision\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:25:00+00:00\",\"description\":\"Make the right choice between DFD and UML by focusing on data flow vs object behavior. Learn when to use each for system modeling based on project complexity and stakeholder needs.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/#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\":\"Decision Frameworks and Criteria\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Primary Decision Factors: Data vs. Object Focus\"}]},{\"@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":"Data vs Object Modeling Decision","description":"Make the right choice between DFD and UML by focusing on data flow vs object behavior. Learn when to use each for system modeling based on project complexity and stakeholder needs.","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\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/","og_locale":"ja_JP","og_type":"article","og_title":"Data vs Object Modeling Decision","og_description":"Make the right choice between DFD and UML by focusing on data flow vs object behavior. Learn when to use each for system modeling based on project complexity and stakeholder needs.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/","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\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/","name":"Data vs Object Modeling Decision","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:25:00+00:00","description":"Make the right choice between DFD and UML by focusing on data flow vs object behavior. Learn when to use each for system modeling based on project complexity and stakeholder needs.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/data-vs-object-modeling-decision\/#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":"Decision Frameworks and Criteria","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/"},{"@type":"ListItem","position":4,"name":"Primary Decision Factors: Data vs. Object Focus"}]},{"@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\/800","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\/800\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/799"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=800"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=800"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}