{"id":802,"date":"2026-02-25T10:25:01","date_gmt":"2026-02-25T10:25:01","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/"},"modified":"2026-02-25T10:25:01","modified_gmt":"2026-02-25T10:25:01","slug":"lifecycle-notation-choice-dfd-vs-uml-by-project-phase","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/","title":{"rendered":"Project Lifecycle Stage Decision Factors"},"content":{"rendered":"<p>Getting the right model at the right time isn\u2019t just about clarity\u2014it\u2019s about avoiding the silent cost of misalignment. Too many teams spend weeks crafting a UML sequence diagram during requirements gathering, only to realize the business can\u2019t interpret it. The real win isn\u2019t in drawing diagrams\u2014it\u2019s in choosing the one that resonates with your audience at each stage. I\u2019ve seen teams lose months because they used the wrong notation at the wrong moment, even when the content was technically sound.<\/p>\n<p>My rule? Match the model to the purpose, not the tool. In early phases, DFDs shine because they speak the language of data. In detailed design, UML\u2019s object clarity becomes essential. This chapter breaks down when to shift from one to the other, how to transition smoothly, and why mixing both effectively is not a compromise\u2014it\u2019s a strategic advantage.<\/p>\n<h2>Early Requirements: DFD Context First<\/h2>\n<p>When you\u2019re first engaging stakeholders, especially non-technical ones, the goal isn\u2019t to model behavior. It\u2019s to map data movement. DFD context diagrams do this with unmatched simplicity.<\/p>\n<p>They answer one question: What data moves in or out of the system, and who sends or receives it?<\/p>\n<p>This clarity avoids premature assumptions about object behavior or internal processes. A bank\u2019s payment processing team will immediately understand a DFD showing \u201cPayment Instruction\u201d flowing from a customer to a processing engine. They don\u2019t care about classes or messages yet.<\/p>\n<h3>Why DFDs win in early requirements<\/h3>\n<ul>\n<li><strong>Stakeholder comprehension:<\/strong> Non-technical users grasp data sources and sinks faster than object interactions.<\/li>\n<li><strong>Focus on data flow:<\/strong> Highlights where data originates, what it changes, and where it ends up\u2014critical for compliance and audit.<\/li>\n<li><strong>Minimal abstraction:<\/strong> Avoids object-oriented baggage when the system\u2019s core is transactional.<\/li>\n<\/ul>\n<p>Use a <strong>DFD Level 0 (context diagram)<\/strong> as your first deliverable in any requirements workshop. It\u2019s not a placeholder\u2014it\u2019s the foundation.<\/p>\n<h2>Detailed Design: Shift to UML for Behavior and Structure<\/h2>\n<p>Once requirements are stable, the focus shifts from \u201cwhat flows\u201d to \u201chow it transforms.\u201d This is where UML takes over.<\/p>\n<p>UML\u2019s class, sequence, and state diagrams provide the fidelity needed for developers to implement. A DFD process like \u201cValidate Payment\u201d becomes a sequence of method calls: <code>PaymentValidator.validate()<\/code>, <code>TransactionService.create()<\/code>, <code>NotificationService.notify()<\/code>.<\/p>\n<p>But don\u2019t assume a direct 1:1 mapping. A single DFD process often spans multiple UML use cases or operations. The transition requires attention to granularity and responsibility.<\/p>\n<h3>Transition pattern: DFD to UML handoff<\/h3>\n<ol>\n<li>Start with a DFD Level 1 (process decomposition) to break down the main functionality.<\/li>\n<li>Map each DFD process to a UML use case or operation.<\/li>\n<li>Use DFD data flows to define input\/output parameters in UML operations.<\/li>\n<li>Use DFD data stores as class attributes or repositories.<\/li>\n<li>Validate via traceability: Each DFD process should correspond to at least one UML interaction.<\/li>\n<\/ol>\n<p>This isn\u2019t a swap\u2014it\u2019s an evolution. The DFD gives you the \u201cwhat.\u201d UML tells you \u201chow\u201d and \u201cwho.\u201d<\/p>\n<h2>Reverse Engineering: Start with DFD, Then Layer UML<\/h2>\n<p>When modernizing legacy systems\u2014COBOL, mainframes, or poorly documented code\u2014DFD is often the only viable starting point.<\/p>\n<p>Why? Legacy systems were built around data flow, not object behavior. They weren\u2019t designed with classes in mind. DFDs can untangle complex sequences of batch processing, file reads, and data transformations that UML would struggle to represent cleanly.<\/p>\n<p>Begin with a DFD context diagram to identify the system boundary and external entities. Then drill down into Level 1 and Level 2 diagrams to map out business processes and data stores.<\/p>\n<h3>From DFD to UML: A phased reverse engineering approach<\/h3>\n<ul>\n<li><strong>Phase 1: DFD Analysis<\/strong> \u2013 Reverse engineer data flows and processes. Identify input\/output patterns and key data stores.<\/li>\n<li><strong>Phase 2: Identify Candidates for Objects<\/strong> \u2013 Map data stores to potential classes. Look for repeated data patterns (e.g., \u201cCustomer,\u201d \u201cOrder\u201d) to define object boundaries.<\/li>\n<li><strong>Phase 3: UML Modeling<\/strong> \u2013 Create class diagrams from identified objects. Add operations based on DFD processes.<\/li>\n<li><strong>Phase 4: Sequence and State Diagrams<\/strong> \u2013 Use UML to model complex interactions, especially those involving state changes like \u201cOrder Status: Processing \u2192 Shipped.\u201d<\/li>\n<\/ul>\n<p>This layered approach respects the legacy system\u2019s logic while enabling modernization.<\/p>\n<h2>Maintenance and Evolution: A Mixed-Notation Strategy<\/h2>\n<p>Once a system is live, the need for modeling shifts from \u201cbuilding\u201d to \u201cunderstanding.\u201d Maintenance isn\u2019t about design\u2014it\u2019s about impact analysis.<\/p>\n<p>Here\u2019s the truth: you\u2019ll need both notations. DFDs help answer questions like \u201cWhat happens when we remove this file?\u201d or \u201cWhere does this data go after the audit?\u201d UML helps with \u201cWhat breaks when we change this method?\u201d<\/p>\n<p>Keep both models updated. Use DFDs to track data lineage across system changes, and UML to trace behavioral impact.<\/p>\n<h3>Maintenance handoff checklist<\/h3>\n<ul>\n<li>Update DFDs when a data source or destination changes.<\/li>\n<li>Update UML diagrams when a method, class, or state behavior evolves.<\/li>\n<li>Use traceability links (e.g., in Visual Paradigm) to connect DFD processes to UML operations.<\/li>\n<li>Review model consistency during release planning: Is the data flow still valid?<\/li>\n<\/ul>\n<p>Think of DFD as the system\u2019s bloodstream. UML is its nervous system. Both are needed to understand how it functions\u2014and how to fix it when it fails.<\/p>\n<h2>Phase Transition Patterns: From DFD to UML and Back<\/h2>\n<p>Notation transitions aren\u2019t one-way handoffs. They\u2019re iterative, evolving steps in a system\u2019s lifecycle.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Phase<\/th>\n<th>Recommended Notation<\/th>\n<th>Key Purpose<\/th>\n<th>Transition Strategy<\/th>\n<\/tr>\n<tr>\n<td>Requirements Gathering<\/td>\n<td>DFD (Level 0)<\/td>\n<td>Clarify data boundaries and stakeholder interactions<\/td>\n<td>Use context diagram to identify key processes<\/td>\n<\/tr>\n<tr>\n<td>Analysis (Detailed)<\/td>\n<td>DFD (Level 1\u20132)<\/td>\n<td>Break down processes and data flows<\/td>\n<td>Map each process to UML use cases<\/td>\n<\/tr>\n<tr>\n<td>Design (Implementation)<\/td>\n<td>UML (Class, Sequence, State)<\/td>\n<td>Specify behavior, structure, and collaboration<\/td>\n<td>Use DFD for validation of data flow paths<\/td>\n<\/tr>\n<tr>\n<td>Maintenance<\/td>\n<td>Mixed (DFD + UML)<\/td>\n<td>Enable impact analysis and troubleshooting<\/td>\n<td>Maintain traceability and update both models<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This table isn\u2019t a rigid rulebook. It\u2019s a guide for intention and flow. The goal is to use the right tool for the question you\u2019re trying to answer.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can I use both DFD and UML in the same project?<\/h3>\n<p>Absolutely. In fact, doing so is common in large or regulated systems. Use DFDs to model audit trails, data flows, and compliance paths. Use UML to detail implementation logic, object behavior, and interaction patterns.<\/p>\n<h3>How do I know when to switch from DFD to UML?<\/h3>\n<p>When the focus shifts from \u201cwhat data moves\u201d to \u201chow it is transformed.\u201d This typically happens after requirements are validated. If developers need to understand how a process works, UML becomes essential.<\/p>\n<h3>Is it bad to start with UML in requirements?<\/h3>\n<p>It\u2019s not inherently bad, but it risks overwhelming stakeholders. If the model is too detailed, it may obscure the core data flow. Start with DFD to establish clarity, then add UML for design detail.<\/p>\n<h3>What if my team prefers only one notation?<\/h3>\n<p>Start by aligning on the project&rsquo;s purpose. If compliance is key (e.g., finance, healthcare), lean toward DFD. If the system is behaviorally complex (e.g., e-commerce, real-time systems), UML is better. Gradually introduce the other when needed.<\/p>\n<h3>Can I generate code from DFDs?<\/h3>\n<p>Not directly. DFDs are not designed for code generation. But they can generate pseudocode or script prototypes. For actual code, use UML models with round-trip engineering tools.<\/p>\n<h3>What about automated model synchronization between DFD and UML?<\/h3>\n<p>Tools like Visual Paradigm support cross-referencing and traceability. Use them to link DFD processes to UML use cases, and data stores to classes. Manual validation is still required\u2014no tool fully automates this.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Getting the right model at the right time isn\u2019t just about clarity\u2014it\u2019s about avoiding the silent cost of misalignment. Too many teams spend weeks crafting a UML sequence diagram during requirements gathering, only to realize the business can\u2019t interpret it. The real win isn\u2019t in drawing diagrams\u2014it\u2019s in choosing the one that resonates with your [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":799,"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-802","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>lifecycle notation choice: DFD vs UML by project phase<\/title>\n<meta name=\"description\" content=\"Make the right modeling choice at each project phase. Learn when to use DFD vs UML across requirements, design, and maintenance. Master the modeling notation lifecycle for better system clarity and team alignment.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"lifecycle notation choice: DFD vs UML by project phase\" \/>\n<meta property=\"og:description\" content=\"Make the right modeling choice at each project phase. Learn when to use DFD vs UML across requirements, design, and maintenance. Master the modeling notation lifecycle for better system clarity and team alignment.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/\" \/>\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\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/\",\"name\":\"lifecycle notation choice: DFD vs UML by project phase\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:25:01+00:00\",\"description\":\"Make the right modeling choice at each project phase. Learn when to use DFD vs UML across requirements, design, and maintenance. Master the modeling notation lifecycle for better system clarity and team alignment.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/#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\":\"Decision Frameworks and Criteria\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Project Lifecycle Stage Decision Factors\"}]},{\"@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":"lifecycle notation choice: DFD vs UML by project phase","description":"Make the right modeling choice at each project phase. Learn when to use DFD vs UML across requirements, design, and maintenance. Master the modeling notation lifecycle for better system clarity and team alignment.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/","og_locale":"fr_FR","og_type":"article","og_title":"lifecycle notation choice: DFD vs UML by project phase","og_description":"Make the right modeling choice at each project phase. Learn when to use DFD vs UML across requirements, design, and maintenance. Master the modeling notation lifecycle for better system clarity and team alignment.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/","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\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/","name":"lifecycle notation choice: DFD vs UML by project phase","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:25:01+00:00","description":"Make the right modeling choice at each project phase. Learn when to use DFD vs UML across requirements, design, and maintenance. Master the modeling notation lifecycle for better system clarity and team alignment.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/lifecycle-notation-choice-dfd-vs-uml-by-project-phase\/#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":"Decision Frameworks and Criteria","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-decision-framework\/"},{"@type":"ListItem","position":4,"name":"Project Lifecycle Stage Decision Factors"}]},{"@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\/802","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\/802\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/799"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=802"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=802"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}