Component and Deployment Diagrams

33.1 Component Diagram The main purpose of a component diagram is to show the structural relationships between the components of a system. UML component diagrams are great for identifying the architectural landscape for a system as they enable us to model the high-level software components, and more importantly the interfaces to those components. A component diagram provides a physical view of the system. Its purpose is to show the dependencies that the software has on the other software components.

33.2 Component Diagram Contd.. The diagram can be shown at a very high level, with just the large-grain components, or it can be shown at the component package level. A component may be A source code component A run time components An executable component Dependency relationship.

33.3 Modelling Techniques To model a system’s source code Identify the different files used in the source code. Under the configuration management, use the tools such as tagged values, author, version number…etc, for each file. Using UML, visualize and document the relationships noted in the following scenario. For larger systems, use packages to show groups of source code files.

33.4 Component Diagram for withdrawal of cash policy.dll Branch Bank.dll customer.dll ATM.exe Bank.exe Bank Server.exe

33.5 Deployment Diagram A deployment diagram shows the relationship among software and hardware components in the delivered system. The deployment diagram shows how a system will be physically deployed in the hardware environment. Its purpose is to show where the different components of the system will physically run and how they will communicate with each other. Since the diagram models the physical runtime, a system's production staff will make considerable use of this diagram.

33.6 Deployment Diagram Contd.. These diagram include nodes and connections between nodes. Each node in deployment diagram represents some kind of computational unit such as physical machine or a virtual machine node. In most cases it is a piece of hardware. To model a node, simply draw a three-dimensional cube with the name of the node at the top of the cube. Use the naming convention used in sequence diagrams. Connection among nodes show the communication path over which the system will interact.

33.7 Deployment diagram: ATM Example machine Bank_ server Branch Ethernet Bank.exe BankServer.exe ATM.exe