In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes

the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among the classes.

The purpose of a class diagram is to depict the classes within a model. In an object oriented application, classes have attributes (member variables), operations (member functions) and relationships with other classes.

A UML class diagram describes the object and information structures used by your application, both internally and in communication with its users.

A use case diagram at its simplest is a representation of a user's interaction with the system and depicting the specifications of a use case. A use case diagram can portray the different types of users of a system and the various ways that they interact with the system. This type of diagram is typically used in conjunction with the textual use case and will often be accompanied by other types of diagrams as well.

In software and systems engineering, a use case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal. The actor can be a human or an external system.

A use case diagram is a graphic depiction of the interactions among the elements of a system.
The purpose of a use case diagram is to demonstrate the different ways that a user might interact with a system.

In UML, deployment diagrams model the physical architecture of a system. Deployment diagrams show the relationships between the software and hardware components in the system and the physical distribution of the processing.

Deployment diagrams depict the physical resources in a system including nodes, components, and connections.

the deployment diagram describes the physical deployment of information generated by the software program on hardware components

The sequence diagram is used primarily to show the interactions between objects in the sequential order that those interactions occur.

UML sequence diagrams are used to show how objects interact in a given situation.

The Sequence Diagram models the collaboration of objects based on a time sequence. It shows how the objects interact with others in a particular scenario of a use case.

In UML, an activity diagram provides a view of the behavior of a system by describing the sequence of actions in a process.

In UML, an activity diagram is used to display the sequence of activities. Activity diagrams show the workflow from a start point to the finish point detailing the many decision paths that exist in the progression of events contained in the activity.

an Activity diagram focuses on the flow of activities involved in a single process.