A part of IOV cc's work

 

A use case diagram consists of the main character, use case, and the relationship between them. This figure shows the relationships in the use case model.

The use case diagram shows how the use cases interact with each other and the same use case participants. Use Case Diagrams are used to visualize the behaviors of systems, subsystems, or classes, so that users can understand how to use these elements and enable developers to implement these elements.

For details, click me

Class digraphs display the static structure of the model, especially the internal structure of classes and classes in the model and their relationships with other classes. The class chart does not display temporary information.

For details, click me

For more information about the package chart, click me.

Why do you want to create a package chart? Click I

Activity diagram (dynamic diagram) is a workflow that clarifies the implementation of business use cases.

For details, click me

 

A sequence diagram is a two-dimensional diagram that represents interactions. The vertical line is the timeline, and the time goes down along the vertical line. The horizontal axis represents the class meta-roles of independent objects in the collaboration. The class meta-role is represented by a lifeline. When an object exists, the role uses a dotted line. When the object is activated, the lifeline is a dual line.

For details, click me

A deployment diagram (deployment divisor) is used to display the physical architecture of software and hardware in the system. From the deployment diagram, you can understand the physical relationship between software and hardware components and the component distribution of processing nodes. The deployment diagram shows the structure of the runtime system and the configuration and deployment modes of the hardware and software elements that constitute the application.

For details, click me

A component diagram is used to reflect the physical structure of the Code. From the component diagram, you can understand the compiler and runtime dependencies between software components (such as source code files or dynamic link libraries. You can use a component diagram to divide the system into cohesion components and display the code structure.

For details, click me