Unified modeling language profile
(This article is reproduced from Software Engineering Expert Network www.21cmm.com)
The software engineering field has made unprecedented progress in 1995 and 1997, and its achievements exceed the sum of the achievements in the software engineering industry in the past 15 years. One of these most importantly, one of the more expensive results is the emergence of unified modeling languages (UML: Unified Modeling Language). In the world, at least in the nearly 10 years, UML will be a standard modeling language that dominates in the field of object technology. UML is completely necessary: First, dozens of object-oriented modeling languages are independent of each other, and UML can eliminate some potential unnecessary differences to prevent users; secondly, Through unified semantics and symbols, it is possible to stabilize the object-oriented technology market in my country, so that the project roots in a mature standard modeling language, which can greatly broaden the applicable scope of the software system developed and developed, and greatly improve its flexibility.
Unified Modeling Language (UML) is a language used to describe, construct, visualize, and documentation of software intensive systems.
First of all, it is also the most important point. Unified construction language combines the concepts in the Booch, OMT and OOSE methods. It is a simple, consistent, universal modeling language that can be widely used by users of the above and other methods.
Second, the unified modeling language extends the application range of existing methods. It is particularly worth mentioning that UML developers use the modeling of parallel distributed systems as UML design objectives, that is, UML has the ability to handle such problems.
Third, unified modeling languages are standard modeling languages, not a standard development process. Although UML applications necessarily use the system's development process, depending on our experience, different organizations, different development processes in different applications. For example, the development of intricate software is very interesting, but developing such software and construction strict real-time air electronic systems is very different, the latter is a major event. Therefore, we first focus on the design of the universal meta-model (the semantics of different methods), followed by establishing a general representation (providing expression of these semantics). Although UML developers will continue to advocate the use of examples to be driven to the architecture, the software development process is continuously improved, and the development process that actually designs standards is not very necessary.
