{"id":947,"date":"2026-02-25T10:32:37","date_gmt":"2026-02-25T10:32:37","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/"},"modified":"2026-02-25T10:32:37","modified_gmt":"2026-02-25T10:32:37","slug":"collaborative-uml-design-crc-to-uml-sessions","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/","title":{"rendered":"Collaborative Workshops: Team-Based CRC-to-UML Sessions"},"content":{"rendered":"<p>Great software architecture begins not with a diagram, but with a conversation.<\/p>\n<p>When I walk into a room where CRC cards are scattered across a table, and developers, analysts, and product owners are leaning in\u2014this is where real design happens. The real power of CRC modeling isn\u2019t in the cards themselves, but in the <strong>collaborative UML design<\/strong> they unlock.<\/p>\n<p>But turning that energy into a shared, formal UML model requires more than just skill\u2014it demands intentional facilitation. I\u2019ve led dozens of these sessions, from startup sprints to enterprise rewrites. The most successful ones weren\u2019t the ones with the cleanest diagrams. They were the ones where the team *felt* the design, discussed it, challenged it, and owned it.<\/p>\n<p>This chapter walks you through how to run a <strong>team modeling session<\/strong> that transforms CRC sessions into a robust, documented class diagram\u2014without losing the spark of discovery.<\/p>\n<h2>Why Team-Based Translation Matters<\/h2>\n<p>Translating CRC cards to UML isn\u2019t a solo task. It\u2019s a <em>conversation in motion<\/em>. The moment you hand off a pile of cards to a single person to draw a diagram, you risk losing context, intent, and buy-in.<\/p>\n<p>When you run a <strong>group UML building<\/strong> session, you\u2019re not just drawing lines and rectangles\u2014you\u2019re aligning mental models. You\u2019re making visible what was implicit.<\/p>\n<p>Think of it like a jazz ensemble: each member brings a part. The conductor doesn\u2019t dictate the score\u2014she ensures everyone stays in tune, listens to each other, and plays with purpose.<\/p>\n<h3>What Goes Wrong Without Team Alignment<\/h3>\n<ul>\n<li>Designers draw assumptions that developers don\u2019t understand.<\/li>\n<li>UML diagrams become \u201cartifacts\u201d rather than living models.<\/li>\n<li>Key responsibilities get lost in translation.<\/li>\n<li>Team members disengage by the end, feeling like they weren\u2019t part of the process.<\/li>\n<\/ul>\n<p>These aren\u2019t just inefficiencies\u2014they\u2019re design debt. But they\u2019re preventable.<\/p>\n<h2>Facilitation Framework: 5 Steps for a High-Trust CRC-to-UML Session<\/h2>\n<h3>Step 1: Set the Stage with Clear Intent<\/h3>\n<p>Start with a simple, shared goal: \u201cToday, we\u2019re turning our CRC brainstorm into a class diagram that the team can use to build the core module.\u201d Avoid vague promises like \u201cWe\u2019ll create a good design.\u201d Be specific.<\/p>\n<p>Set the tone: this isn\u2019t a drill. It\u2019s a design workshop. The goal is not perfection\u2014it\u2019s clarity and shared ownership.<\/p>\n<h3>Step 2: Assign Roles to Foster Engagement<\/h3>\n<p>Use a rotating role system to ensure equal participation:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Role<\/th>\n<th>Responsibilities<\/th>\n<\/tr>\n<tr>\n<td>Facilitator<\/td>\n<td>Keeps time, asks clarifying questions, ensures all voices are heard.<\/td>\n<\/tr>\n<tr>\n<td>Recorder<\/td>\n<td>Documents the evolving design\u2014on a whiteboard, digital canvas, or shared doc.<\/td>\n<\/tr>\n<tr>\n<td>Challenger<\/td>\n<td>Asks \u201cWhy?\u201d and \u201cCould we do better?\u201d to pressure-test assumptions.<\/td>\n<\/tr>\n<tr>\n<td>Timekeeper<\/td>\n<td>Tracks session segments to maintain momentum.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Rotate roles every 20\u201330 minutes. This prevents dominance and builds empathy across roles.<\/p>\n<h3>Step 3: Translate CRC to UML in Phases<\/h3>\n<p>Don\u2019t try to map everything at once. Break the session into stages:<\/p>\n<ol>\n<li><strong>Identify Core Classes<\/strong>: Pull out all class names from CRC cards. Cluster duplicates. Clarify ambiguous names.<\/li>\n<li><strong>Map Responsibilities to Attributes and Methods<\/strong>: For each class, list all responsibilities. Decide which are attributes and which are operations (methods).<\/li>\n<li><strong>Define Relationships<\/strong>: For each collaboration, determine if it\u2019s an association, aggregation, or dependency. Label with multiplicity.<\/li>\n<li><strong>Review for Completeness<\/strong>: Check for missing responsibilities, unconnected classes, or unclear roles.<\/li>\n<li><strong>Refine and Name<\/strong>: Use consistent naming, apply visibility (public\/private), and ensure each class has a clear purpose.<\/li>\n<\/ol>\n<p>Each phase should end with a quick check-in: \u201cWhat\u2019s one thing we\u2019ve learned?\u201d<\/p>\n<h3>Step 4: Use Real Tools, Not Just Paper<\/h3>\n<p>While physical cards are great for brainstorming, use tools like <strong>Visual Paradigm<\/strong>&nbsp;for the UML phase. These platforms allow real-time collaboration, versioning, and export to documentation.<\/p>\n<p>I once led a session where we used Visual Paradigm&#8217;s CRC tool. After 30 minutes of CRC discussion, we had a clean, shared diagram. Two days later, the dev team said they \u201cknew exactly how the module should work\u201d because they\u2019d helped build it.<\/p>\n<h3>Step 5: End with a Design Story<\/h3>\n<p>Conclude the session not with a diagram, but with a narrative. Ask: \u201cTell me, in 3 sentences, how this system works.\u201d<\/p>\n<p>One team described their payment gateway as: \u201cThe Order creates a PaymentRequest. The PaymentService validates it and sends it to the Processor. The Processor returns a success or failure, which the service logs and notifies the user.\u201d<\/p>\n<p>That story\u2014built from the team\u2019s own words\u2014was far more valuable than any UML diagram. It proved they understood, aligned, and owned the design.<\/p>\n<h2>Key CRC Workshop Techniques for Success<\/h2>\n<p>These aren\u2019t just tips\u2014they\u2019re time-tested <strong> CRC workshop techniques <\/strong> I\u2019ve used across startups and enterprises.<\/p>\n<ul>\n<li><strong>Time-boxed Brainstorming<\/strong>: Give 15 minutes for free-form CRC creation. No editing, no judging. Just ideas.<\/li>\n<li><strong>Dot Voting for Prioritization<\/strong>: After cards are up, each team member gets three sticky dots. Vote on the top 3 classes or collaborations to refine first.<\/li>\n<li><strong>\u201cWhy Is This a Responsibility?\u201d Drill<\/strong>: For each responsibility, assign someone to defend it. If they can\u2019t, it\u2019s not a real responsibility.<\/li>\n<li><strong>Rolestorming<\/strong>: Ask, \u201cHow would a user, a payment processor, or a system administrator interact with this class?\u201d This reveals missing constraints.<\/li>\n<\/ul>\n<p>These techniques keep the session dynamic, focused, and rooted in real usage scenarios.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with good structure, things can go sideways. Here are the most frequent issues\u2014and how to fix them.<\/p>\n<ul>\n<li><strong>Pitfall: Over-abstracting too early<\/strong><br \/>Don\u2019t jump to \u201cAbstractOrder\u201d or \u201cBaseProcessor\u201d in the first pass. Stick to concrete names. Refactor later.<\/li>\n<li><strong>Pitfall: Confusing collaboration with inheritance<\/strong><br \/>Just because a class \u201cuses\u201d another doesn\u2019t mean it inherits. Use association or dependency, not inheritance.<\/li>\n<li><strong>Pitfall: Ignoring multiplicity<\/strong><br \/>Always ask: \u201cCan a Customer have zero or many Orders?\u201d Get this wrong, and your data model fails under load.<\/li>\n<li><strong>Pitfall: One person dominates the drawing<\/strong><br \/>Use a shared digital board with multiple cursors. Or, assign one person to draw, but everyone must agree on each line.<\/li>\n<\/ul>\n<p>These aren\u2019t mistakes\u2014they\u2019re signals. They mean the team isn\u2019t yet aligned. Pause. Revisit the conversation.<\/p>\n<h2>Final Insights: Design Is a Team Sport<\/h2>\n<p>UML isn\u2019t a static output. It\u2019s a living agreement. The best class diagrams are the ones where the team says, \u201cYes, that\u2019s how it works.\u201d<\/p>\n<p>When you run a <strong>team modeling session<\/strong> with intention, you\u2019re not just creating a diagram\u2014you\u2019re building trust, clarity, and shared ownership. The <strong>group UML building<\/strong> process becomes the bridge between idea and implementation.<\/p>\n<p>Remember: the goal isn\u2019t to draw a perfect diagram. It\u2019s to make sure everyone at the table sees the same system\u2014and can explain it the same way.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How long should a team modeling session last?<\/h3>\n<p>30 to 60 minutes is ideal. For complex systems, break into multiple sessions. Shorter sessions keep energy high. Longer ones lead to fatigue and noise.<\/p>\n<h3>Can non-technical team members contribute to a CRC-to-UML session?<\/h3>\n<p>Absolutely. Product owners, UX designers, and even testers often identify key responsibilities or collaborations that developers miss. Their domain insight is invaluable.<\/p>\n<h3>What if the team disagrees on a class name or relationship?<\/h3>\n<p>That\u2019s not a problem\u2014it\u2019s a design opportunity. Use \u201cWhy?\u201d and \u201cWhat happens if\u2026?\u201d to explore differences. It\u2019s often the clash of perspectives that reveals the best solution.<\/p>\n<h3>Should we record the CRC-to-UML session?<\/h3>\n<p>Yes. Use audio or video for reference. But don\u2019t rely on it. The real value is in the shared process, not the recording. Use the session to capture decisions, not just output.<\/p>\n<h3>How do we handle incomplete CRC cards during translation?<\/h3>\n<p>Mark them as \u201cPending.\u201d Use a \u201cParking Lot\u201d column on the whiteboard. Return to them after core classes and relationships are defined.<\/p>\n<h3>Is it okay to use UML stereotypes or annotations in early team sessions?<\/h3>\n<p>Not initially. Keep it simple: class names, attributes, methods, associations. Add stereotypes (\u00abinterface\u00bb, \u00ababstract\u00bb) only after the structure is solid and the team agrees on the hierarchy.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Great software architecture begins not with a diagram,  [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":945,"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-947","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>Collaborative UML Design: Team-Based CRC-to-UML Sessions<\/title>\n<meta name=\"description\" content=\"Master collaborative UML design through team-based CRC-to-UML sessions. Learn proven CRC workshop techniques, group UML building strategies, and team modeling session best practices for cohesive, shared understanding in software design.\" \/>\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-case-study\/collaborative-uml-design-crc-to-uml-sessions\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Collaborative UML Design: Team-Based CRC-to-UML Sessions\" \/>\n<meta property=\"og:description\" content=\"Master collaborative UML design through team-based CRC-to-UML sessions. Learn proven CRC workshop techniques, group UML building strategies, and team modeling session best practices for cohesive, shared understanding in software design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/\" \/>\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-case-study\/collaborative-uml-design-crc-to-uml-sessions\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/\",\"name\":\"Collaborative UML Design: Team-Based CRC-to-UML Sessions\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:32:37+00:00\",\"description\":\"Master collaborative UML design through team-based CRC-to-UML sessions. Learn proven CRC workshop techniques, group UML building strategies, and team modeling session best practices for cohesive, shared understanding in software design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/#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\":\"Practical Application Scenarios\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Collaborative Workshops: Team-Based CRC-to-UML Sessions\"}]},{\"@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":"Collaborative UML Design: Team-Based CRC-to-UML Sessions","description":"Master collaborative UML design through team-based CRC-to-UML sessions. Learn proven CRC workshop techniques, group UML building strategies, and team modeling session best practices for cohesive, shared understanding in software design.","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-case-study\/collaborative-uml-design-crc-to-uml-sessions\/","og_locale":"zh_CN","og_type":"article","og_title":"Collaborative UML Design: Team-Based CRC-to-UML Sessions","og_description":"Master collaborative UML design through team-based CRC-to-UML sessions. Learn proven CRC workshop techniques, group UML building strategies, and team modeling session best practices for cohesive, shared understanding in software design.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/","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-case-study\/collaborative-uml-design-crc-to-uml-sessions\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/","name":"Collaborative UML Design: Team-Based CRC-to-UML Sessions","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:32:37+00:00","description":"Master collaborative UML design through team-based CRC-to-UML sessions. Learn proven CRC workshop techniques, group UML building strategies, and team modeling session best practices for cohesive, shared understanding in software design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/collaborative-uml-design-crc-to-uml-sessions\/#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":"Practical Application Scenarios","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-to-uml-case-study\/"},{"@type":"ListItem","position":4,"name":"Collaborative Workshops: Team-Based CRC-to-UML Sessions"}]},{"@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\/947","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\/947\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/945"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=947"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=947"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}