Component Diagram

The component diagram's main purpose is to show the structural relationships between the components of a system 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 (e.g., software libraries) in the system 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

Component Diagram (Whitten)

Component Diagrams are implementation-type diagrams that are used to graphically depict the physical architecture of the software of the system. A single software component often implements a group of classes that form a cohesive subset of the system. Component diagrams can be used to show how programming code is divided into components and to depict the dependencies between those components

Component Diagram

Component Diagram

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 The notation in a deployment diagram includes the notation elements used in a component diagram, with a couple of additions, including the concept of a node. A node represents either a physical machine or a virtual machine node

Deployment Diagram (Whitten)

Deployment Diagram are implementation-type diagrams that describe the physical architecture of the hardware and software in the system. They depict the software components, processors, and devices that make up the systems architecture

Deployment Diagram