{"id":775,"date":"2026-02-25T10:24:30","date_gmt":"2026-02-25T10:24:30","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/"},"modified":"2026-02-25T10:24:30","modified_gmt":"2026-02-25T10:24:30","slug":"crc-design-cohesion-balancing-collaboration","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/","title":{"rendered":"Balancing Collaboration and Cohesion"},"content":{"rendered":"<p>There\u2019s no such thing as a perfect CRC model \u2014 not in practice, not even in theory. The truth is, every design decision you make about collaboration creates trade-offs. You can\u2019t reduce coupling without touching cohesion, and you can\u2019t improve cohesion without rethinking who talks to whom. That\u2019s the real challenge: building a model that\u2019s flexible, readable, and maintainable, not just technically correct.<\/p>\n<p>CRC design cohesion isn\u2019t about making every class do one thing. It\u2019s about ensuring that when classes work together, they do so for a clear, shared purpose. Too much coupling, and your model becomes brittle. Too little collaboration, and you end up with isolated, underused classes. The sweet spot lies in mindful design \u2014 where responsibilities are meaningful, and interactions feel natural, not forced.<\/p>\n<p>What you\u2019ll learn here is how to spot when your model is drifting toward fragmentation or entanglement. You\u2019ll gain practical strategies to keep your CRC design modular, resilient, and aligned with real-world behavior. This isn\u2019t about memorizing rules \u2014 it\u2019s about spotting patterns, fixing drift, and making decisions with confidence.<\/p>\n<h2>Understanding the Two Sides of CRC Design<\/h2>\n<h3>What Is Cohesion in CRC?<\/h3>\n<p>Cohesion measures how well a class\u2019s responsibilities support a single, unified purpose. A high-cohesion class has responsibilities that directly relate to its role. For example, a <code>BankAccount<\/code> class that manages deposits, withdrawals, and balance checks has strong cohesion.<\/p>\n<p>Low cohesion appears when responsibilities don\u2019t belong together \u2014 like if the same class handled both user authentication and interest rate calculations. This suggests the class is doing too much, or its purpose is unclear.<\/p>\n<p>High cohesion is not about minimizing responsibilities. It\u2019s about aligning them so that each one supports the class\u2019s central intent.<\/p>\n<h3>What Is Coupling in CRC?<\/h3>\n<p>Coupling refers to how tightly classes depend on each other. High coupling means one class knows too much about how another works \u2014 for instance, calling internal methods, relying on specific data structures, or assuming a particular design.<\/p>\n<p>Low coupling means classes interact through well-defined, stable interfaces. They don\u2019t care how the other works \u2014 only what it does.<\/p>\n<p>Consider a <code>PaymentProcessor<\/code> that accepts a <code>Payment<\/code> object and sends it to a <code>BankingService<\/code>. If the processor assumes the banking service uses a specific database schema, it\u2019s tightly coupled. If it only calls a <code>processPayment()<\/code> method, it\u2019s loosely coupled.<\/p>\n<h2>Striking the Balance: Class Collaboration Balance<\/h2>\n<p>Every design must balance cohesion and coupling. You can\u2019t optimize one without impacting the other. The key is to focus on <strong>modular CRC design<\/strong> \u2014 where classes are cohesive, and their interactions are clear and minimal.<\/p>\n<p>Here\u2019s how to approach this balance step by step.<\/p>\n<h3>Step 1: Start with a Clear Purpose<\/h3>\n<p>Ask: What is this class for? If you can\u2019t answer in a single sentence, the class likely lacks cohesion.<\/p>\n<p>Example: A <code>ReportGenerator<\/code> should generate reports. If it also manages user permissions or handles file storage, it\u2019s doing too much. Split it into <code>ReportGenerator<\/code>, <code>UserAccessControl<\/code>, and <code>FileStorageManager<\/code>.<\/p>\n<h3>Step 2: Refactor Based on Responsibility Overlap<\/h3>\n<p>When multiple classes share responsibilities, ask: Do they belong together, or do they serve different domains?<\/p>\n<p>Use the <strong>Single Responsibility Principle<\/strong> as a guide. If responsibilities are related to the same actor or process, they might belong under the same class. If not, consider separation.<\/p>\n<h3>Step 3: Minimize Direct Dependencies<\/h3>\n<p>Avoid direct references to implementation details. Instead, depend on abstractions.<\/p>\n<p>Instead of:<\/p>\n<pre><code>class ReportGenerator {\n    void sendToBank(BankAccount account) {\n        \/\/ accesses account.balance directly\n    }\n}<\/code><\/pre>\n<p>Prefer:<\/p>\n<pre><code>class ReportGenerator {\n    void sendToBank(PaymentService service) {\n        \/\/ only knows it needs to use service\n    }\n}<\/code><\/pre>\n<p>This reduces <strong>CRC coupling<\/strong> and improves flexibility.<\/p>\n<h3>Step 4: Prioritize Communication Over Complexity<\/h3>\n<p>Certain collaborations are inevitable. A <code>Customer<\/code> must interact with an <code>Order<\/code>, and an <code>Order<\/code> must connect to a <code>Product<\/code>. But how?<\/p>\n<p>Use clear, high-level concepts: \u201c<em>Customer places Order<\/em>\u201d is better than \u201c<em>Customer calls Order\u2019s addProduct()<\/em>\u201d \u2014 the latter creates tighter coupling.<\/p>\n<p>Let the collaboration focus on intent, not implementation.<\/p>\n<h2>Practical Guidelines for Modular CRC Design<\/h2>\n<p>Here are four habits I\u2019ve seen work consistently in real-world CRC sessions.<\/p>\n<ul>\n<li><strong>Start with actors and workflows.<\/strong> Model from business events \u2014 not from code. Let the user story or process guide your class roles.<\/li>\n<li><strong>Use domain language in responsibilities.<\/strong> Say \u201ccalculate interest\u201d instead of \u201cperform calculation.\u201d This keeps cohesion tied to meaning.<\/li>\n<li><strong>Review collaboration paths after adding each class.<\/strong> Ask: Is this interaction necessary? Can another class handle it?<\/li>\n<li><strong>Set a \u00ab\u00a0cohesion threshold\u00a0\u00bb for your session.<\/strong> If a class has more than 3\u20134 responsibilities, pause and ask: Are these truly about the same intent?<\/li>\n<\/ul>\n<h3>When to Split a Class<\/h3>\n<p>Use this checklist to decide if a class needs splitting.<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Indicator<\/th>\n<th>Sign of Problem<\/th>\n<\/tr>\n<tr>\n<td>More than 4 responsibilities<\/td>\n<td>High risk of low cohesion<\/td>\n<\/tr>\n<tr>\n<td>Responsibilities span different domains<\/td>\n<td>Signs of mixed concerns<\/td>\n<\/tr>\n<tr>\n<td>One responsibility depends on a method in another class<\/td>\n<td>High CRC coupling<\/td>\n<\/tr>\n<tr>\n<td>Refactoring leads to code duplication<\/td>\n<td>Class may be doing too much<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>If two or more indicators apply, consider splitting the class.<\/p>\n<h2>Real-World Example: A Hospital Appointment System<\/h2>\n<p>Let\u2019s say you\u2019re modeling a hospital system. A <code>Appointment<\/code> class initially holds:<\/p>\n<ul>\n<li>Set patient ID<\/li>\n<li>Set doctor ID<\/li>\n<li>Set date and time<\/li>\n<li>Calculate fee based on doctor level<\/li>\n<li>Send confirmation email<\/li>\n<\/ul>\n<p>The fee calculation and email sending are unrelated to appointment scheduling. This is low cohesion and high coupling.<\/p>\n<p>Refactor:<\/p>\n<ul>\n<li><code>Appointment<\/code>: handles scheduling, date\/time, patient\/doctor assignment<\/li>\n<li><code>AppointmentPricer<\/code>: calculates fees based on doctor level<\/li>\n<li><code>EmailService<\/code>: sends confirmation<\/li>\n<\/ul>\n<p>Now, <code>Appointment<\/code> is cohesive, and dependencies are minimal and well-defined.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<h3>Over-Collaborating: The \u201cEverything Talks to Everything\u201d Trap<\/h3>\n<p>When every class calls every other, you\u2019re building a spaghetti model. That\u2019s high coupling and poor cohesion.<\/p>\n<p>Solution: Step back. Ask: Who is responsible for this action? If only one class should manage the process, let it own the logic \u2014 don\u2019t spread it out.<\/p>\n<h3>Under-Collaborating: The \u201cI\u2019ll Do It All\u201d Class<\/h3>\n<p>One class taking on every task isn\u2019t a solution \u2014 it\u2019s a design failure.<\/p>\n<p>Solution: Use the \u201cif it feels like a second role, it probably is\u201d rule. If a class starts handling tasks from multiple domains, split it.<\/p>\n<h3>Ignoring Communication Patterns<\/h3>\n<p>Just because two classes need to talk doesn\u2019t mean they should. Sometimes, a third class \u2014 a coordinator or coordinator pattern \u2014 handles the interaction.<\/p>\n<p>Example: <code>Order<\/code> and <code>Inventory<\/code> don\u2019t need direct access. A <code>StockManager<\/code> can validate and reserve stock, reducing direct coupling.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if my CRC model has good cohesion?<\/h3>\n<p>If all responsibilities in a class support a single purpose, and no major changes in behavior are needed when adding new features, you\u2019re likely on the right track.<\/p>\n<h3>Is low coupling always better than high coupling?<\/h3>\n<p>No \u2014 some coupling is necessary. The goal is <strong>controlled<\/strong> coupling. You want minimal, intentional dependencies. Not zero. Some coupling is required for the system to function, but it should be visible, stable, and changeable without ripple effects.<\/p>\n<h3>Can I achieve high cohesion without reducing collaboration?<\/h3>\n<p>Yes. High cohesion doesn\u2019t mean no collaboration. It means the collaboration is intentional and driven by a shared purpose. Good collaboration doesn\u2019t destroy cohesion \u2014 poor collaboration does.<\/p>\n<h3>What if my team insists on keeping a class with many responsibilities?<\/h3>\n<p>Present the trade-offs: increased bug risk, longer testing cycles, difficulty refactoring. Use metrics like \u201cnumber of responsibilities\u201d and \u201cnumber of classes it calls\u201d to demonstrate coupling and cohesion visually. Show how splitting improves maintainability over time.<\/p>\n<h3>How do I teach CRC design cohesion to beginners?<\/h3>\n<p>Start with a simple, relatable example \u2014 like a bakery, library, or classroom. Let them write responsibilities in natural language. Then, ask: \u201cDoes everything here belong to the same role?\u201d Use red pens to mark responsibilities that don\u2019t fit. This builds intuition before introducing theory.<\/p>\n<h3>Should I use CRC coupling and cohesion metrics in every model?<\/h3>\n<p>Not for every model \u2014 but yes, in every team project. Use them as a conversation tool, not a scorecard. The goal is alignment, not perfection. A CRC model is a conversation starter \u2014 not a final artifact.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There\u2019s no such thing as a perfect CRC model \u2014 not in practice, not even in theory. The truth is, every design decision you make about collaboration creates trade-offs. You can\u2019t reduce coupling without touching cohesion, and you can\u2019t improve cohesion without rethinking who talks to whom. That\u2019s the real challenge: building a model that\u2019s [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":772,"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-775","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>CRC Design Cohesion: Balance Collaboration &amp; Cohesion<\/title>\n<meta name=\"description\" content=\"Achieve modular CRC design with ideal class collaboration balance. Learn how to manage CRC coupling and boost cohesion for maintainable, flexible object models.\" \/>\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\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CRC Design Cohesion: Balance Collaboration &amp; Cohesion\" \/>\n<meta property=\"og:description\" content=\"Achieve modular CRC design with ideal class collaboration balance. Learn how to manage CRC coupling and boost cohesion for maintainable, flexible object models.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/\" \/>\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=\"7 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\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/\",\"name\":\"CRC Design Cohesion: Balance Collaboration & Cohesion\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:24:30+00:00\",\"description\":\"Achieve modular CRC design with ideal class collaboration balance. Learn how to manage CRC coupling and boost cohesion for maintainable, flexible object models.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CRC Cards Explained: A Beginner\u2019s Modeling Guide\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Thinking in Responsibilities\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Balancing Collaboration and Cohesion\"}]},{\"@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":"CRC Design Cohesion: Balance Collaboration & Cohesion","description":"Achieve modular CRC design with ideal class collaboration balance. Learn how to manage CRC coupling and boost cohesion for maintainable, flexible object models.","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\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/","og_locale":"fr_FR","og_type":"article","og_title":"CRC Design Cohesion: Balance Collaboration & Cohesion","og_description":"Achieve modular CRC design with ideal class collaboration balance. Learn how to manage CRC coupling and boost cohesion for maintainable, flexible object models.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/","name":"CRC Design Cohesion: Balance Collaboration & Cohesion","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:24:30+00:00","description":"Achieve modular CRC design with ideal class collaboration balance. Learn how to manage CRC coupling and boost cohesion for maintainable, flexible object models.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/crc-design-cohesion-balancing-collaboration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"CRC Cards Explained: A Beginner\u2019s Modeling Guide","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/"},{"@type":"ListItem","position":3,"name":"Thinking in Responsibilities","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-explained\/thinking-in-responsibilities\/"},{"@type":"ListItem","position":4,"name":"Balancing Collaboration and Cohesion"}]},{"@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\/775","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\/775\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/772"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=775"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}