UML has been applied in many places in China. This should be said to be a good thing, but we also see behind that this application is not a calm speculation and heel, UML has become a formalism in many times. In fact, the main purpose advocated by the UML itself is very good. It guarantees the exchange language between programmers. The tools such as RUP also guarantee the normative nature of the software development process, strictly guarantee the development and design phase of the first design. Have an informative standardized documentation, etc. Next, we have to see how the current UML boom is produced? Why does there be formalism? What problems exist in the tools such as RUP. The first is that almost all UML tools are very difficult, unrestrained, not intuitive, and more inconvenient, and it is also difficult to conduct synchronous maintenance in the project. Many projects are basically commercially available in formalism in the formalism in many projects. In fact, the UML itself is a norm, and the purpose of the standard itself is to better exchange communication and better design quality. In fact, the development of UML has deviated from these more basic purposes. I advocate simple is beautiful, the most traditional flow chart can understand (or even programmers), what about UML now? Too much is not considerate enough, it is too abstracting and formulating. I want to have new and more similar things in the future, replacing backward, redundant and closed UML. I personally advocate simple is beautiful ... The second question is that the current programmer is not enough. UML itself is basically the object-oriented software design idea, there is not enough OO design capabilities, it is difficult to really need UML category design tools to express their design intentions. This point is not exaggerated. In fact, some people OO theory is very strong, but truly in practice, it is often over-designed, or the design itself is extremely imbalance, and the project development has been changed to research experiments and experiment. In addition, some people trust their own hands-on ability, often neglect the design link, and basic projects have been in repeated and turmoil. These programmers do not give them a period of time learning and practice. It is difficult to become a mature designer. Before basically mature, UML will be a formal thing, there will be no strong meaning. Andrei once said that the programmer will be mature until the age of 35, and the codec may be in 20 years old. This sentence has probably has the meaning of "design itself is a very experienced work". The third issue is a propaganda misleading of a few social levels. India Haiguheng, foreign company employees, IT translation author and publishing house, vocational training institutions, etc. are in their respective experience, purpose and reasons, most people completely deviazely from reality blindly, even almost one side think UML is software engineering. The foreign company's application UML is actually not successful, but they have a mature training system, so they have a certain degree to make up for UML too embarrassing weaknesses. As a mastery of foreign companies, there are some welcomed UMLs that may compare them. The purpose of the Indian sea is not to say more. Many of the people who trains and transfers are larger than the actual composition. They need to advocate UML, but they will find better things in the morning and evening to give up the advocacy of UML. In fact, some people have begun to consider this. The fourth problem is that a few programmers are very dependent on the automatic code framework, which is actually a key issue that is not UML. In order to use certain tools, they do not conform to the code of Chinese reading habits, and they are willing to give up everything else. For them UML is just a code generation tool, so they don't have much value, and compare formulations. The fifth problem is the problem of project resources. The actual domain of domestic projects is very limited, and if the developers of other foreign companies have to see whether the development cycle is still ridiculous, it is ridiculous. UMLs should actually run through, rather than only in the original design phase, should also run through the entire project group, including design, management, development, and test all people should apply it.
