UML drawing summary

Labels: uml visual object-oriented data center charging system

The nine types of images have finally been drawn, and they have been entangled for a while. Fortunately, it is done. Although there are still some shortcomings, it is finally defeated. The following describes the drawing process.

  I. Use case diagram

The first UML diagram should be a use case diagram. This is the prerequisite for drawing. It is analyzed based on the user's needs and functional requirements, and is the basis of the entire drawing phase.

The first is the top-level graph, which is expanded based on different levels.

      

There is another question: Some people say that the student has little to do with the system and does not need to be directly associated with the user. I have some questions about this point of view, because users need to pass students on the basis of management. If you have a better idea, you can discuss it...

  II. Static graph

Static graphs mainly include class graphs and object graphs. There are a lot of problems when you draw a class image. Remember to hear it clearly when you watch the video, but when you do it, you can't do it. Is it necessary to find a noun in the video and then filter it? I feel a little unreliable and too troublesome. Therefore, I still use my previous use case diagram to divide modules and then refine them. In fact, a class chart is similar to a use case chart. A class chart abstracts a class based on the use case chart and finds out the relationship between them.

After the class picture is finished, the object graph is easy to draw. The object graph is actually an instantiation of the class graph.

       

   3. Behavior diagram

       1. Status chart

          

This is the status chart for students to go on and off the machine. I still remember that the figure at the beginning was a hundred errors, with incorrect conditions. In addition, the synchronization entries were not used, but were verified one by one, resulting in a large figure, not beautiful. After receiving a reminder from the master, I thought of synchronization.

      2. Activity diagram

This is part of my activity diagram. I have painted all the processes of the entire system in one diagram. It seems like a mess, so I should keep the sub-module picture, this will make people look comfortable, and at the same time, it is easy to clarify their own ideas. The only thing I don't quite understand about this part is the swimming track. In fact, it is too difficult to search for materials from time to time, that is, to classify the same operation to make the picture clearer and clearer.

        3. Interaction diagram

Sequence diagram:

             

Collaboration diagram:

          

Remember to draw the sequence chart according to the system process, but do not pay attention to the returned line. When the master accepts the request, the system reminds the sequence diagram that a few lines should be input to return several lines. This ensures that each input can be returned to the user and avoids dumb operations. Another thing to note is the extinction.

Sequence and collaboration graphs can be converted to each other (shortcut key F5). These two graphs actually describe one type, but emphasize different objects, the sequence diagram emphasizes the interaction sequence between objects, while the collaboration diagram emphasizes the cooperative relationship between objects.

       4. Implementation diagram

Component diagram:

The component diagram is the physical structure of the component, so it seems that the diagram is not too accurate. When searching for information, it is found that some files are of the exe or dll type, which is not too understandable. Therefore, we will draw a picture based on our own ideas for the time being and refine it when there is more contact.

 

  Summary

UML diagram is a graphical description of the system, which helps us understand all aspects of the system. At the same time, the drawing process can deepen our understanding of the problem and the comprehensive understanding. Just like life and study, we can only learn from different aspects after we practice in person and continue to practice and contact, in order to deepen our understanding depth and understanding proficiency. Although what we are currently engaged with is fundamental, the truth is that we have benefited a lot. Continue to work...

Tip: You don't know how to start at the beginning. It doesn't matter. You can draw pictures based on your own ideas and understanding, and then modify and process them by searching for information. Never view others' pictures directly, so you can easily lose your thoughts.

UML drawing summary