Learning and using UML

After learning UML and RUP for a long time, it seems that everything is confusing. Then I began to look for the reason: do you think there are any cool people? Have you received system training? The company does not apply the conditions. For example, the time cannot be used? Is there a lot of companies in China ?......

I attended the Microsoft vs2005 meeting and chatted with the Microsoft Senior friend about support for the development process and modeling ideas in vs2005. He said, "You have a profound problem, this is a problem with the product line ". Then, he said: In a private identity, Microsoft rejects (or is not advocating, not supporting, or optimistic) UML, because Microsoft advocates rapid development, the idea of UML is too long, and Microsoft is not very familiar with UML. [Do not give full play to the principle of this old man]

At that time, there was a strong feeling. So naturally, UML may not be necessary. If you look at Microsoft, it is useless to use UML. Who can say that he is not doing well? Next, I thought that UML has its own problems in its popularization and application as imagined, because it contains too many confusing and obscure concepts and ideas, there is no need to figure it out unless you study it. I have seen a lot of posts about system and business use cases, about how to write quarrel cases (which is the most controversial), composition or aggregation, and so on. When do you say you have to wait for so many people to figure out how to do the software? So the attitude towards UML was quite negative, and I felt that UML was a bit idealistic and not practical enough.

Then, after listening to the Open Class class of umlchina Pan Jiayu, he told him about Microsoft's attitude. He immediately said, "Who said? They asked me to give lectures at the beginning of this year. He said: we are talking about this kind of thinking. No matter what software is used, he has to consider the interaction between objects and the state of objects. UML may be swallowed up or lost by other methods in the future, but this idea must exist. As software grows and becomes more and more complex, the human brain cannot cope with the problem. These methods must be used to analyze the problem.

So often, we have a more objective understanding of this problem: UML is just a stage people are pursuing to solve software modeling problems. Don't argue whether it is the best. If you only want to solve practical problems, you can use it. To some extent, it is the best at present, but it does not mean it is perfect, it still needs to be improved or innovated!