{"id":4510,"date":"2026-01-19T14:16:03","date_gmt":"2026-01-19T06:16:03","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/"},"modified":"2026-01-19T14:54:48","modified_gmt":"2026-01-19T06:54:48","slug":"3-1-intelligent-relationship-identification","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/","title":{"rendered":"3.1 Intelligent Relationship Identification"},"content":{"rendered":"<h2 dir=\"auto\"><strong>Analyzing Diagrams for Shared Functionality (\u00abinclude\u00bb) and Optional Behavior (\u00abextend\u00bb)<\/strong><\/h2>\n<p dir=\"auto\">Once you have an initial Use Case Diagram with actors and use cases connected directly, the next level of maturity is to <strong>identify reuse and variability<\/strong> in the model. Two of the most important UML relationships in use case diagrams are:<\/p>\n<ul dir=\"auto\">\n<li><strong>\u00abinclude\u00bb<\/strong> \u2014 Used when one use case <strong>always<\/strong> incorporates the behavior of another use case as a mandatory sub-step. This relationship eliminates duplication by factoring out common, required functionality that multiple use cases share.<\/li>\n<li><strong>\u00abextend\u00bb<\/strong> \u2014 Used when one use case <strong>optionally<\/strong> adds behavior to another use case at specific, well-defined extension points. This is ideal for conditional, alternative, or exceptional paths that only occur under certain circumstances.<\/li>\n<\/ul>\n<p dir=\"auto\">Manually spotting these relationships can be time-consuming and error-prone, especially in larger systems. Visual Paradigm\u2019s <strong>AI Use Case Diagram Refinement Tool<\/strong> automates much of this analysis by:<\/p>\n<ul dir=\"auto\">\n<li>Scanning the names, actors, and context of your use cases<\/li>\n<li>Detecting semantic patterns of shared responsibility (for \u00abinclude\u00bb)<\/li>\n<li>Identifying conditional or variant behavior (for \u00abextend\u00bb)<\/li>\n<li>Proposing directed arrows with proper stereotypes (\u00abinclude\u00bb or \u00abextend\u00bb)<\/li>\n<li>Highlighting potential extension points on base use cases<\/li>\n<\/ul>\n<p dir=\"auto\">The tool presents suggestions in a review panel or directly on the diagram (with hover explanations), allowing you to accept, reject, or modify each one. Accepted relationships automatically update the diagram with clean, non-crossing arrows and maintain traceability.<\/p>\n<h3 dir=\"auto\">Practical Examples<\/h3>\n<p dir=\"auto\"><strong>Example 1: GourmetReserve \u2013 Mobile Dining Reservation App<\/strong><\/p>\n<p dir=\"auto\"><strong>AI Analysis &amp; Suggested Relationships<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li><strong>\u00abinclude\u00bb relationships<\/strong> (shared mandatory functionality):\n<ul dir=\"auto\">\n<li>Book a Table <strong>\u00abinclude\u00bb<\/strong> Authenticate User \u2192 Every booking requires the diner to be logged in or verified.<\/li>\n<li>Book a Table <strong>\u00abinclude\u00bb<\/strong> Process Payment \u2192 A deposit or full payment is mandatory to confirm the reservation.<\/li>\n<li>Pre-order Meal <strong>\u00abinclude\u00bb<\/strong> Process Payment \u2192 Pre-ordering also requires payment confirmation.<\/li>\n<li>Cancel Reservation <strong>\u00abinclude\u00bb<\/strong> Authenticate User \u2192 Only the account holder can cancel.<\/li>\n<\/ul>\n<\/li>\n<li><strong>\u00abextend\u00bb relationships<\/strong> (optional\/conditional behavior):\n<ul dir=\"auto\">\n<li>Apply Discount Coupon <strong>\u00abextend\u00bb<\/strong> Book a Table \u2192 Extension point: \u201cEnter promo code\u201d \u2014 only occurs if user provides a valid code.<\/li>\n<li>Handle Waitlist <strong>\u00abextend\u00bb<\/strong> Book a Table \u2192 Extension point: \u201cNo tables available\u201d \u2014 adds waitlist registration behavior conditionally.<\/li>\n<li>Send No-Show Charge Notification <strong>\u00abextend\u00bb<\/strong> Cancel Reservation \u2192 Extension point: \u201cCancellation within 2 hours of booking\u201d \u2014 applies late-cancellation fee logic only in specific cases.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Diagram impact<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li>\u201cAuthenticate User\u201d and \u201cProcess Payment\u201d become central hubs with multiple incoming \u00abinclude\u00bb arrows \u2192 dramatically reduces line clutter.<\/li>\n<li>\u201cBook a Table\u201d oval shows two extension points with dashed \u00abextend\u00bb arrows coming in \u2192 clearly communicates that discounts and waitlisting are optional enhancements.<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Example 2: SecureATM \u2013 Next-Generation ATM Network<\/strong><\/p>\n<p dir=\"auto\"><strong>AI-Identified Relationships<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li><strong>\u00abinclude\u00bb<\/strong> (mandatory shared steps):\n<ul dir=\"auto\">\n<li>Withdraw Cash <strong>\u00abinclude\u00bb<\/strong> Authenticate User<\/li>\n<li>Transfer Funds <strong>\u00abinclude\u00bb<\/strong> Authenticate User<\/li>\n<li>Deposit Check <strong>\u00abinclude\u00bb<\/strong> Authenticate User<\/li>\n<li>Withdraw Cash <strong>\u00abinclude\u00bb<\/strong> Validate Transaction Limits<\/li>\n<li>Transfer Funds <strong>\u00abinclude\u00bb<\/strong> Validate Transaction Limits<\/li>\n<\/ul>\n<\/li>\n<li><strong>\u00abextend\u00bb<\/strong> (conditional extras):\n<ul dir=\"auto\">\n<li>Request Biometric Verification <strong>\u00abextend\u00bb<\/strong> Withdraw Cash \u2192 Extension point: \u201cAmount &gt; $1,000\u201d \u2014 adds extra security step only for large withdrawals.<\/li>\n<li>Print Receipt <strong>\u00abextend\u00bb<\/strong> Withdraw Cash \u2192 Extension point: \u201cUser selects print\u201d \u2014 optional at the end of most transactions.<\/li>\n<li>Issue Temporary Card <strong>\u00abextend\u00bb<\/strong> Report Lost\/Stolen Card \u2192 Extension point: \u201cCustomer requests emergency access\u201d \u2014 conditional emergency feature.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Visual benefit<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li>Authentication and limit validation are factored out once \u2192 reused across many customer use cases.<\/li>\n<li>High-value transactions clearly show additional security layers via \u00abextend\u00bb arrows.<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Example 3: CorpLearn \u2013 Corporate E-Learning Platform<\/strong><\/p>\n<p dir=\"auto\"><strong>AI-Proposed Relationships<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li><strong>\u00abinclude\u00bb<\/strong>:\n<ul dir=\"auto\">\n<li>Enroll in Course <strong>\u00abinclude\u00bb<\/strong> Authenticate via SSO<\/li>\n<li>Take Final Assessment <strong>\u00abinclude\u00bb<\/strong> Record Learning Progress<\/li>\n<li>Complete Learning Module <strong>\u00abinclude\u00bb<\/strong> Record Learning Progress<\/li>\n<\/ul>\n<\/li>\n<li><strong>\u00abextend\u00bb<\/strong>:\n<ul dir=\"auto\">\n<li>Request Manager Approval <strong>\u00abextend\u00bb<\/strong> Enroll in Course \u2192 Extension point: \u201cCourse cost &gt; $500 or marked as manager-approved only\u201d<\/li>\n<li>Issue Certificate <strong>\u00abextend\u00bb<\/strong> Take Final Assessment \u2192 Extension point: \u201cScore \u2265 80%\u201d \u2014 certificate generation is conditional on passing.<\/li>\n<li>Send Completion Reminder <strong>\u00abextend\u00bb<\/strong> Complete Learning Module \u2192 Extension point: \u201cModule not finished within assigned deadline\u201d \u2014 nudges only when overdue.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Resulting clarity<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li>Repeated authentication and progress-tracking steps are modeled once.<\/li>\n<li>Managers and compliance teams immediately see that approvals and certificates are not automatic\u2014they depend on conditions.<\/li>\n<\/ul>\n<h3 dir=\"auto\">Quick Guidelines for Reviewing AI Suggestions<\/h3>\n<ul dir=\"auto\">\n<li><strong>\u00abinclude\u00bb<\/strong> \u2192 Ask: \u201cIs this behavior <strong>always<\/strong> required for the base use case to succeed?\u201d<\/li>\n<li><strong>\u00abextend\u00bb<\/strong> \u2192 Ask: \u201cDoes this behavior happen <strong>only sometimes<\/strong>, at a specific point, and add optional\/conditional value?\u201d<\/li>\n<li>Reject or adjust if the AI misinterprets domain rules (e.g., suggesting \u00abinclude\u00bb for something that\u2019s actually optional).<\/li>\n<li>After accepting, check that extension points are clearly named on the base use case oval.<\/li>\n<\/ul>\n<p dir=\"auto\">By the end of this intelligent relationship identification step, your Use Case Diagram evolves from a simple \u201cwho does what\u201d list into a structured model that explicitly expresses <strong>reuse<\/strong>, <strong>dependencies<\/strong>, and <strong>variability<\/strong>. This significantly reduces redundancy, improves maintainability, and prepares the ground for writing precise, non-repetitive flow-of-events descriptions in the next module. The AI handles pattern detection\u2014you bring the business judgment to make the relationships meaningful.<\/p>\n","protected":false},"featured_media":0,"parent":4509,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"_yoast_wpseo_title":"","_yoast_wpseo_metadesc":"","_eb_attr":"","neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":""},"doc_tag":[],"class_list":["post-4510","docs","type-docs","status-publish","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>3.1 Intelligent Relationship Identification - Visual Paradigm Guides Japanese<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"3.1 Intelligent Relationship Identification - Visual Paradigm Guides Japanese\" \/>\n<meta property=\"og:description\" content=\"Analyzing Diagrams for Shared Functionality (\u00abinclude\u00bb) and Optional Behavior (\u00abextend\u00bb) Once you have an initial Use Case Diagram with actors and use cases connected directly, the next level of maturity is to identify reuse and variability in the model. Two of the most important UML relationships in use case diagrams are: \u00abinclude\u00bb \u2014 Used when one use case always incorporates the behavior of another use case as a mandatory sub-step. This relationship eliminates duplication by factoring out common, required functionality that multiple use cases share. \u00abextend\u00bb \u2014 Used when one use case optionally adds behavior to another use case at specific, well-defined extension points. This is ideal for conditional, alternative, or exceptional paths that only occur under certain circumstances. Manually spotting these relationships can be time-consuming and error-prone, especially in larger systems. Visual Paradigm\u2019s AI Use Case Diagram Refinement Tool automates much of this analysis by: Scanning th3.1 Intelligent Relationship Identification\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Japanese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-19T06:54:48+00:00\" \/>\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=\"4\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/\",\"name\":\"3.1 Intelligent Relationship Identification - Visual Paradigm Guides Japanese\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-01-19T06:16:03+00:00\",\"dateModified\":\"2026-01-19T06:54:48+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Streamlining the Software Lifecycle: Integrating AI Use Case Modeling with Visual Paradigm\u2019s All-in-One Platform\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"3. Use Case Refinement and Relationships\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"3.1 Intelligent Relationship Identification\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Guides Japanese\",\"description\":\"Smart guides for an AI-driven world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"3.1 Intelligent Relationship Identification - Visual Paradigm Guides Japanese","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:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/","og_locale":"ja_JP","og_type":"article","og_title":"3.1 Intelligent Relationship Identification - Visual Paradigm Guides Japanese","og_description":"Analyzing Diagrams for Shared Functionality (\u00abinclude\u00bb) and Optional Behavior (\u00abextend\u00bb) Once you have an initial Use Case Diagram with actors and use cases connected directly, the next level of maturity is to identify reuse and variability in the model. Two of the most important UML relationships in use case diagrams are: \u00abinclude\u00bb \u2014 Used when one use case always incorporates the behavior of another use case as a mandatory sub-step. This relationship eliminates duplication by factoring out common, required functionality that multiple use cases share. \u00abextend\u00bb \u2014 Used when one use case optionally adds behavior to another use case at specific, well-defined extension points. This is ideal for conditional, alternative, or exceptional paths that only occur under certain circumstances. Manually spotting these relationships can be time-consuming and error-prone, especially in larger systems. Visual Paradigm\u2019s AI Use Case Diagram Refinement Tool automates much of this analysis by: Scanning th3.1 Intelligent Relationship Identification","og_url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/","og_site_name":"Visual Paradigm Guides Japanese","article_modified_time":"2026-01-19T06:54:48+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"4\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/","url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/","name":"3.1 Intelligent Relationship Identification - Visual Paradigm Guides Japanese","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-01-19T06:16:03+00:00","dateModified":"2026-01-19T06:54:48+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-1-intelligent-relationship-identification\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Streamlining the Software Lifecycle: Integrating AI Use Case Modeling with Visual Paradigm\u2019s All-in-One Platform","item":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/"},{"@type":"ListItem","position":3,"name":"3. Use Case Refinement and Relationships","item":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/"},{"@type":"ListItem","position":4,"name":"3.1 Intelligent Relationship Identification"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website","url":"https:\/\/guides.visual-paradigm.com\/ja\/","name":"Visual Paradigm Guides Japanese","description":"Smart guides for an AI-driven world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4510","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/comments?post=4510"}],"version-history":[{"count":2,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4510\/revisions"}],"predecessor-version":[{"id":4555,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4510\/revisions\/4555"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4509"}],"next":[{"title":"3.2 Automated Refinement","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/3-use-case-refinement-and-relationships\/3-2-automated-refinement\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4511"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=4510"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=4510"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}