1. Unified Modelling Language
Component and Deployment Diagrams

2. Component Diagram

3. What is a component?
A software component is a modular part of a system
It is the software implementation of one or more classes
Provides interfaces to other components
In UML 1.x, a component represented implementation items, such as files and executables
In UML 2.0 components are considered encapsulated units within a system or subsystem that provide one or more interfaces
The physical items that UML1.x called components are now called "artifacts" in UML 2 - an artifact is a physical unit, such as a file, executable, script
Components can be flexibly REUSED and REPLACED

4. Component Diagram
A component diagram shows the various high-level components in a system, and their dependencies

5. Component Diagram Notation in UML 1.x
This is also supported in UML 2.0

6. Component Diagram Notation in UML 2.0 – different possible notations

7. Modeling a component's interfaces (1)
A provided interface
Characterize services that the component offers to its environment
A required interface
Characterize services that the component expects from its environment
Two notations for representing the interfaces

8. Modeling a component's interfaces (2)

9. Example (UML1.x) Component diagram for the "Courseware Management System "

10. An Example (UML 2.0)

11. Deployment Diagram

12. Deployment Diagram
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
This diagram is more useful when a system is built and ready to be deployed

13. Deployment Diagram vs Component Diagram
While components provide the application functionality, the deployment diagram elements provide the necessary environment for the components to execute in
Components can also be shown on a Deployment diagram to show the location of their deployment

14. Elements of a Deployment Diagram
Element and its description
Symbol
Node: The element that provides the execution environment for the components of a system. Depicted by a cube with the name of the object in it, preceded by a colon, and underlined.
                                    
Connection: Similar to the relation/association used in class diagrams to define the interconnection between nodes.
                                                

15. Example 1

16. Example 2

17. Example 3

18. Artifact
An artifact is a classifier that represents some physical entity, a piece of information that is used or is produced by a software development process, or by deployment and operation of a system

19. An example of deployment diagram for Apple iTunes

20. Point to Remember
There is no substitute to experience in order to master UML diagrams. As you build more and more complex systems, you will evolve your skills and gain a deeper understanding and varied ways to utilize the power of UML diagrams

21. References
examples.html
The following link contains an example of an online shopping application and provides use case, sequence, communication, component and deployment diagrams
example.html