I have been in contact with UML for almost a month. I feel that the main function of UML is to give you a better understanding of the system you designed and design it in an object-oriented way. For tools, we have used Rational Rose, argouml, and trufun. Rational Rose with 2003, which is designed based on uml1.4, so we cannot use uml2.0 functions. Rotional rose also has the 2005 version. But it seems that it has not been cracked yet. Argouml is open-source and written in Java. It is good to use and supports uml2.0. Trufun is a UML tool designed by Chinese companies. Currently, version 2007 supports uml2.1. It looks like it was developed using Eclipse plug-ins and can be used directly without installation. The free version is also good. But not supported CodeAnd other functions. The sequence diagram and communication diagram of this tool have limited functions. It may be improved in the future. However, there may be crashes in use. It may be that the performance of my machine is too poor (Ben San 700 CPU ).
There is also experience in design. I have read <UML basics, cases and applications>, <Agile Software Development> and other books. The two books are the most impressive. I also bought the <object-oriented embedded development> book, because I mainly want to apply UML to the design of embedded systems. I feel that the use case and activity diagram are the same at the same time to form a complementary relationship. The next step is the process of determining the class. Of course, most of the process is the result of the first step. Then determine the relationship between classes. Draw a sequence chart and a state chart. Final deployment. In this process, it is an iterative process. There are relationships between various graphs. Achieve the ultimate goal through continuous refinement. It is best to discuss it in the form of multiple people, so that the considerations will be more comprehensive.
There are still some lower-level issues about using UML for embedded systems. Some aspects have been taken into account in uml2.0. We are still continuing to study this aspect. It will be more detailed next time.
