<I posted the original article in The colorshop on>
I have always thought that UML is the statement of SA. Only sa should be familiar with UML, so I only have the concept of class digoal ratio ‧
Recently, I was busy handing over the program to other colleagues because I was about to renew the program. The whole program also ran for several times and showed it to my colleagues, the schema and relation of the database are also parsed at the same time, and files are also left behind. I also have regular expressions in the Common Program, leaving unknown solutions ‧
It seems very difficult, but my colleague said to me, "If a bug occurs, I still don't know where to change it ...』
In fact, he did not say anything. I would say the same thing if I ran his program ‧
I should leave use case digoal to describe the architecture of the entire program in the form of a huge volume ‧ and then use sequence digoal, describe the network elements and components that the entire process will pass... when a program has a bug, as long as he looks at the sequence digoal, he will be able to fix the bug with a single knife, rather than killing the trace program, after all, this is the last and most effective tactic ‧
So I really want to learn UML well. It's not just about file transfer. I heard my colleagues say that when I use UML, I can help the object forward analysis, this is also the case that the big metric of OOA/D should be used to develop the UML standard ‧
The computer has no experience in computer engineering, and most of them do not have the concept of files, I want to bring the concepts of UML and software engineering into the computer domain. No matter whether it is a development-in-style system or a development-driven program, I want to use the UML license file for myself, my classmates, and my colleagues. Instead of every time I hand over other programs, I have to start with the trace program ‧