{"id":791,"date":"2026-02-25T10:24:56","date_gmt":"2026-02-25T10:24:56","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/"},"modified":"2026-02-25T10:24:56","modified_gmt":"2026-02-25T10:24:56","slug":"notation-choice-impact","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/","title":{"rendered":"When Notation Choice Actually Matters Most"},"content":{"rendered":"

Too many teams treat DFD and UML as interchangeable tools. That\u2019s a misconception. The right choice isn\u2019t about preference\u2014it\u2019s about context. One misstep in notation selection at the wrong phase can force rework, miscommunication, and compliance gaps that ripple through every stage. I\u2019ve seen projects stall because a business analyst used UML sequence diagrams in a requirements workshop, overwhelming stakeholders. Conversely, I\u2019ve seen complex systems fail to scale because developers built on an over-simplified DFD without modeling object behavior. The consequence? Time lost, cost overruns, and team frustration.<\/p>\n

Notation choice impact is most profound during three high-leverage moments: stakeholder alignment, architectural handoff, and compliance documentation. Choosing the wrong tool at these points compounds complexity and erodes trust. The good news? With the right criteria, you can make consistent, confident choices that serve both business and technical goals. This chapter breaks down exactly when and why notation matters most, supported by real-world scenarios and decision patterns.<\/p>\n

High-Leverage Decision Moments<\/h2>\n

1. Requirements Workshops: Stakeholder Clarity First<\/h3>\n

When gathering business requirements, clarity trumps complexity. DFDs, with their focus on data flows and external entities, are ideal for explaining *what* data moves and *where* it comes from. Stakeholders\u2014especially non-technical ones\u2014respond better to visual representations of transactions and data sources than to object lifecycles.<\/p>\n

UML use case diagrams are powerful for outlining functional goals, but they require understanding actors, system boundaries, and dependencies. In a financial services project, I used a DFD context diagram to explain how customer data flowed from branches to core systems. The business team could instantly see data gaps. Switching to UML at that stage would have introduced unnecessary abstraction.<\/p>\n

Rule:<\/strong> When the goal is stakeholder understanding, prioritize DFD. Use UML only when you need to model user goals and system interactions at a deeper level.<\/p>\n

2. Architecture Definition: Developer Handoff and Precision<\/h3>\n

At the architecture stage, developers need precise, behavior-driven models. UML excels here\u2014class diagrams clarify object relationships, sequence diagrams model message flows, and component diagrams define modular boundaries.<\/p>\n

But here\u2019s the trap: teams that rely solely on DFD for architecture risk missing critical behavioral details. A DFD shows a process transforms data, but not how or when. UML fills that gap with state machines, timing diagrams, and method signatures.<\/p>\n

In a healthcare system I reviewed, the initial DFD showed \u00ab\u00a0Patient Record Updated\u00a0\u00bb as a process. But without UML sequence diagrams, the team missed that updates required validation, audit logging, and triggering of downstream clinical alerts. The gap led to a compliance audit failure.<\/p>\n

Rule:<\/strong> For architecture handoffs, use UML to define behavior and collaboration. Use DFD to validate data lineage and ensure no critical flow is missing.<\/p>\n

3. Compliance and Audit Trails: Proof of Data Integrity<\/h3>\n

Regulatory frameworks like SOX, HIPAA, and PCI-DSS require auditable data flows. DFDs are the gold standard here because they explicitly map data movement across systems, who accesses it, and how it changes.<\/p>\n

UML, focused on object state and behavior, doesn\u2019t naturally express data lineage. While you can create custom diagrams, they\u2019re not standard. In a banking modernization project, the audit team rejected UML-based explanations of transaction data movement. Only a DFD-level flow with data store mappings passed inspection.<\/p>\n

Rule:<\/strong> When compliance is a factor, DFD is not optional\u2014it\u2019s mandatory. Use it to document data movement, retention, and access rights.<\/p>\n

4. Reverse Engineering Legacy Systems: DFD First<\/h3>\n

Legacy systems often lack documentation. DFDs provide the clearest path to understanding data flows in procedural or batch systems. They expose the real functional logic behind code.<\/p>\n

Attempting to model a COBOL-based payroll system with UML would have required reverse-engineering every object, state transition, and method call\u2014far too complex for initial understanding. DFD Level 0 revealed the core processes: data input \u2192 payroll calculation \u2192 output file. That single diagram clarified 80% of the system.<\/p>\n

Rule:<\/strong> For legacy systems, start with DFD. Use it to reverse engineer the functional structure before modeling objects or behavior.<\/p>\n

When Wrong Diagram Notation Costs More Than You Think<\/h2>\n

Choosing the wrong notation isn\u2019t just inefficient\u2014it\u2019s expensive. The cost compounds over time:<\/p>\n

    \n
  • Communication failure:<\/strong> A UML diagram in a requirements workshop confuses stakeholders, leading to rework and delays.<\/li>\n
  • Implementation errors:<\/strong> A DFD without behavioral details leads to missing validation, logging, or error handling in code.<\/li>\n
  • Compliance failure:<\/strong> A project relying solely on UML for data flow will fail audits, requiring costly rework.<\/li>\n
  • Team friction:<\/strong> Developers and business analysts speaking different modeling languages create handoff gaps.<\/li>\n<\/ul>\n

    One client spent three months reworking a UML-based design because the DFD context diagram had been ignored. The business model was correct, but the technical implementation missed key data access points.<\/p>\n

    Practical Frameworks for Notation Choice<\/h2>\n

    Decision Checklist: When to Choose DFD vs UML<\/h3>\n

    Use this checklist to evaluate your project\u2019s needs:<\/p>\n

      \n
    1. Is the primary goal stakeholder understanding<\/strong>? \u2192 Choose DFD.<\/li>\n
    2. Are you modeling object behavior, state, or collaboration<\/strong>? \u2192 Choose UML.<\/li>\n
    3. Do you need audit trails or regulatory compliance<\/strong>? \u2192 Choose DFD.<\/li>\n
    4. Are you analyzing or modernizing a legacy or batch system<\/strong>? \u2192 Start with DFD.<\/li>\n
    5. Is the team technical<\/strong> and familiar with UML? \u2192 Use UML for architecture.<\/li>\n
    6. Are you designing a real-time, event-driven, or service-oriented system<\/strong>? \u2192 Use UML.<\/li>\n<\/ol>\n

      When in doubt, start with DFD for analysis, then refine with UML for design. This hybrid approach maximizes clarity and precision.<\/p>\n

      Modeling Notation Project Impact: Real Examples<\/h2>\n

      Here\u2019s how notation choice impact played out in actual projects:<\/p>\n\n\n\n\n\n\n\n
      Project Type<\/th>\nPreferred Notation<\/th>\nOutcome of Wrong Choice<\/th>\nImpact<\/th>\n<\/tr>\n
      Banking Compliance System<\/td>\nDFD<\/td>\nUsed UML only<\/td>\nAudit failed; required rework<\/td>\n<\/tr>\n
      E-Commerce Checkout<\/td>\nUML (Sequence + State)<\/td>\nUsed DFD only<\/td>\nMissed session timeouts and error flows<\/td>\n<\/tr>\n
      Insurance Claims Processing<\/td>\nDFD<\/td>\nUsed UML in requirements<\/td>\nStakeholders misunderstood; rework needed<\/td>\n<\/tr>\n
      ERP Material Flow<\/td>\nDFD<\/td>\nUsed UML<\/td>\nOver-engineered; failed to capture key flow<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Frequently Asked Questions<\/h2>\n

      When to choose DFD vs UML in a requirements workshop?<\/h3>\n

      Choose DFD. It focuses on data inputs, outputs, and sources\u2014what stakeholders understand. UML use case diagrams add abstraction that can confuse non-technical staff. DFDs keep the focus on what\u2019s happening with data.<\/p>\n

      How does notation choice impact project timeline?<\/h3>\n

      Wrong notation leads to rework, miscommunication, and rework. A DFD used in design can miss critical behavior; UML in requirements can delay understanding. Early correct choice avoids rework, saving 2\u20136 weeks in average projects.<\/p>\n

      Can I use both DFD and UML in the same project?<\/h3>\n

      Yes\u2014and it\u2019s often recommended. Use DFD for analysis (data flows), UML for design (object behavior). A layered approach (DFD context \u2192 UML packages\/sequences) ensures clarity and precision.<\/p>\n

      What if my team is more familiar with UML?<\/h3>\n

      Start with UML for design, but validate with DFD during requirements. Use DFD to ensure data flows are complete. You can model UML elements on top of DFD to maintain traceability.<\/p>\n

      Is DFD still relevant in the age of microservices?<\/h3>\n

      Yes. DFD is essential for tracing data across services. Microservices may use UML for internal logic, but DFD reveals how data moves through the system\u2014critical for compliance, monitoring, and debugging.<\/p>\n

      How do I convince a stakeholder to use DFD instead of UML?<\/h3>\n

      Show a before\/after example. Use a DFD to explain a process in simple terms. Then show how the UML version confuses stakeholders. Highlight that clarity leads to fewer errors, faster sign-offs, and fewer change requests.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Too many teams treat DFD and UML as interchangeable tools. That\u2019s a misconception. The right choice isn\u2019t about preference\u2014it\u2019s about context. One misstep in notation selection at the wrong phase can force rework, miscommunication, and compliance gaps that ripple through every stage. I\u2019ve seen projects stall because a business analyst used UML sequence diagrams in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":787,"menu_order":3,"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-791","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nNotation Choice Impact: When It Actually Matters<\/title>\n<meta name=\"description\" content=\"Discover why notation choice impact determines project success. Learn when to pick DFD vs UML across key phases to avoid costly mistakes and maximize clarity, maintainability, and compliance.\" \/>\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\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Notation Choice Impact: When It Actually Matters\" \/>\n<meta property=\"og:description\" content=\"Discover why notation choice impact determines project success. Learn when to pick DFD vs UML across key phases to avoid costly mistakes and maximize clarity, maintainability, and compliance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/\",\"name\":\"Notation Choice Impact: When It Actually Matters\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:24:56+00:00\",\"description\":\"Discover why notation choice impact determines project success. Learn when to pick DFD vs UML across key phases to avoid costly mistakes and maximize clarity, maintainability, and compliance.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data Flow Diagrams vs. UML: When to Use Each\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Understanding the Methodologies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"When Notation Choice Actually Matters Most\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Notation Choice Impact: When It Actually Matters","description":"Discover why notation choice impact determines project success. Learn when to pick DFD vs UML across key phases to avoid costly mistakes and maximize clarity, maintainability, and compliance.","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\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/","og_locale":"fr_FR","og_type":"article","og_title":"Notation Choice Impact: When It Actually Matters","og_description":"Discover why notation choice impact determines project success. Learn when to pick DFD vs UML across key phases to avoid costly mistakes and maximize clarity, maintainability, and compliance.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/","name":"Notation Choice Impact: When It Actually Matters","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:24:56+00:00","description":"Discover why notation choice impact determines project success. Learn when to pick DFD vs UML across key phases to avoid costly mistakes and maximize clarity, maintainability, and compliance.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/notation-choice-impact\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Data Flow Diagrams vs. UML: When to Use Each","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/"},{"@type":"ListItem","position":3,"name":"Understanding the Methodologies","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/"},{"@type":"ListItem","position":4,"name":"When Notation Choice Actually Matters Most"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/791","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/791\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/787"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=791"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=791"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}