\u2022 A component is an encapsulated, reusable, and replaceable part of your software
\n\u2022 Reducing and defying coupling between software components
\n\u2022 Reusing existing components
\n\u2022 Model physical software components and the interfaces between them
\n\u2022 Show the structure of the code itself
\n\u2022 Can be used to hide the specification detail (i.e., information hiding) and focus on the relationship between components
\n\u2022 Model the structure of software releases; show how components integrate with current system design
\n\u2022 Model source code and relationships between files
\n\u2022 Specify the files that are compiled into an executable<\/p>\n
In\u00a0Unified Modeling Language<\/a>\u00a0(UML), a\u00a0component diagram<\/b>\u00a0depicts how\u00a0components<\/a>\u00a0are wired together to form larger components or\u00a0software systems<\/a>. They are used to illustrate the structure of arbitrarily complex systems.<\/p>\n A component diagram allows verification that a system’s required functionality is acceptable. These diagrams are also used as a communication tool between the developer and stakeholders of the system. Programmers and developers use the diagrams to formalize a roadmap for the implementation, allowing for better decision-making about task assignment or needed skill improvements. System administrators can use component diagrams to plan ahead, using the view of the logical software components and their relationships on the system.<\/p>\n The component diagram extends the information given in a component notation element. One way of illustrating the provided and required\u00a0interfaces<\/a>\u00a0by the specified component is in the form of a rectangular compartment attached to the component element. Another accepted way of presenting the interfaces is to use the\u00a0ball-and-socket graphic convention<\/a>. A\u00a0provided<\/i>\u00a0dependency from a component to an interface is illustrated with a solid line to the component using the interface from a “lollipop”, or ball, labelled with the name of the interface. A\u00a0required<\/i>\u00a0usage dependency from a component to an interface is illustrated by a half-circle, or socket, labelled with the name of the interface, attached by a solid line to the component that requires this interface. Inherited interfaces may be shown with a lollipop, preceding the name label with a\u00a0caret<\/a>\u00a0symbol. To illustrate dependencies between the two, use a solid line with a plain arrowhead joining the socket to the lollipop.<\/p>\n \n","protected":false},"excerpt":{"rendered":"Overview<\/span><\/h3>\n
Diagram elements<\/span><\/h3>\n