Class digraphs are graphs describing classes, interfaces, collaboration, and relationships between them.
A class diagram is a part of a static view in the system. A static view can contain many class diagrams.
Static views are used for Structural Modeling of the software system. They construct the vocabulary and relationships of the system, and the visualization of structural models is achieved through class diagrams.
A class chart consists of the following basic elements: Class, interface, collaboration, and relationship (dependency, generalization, implementation, and Association ).
The following uses a diagram to summarize the basic content of a class chart:
Class diagrams are usually used in one of the following three methods:
1. Vocabulary modeling of the system
Building a system with UML usually starts from the basic vocabulary of the system and is used to describe the boundaries of the system. That is to say, it is used to determine which abstractions are part of the system to be modeled, which abstractions are outside of the modeling system. This is a very important task, because the most basic elements of the system are determined here. Class diagrams can be used to describe abstraction and their responsibilities.
2. Simple Collaborative Modeling
In the real world, most things are interrelated and affect each other. This is also true after these things are abstracted into classes. Classes in the software system to be constructed are rarely isolated. They always work together with other classes to achieve semantics stronger than a single class. Therefore, After abstracting system words, system analysts must visualize and detail the ways in which these words work collaboratively.
3. logical database mode Modeling
When designing a database, we usually use the database mode to describe the concept design of the database. Database mode modeling is a blueprint for the database concept design. You can use class diagrams to model the modes of these databases.