{"id":931,"date":"2026-02-25T10:32:30","date_gmt":"2026-02-25T10:32:30","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/"},"modified":"2026-02-25T10:32:30","modified_gmt":"2026-02-25T10:32:30","slug":"difference-crc-and-uml-conceptual-vs-structural-modeling","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/","title":{"rendered":"Understanding the Gap Between CRC Models and Class Diagrams"},"content":{"rendered":"<p>Most teams don\u2019t fail because they misunderstand the tools\u2014they fail because they confuse exploration with execution. CRC cards are not a draft of a class diagram. They\u2019re not a blueprint. They\u2019re a conversation starter. The real danger lies in treating CRC as if it were a finished model. The difference CRC and UML represents isn\u2019t just syntax\u2014it\u2019s mindset. One is for thinking. The other is for communicating with precision.<\/p>\n<p>I\u2019ve spent two decades guiding teams through this exact shift. The moment you start drawing lines and boxes before the team has settled on responsibilities, you\u2019ve already lost the benefit of collaborative design. CRC cards are about shared understanding. UML is about shared commitment.<\/p>\n<p>This chapter gives you a field-tested framework to recognize where you are in the design lifecycle, how to avoid rushing into formality, and what to look for before jumping from CRC models to class diagrams. You\u2019ll learn how to distinguish between conceptual and structural modeling, and how to time the transition so that your documentation reflects real insight\u2014not just notation.<\/p>\n<h2>Why CRC and UML Are Fundamentally Different<\/h2>\n<p>CRC cards were never meant to be precise. They were conceived as a lightweight way to explore roles, responsibilities, and collaborations in a team setting. Each card is a hypothesis, not a declaration.<\/p>\n<p>UML, by contrast, is a formal language. Its grammar governs visibility, multiplicity, inheritance, and interface contracts. Drawing a class diagram isn\u2019t just sketching\u2014it\u2019s defining a system\u2019s public face.<\/p>\n<p>The difference CRC and UML isn\u2019t about capability. It\u2019s about intent. One is exploratory. The other is declarative. One helps you discover. The other helps you document.<\/p>\n<h3>Conceptual vs Structural Modeling: A Critical Distinction<\/h3>\n<p>Let\u2019s be clear: conceptual modeling is not a lower-fidelity version of structural modeling. It\u2019s a different phase of design.<\/p>\n<p>When you\u2019re in early object design stages, you\u2019re not yet defining attributes or method signatures. You\u2019re asking: \u201cWho\u2019s responsible for managing the user session?\u201d \u201cWho handles the payment confirmation?\u201d<\/p>\n<p>That\u2019s conceptual modeling. It\u2019s about roles, behaviors, and dependencies\u2014what the system does, not how it\u2019s built.<\/p>\n<p>Structural modeling, on the other hand, is about precision. It\u2019s where you define the class name in PascalCase, declare attributes with types, specify method return types, and assign ownership to a package or namespace.<\/p>\n<p>Trying to assign a return type to a method before the team agrees on its purpose is like writing code before you\u2019ve decided what the app is for.<\/p>\n<h2>The Hidden Risks of Premature Formality<\/h2>\n<p>Jumping too early into UML from CRC isn\u2019t just inefficient\u2014it introduces bias. The moment you draw a class with attributes, you imply that those are fixed, agreed-upon properties. But in reality, they\u2019re still hypotheses.<\/p>\n<p>Here\u2019s a common trap: a developer draws a \u201cUser\u201d class with \u201cname,\u201d \u201cemail,\u201d and \u201cpassword\u201d before the team has even defined what \u201cmanaging a user\u201d means in context. That\u2019s not design\u2014it\u2019s assumption.<\/p>\n<p>I\u2019ve seen teams lose weeks of rework because they skipped CRC and went straight to UML. The result? A model that looks correct but doesn\u2019t reflect the actual domain logic.<\/p>\n<h3>When Premature Formality Backfires<\/h3>\n<ul>\n<li>Teams lock into a single interpretation of a role before consensus.<\/li>\n<li>Attributes are added without understanding their purpose or lifecycle.<\/li>\n<li>Collaborations become rigid associations before dependencies are understood.<\/li>\n<li>Feedback is stifled\u2014because the diagram &#8220;looks complete&#8221; even when it\u2019s wrong.<\/li>\n<\/ul>\n<p>These aren\u2019t minor errors. They\u2019re design traps. The fix? Let the CRC phase do its job.<\/p>\n<h2>How Teams Actually Transition from CRC to UML<\/h2>\n<p>There is no universal formula. But there is a rhythm. The transition isn\u2019t a one-time event\u2014it\u2019s a process of refinement.<\/p>\n<p>After several rounds of CRC card sessions, the team should be able to answer: \u201cWhat are the core entities? What do they do? Who interacts with whom?\u201d<\/p>\n<p>That\u2019s when you begin the shift to formal structure. But it\u2019s not about redrawing. It\u2019s about validating.<\/p>\n<h3>Key Signals That You&#8217;re Ready to Transition<\/h3>\n<ol>\n<li>All key domain entities have been identified and named consistently.<\/li>\n<li>Responsibilities are no longer vague\u2014phrases like \u201chandle payment\u201d have become \u201cvalidate payment details and initiate transfer.\u201d<\/li>\n<li>Collaborations are stable: the team agrees on who calls whom and why.<\/li>\n<li>Multiple team members can explain the model without referencing notes.<\/li>\n<\/ol>\n<p>If these aren\u2019t met, you\u2019re not ready. Don\u2019t rush the next step.<\/p>\n<h3>Mapping CRC to UML: A Practical Workflow<\/h3>\n<p>When the time is right, here\u2019s how to convert CRC into a UML class diagram with integrity:<\/p>\n<ol>\n<li><strong>Extract Classes<\/strong>: Each CRC card becomes a class. Use PascalCase. Avoid abbreviations unless they\u2019re universally understood.<\/li>\n<li><strong>Define Responsibilities as Methods and Attributes<\/strong>: \u201cCalculate total\u201d becomes a method. \u201cBilling address\u201d becomes an attribute.<\/li>\n<li><strong>Model Collaborations as Associations<\/strong>: If \u201cOrder\u201d sends a message to \u201cPaymentProcessor,\u201d draw a line with a label like \u201cuses\u201d or \u201cinitiates.\u201d<\/li>\n<li><strong>Assign Visibility and Types<\/strong>: Use <code>+<\/code> for public, <code>-<\/code> for private, <code>#<\/code> for protected. Add types like <code>String<\/code>, <code>DateTime<\/code>, <code>PaymentStatus<\/code>.<\/li>\n<li><strong>Refactor for Inheritance and Interfaces<\/strong>: Look for shared behavior. Can \u201cPayment\u201d and \u201cRefund\u201d share a common base? Do they implement a \u201cProcessable\u201d interface?<\/li>\n<\/ol>\n<p>This is not a mechanical conversion. It\u2019s a transformation of intent into structure.<\/p>\n<h2>Comparing CRC and UML: A Side-by-Side View<\/h2>\n<table>\n<thead>\n<tr>\n<th>Aspect<\/th>\n<th>CRC Cards<\/th>\n<th>UML Class Diagram<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Primary Use<\/strong><\/td>\n<td>Brainstorming, team alignment<\/td>\n<td>Documentation, communication with developers and testers<\/td>\n<\/tr>\n<tr>\n<td><strong>Modeling Focus<\/strong><\/td>\n<td>Responsibility, collaboration, behavior<\/td>\n<td>Structure, visibility, type safety<\/td>\n<\/tr>\n<tr>\n<td><strong>Formality Level<\/strong><\/td>\n<td>Low (free-form, sticky notes)<\/td>\n<td>High (strict syntax, notation)<\/td>\n<\/tr>\n<tr>\n<td><strong>Change Frequency<\/strong><\/td>\n<td>High (iterative, responsive)<\/td>\n<td>Limited (requires formal revision)<\/td>\n<\/tr>\n<tr>\n<td><strong>Team Role<\/strong><\/td>\n<td>Shared ownership<\/td>\n<td>Designer or analyst responsibility<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This table is not just a comparison\u2014it\u2019s a reminder. The difference CRC and UML isn\u2019t just technical. It\u2019s cultural. One fosters discovery. The other enforces agreement.<\/p>\n<h2>When to Hold Off on UML: A Checklist<\/h2>\n<p>Use this checklist before converting CRC to UML. If any item is missing, pause.<\/p>\n<ul>\n<li>Are all core domain entities named and agreed upon by the team?<\/li>\n<li>Are responsibilities phrased in active verbs (\u201ccalculate,\u201d \u201cvalidate,\u201d \u201cnotify\u201d)?<\/li>\n<li>Have collaborations been tested with real-life scenarios?<\/li>\n<li>Can a new team member explain the core model without diagrams?<\/li>\n<li>Are there no more than three unresolved ambiguities in collaboration paths?<\/li>\n<\/ul>\n<p>If any answer is \u201cno,\u201d the model isn\u2019t ready. Don\u2019t force it.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the main difference between CRC cards and UML?<\/h3>\n<p>CRC cards are for thinking\u2014exploring roles and responsibilities in a collaborative, informal setting. UML is for documenting\u2014expressing the precise structure of a system with standardized notation. One is exploratory; the other is declarative.<\/p>\n<h3>Can I use CRC cards and UML together in the same project?<\/h3>\n<p>Absolutely. CRC cards come first. They help discover the model. UML comes next, to formalize and communicate it. Teams that skip CRC often end up with over-engineered or misaligned diagrams.<\/p>\n<h3>Is it wrong to start with UML if I\u2019m more comfortable with it?<\/h3>\n<p>Not wrong\u2014but risky. UML without CRC can lead to premature design decisions. You might define a class with attributes before understanding its role. CRC ensures you\u2019re modeling the domain, not just the code.<\/p>\n<h3>When should I move from CRC to UML?<\/h3>\n<p>When the model is stable\u2014when roles are clear, responsibilities are verbs, collaborations are tested, and the team agrees on the core structure. That\u2019s when you transition, not before.<\/p>\n<h3>Are CRC cards still useful after creating the UML diagram?<\/h3>\n<p>Yes. CRC cards remain valuable during maintenance. When a new feature arises, revisiting CRC sessions helps revalidate responsibilities. They\u2019re not obsolete\u2014they\u2019re a living part of the design process.<\/p>\n<h3>Can I use tools like Visual Paradigm to convert CRC to UML automatically?<\/h3>\n<p>Some tools support digitizing CRC cards and generating UML. But automation can\u2019t replace understanding. The tool helps you structure your thinking\u2014but only you can ensure the model reflects real business intent.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most teams don\u2019t fail because they misunderstand the to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":930,"menu_order":0,"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-931","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>Difference CRC and UML: From Concept to Structure<\/title>\n<meta name=\"description\" content=\"Understand the difference between CRC cards and UML\u2014conceptual vs structural modeling. Learn when and how to transition from early object design stages to formal documentation with real-world guidance.\" \/>\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\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Difference CRC and UML: From Concept to Structure\" \/>\n<meta property=\"og:description\" content=\"Understand the difference between CRC cards and UML\u2014conceptual vs structural modeling. Learn when and how to transition from early object design stages to formal documentation with real-world guidance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/\",\"name\":\"Difference CRC and UML: From Concept to Structure\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:32:30+00:00\",\"description\":\"Understand the difference between CRC cards and UML\u2014conceptual vs structural modeling. Learn when and how to transition from early object design stages to formal documentation with real-world guidance.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"From CRC Cards to Class Diagrams\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Setting the Stage: Why CRC-to-UML Matters\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Understanding the Gap Between CRC Models and Class Diagrams\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Difference CRC and UML: From Concept to Structure","description":"Understand the difference between CRC cards and UML\u2014conceptual vs structural modeling. Learn when and how to transition from early object design stages to formal documentation with real-world guidance.","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\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/","og_locale":"zh_CN","og_type":"article","og_title":"Difference CRC and UML: From Concept to Structure","og_description":"Understand the difference between CRC cards and UML\u2014conceptual vs structural modeling. Learn when and how to transition from early object design stages to formal documentation with real-world guidance.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"7 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/","name":"Difference CRC and UML: From Concept to Structure","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:32:30+00:00","description":"Understand the difference between CRC cards and UML\u2014conceptual vs structural modeling. Learn when and how to transition from early object design stages to formal documentation with real-world guidance.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/difference-crc-and-uml-conceptual-vs-structural-modeling\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"From CRC Cards to Class Diagrams","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/"},{"@type":"ListItem","position":3,"name":"Setting the Stage: Why CRC-to-UML Matters","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-overview\/"},{"@type":"ListItem","position":4,"name":"Understanding the Gap Between CRC Models and Class Diagrams"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/931","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/931\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/930"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=931"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=931"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}