{"id":763,"date":"2026-02-25T10:24:26","date_gmt":"2026-02-25T10:24:26","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/"},"modified":"2026-02-25T10:24:26","modified_gmt":"2026-02-25T10:24:26","slug":"crc-cards-responsibilities-collaborations","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/","title":{"rendered":"The Core Idea: Classes, Responsibilities, and Collaborations"},"content":{"rendered":"<p>About 8 out of 10 teams I\u2019ve worked with initially misplace responsibilities or overuse collaboration, not because they lack skill, but because they misunderstand how classes, responsibilities, and collaborations interact. It\u2019s not about writing code\u2014it\u2019s about thinking in roles. A class isn\u2019t just a container; it\u2019s a role player with duties and relationships.<\/p>\n<p>When you grasp CRC modeling correctly, you\u2019re no longer chasing syntax. You\u2019re building a shared understanding of how objects work together. This chapter breaks down the three pillars: class, responsibility, and collaboration. Each is essential\u2014and none can stand alone.<\/p>\n<h2>The Three Pillars of CRC Modeling<\/h2>\n<h3>Class: The Identity of an Object<\/h3>\n<p>A class is more than a name\u2014it\u2019s a role. It represents an entity in your system with a distinct identity and purpose.<\/p>\n<p>For example, in a library system, <code>Book<\/code> isn\u2019t just a data container. It\u2019s a role: &#171;holds information about a published work.&#187; The name defines the job, not the data.<\/p>\n<p>When defining a CRC class, ask: What real-world object or concept does this represent? Is it a noun? Can multiple instances exist? These questions clarify the class definition.<\/p>\n<h3>Responsibility: What the Class Must Do<\/h3>\n<p>Responsibilities are duties\u2014what the class *must* do to fulfill its role. They\u2019re not methods; they\u2019re actions the class is responsible for.<\/p>\n<p>Consider <code>Loan<\/code> in a library system. Its responsibilities might include:<\/p>\n<ul>\n<li>Track the check-out date<\/li>\n<li>Calculate due date<\/li>\n<li>Record late fees<\/li>\n<li>Notify when overdue<\/li>\n<\/ul>\n<p>Each responsibility is a verb phrase, concise and focused. Avoid vague terms like &#171;manage&#187; or &#171;handle.&#187; Instead, use precise, actionable language.<\/p>\n<p>Good responsibilities are measurable. If you can\u2019t test whether a class \u201chas\u201d a responsibility, it\u2019s too broad. A responsibility like \u201cupdate borrower status\u201d lacks clarity\u2014\u201ccheck if borrower is overdue\u201d is better.<\/p>\n<h3>Collaboration: Who Helps, and How<\/h3>\n<p>Collaboration defines who the class works with to fulfill its responsibilities. It\u2019s not about inheritance or inheritance\u2014this is about interaction.<\/p>\n<p>Take <code>Loan<\/code> again. To calculate due date, it may need to collaborate with <code>DueDateCalculator<\/code>. To notify the user, it may collaborate with <code>NotificationService<\/code>.<\/p>\n<p>Modeling collaborations means identifying the *other classes involved* in achieving a responsibility. Use simple names. No need for UML notation here\u2014just clear labels.<\/p>\n<p>Collaborations should be minimal and meaningful. If a class depends on five others to do one small task, you likely have a design smell. Re-evaluate responsibilities\u2014perhaps they\u2019re too fragmented.<\/p>\n<h2>How the Three Work Together<\/h2>\n<p>Let\u2019s walk through a real example: a <code>BankAccount<\/code> system.<\/p>\n<p><strong>Class:<\/strong> <code>BankAccount<\/code><\/p>\n<p><strong>Responsibilities:<\/strong><\/p>\n<ul>\n<li>Track current balance<\/li>\n<li>Accept deposits<\/li>\n<li>Process withdrawals<\/li>\n<li>Apply monthly interest<\/li>\n<\/ul>\n<p><strong>Collections:<\/strong><\/p>\n<ul>\n<li>Collaborates with <code>TransactionLogger<\/code> to record each deposit or withdrawal<\/li>\n<li>Collaborates with <code>InterestCalculator<\/code> to compute monthly interest<\/li>\n<li>Collaborates with <code>AccountManager<\/code> to validate account status<\/li>\n<\/ul>\n<p>Notice how no single class holds all the logic. The <code>BankAccount<\/code> focuses on managing its state and core behaviors. Other classes handle specialized tasks. This is separation of concerns through collaboration.<\/p>\n<p>The key insight: a class\u2019s responsibilities are defined by its role, and its collaborations are the tools it uses to fulfill them.<\/p>\n<h2>Best Practices for CRC Card Elements<\/h2>\n<p>Creating effective CRC cards isn\u2019t about perfection\u2014it\u2019s about clarity and alignment. Here are proven techniques:<\/p>\n<ol>\n<li><strong>Start with nouns, then verbs<\/strong>: Identify real-world objects first. Then ask: What do they do?<\/li>\n<li><strong>Use active verbs<\/strong>: \u201cCalculate\u201d, \u201cstore\u201d, \u201cnotify\u201d, \u201cvalidate\u201d\u2014not \u201chas\u201d, \u201cis\u201d, or \u201cmanages\u201d.<\/li>\n<li><strong>One responsibility per line<\/strong>: Avoid combining tasks. \u201cProcess and record transaction\u201d is two actions.<\/li>\n<li><strong>Keep collaborations simple<\/strong>: List only classes directly involved. Avoid abstract or generic names like \u201csystem\u201d or \u201cmanager\u201d.<\/li>\n<li><strong>Revisit and refactor<\/strong>: After the first pass, ask: Can any responsibilities be moved to better classes? Is collaboration necessary?<\/li>\n<\/ol>\n<p>These aren\u2019t rules\u2014they\u2019re habits that lead to better design.<\/p>\n<h2>Modeling Collaborations with Real Intent<\/h2>\n<p>I\u2019ve seen teams list collaborations like \u201cworks with database\u201d or \u201cuses the backend.\u201d That\u2019s not collaboration\u2014it\u2019s abstraction. Real collaboration is about *roles*, not technology.<\/p>\n<p>Ask: What role does the other class play? What does it offer? For example:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Collaboration<\/th>\n<th>Role<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td><code>NotificationService<\/code><\/td>\n<td>Sends email alerts<\/td>\n<td>Ensures the account doesn\u2019t act as a messaging engine<\/td>\n<\/tr>\n<tr>\n<td><code>InterestCalculator<\/code><\/td>\n<td>Applies interest rate logic<\/td>\n<td>Separates business logic from account state<\/td>\n<\/tr>\n<tr>\n<td><code>TransactionLogger<\/code><\/td>\n<td>Records financial events<\/td>\n<td>Enables audit trails without cluttering the account<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This table isn\u2019t just a list\u2014it\u2019s a design decision. Each collaboration supports a specific responsibility and reduces coupling.<\/p>\n<h2>Common Challenges and How to Fix Them<\/h2>\n<p>Even experienced teams stumble. Here are the most frequent issues and how to overcome them:<\/p>\n<ul>\n<li><strong>Overloaded responsibilities<\/strong>: A class like <code>User<\/code> listing \u201cmanage profile\u201d, \u201csend messages\u201d, \u201chandle login\u201d, \u201ctrack preferences\u201d is a red flag. Split into <code>ProfileManager<\/code>, <code>MessageService<\/code>, etc.<\/li>\n<li><strong>Missing or vague collaborations<\/strong>: If a class needs to \u201cnotify\u201d someone, name the actual collaborator: <code>NotificationService<\/code>, not \u201cthe system\u201d.<\/li>\n<li><strong>Too many collaborations<\/strong>: More than 3\u20134 collaborators per class often shows fragmentation. Reassess if responsibilities are properly grouped.<\/li>\n<li><strong>Collaboration without purpose<\/strong>: If a class collaborates but doesn\u2019t use the other\u2019s output, the collaboration is likely unnecessary.<\/li>\n<\/ul>\n<p>These aren\u2019t errors\u2014they\u2019re signals. They mean something in the design is misaligned.<\/p>\n<h2>From CRC Cards to Real Code<\/h2>\n<p>There\u2019s no magic leap from CRC cards to code. But there\u2019s a clear path.<\/p>\n<p>Each responsibility becomes a method. Each collaboration becomes a dependency or method call. For example:<\/p>\n<pre><code>\npublic class BankAccount {\n    private double balance;\n    private final InterestCalculator interestCalculator;\n    private final TransactionLogger transactionLogger;\n\n    public void deposit(double amount) {\n        balance += amount;\n        transactionLogger.log(\"Deposit\", amount);\n    }\n\n    public void applyMonthlyInterest() {\n        double interest = interestCalculator.calculate(balance);\n        balance += interest;\n    }\n}\n<\/code><\/pre>\n<p>The CRC card guided this design. The code implements it.<\/p>\n<p>Don\u2019t expect to write code from the card. Use the card to design the intent. Then write code that matches.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What makes a good responsibility on a CRC card?<\/h3>\n<p>A good responsibility is specific, measurable, and verb-driven. It describes an action the class is accountable for. Examples: \u201cCalculate due date\u201d, \u201cValidate email\u201d, \u201cSend notification\u201d. Avoid vague terms like \u201cmanage\u201d or \u201chandle\u201d.<\/p>\n<h3>How many collaborations should a class have?<\/h3>\n<p>Two to four is ideal. More than four suggests the class may be doing too much or responsibilities are poorly grouped. Re-evaluate responsibilities\u2014can any be moved to another class?<\/p>\n<h3>Can a class have no responsibilities?<\/h3>\n<p>No. Every class must have at least one responsibility. A class with no responsibilities has no reason to exist and likely represents a design gap.<\/p>\n<h3>Should I use CRC cards for every system?<\/h3>\n<p>Not always. They\u2019re most useful in early design, especially for new teams or complex domains. For simple systems, you may skip them\u2014but never skip thinking in responsibilities.<\/p>\n<h3>How do CRC cards help in team collaboration?<\/h3>\n<p>CRC cards create a shared language. They make roles and interactions visible to everyone\u2014developers, testers, product owners. This reduces miscommunication and aligns teams around design intent.<\/p>\n<h3>Do I need to use UML to benefit from CRC modeling?<\/h3>\n<p>No. CRC cards are a standalone modeling tool. You don\u2019t need UML to use them. But they\u2019re excellent for building UML class diagrams later\u2014because the relationships and responsibilities are already mapped.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>About 8 out of 10 teams I\u2019ve worked with initially misplace responsibilities or overuse collaboration, not because they lack skill, but because they misunderstand how classes, responsibilities, and collaborations interact. It\u2019s not about writing code\u2014it\u2019s about thinking in roles. A class isn\u2019t just a container; it\u2019s a role player with duties and relationships. When you [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":761,"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-763","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 Cards Responsibilities and Collaborations<\/title>\n<meta name=\"description\" content=\"Learn how CRC cards responsibilities and collaborations shape effective object-oriented design. Practical guide with real-world examples for beginners.\" \/>\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\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CRC Cards Responsibilities and Collaborations\" \/>\n<meta property=\"og:description\" content=\"Learn how CRC cards responsibilities and collaborations shape effective object-oriented design. Practical guide with real-world examples for beginners.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 \u043c\u0438\u043d\u0443\u0442\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/\",\"name\":\"CRC Cards Responsibilities and Collaborations\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\"},\"datePublished\":\"2026-02-25T10:24:26+00:00\",\"description\":\"Learn how CRC cards responsibilities and collaborations shape effective object-oriented design. Practical guide with real-world examples for beginners.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CRC Cards Explained: A Beginner\u2019s Modeling Guide\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Understanding the Foundations\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"The Core Idea: Classes, Responsibilities, and Collaborations\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ru-RU\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ru-RU\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"CRC Cards Responsibilities and Collaborations","description":"Learn how CRC cards responsibilities and collaborations shape effective object-oriented design. Practical guide with real-world examples for beginners.","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\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/","og_locale":"ru_RU","og_type":"article","og_title":"CRC Cards Responsibilities and Collaborations","og_description":"Learn how CRC cards responsibilities and collaborations shape effective object-oriented design. Practical guide with real-world examples for beginners.","og_url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/","og_site_name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","twitter_card":"summary_large_image","twitter_misc":{"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f":"6 \u043c\u0438\u043d\u0443\u0442"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/","name":"CRC Cards Responsibilities and Collaborations","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website"},"datePublished":"2026-02-25T10:24:26+00:00","description":"Learn how CRC cards responsibilities and collaborations shape effective object-oriented design. Practical guide with real-world examples for beginners.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/crc-cards-responsibilities-collaborations\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ru\/"},{"@type":"ListItem","position":2,"name":"CRC Cards Explained: A Beginner\u2019s Modeling Guide","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/"},{"@type":"ListItem","position":3,"name":"Understanding the Foundations","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/crc-cards-explained\/understanding-the-foundations\/"},{"@type":"ListItem","position":4,"name":"The Core Idea: Classes, Responsibilities, and Collaborations"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website","url":"https:\/\/skills.visual-paradigm.com\/ru\/","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ru-RU"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","url":"https:\/\/skills.visual-paradigm.com\/ru\/","logo":{"@type":"ImageObject","inLanguage":"ru-RU","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/763","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/763\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/761"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media?parent=763"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/doc_tag?post=763"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}