{"id":4380,"date":"2026-01-19T11:44:16","date_gmt":"2026-01-19T03:44:16","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\/component-diagrams\/"},"modified":"2026-01-26T14:47:46","modified_gmt":"2026-01-26T06:47:46","slug":"component-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\/component-diagrams\/","title":{"rendered":"Component Diagrams"},"content":{"rendered":"<h2 dir=\"auto\"><strong>Visualizing the physical implementation and logical organization of software units like executables, libraries, microservices, and modules<\/strong><\/h2>\n<figure id=\"attachment_5133\" aria-describedby=\"caption-attachment-5133\" style=\"width: 1002px\" class=\"wp-caption alignnone\"><img fetchpriority=\"high\" decoding=\"async\" class=\"size-full wp-image-5133\" src=\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png\" alt=\"Web store UML component diagram\" width=\"1002\" height=\"475\" srcset=\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png 1002w, https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram-300x142.png 300w, https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram-768x364.png 768w, https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram-150x71.png 150w\" sizes=\"(max-width: 1002px) 100vw, 1002px\" \/><figcaption id=\"caption-attachment-5133\" class=\"wp-caption-text\">Web store UML component diagram<\/figcaption><\/figure>\n<p dir=\"auto\"><strong>Component diagrams<\/strong> in <a href=\"https:\/\/guides.visual-paradigm.com\/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> focus on the <strong>modular, replaceable building blocks<\/strong> of a software system\u2014showing how larger pieces of implementation (executables, libraries, frameworks, services, subsystems) are structured, connected, and depend on each other. They bridge the logical design (classes, packages) and the physical deployment, emphasizing <strong>modularity<\/strong>, <strong>interfaces<\/strong>, <strong>provided\/required services<\/strong>, and <strong>reusability<\/strong>.<\/p>\n<p dir=\"auto\">Key elements:<\/p>\n<ul dir=\"auto\">\n<li><strong>Component<\/strong> \u2014 A rectangle with a small icon in the upper-right corner (two small rectangles), representing a modular unit (e.g., JAR, DLL, microservice, executable, database schema, web service).<\/li>\n<li><strong>Provided Interface<\/strong> \u2014 Lollipop notation (circle on a line) \u2014 what the component offers to others (API\/contract).<\/li>\n<li><strong>Required Interface<\/strong> \u2014 Socket notation (cup\/half-circle) \u2014 what the component needs from others to function.<\/li>\n<li><strong>Dependency<\/strong> \u2014 Dashed arrow with open head \u2014 one component depends on another (usually via required interface).<\/li>\n<li><strong>Assembly Connector<\/strong> \u2014 Line connecting provided and required interfaces \u2014 explicit wiring between components.<\/li>\n<li><strong>Delegation Connector<\/strong> \u2014 Shows internal realization (a component delegates to sub-components).<\/li>\n<\/ul>\n<p dir=\"auto\">In Agile &amp; use-case-driven projects, component diagrams are used to:<\/p>\n<ul dir=\"auto\">\n<li>Visualize modular architecture (monolith vs. microservices vs. modular monolith)<\/li>\n<li>Define clear service boundaries and contracts early<\/li>\n<li>Support incremental development by identifying independently deployable\/releaseable units<\/li>\n<li>Guide refactoring, extract services, or migrate legacy code<\/li>\n<li>Align implementation with use cases (components realize groups of use cases)<\/li>\n<li>Facilitate communication between architects, developers, DevOps, and stakeholders<\/li>\n<\/ul>\n<h3 dir=\"auto\">Practical Examples of Component Diagrams in Real Projects<\/h3>\n<p dir=\"auto\">Here are many concrete examples across different architectures and domains:<\/p>\n<ul dir=\"auto\">\n<li><strong>E-commerce Platform (Microservices Architecture)<\/strong> Components:\n<ul dir=\"auto\">\n<li>CatalogService (provides ProductCatalog API)<\/li>\n<li>CartService (requires ProductCatalog, provides ShoppingCart API)<\/li>\n<li>OrderService (requires ShoppingCart, ProductCatalog, provides OrderProcessing API)<\/li>\n<li>PaymentService (requires OrderProcessing, provides PaymentGatewayAdapter)<\/li>\n<li>InventoryService (provides StockLevel API) Assembly connectors: CartService \u2192 CatalogService (uses product info), OrderService \u2192 InventoryService (reserves stock). Practical benefit: Clearly shows bounded contexts; helps team decide which services can be scaled independently during peak sales.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Mobile Banking App (Modular Monolith + External Integrations)<\/strong> Components:\n<ul dir=\"auto\">\n<li>MobileApp (executable, requires AuthService, TransactionService)<\/li>\n<li>AuthService (provides Authentication API, uses JWT library)<\/li>\n<li>TransactionService (provides TransferFunds API, requires CoreBankingAdapter)<\/li>\n<li>NotificationService (provides PushNotification API)<\/li>\n<li>CoreBankingAdapter (required interface to legacy mainframe via SOAP)<\/li>\n<li>FraudDetectionService (external SaaS, required interface) Outcome: Visualizes internal layering + external dependencies; prevents direct coupling from MobileApp to legacy systems.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Healthcare Integration Platform (Middleware \/ ESB Style)<\/strong> Components:\n<ul dir=\"auto\">\n<li>PatientPortal (web app, requires PatientService)<\/li>\n<li>PatientService (provides HL7 FHIR API)<\/li>\n<li>EHRAdapter (connects to Epic\/Cerner via FHIR)<\/li>\n<li>AppointmentScheduler (provides Scheduling API)<\/li>\n<li>BillingGateway (required interface to insurance clearinghouse)<\/li>\n<li>AuditLoggingComponent (cross-cutting, used by all) Practical: Shows how adapters isolate external systems; supports incremental addition of new hospital system integrations.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Task Management SaaS (Backend Microservices + Frontend)<\/strong> Components:\n<ul dir=\"auto\">\n<li>WebFrontend (SPA, requires TaskAPI, CollaborationAPI)<\/li>\n<li>TaskService (provides CRUD for Boards\/Lists\/Cards)<\/li>\n<li>CollaborationService (real-time WebSocket, requires TaskService)<\/li>\n<li>NotificationService (email\/push, requires CollaborationService)<\/li>\n<li>AuthService (OAuth2\/OpenID provider) Connectors: CollaborationService assembles with TaskService via required TaskEvents interface. Benefit: Guides API gateway design and real-time vs. REST separation.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Legacy ERP Monolith Refactoring (Strangler Fig Pattern)<\/strong> Components (before):\n<ul dir=\"auto\">\n<li>MonolithicERP (large component containing everything) After incremental extraction:<\/li>\n<li>NewOrderManagement (microservice, provides OrderAPI)<\/li>\n<li>LegacyERPWrapper (adapts old monolith, required by new services)<\/li>\n<li>SharedDomainLibrary (common entities, used by both)<\/li>\n<li>NewReportingService (extracted, requires OrderAPI) Practical: Component diagram tracks progress of strangler migration\u2014shows shrinking legacy footprint over releases.<\/li>\n<\/ul>\n<\/li>\n<li><strong>IoT Device Management Platform<\/strong> Components:\n<ul dir=\"auto\">\n<li>DeviceGateway (handles MQTT\/HTTP ingestion, provides DeviceTelemetry API)<\/li>\n<li>RulesEngine (processes events, requires DeviceTelemetry)<\/li>\n<li>AnalyticsService (provides Dashboard API)<\/li>\n<li>FirmwareUpdateService (provides OTA updates)<\/li>\n<li>DeviceRegistry (provides DeviceMetadata API) Connectors: RulesEngine \u2192 DeviceGateway (required), FirmwareUpdateService \u2192 DeviceRegistry. Outcome: Clarifies edge-to-cloud responsibilities; supports adding new device protocols via pluggable gateways.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Restaurant POS &amp; Online Ordering System<\/strong> Components:\n<ul dir=\"auto\">\n<li>POSClient (desktop app at restaurant, requires OrderProcessing)<\/li>\n<li>OnlineOrderingService (web\/mobile, provides CustomerOrder API)<\/li>\n<li>KitchenDisplaySystem (requires OrderProcessing)<\/li>\n<li>PaymentTerminalAdapter (hardware integration)<\/li>\n<li>CentralOrderService (core business logic) Practical: Shows how in-store and online channels converge on shared order processing without duplication.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Agile Team Using Visual Paradigm<\/strong>\n<ul dir=\"auto\">\n<li>Start with high-level component diagram in early sprints (major subsystems realizing use case groups).<\/li>\n<li>Refine with provided\/required interfaces as APIs solidify.<\/li>\n<li>Use stereotypes: \u00abmicroservice\u00bb, \u00ablibrary\u00bb, \u00abexecutable\u00bb, \u00abdatabase\u00bb, \u00abexternal\u00bb.<\/li>\n<li>Semantic backplane ensures component interfaces link to class\/sequence diagrams.<\/li>\n<li>Generate component-based code skeletons or reverse-engineer from existing modules.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">Common patterns visible in component diagrams:<\/p>\n<ul dir=\"auto\">\n<li>Layered architecture (presentation \u2192 application \u2192 domain \u2192 infrastructure)<\/li>\n<li>Hexagonal\/Ports &amp; Adapters (core domain isolated from external tech)<\/li>\n<li>Microservices with API contracts<\/li>\n<li>Legacy wrapping and gradual extraction<\/li>\n<\/ul>\n<p dir=\"auto\">Component diagrams answer: <strong>\u201cHow is the software physically\/modularly organized and wired together?\u201d<\/strong> \u2014 providing a clear map between logical design (classes\/packages) and deployable units, while keeping models Agile: just enough detail to guide implementation and prevent architectural drift.<\/p>\n<p dir=\"auto\">This prepares you for detailing internal structures with <strong>Composite Structure Diagrams<\/strong> next.<\/p>\n","protected":false},"featured_media":5133,"parent":4377,"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-4380","docs","type-docs","status-publish","has-post-thumbnail","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Component 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\/component-diagrams\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Component Diagrams - Visual Paradigm Guides Japanese\" \/>\n<meta property=\"og:description\" content=\"Visualizing the physical implementation and logical organization of software units like executables, libraries, microservices, and modules Component diagrams in UML 2.5 focus on the modular, replaceable building blocks of a software system\u2014showing how larger pieces of implementation (executables, libraries, frameworks, services, subsystems) are structured, connected, and depend on each other. They bridge the logical design (classes, packages) and the physical deployment, emphasizing modularity, interfaces, provided\/required services, and reusability. Key elements: Component \u2014 A rectangle with a small icon in the upper-right corner (two small rectangles), representing a modular unit (e.g., JAR, DLL, microservice, executable, database schema, web service). Provided Interface \u2014 Lollipop notation (circle on a line) \u2014 what the component offers to others (API\/contract). Required Interface \u2014 Socket notation (cup\/half-circle) \u2014 what the component needs from others to function. Dependency \u2014 DaComponent 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\/component-diagrams\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Japanese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T06:47:46+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1002\" \/>\n\t<meta property=\"og:image:height\" content=\"475\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\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\/component-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\/component-diagrams\/\",\"name\":\"Component Diagrams - Visual Paradigm Guides Japanese\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\"},\"primaryImageOfPage\":{\"@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\/component-diagrams\/#primaryimage\"},\"image\":{\"@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\/component-diagrams\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png\",\"datePublished\":\"2026-01-19T03:44:16+00:00\",\"dateModified\":\"2026-01-26T06:47:46+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\/component-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\/component-diagrams\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@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\/component-diagrams\/#primaryimage\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png\",\"contentUrl\":\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png\",\"width\":1002,\"height\":475,\"caption\":\"Web store UML component diagram\"},{\"@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\/component-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\",\"item\":\"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\":\"ListItem\",\"position\":4,\"name\":\"Component 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":"Component 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\/component-diagrams\/","og_locale":"ja_JP","og_type":"article","og_title":"Component Diagrams - Visual Paradigm Guides Japanese","og_description":"Visualizing the physical implementation and logical organization of software units like executables, libraries, microservices, and modules Component diagrams in UML 2.5 focus on the modular, replaceable building blocks of a software system\u2014showing how larger pieces of implementation (executables, libraries, frameworks, services, subsystems) are structured, connected, and depend on each other. They bridge the logical design (classes, packages) and the physical deployment, emphasizing modularity, interfaces, provided\/required services, and reusability. Key elements: Component \u2014 A rectangle with a small icon in the upper-right corner (two small rectangles), representing a modular unit (e.g., JAR, DLL, microservice, executable, database schema, web service). Provided Interface \u2014 Lollipop notation (circle on a line) \u2014 what the component offers to others (API\/contract). Required Interface \u2014 Socket notation (cup\/half-circle) \u2014 what the component needs from others to function. Dependency \u2014 DaComponent 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\/component-diagrams\/","og_site_name":"Visual Paradigm Guides Japanese","article_modified_time":"2026-01-26T06:47:46+00:00","og_image":[{"width":1002,"height":475,"url":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png","type":"image\/png"}],"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\/component-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\/component-diagrams\/","name":"Component Diagrams - Visual Paradigm Guides Japanese","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website"},"primaryImageOfPage":{"@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\/component-diagrams\/#primaryimage"},"image":{"@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\/component-diagrams\/#primaryimage"},"thumbnailUrl":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png","datePublished":"2026-01-19T03:44:16+00:00","dateModified":"2026-01-26T06:47:46+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\/component-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\/component-diagrams\/"]}]},{"@type":"ImageObject","inLanguage":"ja","@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\/component-diagrams\/#primaryimage","url":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png","contentUrl":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/web-store-uml-component-diagram.png","width":1002,"height":475,"caption":"Web store UML component diagram"},{"@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\/component-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","item":"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":"ListItem","position":4,"name":"Component 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\/4380","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=4380"}],"version-history":[{"count":4,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4380\/revisions"}],"predecessor-version":[{"id":5210,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4380\/revisions\/5210"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4377"}],"next":[{"title":"Composite Structure Diagrams","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\/composite-structure-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4381"}],"prev":[{"title":"Package Diagrams","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\/package-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4379"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media\/5133"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=4380"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=4380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}