These diagrams show the physical components of a system. Component diagrams are special type of UML diagrams used for different purposes. We have already described that component diagrams are used to visualize the static implementation view of a system. The following component diagram has been drawn considering all the points mentioned above. Component diagram cannot be matched directly with other UML diagrams discussed so far as it is drawn for completely different purpose. In the following diagram, four files are identified and their relationships are produced. In actual, the component diagram also contains dlls, libraries, folders, etc. The diagram shows the files in the application and their relationships. Use notes for clarifying important points.ДЇollowing is a component diagram for order management system. Prepare a mental layout before producing the using tools. Use a meaningful name to identify the component for which the diagram is to be drawn.

Libraries and other artifacts relevant to the application.ДЄfter identifying the artifacts, the following points need to be kept in mind. A well-prepared component diagram is also important for other aspects such as application performance, maintenance, etc.Д«efore drawing a component diagram, the following artifacts are to be identified clearly в€’ This diagram is very important as without it the application cannot be implemented efficiently. Initially, the system is designed using different UML diagrams and then when the artifacts are ready, component diagrams are used to get an idea of the implementation. However, it is prepared well in advance to visualize the implementation details. Component diagrams are used during the implementation phase of an application. The purpose of this diagram is different. Includes files, executables, libraries, etc The purpose of the component diagram can be summarized as в€’Д¬onstruct executables by using forward and reverse engineering.Дescribe the organization and relationships of the components.Д¬omponent diagrams are used to describe the physical artifacts of a system. Static implementation represents the organization of the components at a particular moment.ДЄ single component diagram cannot represent the entire system but a collection of These components are libraries, packages, files, etc.Д¬omponent diagrams can also be described as a static implementation view of a system. Thus from that point of view, component diagrams are used to visualize the physical components in a system.

It does not describe the functionality of the system but it describes the components used to make those functionalities.

The purpose is also different from all other diagrams discussed so far. Purpose of Component DiagramsД¬omponent diagram is a special kind of diagram in UML. These diagrams are also used to make executable systems. Now the question is, what are these physical aspects? Physical aspects are the elements such as executables, libraries, files,Д¬omponent diagrams are used to visualize the organization and relationships among components in a system. Component diagrams are used to model the physical aspects of a system. Component diagrams are different in terms of nature and behavior.

Bouml aggregation