{"id":4377,"date":"2026-01-19T11:43:43","date_gmt":"2026-01-19T03:43:43","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/"},"modified":"2026-01-26T11:38:16","modified_gmt":"2026-01-26T03:38:16","slug":"module-3-the-skeleton-the-7-structural-uml-diagrams","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-3-the-skeleton-the-7-structural-uml-diagrams\/","title":{"rendered":"Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams"},"content":{"rendered":"<p dir=\"auto\">Welcome to <strong>Module 3<\/strong>, where we build the <strong>static backbone<\/strong> of the system\u2014the unchanging (or slowly changing) structure that defines <strong>what<\/strong> the system is composed of, how its parts are organized, and how they relate to each other. While Module 2 focused on <strong>use cases<\/strong> (the &#8220;what the system does&#8221; from the user&#8217;s view), this module shifts to the <strong>structural view<\/strong>: the classes, components, packages, and physical deployment that realize those use cases.<\/p>\n<p dir=\"auto\">These <strong>7 structural diagrams<\/strong> in UML 2.5 provide the <strong>skeleton<\/strong>\u2014a clear, visual map of the system&#8217;s architecture at different abstraction levels (conceptual, logical, physical). In Agile contexts, structural models are kept <strong>lightweight and purposeful<\/strong>: created just-in-time to clarify domain concepts, organize large codebases, communicate architecture decisions, support code generation\/reverse engineering, and reduce risks around modularity, scalability, and maintainability.<\/p>\n<p dir=\"auto\">Key benefits in Agile &amp; use-case-driven development:<\/p>\n<ul dir=\"auto\">\n<li><strong>Traceability<\/strong> \u2014 Structural elements realize use cases (e.g., classes implement use case flows).<\/li>\n<li><strong>Risk mitigation<\/strong> \u2014 Early visualization of dependencies, coupling, and layering prevents architectural technical debt.<\/li>\n<li><strong>Incremental refinement<\/strong> \u2014 Start with high-level domain models in early iterations, add detail (e.g., deployment topology) as architecture solidifies.<\/li>\n<li><strong>Communication<\/strong> \u2014 Non-technical stakeholders grasp domain vocabulary via class diagrams; architects &amp; devs use component\/deployment for infrastructure planning.<\/li>\n<li><strong>Code alignment<\/strong> \u2014 Forward\/reverse\/round-trip engineering in Visual Paradigm keeps models and code in sync across sprints.<\/li>\n<\/ul>\n<h3 dir=\"auto\">The 7 Structural UML Diagrams \u2013 Quick Overview with Practical Purpose<\/h3>\n<ol dir=\"auto\">\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/\"><strong>Class Diagram<\/strong><\/a> Models the <strong>vocabulary<\/strong> of the system: classes, attributes, operations, interfaces, and relationships (inheritance, association, aggregation, etc.). Most common structural diagram.<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/\"><strong>Object Diagram<\/strong><\/a> Snapshot of <strong>instances<\/strong> (objects) and links at a specific moment\u2014useful for illustrating examples or debugging runtime states.<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/package-diagrams\/\"><strong>Package Diagram<\/strong><\/a> Organizes large models into hierarchical <strong>packages<\/strong> (namespaces) for modularity, configuration management, and dependency control.<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/component-diagrams\/\"><strong>Component Diagram<\/strong><\/a> Shows <strong>software components<\/strong> (modules, libraries, microservices), their interfaces, and dependencies\u2014ideal for modular\/monolithic vs. microservices design.<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/composite-structure-diagrams\/\"><strong>Composite Structure Diagram<\/strong><\/a> Details the <strong>internal structure<\/strong> of complex classes\/components via parts, ports, and connectors\u2014great for subsystems or collaborations.<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/deployment-diagrams\/\"><strong>Deployment Diagram<\/strong><\/a> Maps software artifacts to <strong>hardware nodes<\/strong> (servers, devices, cloud instances) and communication paths\u2014essential for deployment topology and scaling.<\/li>\n<li><a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/\"><strong>Profile Diagram<\/strong><\/a> Defines <strong>custom extensions<\/strong> (stereotypes, tagged values, constraints) to tailor UML for domains (e.g., Agile stereotypes like \u00abUserStory\u00bb, \u00abEpic\u00bb).<\/li>\n<\/ol>\n<h3 dir=\"auto\">Lots of Practical Examples Across Domains<\/h3>\n<ul dir=\"auto\">\n<li><strong>E-commerce Platform<\/strong>\n<ul dir=\"auto\">\n<li><strong>Class Diagram<\/strong>: Domain model with Order, OrderItem, Product, Customer, Payment, ShippingAddress. Relationships: Order aggregates OrderItems, Customer places Order.<\/li>\n<li><strong>Component Diagram<\/strong>: Microservices like CatalogService, CartService, PaymentService, OrderService\u2014showing provided\/required interfaces.<\/li>\n<li><strong>Deployment Diagram<\/strong>: Frontend (React app) on CDN nodes, backend services on Kubernetes pods, database on cloud RDS instance.<\/li>\n<li>Benefit: Early class diagram reveals missing DiscountRule class \u2192 added before implementation drift.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Mobile Banking App<\/strong>\n<ul dir=\"auto\">\n<li><strong>Class Diagram<\/strong>: Account, Transaction, UserProfile, AuthenticationToken. Generalization: SavingsAccount, CheckingAccount inherit from Account.<\/li>\n<li><strong>Composite Structure Diagram<\/strong>: Internal parts of &#8220;MobileApp&#8221; component (UI Layer, Business Logic, Data Access) with ports to backend APIs.<\/li>\n<li><strong>Package Diagram<\/strong>: Packages like &#8220;com.bank.auth&#8221;, &#8220;com.bank.transactions&#8221;, &#8220;com.bank.ui&#8221; to manage dependencies.<\/li>\n<li>Outcome: Prevents tight coupling between auth and transaction logic.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Healthcare Patient Management System<\/strong>\n<ul dir=\"auto\">\n<li><strong>Class Diagram<\/strong>: Patient, Appointment, Doctor, MedicalRecord, Prescription. Associations: Patient has-many Appointments, Doctor treats Patient.<\/li>\n<li><strong>Profile Diagram<\/strong>: Custom \u00abPHI\u00bb stereotype on sensitive classes with tagged value {confidentiality=high} for HIPAA compliance.<\/li>\n<li><strong>Deployment Diagram<\/strong>: On-prem hospital servers vs. cloud-hosted portal, showing secure connections (HTTPS, VPN).<\/li>\n<li>Practical: Models ensure privacy constraints are architectural, not bolted on later.<\/li>\n<\/ul>\n<\/li>\n<li><strong>IoT Smart Home System<\/strong>\n<ul dir=\"auto\">\n<li><strong>Composite Structure Diagram<\/strong>: &#8220;SmartHub&#8221; with parts (SensorArray, Controller, NetworkInterface) connected via ports.<\/li>\n<li><strong>Component Diagram<\/strong>: Reusable components like &#8220;TemperatureSensor&#8221;, &#8220;LightController&#8221; with required interfaces to cloud gateway.<\/li>\n<li><strong>Deployment Diagram<\/strong>: Edge devices (Raspberry Pi nodes) connected to cloud backend.<\/li>\n<li>Benefit: Visualizes hardware-software boundaries early.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Legacy Monolith to Microservices Migration<\/strong>\n<ul dir=\"auto\">\n<li><strong>Package Diagram<\/strong>: Before\/after views showing extraction of &#8220;Billing&#8221; package into separate service.<\/li>\n<li><strong>Component Diagram<\/strong>: Old monolithic JAR \u2192 new independent BillingService with REST API.<\/li>\n<li><strong>Class Diagram<\/strong>: Reverse-engineered from legacy code to understand domain before refactoring.<\/li>\n<li>Real impact: Guides safe incremental migration without big-bang rewrite.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Task Management SaaS<\/strong>\n<ul dir=\"auto\">\n<li><strong>Class Diagram<\/strong>: Board, List, Card, User, Label, Comment. Aggregation: Board contains Lists, List contains Cards.<\/li>\n<li><strong>Object Diagram<\/strong>: Example snapshot: &#8220;ProjectX Board&#8221; with specific &#8220;To Do List&#8221; containing &#8220;Implement Login&#8221; Card assigned to &#8220;John&#8221;.<\/li>\n<li><strong>Deployment Diagram<\/strong>: Multi-region cloud deployment for low-latency global access.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Agile Team in Visual Paradigm<\/strong>\n<ul dir=\"auto\">\n<li>Use <strong>Profile Diagram<\/strong> to create \u00abSprint\u00bb, \u00abBacklogItem\u00bb stereotypes.<\/li>\n<li><strong>Package Diagram<\/strong> organizes by release\/sprint: &#8220;Iteration-1-Core&#8221;, &#8220;Iteration-2-Enhancements&#8221;.<\/li>\n<li>Models evolve incrementally: start with conceptual class diagram from use cases, refine to design-level with operations.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">In this module&#8217;s <strong>Practical 3<\/strong>, you&#8217;ll:<\/p>\n<ul dir=\"auto\">\n<li>Build a <strong>logical database schema<\/strong> using class diagrams (entities, relationships, multiplicities).<\/li>\n<li>Map components to nodes in deployment views.<\/li>\n<li>Use Visual Paradigm&#8217;s semantic backplane to keep elements consistent across diagrams.<\/li>\n<\/ul>\n<p dir=\"auto\">By mastering these structural diagrams, you&#8217;ll create a solid, evolvable foundation that supports use-case realization, architectural decisions, and Agile iteration\u2014preparing for the <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\/\">dynamic heartbeat of behavioral diagrams<\/a> in Module 4.<\/p>\n","protected":false},"featured_media":0,"parent":4354,"menu_order":2,"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-4377","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 3: The Skeleton \u2013 The 7 Structural UML Diagrams - 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-3-the-skeleton-the-7-structural-uml-diagrams\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams - Visual Paradigm Guides Japanese\" \/>\n<meta property=\"og:description\" content=\"Welcome to Module 3, where we build the static backbone of the system\u2014the unchanging (or slowly changing) structure that defines what the system is composed of, how its parts are organized, and how they relate to each other. While Module 2 focused on use cases (the &#8220;what the system does&#8221; from the user&#8217;s view), this module shifts to the structural view: the classes, components, packages, and physical deployment that realize those use cases. These 7 structural diagrams in UML 2.5 provide the skeleton\u2014a clear, visual map of the system&#8217;s architecture at different abstraction levels (conceptual, logical, physical). In Agile contexts, structural models are kept lightweight and purposeful: created just-in-time to clarify domain concepts, organize large codebases, communicate architecture decisions, support code generation\/reverse engineering, and reduce risks around modularity, scalability, and maintainability. Key benefits in Agile &amp; use-case-driven development: Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams\" \/>\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-3-the-skeleton-the-7-structural-uml-diagrams\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Japanese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T03:38:16+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-3-the-skeleton-the-7-structural-uml-diagrams\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/\",\"name\":\"Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams - Visual Paradigm Guides Japanese\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-01-19T03:43:43+00:00\",\"dateModified\":\"2026-01-26T03:38:16+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/#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-3-the-skeleton-the-7-structural-uml-diagrams\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/#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 3: The Skeleton \u2013 The 7 Structural UML Diagrams\"}]},{\"@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":"Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams - 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-3-the-skeleton-the-7-structural-uml-diagrams\/","og_locale":"ja_JP","og_type":"article","og_title":"Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams - Visual Paradigm Guides Japanese","og_description":"Welcome to Module 3, where we build the static backbone of the system\u2014the unchanging (or slowly changing) structure that defines what the system is composed of, how its parts are organized, and how they relate to each other. While Module 2 focused on use cases (the &#8220;what the system does&#8221; from the user&#8217;s view), this module shifts to the structural view: the classes, components, packages, and physical deployment that realize those use cases. These 7 structural diagrams in UML 2.5 provide the skeleton\u2014a clear, visual map of the system&#8217;s architecture at different abstraction levels (conceptual, logical, physical). In Agile contexts, structural models are kept lightweight and purposeful: created just-in-time to clarify domain concepts, organize large codebases, communicate architecture decisions, support code generation\/reverse engineering, and reduce risks around modularity, scalability, and maintainability. Key benefits in Agile &amp; use-case-driven development: Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams","og_url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/","og_site_name":"Visual Paradigm Guides Japanese","article_modified_time":"2026-01-26T03:38:16+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-3-the-skeleton-the-7-structural-uml-diagrams\/","url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/","name":"Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams - Visual Paradigm Guides Japanese","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-01-19T03:43:43+00:00","dateModified":"2026-01-26T03:38:16+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/#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-3-the-skeleton-the-7-structural-uml-diagrams\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/#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 3: The Skeleton \u2013 The 7 Structural UML Diagrams"}]},{"@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\/4377","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=4377"}],"version-history":[{"count":4,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4377\/revisions"}],"predecessor-version":[{"id":5199,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4377\/revisions\/5199"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4354"}],"next":[{"title":"Module 4: The Heartbeat \u2013 The 7 Behavioral UML 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\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4388"}],"prev":[{"title":"Module 2: The Driver \u2013 Use Case Driven Requirements","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4366"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=4377"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=4377"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}