{"id":4388,"date":"2026-01-19T11:45:07","date_gmt":"2026-01-19T03:45:07","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/"},"modified":"2026-01-26T14:52:03","modified_gmt":"2026-01-26T06:52:03","slug":"module-4-the-heartbeat-the-7-behavioral-uml-diagrams","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/","title":{"rendered":"Module 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams"},"content":{"rendered":"<p dir=\"auto\">Welcome to <strong>Module 4<\/strong>, the dynamic core of our UML course\u2014where we bring the system to life by modeling <strong>how it behaves over time<\/strong>. If Module 3 gave us the <strong>skeleton<\/strong> (the static structure of classes, components, packages, and deployment), this module supplies the <strong>heartbeat<\/strong>: the workflows, interactions, state changes, sequences, and timing that make the system respond, react, and deliver value.<\/p>\n<p dir=\"auto\">Behavioral diagrams focus on <strong>dynamics<\/strong>\u2014the sequences of actions, message exchanges, control flows, event responses, and temporal constraints that realize use cases from <a href=\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/\">Module 2<\/a>. In an Agile, use-case-driven approach, these diagrams are essential for:<\/p>\n<ul dir=\"auto\">\n<li>Validating that the structure from Module 3 actually supports the required behavior<\/li>\n<li>Discovering missing operations, message flows, concurrency issues, and edge cases early<\/li>\n<li>Simulating and communicating runtime scenarios with stakeholders and developers<\/li>\n<li>Generating test cases (sequence diagrams \u2192 unit\/integration tests; activity diagrams \u2192 process tests)<\/li>\n<li>Supporting iterative refinement: sketch high-level flows first, add detail as implementation progresses<\/li>\n<li>Reducing risk by visualizing complex interactions before coding<\/li>\n<\/ul>\n<p dir=\"auto\">The <strong>7 behavioral UML diagrams<\/strong> capture different aspects of system dynamics:<\/p>\n<ol dir=\"auto\">\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/use-case-view\/\"><strong>Use Case Diagram<\/strong><\/a> (behavioral view of functional requirements from external actors) \u2014 Already covered in Module 2, but revisited here as the entry point for behavioral modeling.<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/activity-diagrams\/\"><strong>Activity Diagram<\/strong><\/a> Models workflows, business processes, algorithms, and concurrent flows using actions, control nodes (decision, merge, fork, join), object flows, swimlanes\/partitions, and pins.<\/li>\n<li><strong>State Machine Diagram<\/strong> (Statechart) Captures the lifecycle and event-driven reactive behavior of objects, subsystems, or the entire system (states, transitions, guards, entry\/exit\/do activities, composite states).<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/sequence-diagrams\/\"><strong>Sequence Diagram<\/strong><\/a> Shows time-ordered interactions: messages exchanged between participants (lifelines) over time\u2014most popular for detailing use case scenarios, API calls, and collaborations.<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/communication-diagrams\/\"><strong>Communication Diagram<\/strong><\/a> (formerly Collaboration) Emphasizes structural relationships between objects while still showing message sequence (numbered messages) \u2014 useful when topology matters more than strict timing.<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-overview-diagrams\/\"><strong>Interaction Overview Diagram<\/strong><\/a> High-level orchestration: combines activity diagram control flow with references to detailed interactions (sequence\/communication diagrams) \u2014 ideal for big-picture flows across subsystems.<\/li>\n<li><strong>Timing Diagram<\/strong> Focuses on precise timing, durations, state changes, and constraints over a linear timeline \u2014 critical for real-time, performance-sensitive, or embedded systems.<\/li>\n<\/ol>\n<h3 dir=\"auto\">Why Behavioral Diagrams Are the \u201cHeartbeat\u201d in Agile &amp; Use-Case-Driven Development<\/h3>\n<ul dir=\"auto\">\n<li><strong>Direct realization of use cases<\/strong> \u2014 Each major use case is elaborated with activity (workflow), sequence (detailed scenario), state machine (object lifecycle), etc.<\/li>\n<li><strong>Early validation &amp; simulation<\/strong> \u2014 Walk through diagrams with stakeholders to confirm \u201cthis is how it should work.\u201d<\/li>\n<li><strong>Risk attack on dynamics<\/strong> \u2014 Expose concurrency deadlocks, race conditions, timeout issues, invalid state transitions before implementation.<\/li>\n<li><strong>Incremental &amp; lightweight usage<\/strong> \u2014 In sprints: quick activity sketches for business flows, sequence diagrams for risky integrations, state machines for core domain objects.<\/li>\n<li><strong>Test foundation<\/strong> \u2014 Flows become acceptance criteria; message sequences drive mocks and integration tests.<\/li>\n<li><strong>Traceability &amp; evolution<\/strong> \u2014 Behavioral models link back to use cases and forward to code (e.g., Visual Paradigm code generation from sequence\/activity).<\/li>\n<\/ul>\n<h3 dir=\"auto\">Practical Examples Across Domains<\/h3>\n<ul dir=\"auto\">\n<li><strong>E-commerce Checkout<\/strong>\n<ul dir=\"auto\">\n<li>Activity Diagram: Swimlanes for Customer, Cart, Payment Gateway, Order Service \u2014 shows happy path + payment failure fork.<\/li>\n<li>Sequence Diagram: Customer \u2192 Cart \u2192 PaymentService \u2192 Gateway \u2192 Bank (detailed message flow with alt fragments for success\/fail).<\/li>\n<li>State Machine: Order states (Pending \u2192 Paid \u2192 Shipped \u2192 Delivered \u2192 Returned). Benefit: Spots missing refund path early.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Mobile Banking Transfer Funds<\/strong>\n<ul dir=\"auto\">\n<li>Sequence Diagram: User \u2192 App \u2192 AuthService \u2192 CoreBanking \u2192 NotificationService (with async callbacks).<\/li>\n<li>Timing Diagram: Strict 2-second timeout for transaction confirmation.<\/li>\n<li>Activity Diagram: Concurrent flows for balance check and fraud scoring. Outcome: Reveals potential race conditions in concurrent checks.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Ride-Sharing Ride Lifecycle<\/strong>\n<ul dir=\"auto\">\n<li>State Machine: Ride states (Requested \u2192 Accepted \u2192 En Route \u2192 Arrived \u2192 Completed \u2192 Cancelled).<\/li>\n<li>Interaction Overview: High-level flow referencing detailed sequences for \u201cAccept Ride\u201d and \u201cTrack Location.\u201d<\/li>\n<li>Communication Diagram: Driver \u2194 Passenger \u2194 Server with numbered messages showing structural links. Practical: Ensures smooth handoff between driver app and rider app.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Healthcare Appointment Booking<\/strong>\n<ul dir=\"auto\">\n<li>Activity Diagram: Patient \u2192 Reception \u2192 Doctor Calendar \u2192 Notification (with exception handling for conflicts).<\/li>\n<li>Sequence Diagram: Patient Portal \u2192 Appointment Service \u2192 EHR \u2192 Calendar API. Benefit: Validates end-to-end workflow compliance.<\/li>\n<\/ul>\n<\/li>\n<li><strong>IoT Smart Thermostat<\/strong>\n<ul dir=\"auto\">\n<li>State Machine: Thermostat (Idle \u2192 Heating \u2192 Cooling \u2192 Standby) with timed transitions.<\/li>\n<li>Timing Diagram: Temperature change response within 30 seconds. Practical: Critical for energy efficiency and user comfort guarantees.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Real-Time Trading Platform<\/strong>\n<ul dir=\"auto\">\n<li>Timing Diagram: Order submission to matching engine (&lt;5 ms latency requirement).<\/li>\n<li>Sequence Diagram: Trader \u2192 Gateway \u2192 MatchingEngine \u2192 MarketDataFeed. Outcome: Exposes performance bottlenecks before go-live.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">In <strong>Practical 4: Behavioral Simulation<\/strong>, you\u2019ll:<\/p>\n<ul dir=\"auto\">\n<li>Model business workflows with activity diagrams (swimlanes, decisions, parallelism).<\/li>\n<li>Validate use cases through detailed sequence and communication diagrams.<\/li>\n<li>Use Visual Paradigm to animate\/simulate flows, generate test scripts, and link behavioral elements back to use cases and structural models via the semantic backplane.<\/li>\n<\/ul>\n<p dir=\"auto\">By mastering these 7 behavioral diagrams, you\u2019ll capture the living, breathing dynamics of the system\u2014ensuring that the static skeleton from Module 3 actually moves, responds, and delivers on user goals in predictable, reliable ways. This dynamic modeling capability completes the foundation for architecture-centric, iterative implementation in Module 5.<\/p>\n<p dir=\"auto\">Ready to dive into the first behavioral diagram section &#8211; <a href=\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/activity-diagrams\/\">Activity Diagrams<\/a>?<\/p>\n","protected":false},"featured_media":0,"parent":4354,"menu_order":3,"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-4388","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>Module 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams - Visual Paradigm Guides Traditional Chinese<\/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\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Module 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams - Visual Paradigm Guides Traditional Chinese\" \/>\n<meta property=\"og:description\" content=\"Welcome to Module 4, the dynamic core of our UML course\u2014where we bring the system to life by modeling how it behaves over time. If Module 3 gave us the skeleton (the static structure of classes, components, packages, and deployment), this module supplies the heartbeat: the workflows, interactions, state changes, sequences, and timing that make the system respond, react, and deliver value. Behavioral diagrams focus on dynamics\u2014the sequences of actions, message exchanges, control flows, event responses, and temporal constraints that realize use cases from Module 2. In an Agile, use-case-driven approach, these diagrams are essential for: Validating that the structure from Module 3 actually supports the required behavior Discovering missing operations, message flows, concurrency issues, and edge cases early Simulating and communicating runtime scenarios with stakeholders and developers Generating test cases (sequence diagrams \u2192 unit\/integration tests; activity diagrams \u2192 process tests) SuModule 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Traditional Chinese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T06:52:03+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9810\u4f30\u95b1\u8b80\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 \u5206\u9418\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/\",\"name\":\"Module 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams - Visual Paradigm Guides Traditional Chinese\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-01-19T03:45:07+00:00\",\"dateModified\":\"2026-01-26T06:52:03+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/tw\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling\",\"item\":\"https:\/\/guides.visual-paradigm.com\/tw\/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\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/tw\/\",\"name\":\"Visual Paradigm Guides Traditional Chinese\",\"description\":\"Just another WordPress site\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/tw\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-TW\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Module 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams - Visual Paradigm Guides Traditional Chinese","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\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/","og_locale":"zh_TW","og_type":"article","og_title":"Module 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams - Visual Paradigm Guides Traditional Chinese","og_description":"Welcome to Module 4, the dynamic core of our UML course\u2014where we bring the system to life by modeling how it behaves over time. If Module 3 gave us the skeleton (the static structure of classes, components, packages, and deployment), this module supplies the heartbeat: the workflows, interactions, state changes, sequences, and timing that make the system respond, react, and deliver value. Behavioral diagrams focus on dynamics\u2014the sequences of actions, message exchanges, control flows, event responses, and temporal constraints that realize use cases from Module 2. In an Agile, use-case-driven approach, these diagrams are essential for: Validating that the structure from Module 3 actually supports the required behavior Discovering missing operations, message flows, concurrency issues, and edge cases early Simulating and communicating runtime scenarios with stakeholders and developers Generating test cases (sequence diagrams \u2192 unit\/integration tests; activity diagrams \u2192 process tests) SuModule 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams","og_url":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/","og_site_name":"Visual Paradigm Guides Traditional Chinese","article_modified_time":"2026-01-26T06:52:03+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"4 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/","url":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/","name":"Module 4: The Heartbeat \u2013 The 7 Behavioral UML Diagrams - Visual Paradigm Guides Traditional Chinese","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-01-19T03:45:07+00:00","dateModified":"2026-01-26T06:52:03+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/tw\/"},{"@type":"ListItem","position":2,"name":"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling","item":"https:\/\/guides.visual-paradigm.com\/tw\/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"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/tw\/#website","url":"https:\/\/guides.visual-paradigm.com\/tw\/","name":"Visual Paradigm Guides Traditional Chinese","description":"Just another WordPress site","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/tw\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-TW"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4388","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/comments?post=4388"}],"version-history":[{"count":4,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4388\/revisions"}],"predecessor-version":[{"id":5260,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4388\/revisions\/5260"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4354"}],"next":[{"title":"Module 5: Agile Architecture and Implementation Workflows","link":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/","href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4410"}],"prev":[{"title":"Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams","link":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4377"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=4388"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=4388"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}