{"id":4381,"date":"2026-01-19T11:44:25","date_gmt":"2026-01-19T03:44:25","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/es\/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\/"},"modified":"2026-01-26T11:56:36","modified_gmt":"2026-01-26T03:56:36","slug":"composite-structure-diagrams","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/es\/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\/","title":{"rendered":"Composite Structure Diagrams"},"content":{"rendered":"<h2 dir=\"auto\"><strong>Showing the internal runtime structure of complex classes, components, or subsystems \u2014 parts, ports, and internal connectors<\/strong><\/h2>\n<figure id=\"attachment_5134\" aria-describedby=\"caption-attachment-5134\" style=\"width: 548px\" class=\"wp-caption alignnone\"><img fetchpriority=\"high\" decoding=\"async\" class=\"size-full wp-image-5134\" src=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png\" alt=\"Car UML composite structure diagram\" width=\"548\" height=\"165\" srcset=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png 548w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram-300x90.png 300w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram-150x45.png 150w\" sizes=\"(max-width: 548px) 100vw, 548px\" \/><figcaption id=\"caption-attachment-5134\" class=\"wp-caption-text\">Car UML composite structure diagram<\/figcaption><\/figure>\n<p dir=\"auto\"><strong>Composite Structure 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> provide a detailed, runtime-oriented view inside a single <strong>structured classifier<\/strong> (typically a complex class, component, subsystem, or collaboration). They show how the classifier is decomposed into <strong>parts<\/strong> (internal instances\/roles), connected via <strong>connectors<\/strong>, and exposed to the outside world through <strong>ports<\/strong>.<\/p>\n<p dir=\"auto\">While class diagrams define types and vocabulary, and component diagrams show modular assembly at the architectural level, composite structure diagrams &#8220;open the box&#8221; to reveal <strong>how internal elements collaborate at runtime<\/strong> to realize behavior. They are particularly powerful for modeling complex objects with intricate internal structure (e.g., embedded systems, frameworks, engines, UI widgets, or domain aggregates) without showing external deployment concerns.<\/p>\n<p dir=\"auto\">Key elements:<\/p>\n<ul dir=\"auto\">\n<li><strong>Structured Classifier<\/strong> \u2014 The containing element (class or component) shown with a dashed border or rectangle; its name at the top.<\/li>\n<li><strong>Part<\/strong> \u2014 Rectangle inside the classifier representing a role or set of instances (multiplicity shown, e.g., 1..*, 4); typed by a class.<\/li>\n<li><strong>Port<\/strong> \u2014 Small square on the boundary (or on parts); typed by interface(s); defines interaction points to environment or internals.<\/li>\n<li><strong>Provided\/Required Interfaces<\/strong> \u2014 Ball (provided) and socket (required) on ports; ball-and-socket notation for contracts.<\/li>\n<li><strong>Connector<\/strong> \u2014 Solid line linking parts\/ports; shows runtime communication paths (can be assembly or delegation).<\/li>\n<li><strong>Role<\/strong> \u2014 Named part or port indicating behavioral responsibility.<\/li>\n<\/ul>\n<p dir=\"auto\">In Agile &amp; use-case-driven projects, composite structure diagrams are used to:<\/p>\n<ul dir=\"auto\">\n<li>Detail complex domain objects or components derived from use cases (e.g., &#8220;Order&#8221; with internal line items, pricing engine, validation rules).<\/li>\n<li>Clarify internal collaborations for tricky scenarios (alternatives\/exceptions in flows).<\/li>\n<li>Support refactoring of god-classes or monolithic components by exposing internal parts.<\/li>\n<li>Model embedded\/real-time systems where internal structure drives behavior.<\/li>\n<li>Bridge analysis (class diagrams) to detailed design without jumping to code.<\/li>\n<li>Remain lightweight \u2014 use only for classifiers that benefit from &#8220;inside view&#8221;; avoid over-modeling simple classes.<\/li>\n<\/ul>\n<h3 dir=\"auto\">Practical Examples of Composite Structure Diagrams in Real Projects<\/h3>\n<p dir=\"auto\">Here are many concrete examples across domains, showing internal decomposition, ports, and runtime connectors:<\/p>\n<ul dir=\"auto\">\n<li><strong>Automotive Engine Control Unit (ECU) in Embedded System<\/strong>:\n<ul dir=\"auto\">\n<li>Structured Classifier: EngineController<\/li>\n<li>Parts: FuelInjector (4), SparkPlugController (4), SensorHub, ThrottleActuator, ECUCore (processor)<\/li>\n<li>Ports: SensorPort (required interfaces for temperature\/pressure), ActuatorPort (provided for control signals), DiagnosticPort (OBD-II)<\/li>\n<li>Connectors: ECUCore \u2192 SensorHub (delegation), ECUCore \u2192 FuelInjector (assembly via control signals)<\/li>\n<li>Practical benefit: Reveals how sensor data flows to actuators; helps validate real-time constraints for &#8220;Accelerate Vehicle&#8221; use case; supports hardware-in-loop testing.<\/li>\n<\/ul>\n<\/li>\n<li><strong>E-commerce Order Aggregate (Domain-Driven Design)<\/strong>:\n<ul dir=\"auto\">\n<li>Structured Classifier: Order<\/li>\n<li>Parts: OrderHeader, LineItem (1..*), PricingEngine, DiscountCalculator, ValidationRules, PaymentStatus<\/li>\n<li>Ports: ExternalOrderPort (provided OrderAPI), PaymentPort (required PaymentGateway)<\/li>\n<li>Connectors: OrderHeader \u2192 LineItem (composition links), PricingEngine \u2192 DiscountCalculator (delegation), ValidationRules \u2192 OrderHeader<\/li>\n<li>Outcome: Shows internal consistency rules (e.g., total recalculation); clarifies &#8220;Apply Coupon&#8221; extension without bloating class diagram.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Healthcare Patient Record System (Complex Entity)<\/strong>:\n<ul dir=\"auto\">\n<li>Structured Classifier: PatientRecord<\/li>\n<li>Parts: Demographics, MedicalHistory, CurrentMedications (1..*), Allergies, VisitHistory, ConsentManager<\/li>\n<li>Ports: AccessPort (provided FHIR API), AuditPort (required LoggingService)<\/li>\n<li>Connectors: Demographics \u2192 ConsentManager (checks access), VisitHistory \u2192 CurrentMedications<\/li>\n<li>Practical: Models privacy-by-design internals; ports enforce controlled access; useful for compliance reviews and &#8220;View Patient Record&#8221; use case validation.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Smart Home Thermostat Device<\/strong>:\n<ul dir=\"auto\">\n<li>Structured Classifier: Thermostat<\/li>\n<li>Parts: TemperatureSensor, UserInterface (display\/buttons), ControlLogic, RelayActuator, WiFiModule<\/li>\n<li>Ports: EnvironmentPort (required temp\/humidity), CloudPort (provided status API), LocalControlPort<\/li>\n<li>Connectors: ControlLogic \u2192 TemperatureSensor \u2192 RelayActuator; WiFiModule \u2192 ControlLogic<\/li>\n<li>Benefit: Details internal decision-making for &#8220;Maintain Temperature&#8221; use case; ports allow swapping sensors; supports firmware updates.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Task Management Card (Trello-like Component)<\/strong>:\n<ul dir=\"auto\">\n<li>Structured Classifier: Card<\/li>\n<li>Parts: Description, Checklist (0..*), Attachments, Comments (0..*), Labels, DueDateTracker, Assignee<\/li>\n<li>Ports: CollaborationPort (provided real-time updates), NotificationPort (required)<\/li>\n<li>Connectors: Checklist \u2192 DueDateTracker (progress affects date), Comments \u2192 Assignee<\/li>\n<li>Practical: Shows runtime composition for &#8220;Update Card&#8221; flow; helps optimize sync logic in collaborative SaaS.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Inventory Management Warehouse Robot<\/strong>:\n<ul dir=\"auto\">\n<li>Structured Classifier: PickingRobot<\/li>\n<li>Parts: NavigationModule, ArmController, Scanner, BatteryManager, CentralBrain<\/li>\n<li>Ports: FleetPort (required commands from warehouse system), SensorPort<\/li>\n<li>Connectors: CentralBrain \u2192 NavigationModule \u2192 Scanner; ArmController \u2192 CentralBrain<\/li>\n<li>Outcome: Clarifies internal coordination for &#8220;Pick Item&#8221; use case; ports isolate robot from fleet changes.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Banking Transaction Processor (Internal View)<\/strong>:\n<ul dir=\"auto\">\n<li>Structured Classifier: TransactionProcessor<\/li>\n<li>Parts: ValidationEngine, FraudDetector, LedgerUpdater, NotificationSender<\/li>\n<li>Ports: IncomingTxPort (provided), ExternalFraudPort (required)<\/li>\n<li>Connectors: ValidationEngine \u2192 FraudDetector \u2192 LedgerUpdater<\/li>\n<li>Practical: Models sequential\/internal checks for &#8220;Transfer Funds&#8221;; easy to insert new fraud rules as parts.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Restaurant Kitchen Order Flow Subsystem<\/strong>:\n<ul dir=\"auto\">\n<li>Structured Classifier: KitchenStation<\/li>\n<li>Parts: OrderQueue, PrepArea, CookingStation, Expediter, DisplayScreen<\/li>\n<li>Connectors: OrderQueue \u2192 PrepArea \u2192 CookingStation \u2192 Expediter<\/li>\n<li>Benefit: Visualizes internal handoffs; supports &#8220;Prepare Order&#8221; use case optimization.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">In Visual Paradigm:<\/p>\n<ul dir=\"auto\">\n<li>Create via <strong>Diagram &gt; New &gt; Composite Structure Diagram<\/strong>.<\/li>\n<li>Drag structured classifier; add parts\/ports from Resource Catalog or toolbox.<\/li>\n<li>Connect parts with connectors; add ball\/socket for interfaces on ports.<\/li>\n<li>Use semantic backplane: link parts to classes\/objects from class diagrams; trace to use cases.<\/li>\n<li>Generate from complex classes or collaborate with team on internal details iteratively.<\/li>\n<\/ul>\n<p dir=\"auto\">Composite structure diagrams answer: <strong>\u201cWhat\u2019s inside this complex element, and how do its parts collaborate at runtime?\u201d<\/strong> \u2014 offering a precise, focused &#8220;x-ray&#8221; view that complements component diagrams (external modularity) and class diagrams (types). They excel at modeling intricate internals while staying Agile: detail only where runtime structure matters.<\/p>\n<p dir=\"auto\">This leads naturally to <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/deployment-diagrams\/\">Deployment Diagrams<\/a> for mapping software to hardware nodes.<\/p>\n","protected":false},"featured_media":0,"parent":4377,"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-4381","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>Composite Structure Diagrams - Visual Paradigm Guides Spanish<\/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\/es\/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\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Composite Structure Diagrams - Visual Paradigm Guides Spanish\" \/>\n<meta property=\"og:description\" content=\"Showing the internal runtime structure of complex classes, components, or subsystems \u2014 parts, ports, and internal connectors Composite Structure Diagrams in UML 2.5 provide a detailed, runtime-oriented view inside a single structured classifier (typically a complex class, component, subsystem, or collaboration). They show how the classifier is decomposed into parts (internal instances\/roles), connected via connectors, and exposed to the outside world through ports. While class diagrams define types and vocabulary, and component diagrams show modular assembly at the architectural level, composite structure diagrams &#8220;open the box&#8221; to reveal how internal elements collaborate at runtime to realize behavior. They are particularly powerful for modeling complex objects with intricate internal structure (e.g., embedded systems, frameworks, engines, UI widgets, or domain aggregates) without showing external deployment concerns. Key elements: Structured Classifier \u2014 The containing element (class or component) shown with a dashed border or rectangle; its name at the top. Part \u2014 Rectangle inside the classifier representing a role or set of instances (multiplicity shown, e.g., 1..*, 4); typed by a class. Port \u2014 Small square on the boundary (or on parts); typed by interface(s); defines interaction points to environment or internals. Provided\/Required Interfaces \u2014 Ball (provided) and socket (required) on ports; ball-and-socket notation for contracts. Connector \u2014 Solid line linking parts\/ports; shows runtime communication paths (can be assembly or delegation). Role \u2014 Named part or port indicating behavioral responsibility. In Agile &amp; use-case-driven projects, composite structure diagrams are used to: Detail complex domain objects or components derived from use cases (e.g., &#8220;Order&#8221; with internal line items, pricing engine, validation rules). Clarify internal collaborations for tricky scenarios (alternatives\/exceptions in flows). Support refactoring of god-classes or monolithic components by exposing internal parts. Model embedded\/real-time systems where internal structure drives behavior. Bridge analysis (class diagrams) to detailed design without jumping to code. Remain lightweight \u2014 use only for classifiers that benefit from &#8220;inside view&#8221;; avoid over-modeling simple classes. Practical Examples of Composite Structure Diagrams in Real Projects Here are many concrete examples across domains, showing internal decomposition, ports, and runtime connectors: Automotive Engine Control Unit (ECU) in Embedded System: Structured Classifier: EngineController Parts: FuelInjector (4), SparkPlugController (4), SensorHub, ThrottleActuator, ECUCore (processor) Ports: SensorPort (required interfaces for temperature\/pressure), ActuatorPort (provided for control signals), DiagnosticPort (OBD-II) Connectors: ECUCore \u2192 SensorHub (delegation), ECUCore \u2192 FuelInjector (assembly via control signals) Practical benefit: Reveals how sensor data flows to actuators; helps validate real-time constraints for &#8220;Accelerate Vehicle&#8221; use case; supports hardware-in-loop testing. E-commerce Order Aggregate (Domain-Driven Design): Structured Classifier: Order Parts: OrderHeader, LineItem (1..*), PricingEngine, DiscountCalculator, ValidationRules, PaymentStatus Ports: ExternalOrderPort (provided OrderAPI), PaymentPort (required PaymentGateway) Connectors: OrderHeader \u2192 LineItem (composition links), PricingEngine \u2192 DiscountCalculator (delegation), ValidationRules \u2192 OrderHeader Outcome: Shows internal consistency rules (e.g., total recalculation); clarifies &#8220;Apply Coupon&#8221; extension without bloating class diagram. Healthcare Patient Record System (Complex Entity): Structured Classifier: PatientRecord Parts: Demographics, MedicalHistory, CurrentMedications (1..*), Allergies, VisitHistory, ConsentManager Ports: AccessPort (provided FHIR API), AuditPort (required LoggingService) Connectors: Demographics \u2192 ConsentManager (checks access), VisitHistory \u2192 CurrentMedications Practical: Models privacy-by-design internals; ports enforce controlled access; useful for compliance reviews and &#8220;View Patient Record&#8221; use case validation. Smart Home Thermostat Device: Structured Classifier: Thermostat Parts: TemperatureSensor, UserInterface (display\/buttons), ControlLogic, RelayActuator, WiFiModule Ports: EnvironmentPort (required temp\/humidity), CloudPort (provided status API), LocalControlPort Connectors: ControlLogic \u2192 TemperatureSensor \u2192 RelayActuator; WiFiModule \u2192 ControlLogic Benefit: Details internal decision-making for &#8220;Maintain Temperature&#8221; use case; ports allow swapping sensors; supports firmware updates. Task Management Card (Trello-like Component): Structured Classifier: Card Parts: Description, Checklist (0..*), Attachments, Comments (0..*), Labels, DueDateTracker, Assignee Ports: CollaborationPort (provided real-time updates), NotificationPort (required) Connectors: Checklist \u2192 DueDateTracker (progress affects date), Comments \u2192 Assignee Practical: Shows runtime composition for &#8220;Update Card&#8221; flow; helps optimize sync logic in collaborative SaaS. Inventory Management Warehouse Robot: Structured Classifier: PickingRobot Parts: NavigationModule, ArmController, Scanner, BatteryManager, CentralBrain Ports: FleetPort (required commands from warehouse system), SensorPort Connectors: CentralBrain \u2192 NavigationModule \u2192 Scanner; ArmController \u2192 CentralBrain Outcome: Clarifies internal coordination for &#8220;Pick Item&#8221; use case; ports isolate robot from fleet changes. Banking Transaction Processor (Internal View): Structured Classifier: TransactionProcessor Parts: ValidationEngine, FraudDetector, LedgerUpdater, NotificationSender Ports: IncomingTxPort (provided), ExternalFraudPort (required) Connectors: ValidationEngine \u2192 FraudDetector \u2192 LedgerUpdater Practical: Models sequential\/internal checks for &#8220;Transfer Funds&#8221;; easy to insert new fraud rules as parts. Restaurant Kitchen Order Flow Subsystem: Structured Classifier: KitchenStation Parts: OrderQueue, PrepArea, CookingStation, Expediter, DisplayScreen Connectors: OrderQueue \u2192 PrepArea \u2192 CookingStation \u2192 Expediter Benefit: Visualizes internal handoffs; supports &#8220;Prepare Order&#8221; use case optimization. In Visual Paradigm: Create via Diagram &gt; New &gt; Composite Structure Diagram. Drag structured classifier; add parts\/ports from Resource Catalog or toolbox. Connect parts with connectors; add ball\/socket for interfaces on ports. Use semantic backplane: link parts to classes\/objects from class diagrams; trace to use cases. Generate from complex classes or collaborate with team on internal details iteratively. Composite structure diagrams answer: \u201cWhat\u2019s inside this complex element, and how do its parts collaborate at runtime?\u201d \u2014 offering a precise, focused &#8220;x-ray&#8221; view that complements component diagrams (external modularity) and class diagrams (types). They excel at modeling intricate internals while staying Agile: detail only where runtime structure matters. This leads naturally to Deployment Diagrams for mapping software to hardware nodes.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/es\/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\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Spanish\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T03:56:36+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png\" \/>\n\t<meta property=\"og:image:width\" content=\"548\" \/>\n\t<meta property=\"og:image:height\" content=\"165\" \/>\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=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/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\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/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\/\",\"name\":\"Composite Structure Diagrams - Visual Paradigm Guides Spanish\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/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\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/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\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png\",\"datePublished\":\"2026-01-19T03:44:25+00:00\",\"dateModified\":\"2026-01-26T03:56:36+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/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\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/es\/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\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/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\/#primaryimage\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png\",\"contentUrl\":\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png\",\"width\":548,\"height\":165,\"caption\":\"Car UML composite structure diagram\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/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\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/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\/es\/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\":\"Composite Structure Diagrams\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Guides Spanish\",\"description\":\"Smart guides for an AI-driven world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Composite Structure Diagrams - Visual Paradigm Guides Spanish","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\/es\/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\/","og_locale":"es_ES","og_type":"article","og_title":"Composite Structure Diagrams - Visual Paradigm Guides Spanish","og_description":"Showing the internal runtime structure of complex classes, components, or subsystems \u2014 parts, ports, and internal connectors Composite Structure Diagrams in UML 2.5 provide a detailed, runtime-oriented view inside a single structured classifier (typically a complex class, component, subsystem, or collaboration). They show how the classifier is decomposed into parts (internal instances\/roles), connected via connectors, and exposed to the outside world through ports. While class diagrams define types and vocabulary, and component diagrams show modular assembly at the architectural level, composite structure diagrams &#8220;open the box&#8221; to reveal how internal elements collaborate at runtime to realize behavior. They are particularly powerful for modeling complex objects with intricate internal structure (e.g., embedded systems, frameworks, engines, UI widgets, or domain aggregates) without showing external deployment concerns. Key elements: Structured Classifier \u2014 The containing element (class or component) shown with a dashed border or rectangle; its name at the top. Part \u2014 Rectangle inside the classifier representing a role or set of instances (multiplicity shown, e.g., 1..*, 4); typed by a class. Port \u2014 Small square on the boundary (or on parts); typed by interface(s); defines interaction points to environment or internals. Provided\/Required Interfaces \u2014 Ball (provided) and socket (required) on ports; ball-and-socket notation for contracts. Connector \u2014 Solid line linking parts\/ports; shows runtime communication paths (can be assembly or delegation). Role \u2014 Named part or port indicating behavioral responsibility. In Agile &amp; use-case-driven projects, composite structure diagrams are used to: Detail complex domain objects or components derived from use cases (e.g., &#8220;Order&#8221; with internal line items, pricing engine, validation rules). Clarify internal collaborations for tricky scenarios (alternatives\/exceptions in flows). Support refactoring of god-classes or monolithic components by exposing internal parts. Model embedded\/real-time systems where internal structure drives behavior. Bridge analysis (class diagrams) to detailed design without jumping to code. Remain lightweight \u2014 use only for classifiers that benefit from &#8220;inside view&#8221;; avoid over-modeling simple classes. Practical Examples of Composite Structure Diagrams in Real Projects Here are many concrete examples across domains, showing internal decomposition, ports, and runtime connectors: Automotive Engine Control Unit (ECU) in Embedded System: Structured Classifier: EngineController Parts: FuelInjector (4), SparkPlugController (4), SensorHub, ThrottleActuator, ECUCore (processor) Ports: SensorPort (required interfaces for temperature\/pressure), ActuatorPort (provided for control signals), DiagnosticPort (OBD-II) Connectors: ECUCore \u2192 SensorHub (delegation), ECUCore \u2192 FuelInjector (assembly via control signals) Practical benefit: Reveals how sensor data flows to actuators; helps validate real-time constraints for &#8220;Accelerate Vehicle&#8221; use case; supports hardware-in-loop testing. E-commerce Order Aggregate (Domain-Driven Design): Structured Classifier: Order Parts: OrderHeader, LineItem (1..*), PricingEngine, DiscountCalculator, ValidationRules, PaymentStatus Ports: ExternalOrderPort (provided OrderAPI), PaymentPort (required PaymentGateway) Connectors: OrderHeader \u2192 LineItem (composition links), PricingEngine \u2192 DiscountCalculator (delegation), ValidationRules \u2192 OrderHeader Outcome: Shows internal consistency rules (e.g., total recalculation); clarifies &#8220;Apply Coupon&#8221; extension without bloating class diagram. Healthcare Patient Record System (Complex Entity): Structured Classifier: PatientRecord Parts: Demographics, MedicalHistory, CurrentMedications (1..*), Allergies, VisitHistory, ConsentManager Ports: AccessPort (provided FHIR API), AuditPort (required LoggingService) Connectors: Demographics \u2192 ConsentManager (checks access), VisitHistory \u2192 CurrentMedications Practical: Models privacy-by-design internals; ports enforce controlled access; useful for compliance reviews and &#8220;View Patient Record&#8221; use case validation. Smart Home Thermostat Device: Structured Classifier: Thermostat Parts: TemperatureSensor, UserInterface (display\/buttons), ControlLogic, RelayActuator, WiFiModule Ports: EnvironmentPort (required temp\/humidity), CloudPort (provided status API), LocalControlPort Connectors: ControlLogic \u2192 TemperatureSensor \u2192 RelayActuator; WiFiModule \u2192 ControlLogic Benefit: Details internal decision-making for &#8220;Maintain Temperature&#8221; use case; ports allow swapping sensors; supports firmware updates. Task Management Card (Trello-like Component): Structured Classifier: Card Parts: Description, Checklist (0..*), Attachments, Comments (0..*), Labels, DueDateTracker, Assignee Ports: CollaborationPort (provided real-time updates), NotificationPort (required) Connectors: Checklist \u2192 DueDateTracker (progress affects date), Comments \u2192 Assignee Practical: Shows runtime composition for &#8220;Update Card&#8221; flow; helps optimize sync logic in collaborative SaaS. Inventory Management Warehouse Robot: Structured Classifier: PickingRobot Parts: NavigationModule, ArmController, Scanner, BatteryManager, CentralBrain Ports: FleetPort (required commands from warehouse system), SensorPort Connectors: CentralBrain \u2192 NavigationModule \u2192 Scanner; ArmController \u2192 CentralBrain Outcome: Clarifies internal coordination for &#8220;Pick Item&#8221; use case; ports isolate robot from fleet changes. Banking Transaction Processor (Internal View): Structured Classifier: TransactionProcessor Parts: ValidationEngine, FraudDetector, LedgerUpdater, NotificationSender Ports: IncomingTxPort (provided), ExternalFraudPort (required) Connectors: ValidationEngine \u2192 FraudDetector \u2192 LedgerUpdater Practical: Models sequential\/internal checks for &#8220;Transfer Funds&#8221;; easy to insert new fraud rules as parts. Restaurant Kitchen Order Flow Subsystem: Structured Classifier: KitchenStation Parts: OrderQueue, PrepArea, CookingStation, Expediter, DisplayScreen Connectors: OrderQueue \u2192 PrepArea \u2192 CookingStation \u2192 Expediter Benefit: Visualizes internal handoffs; supports &#8220;Prepare Order&#8221; use case optimization. In Visual Paradigm: Create via Diagram &gt; New &gt; Composite Structure Diagram. Drag structured classifier; add parts\/ports from Resource Catalog or toolbox. Connect parts with connectors; add ball\/socket for interfaces on ports. Use semantic backplane: link parts to classes\/objects from class diagrams; trace to use cases. Generate from complex classes or collaborate with team on internal details iteratively. Composite structure diagrams answer: \u201cWhat\u2019s inside this complex element, and how do its parts collaborate at runtime?\u201d \u2014 offering a precise, focused &#8220;x-ray&#8221; view that complements component diagrams (external modularity) and class diagrams (types). They excel at modeling intricate internals while staying Agile: detail only where runtime structure matters. This leads naturally to Deployment Diagrams for mapping software to hardware nodes.","og_url":"https:\/\/guides.visual-paradigm.com\/es\/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\/","og_site_name":"Visual Paradigm Guides Spanish","article_modified_time":"2026-01-26T03:56:36+00:00","og_image":[{"width":548,"height":165,"url":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"4 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/es\/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\/","url":"https:\/\/guides.visual-paradigm.com\/es\/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\/","name":"Composite Structure Diagrams - Visual Paradigm Guides Spanish","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/#website"},"primaryImageOfPage":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/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\/#primaryimage"},"image":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/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\/#primaryimage"},"thumbnailUrl":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png","datePublished":"2026-01-19T03:44:25+00:00","dateModified":"2026-01-26T03:56:36+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/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\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/es\/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\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/guides.visual-paradigm.com\/es\/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\/#primaryimage","url":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png","contentUrl":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/car-uml-composite-structure-diagram.png","width":548,"height":165,"caption":"Car UML composite structure diagram"},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/es\/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\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling","item":"https:\/\/guides.visual-paradigm.com\/es\/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\/es\/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":"Composite Structure Diagrams"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/es\/#website","url":"https:\/\/guides.visual-paradigm.com\/es\/","name":"Visual Paradigm Guides Spanish","description":"Smart guides for an AI-driven world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4381","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/comments?post=4381"}],"version-history":[{"count":5,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4381\/revisions"}],"predecessor-version":[{"id":5209,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4381\/revisions\/5209"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4377"}],"next":[{"title":"Deployment Diagrams","link":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/deployment-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4382"}],"prev":[{"title":"Component Diagrams","link":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/component-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4380"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=4381"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=4381"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}