{"id":4405,"date":"2026-01-19T11:46:45","date_gmt":"2026-01-19T03:46:45","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/"},"modified":"2026-01-26T15:34:24","modified_gmt":"2026-01-26T07:34:24","slug":"interaction-use","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/","title":{"rendered":"Interaction Reuse"},"content":{"rendered":"<h2 dir=\"auto\"><strong>Referencing common interactions within others to support behavioral reuse<\/strong><\/h2>\n<p dir=\"auto\"><strong>Interaction Use<\/strong> (also called <strong>Interaction Occurrence<\/strong> or <strong>ref<\/strong>) is a powerful reuse mechanism in <a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/uml-2-5-overview\/\">UML 2.5<\/a> behavioral modeling. It allows you to reference an entire interaction\u2014typically a sequence diagram, communication diagram, or even another interaction overview diagram\u2014from within a different interaction diagram. This promotes <strong>modularization<\/strong>, <strong>reuse<\/strong>, <strong>consistency<\/strong>, and <strong>maintainability<\/strong> of behavioral specifications, much like calling a subroutine or method in code.<\/p>\n<p dir=\"auto\">Key characteristics:<\/p>\n<ul dir=\"auto\">\n<li>Represented by a <strong>reference frame<\/strong>: a rectangle with the keyword <strong>ref<\/strong> in the top-left corner, followed by the name of the referenced interaction (e.g., ref LoginSequence).<\/li>\n<li>Can appear inside sequence diagrams, communication diagrams, or interaction overview diagrams.<\/li>\n<li>Parameters can be passed (actual gates or arguments) to make the referenced interaction generic and reusable.<\/li>\n<li>The referenced interaction is executed in-line at that point in the calling diagram (substitution semantics).<\/li>\n<li>Gates (entry\/exit points) allow message passing in\/out of the ref box.<\/li>\n<li>Supports <strong>behavioral composition<\/strong> without duplication\u2014change the referenced interaction once, and all usages update.<\/li>\n<\/ul>\n<p dir=\"auto\">In Agile &amp; use-case-driven projects, Interaction Use is extremely valuable because:<\/p>\n<ul dir=\"auto\">\n<li>Common patterns (login, error handling, payment authorization, notification) appear in many scenarios \u2192 define once, reuse everywhere.<\/li>\n<li>Keeps detailed diagrams focused and short (extract repetitive parts).<\/li>\n<li>Improves traceability: one source of truth for shared behavior.<\/li>\n<li>Facilitates incremental refinement: stub a ref early, detail it later.<\/li>\n<li>Enables team collaboration: different developers own different reusable interactions.<\/li>\n<\/ul>\n<h3 dir=\"auto\">Practical Examples of Interaction Use in Real Projects<\/h3>\n<p dir=\"auto\">Here are numerous concrete examples showing how Interaction Use supports reuse across scenarios:<\/p>\n<ul dir=\"auto\">\n<li><strong>E-commerce \u2013 Reusable Payment Authorization<\/strong>\n<ul dir=\"auto\">\n<li>Reusable sequence diagram: <strong>ref PaymentAuthorization<\/strong><\/li>\n<li>Lifelines: :OrderService, :PaymentGateway, :BankAdapter<\/li>\n<li>Messages: authorize(amount, card), approved\/declined, token returned<\/li>\n<li>Gates: in amount:Money, card:CardDetails; out result:AuthorizationResult Usage in multiple diagrams:<\/li>\n<li>Checkout sequence: \u2026 \u2192 ref PaymentAuthorization(amount=total, card=customerCard) \u2192 [result.approved] confirmOrder()<\/li>\n<li>Subscription renewal sequence: \u2026 \u2192 ref PaymentAuthorization(amount=monthlyFee, card=savedCard) \u2192 \u2026<\/li>\n<li>One-click reorder sequence: \u2026 \u2192 ref PaymentAuthorization(amount=cartTotal, card=defaultCard) \u2192 \u2026 Practical benefit: Payment logic defined\/tested once; any change (e.g., adding 3D Secure) updates all payment points instantly.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Mobile Banking \u2013 Reusable Authentication with MFA<\/strong>\n<ul dir=\"auto\">\n<li>Reusable diagram: <strong>ref AuthenticateWithMFA<\/strong><\/li>\n<li>Participants: :MobileApp, :AuthService, :NotificationService<\/li>\n<li>Flow: requestOTP \u2192 sendOTP \u2192 enterOTP \u2192 validateOTP \u2192 return token Usage examples:<\/li>\n<li>Transfer funds sequence: \u2026 \u2192 ref AuthenticateWithMFA(user, device) \u2192 executeTransfer()<\/li>\n<li>View sensitive account details: \u2026 \u2192 ref AuthenticateWithMFA(user, device) \u2192 displayBalance()<\/li>\n<li>Change password: \u2026 \u2192 ref AuthenticateWithMFA(user, device) \u2192 updatePassword()<\/li>\n<li>Add new payee: \u2026 \u2192 ref AuthenticateWithMFA(user, device) \u2192 savePayee() Outcome: Single MFA flow enforces consistent security across all sensitive operations.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Ride-Sharing \u2013 Reusable Real-Time Location Tracking<\/strong>\n<ul dir=\"auto\">\n<li>Reusable sequence: <strong>ref UpdateLocationAndETA<\/strong><\/li>\n<li>Lifelines: :DriverApp, :MatchingService, :RiderApp<\/li>\n<li>Loop: every 5s: sendLocation \u2192 calculateETA \u2192 pushToRider Usage:<\/li>\n<li>Driver en route sequence: \u2026 \u2192 loop [ride active] ref UpdateLocationAndETA(driver, ride)<\/li>\n<li>Ride in progress monitoring: \u2026 \u2192 ref UpdateLocationAndETA(driver, ride)<\/li>\n<li>Post-ride safety check (share trip): \u2026 \u2192 ref UpdateLocationAndETA(driver, ride) Practical: Ensures consistent tracking behavior; easy to adjust polling interval globally.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Healthcare \u2013 Reusable Patient Identity Verification<\/strong>\n<ul dir=\"auto\">\n<li>Reusable diagram: <strong>ref VerifyPatientIdentity<\/strong><\/li>\n<li>Includes DOB check, insurance scan, photo ID validation, fraud flags Usage in:<\/li>\n<li>New patient registration sequence<\/li>\n<li>Telemedicine login sequence<\/li>\n<li>Prescription refill request sequence<\/li>\n<li>Appointment check-in kiosk sequence Benefit: HIPAA-compliant identity verification reused across portals and in-person flows.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Task Management SaaS \u2013 Reusable Notification Broadcast<\/strong>\n<ul dir=\"auto\">\n<li>Reusable communication diagram: <strong>ref NotifySubscribers<\/strong><\/li>\n<li>Participants: :TaskService, :NotificationService, :EmailAdapter, :PushAdapter<\/li>\n<li>Messages: collectSubscribers \u2192 sendEmail \u2192 sendPush \u2192 logDelivery Usage:<\/li>\n<li>Card moved sequence: \u2026 \u2192 ref NotifySubscribers(task, event=&#8221;moved&#8221;)<\/li>\n<li>Comment added sequence: \u2026 \u2192 ref NotifySubscribers(task, event=&#8221;comment&#8221;)<\/li>\n<li>Due date approaching sequence: \u2026 \u2192 ref NotifySubscribers(task, event=&#8221;dueSoon&#8221;) Practical: One notification pattern supports email, push, Slack, Teams\u2014change delivery channels once.<\/li>\n<\/ul>\n<\/li>\n<li><strong>IoT Device Management \u2013 Reusable Firmware Update Handshake<\/strong>\n<ul dir=\"auto\">\n<li>Reusable sequence: <strong>ref FirmwareUpdateHandshake<\/strong><\/li>\n<li>Device \u2194 Server: checkVersion \u2192 if newer: downloadURL \u2192 verifyChecksum \u2192 applyUpdate Usage in:<\/li>\n<li>Scheduled update campaign sequence<\/li>\n<li>Manual update trigger sequence<\/li>\n<li>Post-reboot verification sequence Benefit: Ensures safe, atomic update protocol reused across rollout strategies.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Real-Time Trading \u2013 Reusable Risk Check Before Execution<\/strong>\n<ul dir=\"auto\">\n<li>Reusable diagram: <strong>ref PerformPreTradeRiskCheck<\/strong><\/li>\n<li>Includes position limits, margin check, exposure limits, compliance flags Usage:<\/li>\n<li>Market order placement<\/li>\n<li>Limit order submission<\/li>\n<li>Algo-trading signal execution<\/li>\n<li>Bulk order batch processing Practical: Regulatory risk gate reused everywhere; audit trail consistent.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Library System \u2013 Reusable Loan Eligibility Check<\/strong>\n<ul dir=\"auto\">\n<li>Reusable sequence: <strong>ref CheckLoanEligibility<\/strong><\/li>\n<li>:LibrarySystem \u2192 :MemberRecord: checkOverdues, checkLimits, checkBlacklist Usage:<\/li>\n<li>Self-checkout kiosk<\/li>\n<li>Online reservation confirmation<\/li>\n<li>In-person desk borrowing Practical: One place to update borrowing rules (e.g., max items per member type).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">In Visual Paradigm:<\/p>\n<ul dir=\"auto\">\n<li>Create a standalone sequence\/communication diagram for the reusable part.<\/li>\n<li>In another diagram, drag <strong>Interaction Occurrence<\/strong> (ref) from toolbox.<\/li>\n<li>Name it to match the reusable interaction (auto-hyperlink in repository).<\/li>\n<li>Add parameters\/gates if needed (e.g., ref PaymentAuthorization(amount=$total)).<\/li>\n<li>Use in alt\/opt\/loop\/par fragments for conditional reuse.<\/li>\n<li>Semantic backplane ensures changes to the referenced diagram propagate to all usages.<\/li>\n<\/ul>\n<p dir=\"auto\">Interaction Use turns behavioral modeling into <strong>composable, maintainable modules<\/strong>\u2014eliminating duplication, enforcing consistency, and making complex systems easier to understand, evolve, and test in Agile environments.<\/p>\n<p dir=\"auto\">This completes the core elements of <a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/\">behavioral modeling in Module 4<\/a>. With reuse mechanisms like Interaction Use, you can now efficiently scale detailed interaction modeling without redundancy\u2014setting the stage for architecture-centric workflows and implementation in Module 5.<\/p>\n","protected":false},"featured_media":0,"parent":4388,"menu_order":6,"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-4405","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>Interaction Reuse - 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\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Interaction Reuse - Visual Paradigm Guides Japanese\" \/>\n<meta property=\"og:description\" content=\"Referencing common interactions within others to support behavioral reuse Interaction Use (also called Interaction Occurrence or ref) is a powerful reuse mechanism in UML 2.5 behavioral modeling. It allows you to reference an entire interaction\u2014typically a sequence diagram, communication diagram, or even another interaction overview diagram\u2014from within a different interaction diagram. This promotes modularization, reuse, consistency, and maintainability of behavioral specifications, much like calling a subroutine or method in code. Key characteristics: Represented by a reference frame: a rectangle with the keyword ref in the top-left corner, followed by the name of the referenced interaction (e.g., ref LoginSequence). Can appear inside sequence diagrams, communication diagrams, or interaction overview diagrams. Parameters can be passed (actual gates or arguments) to make the referenced interaction generic and reusable. The referenced interaction is executed in-line at that point in thInteraction Reuse\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Japanese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T07:34:24+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\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/\",\"name\":\"Interaction Reuse - Visual Paradigm Guides Japanese\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-01-19T03:46:45+00:00\",\"dateModified\":\"2026-01-26T07:34:24+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Module 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Interaction Reuse\"}]},{\"@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":"Interaction Reuse - 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\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/","og_locale":"ja_JP","og_type":"article","og_title":"Interaction Reuse - Visual Paradigm Guides Japanese","og_description":"Referencing common interactions within others to support behavioral reuse Interaction Use (also called Interaction Occurrence or ref) is a powerful reuse mechanism in UML 2.5 behavioral modeling. It allows you to reference an entire interaction\u2014typically a sequence diagram, communication diagram, or even another interaction overview diagram\u2014from within a different interaction diagram. This promotes modularization, reuse, consistency, and maintainability of behavioral specifications, much like calling a subroutine or method in code. Key characteristics: Represented by a reference frame: a rectangle with the keyword ref in the top-left corner, followed by the name of the referenced interaction (e.g., ref LoginSequence). Can appear inside sequence diagrams, communication diagrams, or interaction overview diagrams. Parameters can be passed (actual gates or arguments) to make the referenced interaction generic and reusable. The referenced interaction is executed in-line at that point in thInteraction Reuse","og_url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/","og_site_name":"Visual Paradigm Guides Japanese","article_modified_time":"2026-01-26T07:34:24+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\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/","url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/","name":"Interaction Reuse - Visual Paradigm Guides Japanese","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-01-19T03:46:45+00:00","dateModified":"2026-01-26T07:34:24+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-use\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling","item":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/"},{"@type":"ListItem","position":3,"name":"Module 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams","item":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/"},{"@type":"ListItem","position":4,"name":"Interaction Reuse"}]},{"@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\/4405","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=4405"}],"version-history":[{"count":7,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4405\/revisions"}],"predecessor-version":[{"id":5273,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4405\/revisions\/5273"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4388"}],"next":[{"title":"Practical 4: Behavioral Simulation","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/practical-4-behavioral-simulation\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4406"}],"prev":[{"title":"Timing Diagrams","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/timing-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4403"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=4405"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=4405"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}