{"version":"1.0","provider_name":"Go UML \u0420\u0443\u0441\u0441\u043a\u0438\u0439","provider_url":"https:\/\/www.go-uml.com\/ru","author_name":"curtis","author_url":"https:\/\/www.go-uml.com\/ru\/author\/curtis\/","title":"Understanding Composite Structure Diagrams: A Detailed Guide - Go UML \u0420\u0443\u0441\u0441\u043a\u0438\u0439","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"hBEMNQFLOW\"><a href=\"https:\/\/www.go-uml.com\/ru\/understanding-composite-structure-diagrams-a-detailed-guide\/\">Understanding Composite Structure Diagrams: A Detailed Guide<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/www.go-uml.com\/ru\/understanding-composite-structure-diagrams-a-detailed-guide\/embed\/#?secret=hBEMNQFLOW\" width=\"600\" height=\"338\" title=\"\u00abUnderstanding Composite Structure Diagrams: A Detailed Guide\u00bb &#8212; Go UML \u0420\u0443\u0441\u0441\u043a\u0438\u0439\" data-secret=\"hBEMNQFLOW\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script>\n\/*! This file is auto-generated *\/\n!function(d,l){\"use strict\";l.querySelector&&d.addEventListener&&\"undefined\"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!\/[^a-zA-Z0-9]\/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret=\"'+t.secret+'\"]'),o=l.querySelectorAll('blockquote[data-secret=\"'+t.secret+'\"]'),c=new RegExp(\"^https?:$\",\"i\"),i=0;i<o.length;i++)o[i].style.display=\"none\";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(\"style\"),\"height\"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):\"link\"===t.message&&(r=new URL(s.getAttribute(\"src\")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(\"message\",d.wp.receiveEmbedMessage,!1),l.addEventListener(\"DOMContentLoaded\",function(){for(var e,t,s=l.querySelectorAll(\"iframe.wp-embedded-content\"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(\"data-secret\"))||(t=Math.random().toString(36).substring(2,12),e.src+=\"#?secret=\"+t,e.setAttribute(\"data-secret\",t)),e.contentWindow.postMessage({message:\"ready\",secret:t},\"*\")},!1)))}(window,document);\n<\/script>\n","thumbnail_url":"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-composite-structure-diagram\/04-composite-structure-diagram.png","thumbnail_width":"570","thumbnail_height":"169","description":"Introduction Composite Structure Diagrams (CSDs) are a vital part of the Unified Modeling Language (UML), providing a detailed view of the internal structure of a class and the collaborations that this structure makes possible. This article will delve into the key concepts of composite structure diagrams, using a case study to illustrate their application and importance in software design. What is a Composite Structure Diagram? A Composite Structure Diagram is a type of static structure diagram in UML that shows the internal structure of a classifier, its parts, ports, and connectors. It provides a detailed view of how different elements within a classifier (such as a class, component, or deployment node) are composed and how they interact. Key Components of a Composite Structure Diagram Parts: Represent instances of classifiers that are owned by the containing classifier. Ports: Interaction points between the classifier and its environment or between its parts. Connectors: Links between ports, representing the communication paths between parts. Collaborations: Sets of interactions between parts that work together to achieve a common goal. Case Study: StoreManager System Let&#8217;s consider a case study of a StoreManager system to understand how composite structure diagrams are used in practice. Scenario The StoreManager system manages customers and their orders. There are two types of customers: standard customers and member customers. Each type of customer has a specific type of order associated with it. The system needs to model the interactions between these customers and their orders. Composite Structure Diagram for StoreManager &nbsp; Explanation Classifiers: The diagram includes two classifiers:\u00a0Customer\u00a0and\u00a0Order. Parts: Each\u00a0Customer\u00a0classifier has a part that represents an\u00a0Order. The\u00a0Customer\u00a0classifier is further specialized into\u00a0standard\u00a0and\u00a0member\u00a0types. Ports: The\u00a0Order\u00a0parts have ports that represent the interaction points with the\u00a0Item\u00a0class. Connectors: The connectors link the\u00a0Order\u00a0parts to the\u00a0Item\u00a0class, showing the communication path between them. Detailed Breakdown Customer Classifier: standardOrder: Represents the order associated with a standard customer. memberOrder: Represents the order associated with a member customer. Order Parts: Each\u00a0Order\u00a0part is connected to an\u00a0Item\u00a0class through a port, indicating that orders interact with items. Interactions: The connectors between the\u00a0Order\u00a0parts and the\u00a0Item\u00a0class show that orders can include multiple items. The diagram illustrates how different types of customers (standard and member) have different types of orders, but both interact with items in a similar manner. Key Concepts Illustrated Hierarchical Composition The diagram shows how larger structures (customers) are built from smaller parts (orders). This hierarchical composition is a fundamental concept in composite structure diagrams. Internal Structure Representation The diagram provides a detailed view of the internal structure of the Customer classifier, showing how it is composed of different types of orders and how these orders interact with items. Collaborations The diagram illustrates the collaborations between the parts (orders) and the environment (items). This is crucial for understanding how different components of the system work together to achieve a common goal. Benefits of Using Composite Structure Diagrams Detailed Modeling: Composite structure diagrams allow for a detailed representation of the internal structure of classifiers, providing a deeper understanding of how different parts interact. Clarity in Complex Systems: They help in visualizing complex systems by breaking them down into smaller, manageable parts. Improved Communication: These diagrams improve communication among stakeholders by providing a clear and comprehensive view of the system&#8217;s structure. Conclusion Composite Structure Diagrams are essential tools in UML for modeling the internal structure of classifiers and their interactions. The case study of the StoreManager system illustrates how these diagrams can be used to represent complex systems in a clear and detailed manner. By understanding and utilizing composite structure diagrams, software designers can create more robust and well-documented systems. References Composite structure diagram &#8211; Wikipedia A composite structure diagram in the Unified Modeling Language (UML) is a type of static structure diagram that shows the internal structure of a class and the collaborations that this structure makes possible. Class diagram &#8211; Wikipedia In UML, it is graphically represented as a hollow diamond shape on the containing class with a single line that connects it to the contained class. The aggregate is semantically an extended object that is treated as a unit in many operations, although physically it is made of several lesser objects. Unified Modeling Language &#8211; Wikipedia UML diagrams represent two different views of a system model: Static (or structural) view: emphasizes the static structure of the system using objects, attributes, operations and relationships. It includes class diagrams and composite structure diagrams. Composite pattern &#8211; Wikipedia This enables clients to work through the Component interface to treat Leaf and Composite objects uniformly: Leaf objects perform a request directly, and Composite objects forward the request to their child components recursively downwards the tree structure. Component diagram &#8211; Wikipedia In Unified Modeling Language (UML), a component diagram depicts how components are wired together to form larger components or software systems. They are used to illustrate the structure of arbitrarily complex systems. 2.5.1 UML Specifications &#8211; OMG About the Unified Modeling Language Specification Version 2.5.1. Welcome To UML Web Site! &#8211; OMG Welcome to the Unified Modeling Language\u2122 (UML\u00ae) website. Feel free to browse news and articles on UML, success stories, available certification and training, along with the current specifications. About the Precise Semantics of UML Composite Structures Specification Version 1.2 &#8211; OMG This specification defines an extension of fUML syntax and semantics to enable modeling and execution of UML composite structures. What is UML | Unified Modeling Language &#8211; OMG UML 2.0 defines thirteen types of diagrams, divided into three categories: Six diagram types represent static application structure; three represent general types of behavior; and four represent different aspects of interactions: Structure Diagrams include the Class Diagram, Object Diagram, Component Diagram, Composite Structure Diagram, Package Diagram, and Deployment Diagram. What is Composite Structure Diagram? &#8211; Visual Paradigm Composite Structure Diagram is one of the new artifacts added to UML 2.0. A composite structure diagram is a UML structural diagram that contains classes, interfaces, packages, and their relationships, and that provides a logical view of all, or part of a software system. How to Draw Composite Structure Diagram? &#8211;"}