UML object-oriented analysis and its diagrams and modeling steps

Content Overview

1. describes the design process of Object-Oriented Analysis Based on UML.

2. What charts and the functions of each diagram are included in the UML object-oriented model?

1. describes the design process of Object-Oriented Analysis Based on UML.

1. Identify system use cases and Roles
First, conduct a Demand Survey on the project. Based on the business flow chart and data flow chart of the project and the operation personnel at all levels involved in the project, identify all use cases and roles in the system through analysis; next, analyze the relationship between roles and use cases in the system, use the UML modeling tool to draw a system use case diagram, and sketch the concept layer model of the system, use a UML modeling tool to describe the conceptual layer class diagram and activity diagram.

2. Perform System Analysis and abstract the class
The task of system analysis is to identify and describe all requirements in the system, and establish a specific domain model. The establishment of a domain model helps developers evaluate use cases, extract classes from them, and describe the relationships between classes.

3. Design classes and behaviors in the system and system
The design phase consists of structural design and detailed design. ① Structure design is a high-level design. Its task is to define the package (subsystem), including the dependency between packages and the main communication mechanism. The package is used to describe the logical components of the system and the dependencies between each part. ② The detailed design is to refine the content of the package, clearly describe all classes, and use the dynamic model of UML to describe the behavior of instances of these classes in a specific environment.

Ii. What charts and the functions of each diagram are included in the UML object-oriented model?

UML includes nine types of diagrams: use case diagram, class diagram, object diagram, state diagram, sequence diagram, collaboration diagram, activity diagram, component diagram, and configuration diagram.

[1]Use case diagram (usecasedi.pdf)
It is the simplest and most complex diagram in UML. The use case diagram shows the roles and use cases and their relationships. The use case diagram describes a functional unit provided by the system. The purpose of the use case diagram is to help the development team understand the functional requirements of the system in a visualized manner, including "Roles" based on basic processes (actors, other entities that interact with the system) relationship and the relationship between use cases in the system.

[2] classdigraphs)

A class chart shows how different entities (people, things, and data) are related to each other. In other words, it shows the static structure of the system.

[3]Object Graph
In UML object-oriented model, an object diagram is an example of a class diagram. It describes the object and the relationship between objects, and almost uses the same identifier as a class diagram. They differ in that the object graph shows multiple object instances of the class, rather than the class of the instance. An object graph is an instance of a class graph. Because the object has a lifecycle, the object graph can only exist in a certain period of time in the system.

[4]Status chart
Describes the dynamic behavior of an object based on event response, and shows how the object reacts to different times based on the current state. A uml state chart is usually created to study the complex behavior of classes, roles, subsystems, or components for the following purposes. Some people may argue that every class has a state, but not every class should have a state chart. The status chart is described only for "interested" status classes (that is, classes with three or more potential States during system activity.

[5]Sequence Chart
A sequence diagram describes the dynamic interaction between objects and focuses on the time sequence of message passing between objects. A Sequence Chart consists of a group of objects. Each object has a vertical line, called the lifeline of an object. It represents the timeline and the time is stretched down along the vertical line. The sequence diagram shows the call relationships between different objects in the process, and shows different calls to different objects in detail. The sequence chart has two dimensions: the vertical dimension displays the message/call sequence in the order of occurrence, and the horizontal dimension displays the object instance to which the message is sent.

[6]Collaboration Diagram
UML object-oriented co-drawing is used to display the spatial organizational structure of components and their interaction relationships. It does not focus on the interaction sequence. The collaboration diagram shows the organizational interaction between objects and the links between objects in the interaction. The collaboration diagram emphasizes the interaction diagram of the structure of the objects that send and receive messages. Purpose of a collaboration diagram: describes a specific scheme by describing the movement of messages between objects. Displays the organizational structure of the object and its interaction relationships, rather than the interaction sequence.

[7] activity diagram (activitydigoal)

In UML object-oriented, the UML activity diagram records the logic of a single operation or method, a single user case, or a single business flow. Describes the execution sequence of various activities in the system. It is generally used to describe the execution process of each activity in an operation. At the same time, it is often used to describe the processing process of a case or an interactive process. An activity diagram consists of activities that are described at the same time. After an activity is executed, the control moves along the Control Transfer arrow to the next activity. In the activity diagram, the transfer control conditions and parallel execution requirements can also be easily described.

[8] componentdigraphs)

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 various 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. The main purpose of a component diagram is to display the structural relationship between system components.

[9] configuration Diagram

The configuration diagram in UML object-oriented describes the physical configuration and system architecture of hardware and software in the system. In the configuration diagram, nodes are used to represent the actual physical devices, such as computers and various external devices, and the corresponding nodes are connected according to the connection relationship between them, and describes the connection method. In the node, describe the executable components or objects assigned to the node, and describe which software units are allocated to which nodes to run.