{"id":953,"date":"2026-02-25T10:32:39","date_gmt":"2026-02-25T10:32:39","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/"},"modified":"2026-02-25T10:32:39","modified_gmt":"2026-02-25T10:32:39","slug":"crc-to-sequence-diagram","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/","title":{"rendered":"Advanced Extensions: Using CRC Insights for Sequence or Use Case Diagrams"},"content":{"rendered":"

Many teams treat CRC cards as a one-off brainstorming phase\u2014fill them out, move to class diagrams, and forget them. But that\u2019s a missed opportunity. The real power of CRC models lies not just in defining static structure, but in revealing how objects interact over time.<\/p>\n

When you\u2019ve captured responsibilities and collaborations on CRC cards, you\u2019re not just naming classes\u2014you\u2019re outlining a narrative. That narrative is the seed for sequence diagrams, where behavior unfolds across time and objects.<\/p>\n

Don\u2019t jump to drawing interactions without first mapping what your CRC cards already tell you. The best sequence diagrams don\u2019t emerge from guesswork\u2014they emerge from the logic already present in your CRC insights.<\/p>\n

By the end of this chapter, you\u2019ll know how to extract behavioral intent from CRC modeling, translate it into sequence diagrams using real-world patterns, and leverage multi-view UML modeling to maintain consistency across your architecture.<\/p>\n

Why Sequence Diagrams Start with CRC Responsibility<\/h2>\n

Sequence diagrams are not standalone; they\u2019re derived. They show the flow of messages between objects over time, which means they need a foundation in object behavior.<\/p>\n

The key is to treat each responsibility on a CRC card not as a static method name, but as a potential message in a sequence.<\/p>\n

For example: a Book<\/strong> object with the responsibility \u201ccheck out to member\u201d isn\u2019t just a function\u2014it\u2019s an action that happens across a timeline involving a Member<\/strong> and a LibrarySystem<\/strong>.<\/p>\n

Here\u2019s how to extract that into a sequence diagram:<\/p>\n

    \n
  1. Identify the primary object initiating the interaction.<\/li>\n
  2. List all objects involved in fulfilling the responsibility.<\/li>\n
  3. Map each responsibility as a message in the correct order.<\/li>\n
  4. Use the CRC collaboration relationships to determine message direction.<\/li>\n<\/ol>\n

    This is where CRC extension use<\/strong> becomes powerful: your earlier brainstorming already defines the roles and timing of interaction.<\/p>\n

    From Responsibility to Message: A Practical Mapping<\/h3>\n

    Consider a CRC card for OnlineOrder<\/strong> with responsibility: \u201csubmit payment via credit card.\u201d<\/p>\n

    This isn\u2019t just a method\u2014it\u2019s a sequence of steps:<\/p>\n

      \n
    • OnlineOrder<\/strong> sends \u201cvalidateCard\u201d to CreditCard<\/strong>.<\/li>\n
    • CreditCard<\/strong> returns \u201cvalid\u201d or \u201cinvalid.\u201d<\/li>\n
    • If valid, OnlineOrder<\/strong> sends \u201ccharge\u201d to PaymentGateway<\/strong>.<\/li>\n
    • PaymentGateway<\/strong> confirms \u201ccharged\u201d or \u201cfailed.\u201d<\/li>\n
    • OnlineOrder<\/strong> updates status accordingly.<\/li>\n<\/ul>\n

      That sequence, derived directly from CRC responsibilities, is now the skeleton of your sequence diagram.<\/p>\n

      Don\u2019t invent behavior\u2014reveal it. The CRC model already contains the intent.<\/p>\n

      CRC to Use Case: Mapping Roles to Actors<\/h2>\n

      Use case diagrams often start with user stories or interviews. But when you have a solid CRC model, you can derive use cases with precision.<\/p>\n

      Each major responsibility on a CRC card can become a use case. The object performing the responsibility becomes the primary actor<\/strong>\u2014or the system<\/strong> if it\u2019s internal.<\/p>\n

      For example: CRC card for Administrator<\/strong> with responsibility \u201cdelete user account.\u201d<\/p>\n

      This directly maps to a use case: Delete User Account<\/strong>, with Administrator<\/strong> as the actor.<\/p>\n

      But here\u2019s where it gets deeper: CRC collaborations<\/strong> help define the flow of events<\/em>. If the Administrator<\/strong> must consult SystemLog<\/strong> before deletion, that\u2019s a pre-condition or an extension point.<\/p>\n

      Use case diagrams built from CRC insights are more consistent and behaviorally accurate than those built from vague user stories.<\/p>\n

      Mapping CRC to Use Case: A Step-by-Step Workflow<\/h3>\n
        \n
      • Step 1:<\/strong> Extract all responsibilities from CRC cards that involve external interaction.<\/li>\n
      • Step 2:<\/strong> Identify the object initiating the action\u2014it becomes the use case.<\/li>\n
      • Step 3:<\/strong> List collaborating objects as part of the use case\u2019s actors or supporting systems.<\/li>\n
      • Step 4:<\/strong> Use CRC collaboration relationships to define the boundaries of the use case.<\/li>\n
      • Step 5:<\/strong> Refine with scenarios: when does it fail? When is validation needed?<\/li>\n<\/ul>\n

        This process ensures your use cases are not just named after features, but grounded in real object behavior.<\/p>\n

        Building a Consistent Multi-View UML Model<\/h2>\n

        One of the most common missteps is treating UML diagrams as isolated artifacts. But the real value comes from alignment across views.<\/p>\n

        When you derive sequence diagrams from CRC responsibilities and use cases from CRC roles, you create a multi-view UML modeling<\/strong> system where each diagram reinforces the others.<\/p>\n

        Here\u2019s how the pieces connect:<\/p>\n\n\n\n\n\n\n
        UML View<\/th>\nSource in CRC Model<\/th>\nKey Insight<\/th>\n<\/tr>\n
        Class Diagram<\/td>\nClasses, Responsibilities, Collaborations<\/td>\nStructure: what objects exist and what they can do.<\/td>\n<\/tr>\n
        Use Case Diagram<\/td>\nResponsibilities involving external interaction<\/td>\nRole: who triggers what behavior.<\/td>\n<\/tr>\n
        Sequence Diagram<\/td>\nOrder of responsibilities and collaborations<\/td>\nBehavior: the flow of messages over time.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

        Each view should be traceable to the CRC model. If you can\u2019t point to a CRC card for a particular sequence message or use case, you\u2019ve gone off-script.<\/p>\n

        Use case diagrams become more than documentation\u2014they become a direct reflection of how your team thinks about responsibility.<\/p>\n

        Advanced CRC Extension Use: Beyond the Diagram<\/h2>\n

        Once you\u2019ve linked CRC insights to use case and sequence diagrams, you can extend the model further.<\/p>\n

        For example: if a sequence diagram shows repeated use of \u201cvalidate\u201d across multiple steps, that suggests a shared validation service. That insight can be returned to the CRC model to introduce a new object: Validator<\/strong>.<\/p>\n

        This creates a feedback loop: CRC extension use<\/strong> becomes a path for continuous refinement. You don\u2019t need to start over\u2014you build on what you\u2019ve already validated.<\/p>\n

        Another example: if a sequence shows inconsistent error handling, revisit the CRC cards for the involved objects. Ask: \u201cDid we miss an error response in the responsibility?\u201d<\/p>\n

        That kind of feedback is only possible when you maintain the link between CRC and higher-level diagrams.<\/p>\n

        Common Pitfalls and How to Avoid Them<\/h2>\n

        Even with a solid CRC foundation, teams still stumble when building sequence or use case diagrams.<\/p>\n

          \n
        • Pitfall 1:<\/strong> Creating sequence diagrams with objects not present in the CRC model. Solution:<\/em> Only include objects that were already in the CRC collaboration.<\/li>\n
        • Pitfall 2:<\/strong> Overloading sequence diagrams with irrelevant messages. Solution:<\/em> Focus only on messages that fulfill the responsibility\u2014omit fluff.<\/li>\n
        • Pitfall 3:<\/strong> Treating use case diagrams as high-level summaries instead of traceable artifacts. Solution:<\/em> Each use case must map back to at least one CRC card.<\/li>\n
        • Pitfall 4:<\/strong> Ignoring the temporal order in sequence diagrams. Solution:<\/em> Use the CRC responsibility sequence as your guide.<\/li>\n<\/ul>\n

          These aren\u2019t just technical rules\u2014they\u2019re guardrails for maintaining design integrity.<\/p>\n

          Frequently Asked Questions<\/h2>\n

          How do I know if my CRC model is ready for sequence diagrams?<\/h3>\n

          When you\u2019ve identified at least two objects and a clear flow of responsibilities, you\u2019re ready. The CRC card should describe a sequence of actions, not just isolated tasks.<\/p>\n

          Can I create sequence diagrams without a class diagram?<\/h3>\n

          Yes, but not effectively. The class diagram grounds your sequence diagram in real objects. Without it, you risk modeling with unverified or fictional objects.<\/p>\n

          How does CRC to use case mapping help in agile teams?<\/h3>\n

          It turns user stories into executable models. A story like \u201cAs a user, I want to cancel my order\u201d becomes a clear use case: \u201cCancel Order,\u201d triggered by the User<\/strong> object, supported by Order<\/strong> and PaymentProcessor<\/strong>\u2014all from CRC cards.<\/p>\n

          What if multiple CRC cards have the same responsibility?<\/h3>\n

          That\u2019s a sign of shared behavior. Consolidate into a single use case or sequence fragment. Use CRC to identify whether this is duplication or intentional parallelism.<\/p>\n

          Can CRC insights help with exception handling in sequence diagrams?<\/h3>\n

          Absolutely. When a CRC responsibility includes \u201chandle errors,\u201d map that as a conditional branch in the sequence. The collaboration with ErrorLog<\/strong> or NotificationService<\/strong> becomes part of the flow.<\/p>\n

          How often should I revisit CRC cards during design refinement?<\/h3>\n

          At every major design review. Use them as living documents. If a sequence diagram reveals a missing object, update the CRC card. This is CRC extension use<\/strong> at its finest\u2014evolution through insight.<\/p>\n","protected":false},"excerpt":{"rendered":"

          Many teams treat CRC cards as a one-off brainstorming phase\u2014fill them out, move to class diagrams, and forget […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":950,"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-953","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nCRC to Sequence Diagram: From Responsibility to Behavior<\/title>\n<meta name=\"description\" content=\"Learn how CRC cards inform sequence diagrams by translating responsibilities into dynamic behavior. Master multi-view UML modeling with proven techniques for robust 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\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CRC to Sequence Diagram: From Responsibility to Behavior\" \/>\n<meta property=\"og:description\" content=\"Learn how CRC cards inform sequence diagrams by translating responsibilities into dynamic behavior. Master multi-view UML modeling with proven techniques for robust software design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills\u65e5\u672c\u8a9e\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/\",\"name\":\"CRC to Sequence Diagram: From Responsibility to Behavior\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:32:39+00:00\",\"description\":\"Learn how CRC cards inform sequence diagrams by translating responsibilities into dynamic behavior. Master multi-view UML modeling with proven techniques for robust software design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"From CRC Cards to Class Diagrams\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Extending and Automating the Workflow\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Advanced Extensions: Using CRC Insights for Sequence or Use Case Diagrams\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"CRC to Sequence Diagram: From Responsibility to Behavior","description":"Learn how CRC cards inform sequence diagrams by translating responsibilities into dynamic behavior. Master multi-view UML modeling with proven techniques for robust 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\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/","og_locale":"ja_JP","og_type":"article","og_title":"CRC to Sequence Diagram: From Responsibility to Behavior","og_description":"Learn how CRC cards inform sequence diagrams by translating responsibilities into dynamic behavior. Master multi-view UML modeling with proven techniques for robust software design.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"6\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/","name":"CRC to Sequence Diagram: From Responsibility to Behavior","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:32:39+00:00","description":"Learn how CRC cards inform sequence diagrams by translating responsibilities into dynamic behavior. Master multi-view UML modeling with proven techniques for robust software design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/crc-to-sequence-diagram\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"From CRC Cards to Class Diagrams","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/"},{"@type":"ListItem","position":3,"name":"Extending and Automating the Workflow","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/"},{"@type":"ListItem","position":4,"name":"Advanced Extensions: Using CRC Insights for Sequence or Use Case Diagrams"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website","url":"https:\/\/skills.visual-paradigm.com\/ja\/","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","url":"https:\/\/skills.visual-paradigm.com\/ja\/","logo":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills\u65e5\u672c\u8a9e"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/953","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/953\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/950"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=953"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=953"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}