{"id":943,"date":"2026-02-25T10:32:34","date_gmt":"2026-02-25T10:32:34","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/"},"modified":"2026-02-25T10:32:34","modified_gmt":"2026-02-25T10:32:34","slug":"uml-design-review-checklist-consistency-completeness","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/","title":{"rendered":"Checking Design Consistency and Completeness"},"content":{"rendered":"

Many teams start with CRC cards, sketching class responsibilities and collaborations on paper. The moment they draw a UML class diagram, they assume the model is complete. But here\u2019s the truth: a diagram that looks correct often hides ambiguity, missing associations, or duplicated classes. The most misleading visual is one that follows syntax but ignores intent.<\/p>\n

I\u2019ve reviewed hundreds of UML class diagrams\u2014many derived from CRC cards\u2014where the structure is technically valid but fails in practice. The problem is not syntax. It\u2019s design intent<\/strong>. A class may have proper attributes and methods, but if it doesn\u2019t reflect real-world behavior or its relationships don\u2019t align with domain logic, it\u2019s a fragile model.<\/p>\n

This chapter gives you a field-tested UML design review checklist. It\u2019s built from years of mentoring teams through CRC to UML validation, teaching how to catch inconsistencies early. You\u2019ll learn how to verify class model completeness, detect hidden duplication, and align relationships with actual system behavior\u2014without overcomplicating the process.<\/p>\n

Why Consistency Checking UML Matters<\/h2>\n

UML isn\u2019t just about drawing boxes and lines. A well-formed diagram should reflect the real-world domain, not just follow grammar rules. Misaligned associations or ambiguous multiplicities can lead to runtime errors, poor maintainability, or misunderstood requirements.<\/p>\n

During CRC-to-UML validation, teams often assume that if a class is mentioned in multiple cards, it must be in the model. But that\u2019s not enough. The real test is: does the class interact in ways that match the domain? That\u2019s where consistency checking UML becomes essential.<\/p>\n

Consider this: a \u201cCustomer\u201d class might appear in both a \u201cBilling\u201d and \u201cOrder\u201d card. That suggests a role in two processes. But if the association isn\u2019t properly modeled with navigability and multiplicity, the system might incorrectly assume that every order must have a customer\u2014but what about anonymous orders? That\u2019s a design gap hiding in plain sight.<\/p>\n

UML Design Review Checklist: 8 Critical Checks<\/h2>\n

Use this checklist during design reviews, especially after converting from CRC cards to a formal class diagram. Go through each item systematically. If any check fails, pause and investigate.<\/p>\n

    \n
  1. Check for duplicate classes<\/strong>. Review all class names. Are there two classes with similar names (e.g., \u201cUser\u201d and \u201cCustomer\u201d) that might represent the same concept? Use domain logic to determine if they\u2019re truly distinct or if one should be refactored.<\/li>\n
  2. Verify all CRC responsibilities are mapped<\/strong>. Every responsibility from the CRC cards should appear as a method or attribute in the UML class. If a role like \u201ccalculate total\u201d is missing, reassess the model\u2019s completeness.<\/li>\n
  3. Validate associations and multiplicities<\/strong>. Ensure every collaboration from CRC cards is represented as an association. Check that multiplicity (e.g., 1..*, 0..1) reflects the actual business rule. Ask: “Is this cardinality realistic in the domain?”<\/li>\n
  4. Confirm navigation is intentional<\/strong>. If an association is navigable from Class A to Class B, ask: \u201cWould the system logic typically start from A to find B?\u201d If not, reconsider the direction or consider removing the navigability.<\/li>\n
  5. Review inheritance and abstraction<\/strong>. Are shared responsibilities abstracted into a superclass or interface? If two classes have nearly identical methods, ask: \u201cIs this a case for inheritance or an interface?\u201d Avoid deep hierarchies unless justified.<\/li>\n
  6. Ensure no orphaned or unused classes<\/strong>. Remove any class that doesn\u2019t participate in any association or responsibility. If a class exists but isn\u2019t used, it\u2019s likely a leftover from brainstorming or a misinterpretation.<\/li>\n
  7. Check attribute types and constraints<\/strong>. Attributes should be typed appropriately (e.g., not \u201cstring\u201d for a date). If a constraint exists in the domain (e.g., \u201cOrder total must be > 0\u201d), ensure it\u2019s modeled via constraints or validation rules.<\/li>\n
  8. Verify visibility and encapsulation<\/strong>. Public methods should be justified by external collaboration. Private methods should remain internal. If a method is public but rarely used, consider if it\u2019s a design smell.<\/li>\n<\/ol>\n

    Class Model Verification: A Step-by-Step Process<\/h2>\n

    To make this more actionable, here\u2019s a workflow I use in team design sessions:<\/p>\n

      \n
    1. Start with the original CRC cards<\/strong>. Re-read every class, responsibility, and collaboration.<\/li>\n
    2. Map each CRC responsibility to a UML method or attribute. Use a simple table to track mappings.<\/li>\n
    3. For each collaboration, draw the corresponding association. Ensure both ends are correct.<\/li>\n
    4. Ask: Does this relationship reflect a real dependency or interaction?<\/em> If not, reevaluate the link.<\/li>\n
    5. Run the model through the checklist above. Highlight any failures.<\/li>\n
    6. Hold a 15-minute review with a peer. Explain the model aloud. If you struggle, the model is likely incomplete.<\/li>\n<\/ol>\n

      Quick Reference: CRC-to-UML Mapping Table<\/h3>\n\n\n\n\n\n\n\n
      CRC Element<\/th>\nUML Equivalent<\/th>\nVerification Tip<\/th>\n<\/tr>\n
      Class name<\/td>\nClass in UML<\/td>\nCheck for naming consistency. Avoid \u201cManager\u201d and \u201cSupervisor\u201d unless they\u2019re distinct roles.<\/td>\n<\/tr>\n
      Responsibility (e.g., \u201ccalculate total\u201d)<\/td>\nOperation (method)<\/td>\nIf it returns a value, mark it as \u201creturn type.\u201d If it doesn\u2019t return, mark it as \u201cvoid.\u201d<\/td>\n<\/tr>\n
      Collaboration (e.g., \u201cuses Order\u201d)<\/td>\nAssociation (with multiplicity)<\/td>\nAsk: \u201cDoes A always need B? Is B optional? Use 1, 0..1, 1..*, etc.\u201d<\/td>\n<\/tr>\n
      Attribute (e.g., \u201chas name\u201d)<\/td>\nAttribute<\/td>\nEnsure type matches domain (e.g., \u201cString\u201d for name, \u201cDate\u201d for birthday).<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Common Pitfalls in CRC to UML Validation<\/h2>\n

      Even experienced teams make the same mistakes. Here are three I\u2019ve seen repeatedly:<\/p>\n

        \n
      • Overloading with associations<\/strong>. A single class showing 15 associations is a red flag. Ask: \u201cIs this class a hub, or is the model too granular?\u201d Consider introducing a new abstraction.<\/li>\n
      • Ignoring cardinality<\/strong>. A \u201cCustomer\u201d to \u201cOrder\u201d relationship might be 1..* at both ends. But in reality, a customer can have many orders, but an order belongs to exactly one customer. This is a violation of business logic.<\/li>\n
      • Forgetting about constraints<\/strong>. A \u201cPayment\u201d class might have a \u201cstatus\u201d attribute but no constraint on valid values (e.g., \u201cPending,\u201d \u201cCompleted,\u201d \u201cFailed\u201d). Add a constraint like {valid values: Pending, Completed, Failed}.<\/li>\n<\/ul>\n

        Practical Tips for Teams<\/h2>\n

        When working in groups, assign each member one CRC card to map. Then, compare outputs. Discrepancies reveal where the team\u2019s understanding diverges. Use these differences to open discussion, not to blame.<\/p>\n

        Always keep the domain model<\/strong> in mind. Ask: \u201cWould a business expert recognize this as a real process?\u201d If not, simplify or reframe.<\/p>\n

        Use diagrams not as final artifacts, but as collaboration tools. A model is only complete when it\u2019s not just correct\u2014but understandable.<\/p>\n

        Frequently Asked Questions<\/h2>\n

        How do I know if my class model is complete?<\/h3>\n

        It\u2019s complete when every CRC responsibility and collaboration maps to a method, attribute, or association. No card should be left unaccounted for. Run the checklist, and if all items pass, the model is likely complete.<\/p>\n

        What should I do if two classes have the same name but different responsibilities?<\/h3>\n

        That\u2019s a sign of potential misclassification. Re-evaluate the domain. If they\u2019re not distinct roles, consolidate. If they are, add context in the name (e.g., \u201cCustomer\u201d vs. \u201cBillingCustomer\u201d) or use a different domain concept.<\/p>\n

        Is it okay to have a class with no associations?<\/h3>\n

        Only if it\u2019s a data carrier (e.g., \u201cAddress\u201d) with no behavior. If a class has responsibility but no associations, it\u2019s likely incomplete. Revisit the CRC card to see who it collaborates with.<\/p>\n

        How do I handle ambiguous associations?<\/h3>\n

        Ask: \u201cDoes this association reflect a real dependency, or is it speculative?\u201d If you can\u2019t explain the interaction in plain language, the association may not be needed. Remove it and re-evaluate.<\/p>\n

        Should I refactor my model after a design review?<\/h3>\n

        Absolutely. A review isn\u2019t about perfection\u2014it\u2019s about improvement. Use the checklist to identify weak spots. Refactor not for aesthetics, but for clarity and correctness. This is part of the class model verification<\/strong> cycle.<\/p>\n

        What if my team disagrees on a relationship or multiplicity?<\/h3>\n

        Use the CRC cards as a reference. Re-read the collaboration. Ask: \u201cWho depends on whom?\u201d If consensus still fails, simulate a scenario (e.g., \u201cWhat happens if a customer is deleted?\u201d) and let the behavior guide the model.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Many teams start with CRC cards, sketching class responsibilities and collaborations on paper. The moment they draw a UML class diagram, they assume the model is complete. But here\u2019s the truth: a diagram that looks correct often hides ambiguity, missing associations, or duplicated classes. The most misleading visual is one that follows syntax but ignores […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":940,"menu_order":2,"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-943","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nUML Design Review Checklist: Ensure Consistency and Completeness<\/title>\n<meta name=\"description\" content=\"Use this UML design review checklist to validate class model verification, detect missing relationships, and ensure consistency checking UML with proven CRC to UML validation techniques.\" \/>\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\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"UML Design Review Checklist: Ensure Consistency and Completeness\" \/>\n<meta property=\"og:description\" content=\"Use this UML design review checklist to validate class model verification, detect missing relationships, and ensure consistency checking UML with proven CRC to UML validation techniques.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/\",\"name\":\"UML Design Review Checklist: Ensure Consistency and Completeness\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:32:34+00:00\",\"description\":\"Use this UML design review checklist to validate class model verification, detect missing relationships, and ensure consistency checking UML with proven CRC to UML validation techniques.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"From CRC Cards to Class Diagrams\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Refining and Validating the Design\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Checking Design Consistency and Completeness\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"UML Design Review Checklist: Ensure Consistency and Completeness","description":"Use this UML design review checklist to validate class model verification, detect missing relationships, and ensure consistency checking UML with proven CRC to UML validation techniques.","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\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/","og_locale":"id_ID","og_type":"article","og_title":"UML Design Review Checklist: Ensure Consistency and Completeness","og_description":"Use this UML design review checklist to validate class model verification, detect missing relationships, and ensure consistency checking UML with proven CRC to UML validation techniques.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"7 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/","name":"UML Design Review Checklist: Ensure Consistency and Completeness","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:32:34+00:00","description":"Use this UML design review checklist to validate class model verification, detect missing relationships, and ensure consistency checking UML with proven CRC to UML validation techniques.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/uml-design-review-checklist-consistency-completeness\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"From CRC Cards to Class Diagrams","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/"},{"@type":"ListItem","position":3,"name":"Refining and Validating the Design","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-to-class-diagrams\/refining-and-validating-the-design\/"},{"@type":"ListItem","position":4,"name":"Checking Design Consistency and Completeness"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/943","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/943\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/940"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=943"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=943"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}