Software engineering -UML flow chart &; Activity diagram

Let's start with a picture searched by Baidu. As follows, if we want to manage the following data through software. What are we going to do?

Define and name the software and know what we are going to do. Making software is like writing an article. A good article must have a clear central idea, and a good software must have clear business functions.

Activity diagram/flow diagram, here it begins to play its first function: to clarify the business scope and help identify the system boundary.

In other words, we make clear what we want to do and what we shouldn't do through the business flow chart. Software is a process of deep digging, and small is big; This process is too similar to writing an article.

The same picture is Baidu:

This is a non-standard flow chart. Let's learn the basic concepts here.

Flowcharts are process-oriented and are used to describe algorithms or business processes.

This kind of flow chart is not good, so we add various controls and operations to the flow chart to make it more suitable for expressing reality and process-oriented way. Swimming lane is one of the "heavy weapons"

Another non-standard activity diagram of Baidu:

The introduction of swimming lane is the most obvious point of transforming activity diagram into object-oriented diagram.

Swim lane->; Responsibility of the object.

We can know which character did what by swimming lane.

Now, another dimension diagram has been added to the lane diagram: