04 "Mars--UML War Demand Analysis" read Note four

04 "Mars--UML War Demand Analysis" read Note four

In the previous chapter, I looked at the class diagram in the UML War requirements analysis, and in class, the teacher also mentioned the importance of the class diagram for the requirement analysis. In the software requirements analysis, it is important to: Class diagram (structure modeling is the most commonly used UML diagram), time series diagram, use case diagram. Now look at this chapter although not so important, but in the software requirements analysis also has a very important position;

It is mentioned in the book that the activity diagram is one of the most common UML diagrams that can be used to express the process, and is an important tool for behavioral modeling. There is a problem here: if we want to do a project, we have to ask ourselves a few questions: 1, when there is no application system, how the system is running (the relationship between things and things/process-related issues) 2, the application of the system, the system is how to run (from which can be seen, We do the project should be able to understand what we should do, how to do the problem) in the relationship can see the difference in the angle, it will lead to different processes.

At the beginning of the study of UML, we understand the flowchart (each diagram of the shape of living to represent their own meaning), now read the activity diagram, actually they two really like, 1, will be labeled by the shape of the state 2, are each step of the process to walk down (1, write down the Judgment statement 2, direct monitoring 3, Increase activity, judgment), 2, multi-layer Branch 3, Swimlane/partition); There will not be anything like that in the world, so the activity map will have its own characteristics: 1, the activity diagram has a fork will have convergence, and must appear in pairs (flow chart is determined by the diamond).

As can be seen from these, the activity diagram is not so commonly used, but when we are involved in the business process is very complex, I can properly decompose, if the appropriate planning, then the drawing is very simple. Like the process mentioned in the book (1 is very simple to express 15 of the process 2, emphasizing the relationship between the roles of 3, emphasizing the configuration of the various versions of the process) so, think all the pictures have their own characteristics, activity diagram of their own content, we should understand is that every project its process is what, his own start and end, user , what are the key activities, these are the most important things.

We should follow the steps, gradually learn what should be, as long as there are things exist, since there are advantages, there will certainly be shortcomings, but our activity diagram is the best tool to express complex business processes.

My method:

1, why to do this project;

2, understand what is the user, keywords and so on;

3, the process of judgment, clear trunk,

4, join the branch;

5, the optimization analysis, determine;

Problem:

1, is not all the activity diagram can understand all the flow of information;

2, the activity diagram is not on behalf of the system to let customers know everything;

04 "Mars--UML War Demand Analysis" read Note four