{"id":949,"date":"2026-02-25T10:32:37","date_gmt":"2026-02-25T10:32:37","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/"},"modified":"2026-02-25T10:32:37","modified_gmt":"2026-02-25T10:32:37","slug":"crc-uml-mistakes-to-avoid","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/","title":{"rendered":"Common Pitfalls When Converting CRC to UML"},"content":{"rendered":"<p>About 6 out of 10 teams I\u2019ve worked with overlook the behavioral nuance when converting CRC cards to UML, leading to models that are syntactically correct but semantically hollow. The issue isn\u2019t with the mechanics\u2014it\u2019s in how the collaborative intent of CRC gets flattened into static structure. CRC cards are about communication, responsibility, and interaction. When we rush to convert them into UML without preserving that intent, we lose the very foundation the team built together.<\/p>\n<p>What you\u2019ll gain here is a real-world guide to spotting and fixing the most common CRC to UML errors. I\u2019ve distilled years of feedback from design reviews, team workshops, and model audits into clear, actionable insights\u2014no fluff, no jargon overload. You\u2019ll learn how to detect over-engineering, misinterpret collaborations, and misapply relationships, along with practical model validation tips to check your work before it becomes code.<\/p>\n<h2>Over-Engineering the Model: When Simplicity Gets Lost<\/h2>\n<p>One of the most frequent CRC to UML errors is adding attributes and operations that aren\u2019t directly tied to the CRC responsibilities. It\u2019s tempting to anticipate future needs, but this erodes clarity and invites technical debt.<\/p>\n<p>I once saw a team add 17 attributes to a <code>PaymentProcessor<\/code> class because someone said, \u201cWe might need to track the payment method later.\u201d The problem? The original CRC card only listed \u201cprocess payment\u201d and \u201cverify funds\u201d\u2014no mention of method tracking. The extra complexity made the class harder to test, maintain, and understand.<\/p>\n<ul>\n<li>Only add attributes or operations that directly serve a responsibility listed on the CRC card.<\/li>\n<li>Use <strong>intent-driven modeling<\/strong>\u2014ask: \u201cDoes this element help fulfill the responsibility?\u201d<\/li>\n<li>Delay implementation details until the design is validated and refined.<\/li>\n<\/ul>\n<h3>When to Hold Back<\/h3>\n<p>If a class has more than 5 attributes or 8 operations without clear behavioral grouping, re-evaluate. Chances are, you\u2019ve merged responsibilities or introduced hidden complexity.<\/p>\n<h2>Misinterpreting Collaborations: The Hidden Risk<\/h2>\n<p>CRC cards say \u201ccollaborates with\u201d \u2014 but UML treats this as an association, aggregation, or dependency. The misstep? Assuming all collaborations are direct associations, especially when they aren\u2019t.<\/p>\n<p>For example, a <code>Customer<\/code> card might list \u201ccollaborates with: Order, Invoice.\u201d In UML, this often becomes a direct association. But in reality, <code>Order<\/code> might be created by a <code>ShoppingCart<\/code>, and <code>Invoice<\/code> is generated by <code>Order<\/code>\u2014so the relationship isn\u2019t direct.<\/p>\n<p>Misinterpreting collaboration leads to inaccurate dependencies, broken lifecycles, and poor maintainability.<\/p>\n<table>\n<tbody>\n<tr>\n<th>CRC Collaboration<\/th>\n<th>Correct UML Mapping<\/th>\n<th>Common Mistake<\/th>\n<\/tr>\n<tr>\n<td>Customer \u2192 Order<\/td>\n<td>Customer creates Order via ShoppingCart<\/td>\n<td>Direct association between Customer and Order<\/td>\n<\/tr>\n<tr>\n<td>Order \u2192 Invoice<\/td>\n<td>Order generates Invoice (dependency)<\/td>\n<td>Association without proper direction or multiplicity<\/td>\n<\/tr>\n<tr>\n<td>Invoice \u2192 Payment<\/td>\n<td>Invoice triggers Payment (dependency)<\/td>\n<td>Association with no semantic intent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Always trace the actual behavior. Ask: \u201cWhat object creates or triggers this?\u201d Use <strong>dependencies<\/strong> for temporary or event-driven links. Reserve <strong>associations<\/strong> for stable, long-lived relationships.<\/p>\n<h2>Ignoring Behavioral Intent: The Silent Model Degradation<\/h2>\n<p>When teams focus only on structure\u2014class names, attributes, methods\u2014they forget that CRC cards were never just about static elements. They were about <strong>what objects do together<\/strong>.<\/p>\n<p>Consider a CRC card saying: \u201cBankAccount \u2192 transfers money to: SavingsAccount.\u201d The intent is behavioral: a transfer is an action involving two accounts. In UML, this becomes a method like <code>transferTo(SavingsAccount, amount)<\/code>.<\/p>\n<p>But too often, this gets reduced to: <code>transferTo(SavingsAccount)<\/code> with no mention of the source. Worse, some teams rename it to <code>sendFunds()<\/code>\u2014which sounds more generic and loses the domain-specific intent.<\/p>\n<p>Model validation tips:<\/p>\n<ul>\n<li>Review method names: Do they reflect the <strong>action and participants<\/strong>?<\/li>\n<li>Check if responsibilities are mapped to methods with <strong>clear, domain-relevant verbs<\/strong>.<\/li>\n<li>Use <strong>behavioral naming patterns<\/strong>: \u201ctransferTo\u201d, \u201cvalidate\u201d, \u201cgenerateReport\u201d instead of \u201cprocess\u201d or \u201cdoSomething\u201d.<\/li>\n<\/ul>\n<h3>Example: Better Intent in Action<\/h3>\n<p>CRC: \u201cLoanApplication \u2192 sends to: Underwriter\u201d<\/p>\n<p>Bad UML: <code>sendTo(underwriter)<\/code><\/p>\n<p>Good UML: <code>submitTo(underwriter)<\/code> or <code>forwardTo(underwriter)<\/code><\/p>\n<p>Small change, big difference in clarity and maintainability.<\/p>\n<h2>Skipping Model Validation: The Cost of Oversight<\/h2>\n<p>Many teams assume that because the model looks like a UML diagram, it\u2019s valid. But visual correctness \u2260 structural or behavioral correctness. This is where design pitfalls UML often emerge.<\/p>\n<p>Here\u2019s a simple checklist I use in every design review:<\/p>\n<ol>\n<li>Every method in the UML diagram must derive from a <strong>specific CRC responsibility<\/strong>.<\/li>\n<li>Every association must have a <strong>justified reason<\/strong> based on collaboration or lifecycle behavior.<\/li>\n<li>No class should have more than two responsibilities unless clearly separated by <code>public<\/code> and <code>private<\/code> sections.<\/li>\n<li>All <strong>cardinalities<\/strong> must be validated: e.g., Is \u201c0..1\u201d correct for a one-time event?<\/li>\n<li>Check that inheritance hierarchies don\u2019t emerge from accidental abstraction\u2014ask: \u201cWould a subclass <em>replace<\/em> or <em>extend<\/em> this behavior?\u201d<\/li>\n<\/ol>\n<p>These model validation tips are not optional. They\u2019re the difference between a working design and a maintenance nightmare.<\/p>\n<h2>Underestimating the Power of Feedback Loops<\/h2>\n<p>One of the most overlooked CRC UML mistakes is treating the conversion as a one-way process. But good design is iterative.<\/p>\n<p>If your UML class diagram causes confusion in a team meeting, or a developer asks, \u201cWhy is this class so big?\u201d, you\u2019ve missed a feedback loop. Revisit the original CRC cards. Do they still reflect the current understanding?<\/p>\n<p>Every time you find a discrepancy:<\/p>\n<ul>\n<li>Go back to the CRC card.<\/li>\n<li>Re-ask: \u201cWhat were we trying to model here?\u201d<\/li>\n<li>Revise the UML model to reflect the shared understanding.<\/li>\n<\/ul>\n<p>This isn\u2019t a failure\u2014it\u2019s <strong>design maturity<\/strong>. The model evolves, just like the team\u2019s understanding.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Why do my UML models look too complex after CRC to UML conversion?<\/h3>\n<p>Complexity usually comes from adding elements not grounded in CRC responsibilities. Go back to the original CRC cards and ask: \u201cDoes this attribute or method directly support a listed responsibility?\u201d If not, remove it. Focus on intent, not completeness.<\/p>\n<h3>Can I use CRC cards after creating the UML diagram?<\/h3>\n<p>Absolutely. The beauty of CRC is that it stays useful throughout development. Use CRC cards during maintenance, refactoring, or team onboarding to quickly re-establish context. They\u2019re your design memory.<\/p>\n<h3>How do I know if my UML model is correct?<\/h3>\n<p>Use the model validation tips: every method should have a CRC root, every association should serve a behavioral need, and no class should have more than two core responsibilities. Run a team walkthrough\u2014ask someone unfamiliar with the code to explain the model. If they struggle, you\u2019ve overcomplicated it.<\/p>\n<h3>Should I draw associations for every CRC collaboration?<\/h3>\n<p>No. Not all collaborations are stable relationships. Use associations only when two objects interact persistently over time. Use dependencies (dashed line with arrow) for temporary or event-driven links\u2014like \u201cOrder generates Invoice\u201d or \u201cCustomer notifies System\u201d.<\/p>\n<h3>What if the UML model contradicts the CRC card?<\/h3>\n<p>This signals a breakdown in communication. Revisit the original brainstorming session. Was the collaboration misunderstood? Was the responsibility misattributed? Use this as a learning moment to improve team clarity.<\/p>\n<h3>Is it okay to merge CRC cards into a single class in UML?<\/h3>\n<p>Only if the responsibilities are unified and logically cohesive. A class should not be a container for unrelated behaviors. If you\u2019re merging, ask: \u201cIs this one object fulfilling multiple roles?\u201d If yes, consider splitting it into separate classes with clear responsibilities.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>About 6 out of 10 teams I\u2019ve worked with overlook the behavioral nuance when converting CRC cards to UML, leading to models that are syntactically correct but semantically hollow. The issue isn\u2019t with the mechanics\u2014it\u2019s in how the collaborative intent of CRC gets flattened into static structure. CRC cards are about communication, responsibility, and interaction. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":945,"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-949","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 UML Mistakes to Avoid<\/title>\n<meta name=\"description\" content=\"Avoid common CRC UML mistakes in your class diagrams. Learn design pitfalls UML teams face and apply model validation tips to keep your software design accurate and maintainable.\" \/>\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-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CRC UML Mistakes to Avoid\" \/>\n<meta property=\"og:description\" content=\"Avoid common CRC UML mistakes in your class diagrams. Learn design pitfalls UML teams face and apply model validation tips to keep your software design accurate and maintainable.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/\" \/>\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\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/\",\"name\":\"CRC UML Mistakes to Avoid\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:32:37+00:00\",\"description\":\"Avoid common CRC UML mistakes in your class diagrams. Learn design pitfalls UML teams face and apply model validation tips to keep your software design accurate and maintainable.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"From CRC Cards to Class Diagrams\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Practical Application Scenarios\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Common Pitfalls When Converting CRC to UML\"}]},{\"@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 UML Mistakes to Avoid","description":"Avoid common CRC UML mistakes in your class diagrams. Learn design pitfalls UML teams face and apply model validation tips to keep your software design accurate and maintainable.","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-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/","og_locale":"fr_FR","og_type":"article","og_title":"CRC UML Mistakes to Avoid","og_description":"Avoid common CRC UML mistakes in your class diagrams. Learn design pitfalls UML teams face and apply model validation tips to keep your software design accurate and maintainable.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/","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\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/","name":"CRC UML Mistakes to Avoid","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:32:37+00:00","description":"Avoid common CRC UML mistakes in your class diagrams. Learn design pitfalls UML teams face and apply model validation tips to keep your software design accurate and maintainable.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/crc-uml-mistakes-to-avoid\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"From CRC Cards to Class Diagrams","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/"},{"@type":"ListItem","position":3,"name":"Practical Application Scenarios","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/"},{"@type":"ListItem","position":4,"name":"Common Pitfalls When Converting CRC to UML"}]},{"@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\/949","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\/949\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/945"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=949"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=949"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}