Introduction to Unified Modeling Language

Introduction to Unified Modeling Language
(This article is reproduced from the software engineering expert network www.21cm.com)

The software engineering field has made unprecedented progress from 1995 to 1997, and its achievements exceed the total achievements in the software engineering field over the past 15 years. One of the most important and epoch-making achievements is the emergence of the Unified Modeling Language (UML: Unified Modeling Language. In the world, at least in the last 10 years, UML will be the leading standard modeling language in the field of object-oriented technology. Using UML as a unified modeling language in China is completely necessary: first, dozens of object-oriented modeling languages are independent of each other, however, UML can eliminate potential unnecessary differences to avoid user confusion. Secondly, it can stabilize China's object-oriented technology market through unified semantics and Symbol Representation, the project is rooted in a mature standard modeling language, which can greatly broaden the application scope of the developed software system and greatly improve its flexibility.

Unified Modeling Language (UML) is a language used to describe, construct, visualize, and compile software-intensive systems.

First, it is also the most important thing. The Unified Modeling Language integrates the concepts in booch, OMT, and OOSE methods, it is a simple, consistent, and universal modeling language that can be widely used by users of the above and other methods.

Secondly, the Unified Modeling Language extends the application scope of existing methods. It is particularly worth mentioning that UML developers take modeling of parallel distributed systems as the design goal of UML, that is, UML has the ability to deal with such problems.

Third, the Unified Modeling Language is a standard modeling language, rather than a standard development process. Although the application of UML must be based on the system development process, different development processes are required for different organizations and application fields based on our experience. For example, developing complicated software is very interesting, but developing this software is very different from constructing a strictly real-time avionics system, the latter is a major event of life. Therefore, we first focus on the design of General meta-models (to unify the semantics of different methods), followed by the establishment of general notation (to provide Visualized Expression of these semantics ). Although UML developers will continue to advocate the software development process from case-driven to architecture-centered, which is repeatedly improved and constantly added, it is not necessary to design a standard development process.