{"id":774,"date":"2026-02-25T10:24:29","date_gmt":"2026-02-25T10:24:29","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/"},"modified":"2026-02-25T10:24:29","modified_gmt":"2026-02-25T10:24:29","slug":"avoiding-overloaded-misplaced-responsibilities","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/","title":{"rendered":"Avoiding Overloaded or Misplaced Responsibilities"},"content":{"rendered":"<p>When teams start drawing CRC cards, they often rush to assign too many responsibilities to a single class\u2014like making a single role handle everything from data storage to user notifications. That\u2019s a classic sign of a misaligned design. You\u2019ll spot it early: the card fills up with responsibilities that seem unrelated. The symptom isn\u2019t complexity\u2014it\u2019s confusion. This is where most beginners stumble.<\/p>\n<p>Over time, I\u2019ve seen how this leads to maintenance nightmares. A class that handles both user authentication and invoice processing becomes brittle. Change one, and the other breaks. The root issue? A failure in responsibility assignment.<\/p>\n<p>This chapter gives you a clear, step-by-step path to detect and correct overloaded or misplaced responsibilities. You\u2019ll learn to spot CRC pitfalls early, apply RDD heuristics, and refactor designs with confidence. You\u2019ll leave with practical tools to keep your models clean, cohesive, and easy to evolve.<\/p>\n<h2>Spotting the Symptoms: Signs of Overloaded Responsibilities<\/h2>\n<p>Not every class with many responsibilities is problematic. But certain patterns are red flags.<\/p>\n<ul>\n<li>One class manages both data input and output without clear separation.<\/li>\n<li>Responsibilities include tasks like &#8222;notify customer&#8220; and &#8222;calculate tax,&#8220; which belong to different domains.<\/li>\n<li>The class name sounds like a job title (e.g., &#8222;InvoiceProcessor&#8220;) rather than a role (e.g., &#8222;BillingService&#8220;).<\/li>\n<li>Team members argue about where a particular behavior &#8222;should&#8220; live.<\/li>\n<\/ul>\n<p>These aren\u2019t just bad habits. They\u2019re symptoms of a design flaw rooted in poor responsibility assignment.<\/p>\n<p>Ask yourself: <em>Could this class reasonably perform all these tasks without feeling stretched?<\/em> If not, it\u2019s overloaded.<\/p>\n<h3>Real-World Example: The Overloaded Customer Class<\/h3>\n<p>Consider a Customer class that handles:<\/p>\n<ul>\n<li>Storing personal data<\/li>\n<li>Validating email<\/li>\n<li>Processing orders<\/li>\n<li>Sending confirmation emails<\/li>\n<li>Calculating loyalty points<\/li>\n<\/ul>\n<p>It\u2019s not wrong to have a Customer class. But assigning all these duties to one class means it\u2019s doing too much. The responsibilities belong in different domains: data, validation, order processing, communication, and rewards.<\/p>\n<p>Splitting these into separate roles\u2014like <strong>CustomerDataRepository<\/strong>, <strong>OrderProcessor<\/strong>, <strong>EmailService<\/strong>, and <strong>LoyaltyCalculator<\/strong>\u2014improves clarity and cohesion.<\/p>\n<h2>Common CRC Modeling Mistakes to Avoid<\/h2>\n<p>Overloaded responsibilities aren\u2019t the only pitfall. Misplaced duties are just as dangerous.<\/p>\n<p>Here are the most frequent CRC modeling mistakes I\u2019ve seen in real projects:<\/p>\n<ol>\n<li><strong>Assigning behavior to the wrong class<\/strong> \u2014 For example, placing the logic for calculating total cost into the Product class instead of the Order class.<\/li>\n<li><strong>Using vague verbs<\/strong> \u2014 \u201cHandle,\u201d \u201cManage,\u201d or \u201cDo something\u201d don\u2019t define real responsibilities.<\/li>\n<li><strong>Mixing data and behavior<\/strong> \u2014 Creating classes that store state but also run logic without clear boundaries.<\/li>\n<li><strong>Ignoring collaboration patterns<\/strong> \u2014 Failing to model who calls whom or what data flows between roles.<\/li>\n<\/ol>\n<p>Each of these undermines the goal of responsibility-driven design: to build systems where responsibilities are <em>clearly assigned<\/em>, <em>cohesively grouped<\/em>, and <em>logically distributed<\/em>.<\/p>\n<h3>Checklist: Is Your Class Overloaded?<\/h3>\n<p>Before finalizing a CRC card, run this quick check:<\/p>\n<ul>\n<li>Can another class handle one of these responsibilities better?<\/li>\n<li>Are there responsibilities from different domains (e.g., security, communication, business logic) on the same card?<\/li>\n<li>Would renaming the class help clarify its role? (e.g., \u201cBillingService\u201d vs. \u201cCustomer\u201d)<\/li>\n<li>Do multiple responsibilities depend on the same data?<\/li>\n<\/ul>\n<p>If two or more are yes, the class is likely overloaded.<\/p>\n<h2>Design Error Correction: A Step-by-Step Refactor<\/h2>\n<p>When you detect an overloaded class, don\u2019t panic. Refactor with purpose.<\/p>\n<p>Here\u2019s my proven approach:<\/p>\n<ol>\n<li><strong>Identify cohesion clusters<\/strong> \u2014 Group responsibilities by theme: data access, validation, communication, computation.<\/li>\n<li><strong>Create new classes<\/strong> \u2014 For each cluster, define a new class with a clear name, like <code>EmailNotifier<\/code> or <code>PaymentValidator<\/code>.<\/li>\n<li><strong>Move responsibilities<\/strong> \u2014 Transfer each responsibility to the most appropriate class.<\/li>\n<li><strong>Re-evaluate collaborations<\/strong> \u2014 Update CRC cards to reflect new communication paths.<\/li>\n<li><strong>Verify<\/strong> \u2014 Ask: Does each class now do one thing well? Is the system easier to extend?<\/li>\n<\/ol>\n<p>This isn\u2019t about rewriting code\u2014it\u2019s about realigning intent.<\/p>\n<h3>Before and After: The Customer Class<\/h3>\n<p><strong>Before:<\/strong> The <code>Customer<\/code> class handles data, validation, order processing, email sending, and loyalty point tracking.<\/p>\n<p><strong>After:<\/strong> Split into:<\/p>\n<ul>\n<li><code>CustomerDataRepository<\/code> \u2013 Stores and retrieves customer data.<\/li>\n<li><code>OrderProcessor<\/code> \u2013 Handles order creation, status updates.<\/li>\n<li><code>EmailService<\/code> \u2013 Sends notifications.<\/li>\n<li><code>LoyaltyCalculator<\/code> \u2013 Manages point accrual and redemption.<\/li>\n<\/ul>\n<p>The result? Each class has one focus. The system is more modular and easier to test.<\/p>\n<h2>Applying RDD Heuristics for Better Responsibility Assignment<\/h2>\n<p>Responsibility-Driven Design (RDD) provides practical rules for assigning duties. Use these heuristics to avoid common CRC pitfalls.<\/p>\n<h3>1. \u201cTell, Don\u2019t Ask\u201d Rule<\/h3>\n<p>Instead of asking a class for data and then making decisions, tell it what to do.<\/p>\n<p><strong>Bad:<\/strong> <code>Customer.getOrders().sumTotal()<\/code> \u2014 the caller does the work.<\/p>\n<p><strong>Good:<\/strong> <code>Customer.calculateTotalOrders()<\/code> \u2014 the class owns the logic.<\/p>\n<p>Shift responsibility to the class that has the data and context.<\/p>\n<h3>2. Single Responsibility Principle (SRP) in Practice<\/h3>\n<p>Each class should have one reason to change. If a class handles both security and reporting, it has two reasons to change.<\/p>\n<p>Ask: <em>What would cause this class to be modified?<\/em> If more than one, it\u2019s overburdened.<\/p>\n<h3>3. \u201cKnows-Who\u201d vs. \u201cKnows-What\u201d<\/h3>\n<p>Classes should know what data they need to function, not how to get it.<\/p>\n<p>For example, <code>Order<\/code> knows it needs a <code>Customer<\/code> and a <code>Product<\/code>, but it shouldn\u2019t know how to retrieve the customer from a database.<\/p>\n<p>Delegate data access to a <code>CustomerRepository<\/code>.<\/p>\n<h2>Key Takeaways<\/h2>\n<p>Overloaded or misplaced responsibilities are among the most common CRC modeling mistakes. They lead to tangled designs, poor maintainability, and team friction.<\/p>\n<p>But you don\u2019t have to avoid them\u2014they can be caught early and corrected with simple techniques.<\/p>\n<p>Use the checklist and refactor steps above to detect and fix design flaws. Apply RDD heuristics to guide responsibility assignment. Keep classes focused on one domain, one task, one purpose.<\/p>\n<p>The goal isn\u2019t perfection. It\u2019s clarity. And clarity comes from conscious, deliberate design.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between an overloaded and misplaced responsibility?<\/h3>\n<p>An overloaded responsibility means one class holds too many duties, even if they\u2019re legitimate. A misplaced responsibility assigns a task to the wrong class\u2014e.g., having the Product class calculate its own total cost, when the Order should.<\/p>\n<h3>How do I decide which class should own a responsibility?<\/h3>\n<p>Ask: <em>Which class has the data needed to fulfill this task?<\/em> Also consider: <em>Will this responsibility change for the same reason as the class?<\/em> If yes, it likely belongs there.<\/p>\n<h3>Can a class have too few responsibilities?<\/h3>\n<p>Yes. While rare, underloaded classes\u2014those with no meaningful duties\u2014often indicate a missing role. For example, if a <code>Payment<\/code> class only stores data and has no actions, it may be a data holder. But the logic to process it should live elsewhere.<\/p>\n<h3>How often should I review CRC cards for design error correction?<\/h3>\n<p>Review after each major design change. Also revisit during team retrospectives or when bugs appear in areas with complex collaborations. Regular check-ins prevent small flaws from becoming systemic issues.<\/p>\n<h3>What if two classes seem equally responsible for a task?<\/h3>\n<p>Use the \u201cTell, Don\u2019t Ask\u201d rule. The class with the most context and data should own it. If both are equal, consider a third class to mediate the interaction\u2014like a <code>PaymentProcessor<\/code> that coordinates between <code>Customer<\/code> and <code>Bank<\/code>.<\/p>\n<h3>Are design errors in CRC cards always bad?<\/h3>\n<p>No\u2014early models are meant to evolve. A flawed assignment isn\u2019t a failure. It\u2019s feedback. The real risk is ignoring the feedback. CRC cards exist to surface these issues early, before they become code.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When teams start drawing CRC cards, they often rush to assign too many responsibilities to a single class\u2014like making a single role handle everything from data storage to user notifications. That\u2019s a classic sign of a misaligned design. You\u2019ll spot it early: the card fills up with responsibilities that seem unrelated. The symptom isn\u2019t complexity\u2014it\u2019s [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":772,"menu_order":1,"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-774","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>Avoiding Overloaded or Misplaced Responsibilities<\/title>\n<meta name=\"description\" content=\"Learn how to detect and fix common CRC modeling mistakes like overloaded or misplaced responsibilities. Master responsibility assignment and design error correction with real-world examples and RDD heuristics.\" \/>\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\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Avoiding Overloaded or Misplaced Responsibilities\" \/>\n<meta property=\"og:description\" content=\"Learn how to detect and fix common CRC modeling mistakes like overloaded or misplaced responsibilities. Master responsibility assignment and design error correction with real-world examples and RDD heuristics.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/\",\"name\":\"Avoiding Overloaded or Misplaced Responsibilities\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:24:29+00:00\",\"description\":\"Learn how to detect and fix common CRC modeling mistakes like overloaded or misplaced responsibilities. Master responsibility assignment and design error correction with real-world examples and RDD heuristics.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CRC Cards Explained: A Beginner\u2019s Modeling Guide\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Thinking in Responsibilities\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Avoiding Overloaded or Misplaced Responsibilities\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Avoiding Overloaded or Misplaced Responsibilities","description":"Learn how to detect and fix common CRC modeling mistakes like overloaded or misplaced responsibilities. Master responsibility assignment and design error correction with real-world examples and RDD heuristics.","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\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/","og_locale":"de_DE","og_type":"article","og_title":"Avoiding Overloaded or Misplaced Responsibilities","og_description":"Learn how to detect and fix common CRC modeling mistakes like overloaded or misplaced responsibilities. Master responsibility assignment and design error correction with real-world examples and RDD heuristics.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/","name":"Avoiding Overloaded or Misplaced Responsibilities","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:24:29+00:00","description":"Learn how to detect and fix common CRC modeling mistakes like overloaded or misplaced responsibilities. Master responsibility assignment and design error correction with real-world examples and RDD heuristics.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/avoiding-overloaded-misplaced-responsibilities\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"CRC Cards Explained: A Beginner\u2019s Modeling Guide","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/"},{"@type":"ListItem","position":3,"name":"Thinking in Responsibilities","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/crc-cards-explained\/thinking-in-responsibilities\/"},{"@type":"ListItem","position":4,"name":"Avoiding Overloaded or Misplaced Responsibilities"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/774","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/774\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/772"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=774"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=774"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}