UML Interpretation (1)

zhaozj2021-02-08  284

UML Interpretation (1) Error.cao

(This article is reproduced from Software Engineering Expert Network

Www.21cmm.com)

As a strategic related factor in many company software development, we are trying to find techniques that can automatically improve software product quality, reduce costs, and reduce market update cycles. These technologies include component technology, visualization program design, modeling technology, and structured technology. At the same time, companies' business is also looking for technologies that can manage growth market share and sales complex systems. In the details, people's consensus is to solve the problem of repeated modeling. For example: physical division (splitable), synergistic, reuse, security, robustness, and fault tolerance. Also, the development of 3W (WWW), some simple products will deteriorate these modeling issues, UML is designed and produced. UML (Unified Modeling Language) is a language for the software system's products, visualization, constructing, documentation (documentation). Similarly, for commercial modules and other non-software systems, UML description is also an excellent successful establishment of the project implementation of the big and complex template. In fact, the definition of UML is just a category of UML understanding. In "Columns" I use a definition and explanation of several companies created for UML, the definition translation is inconsistent in China, this is not related, everyone first To understand, I will talk about the definition again. In response to the complexity of Chinese Chinese, I have emphasized here, "modeling" is a word to move, indicating this process of modeling, why do I want this to explain this problem? Because this word is used, it can also represent a certain meaning. I have described the three substances of UML in "Columns": System, Mothods and Processes, and the word "modeling" is described for this three substances. UML is the development of Rational Software Company and its partners, which is created on Booch, Oose / Jacobson, Omt and other methods, and a large number of companies are also based on this UML when they develop programs and products. Contains some: commercial templates (original demand description), demand management, analysis, and design, coding, and testing standards. The importance of template implementation For industrial software system development, build and innovate a template in advance, and there is a building blueprint similar to the quality. Good template is essentially for connecting a large number of project teams and stabilizing components (existing or in implementing templates and components). The complication of system growth is, it is, it is necessary to need a good template technology. This has an additional project success factor, but the essence is a strict template language standard. A template language must include: 1. Template element: basic template concept and semantics. 2. Symbol: Visual description of template elements. 3. Guiding Ideology (Design Principle): The usual words of internal communication. In the face of increasingly complex system, clarity and model have become its nature, UML is a standard that is perfectly defined and widely responded. This is selected as a component of the OO system and component-based systems. UML target starts at the beginning of UML design, we did not put it in a design language, in essence, it is to put all the people in various attic, people use UML to dialogue, maybe everyone is doing one thing It uses different programming languages, as if I have dizzy, UML is the international general language in the program design phase. UML is a standard, and the standard will not do anything, but people can customize many products with good specifications, and OMG is working to develop this standard and establish a common template for the software design area. Regarding the current "popular" XML, it is also a defined standard, but XML is more detailed in the software industry programming, but UML provides design standards for programming languages.

The most basic UML design goals are as follows: 1. Provide visual modeling languages ​​to be used and depth to allow them to develop and change those meaningful models. 2. Provides scalability and specializing mechanisms to extend software (or software model) core concepts. 3. Depending on the detailed programming language and development procedures (usually contain operating systems and tool software). 4. Provide reasonable basic understanding standards. 5. Incentive to the growing OO tool market. 6. Support high level development concepts such as collaboration, construction, template, and components. 7. Combined with the optimal exercise OMG-UML development space OMG: A organization that the Object Management organization is recognized by UML. The original narrative of this article is from the definition of UML and translation. I will not copy the things of others, so adding my narrative. Of course, my narrative doesn't have an Omg, and the academic Thai privileges are simple and in place. . I just give a thought, a thought of UML. Unified Modeling Language (UML) is first is dissolved Booch, OMT and OOSE concept. The result is single, versatility, and can be widely used for these users. Second, UML introduces packaging capable of handling existing models, an example: UML scholars are targeted by collaborative and distributed system templates, so that UML can take advantage of this area. Third, UML is dedicated to standard template language, not a standard program, although UML must be applied to the program description, experience also shows different organizations and different issues require different procedures. However, the concentrated factor is the first common template element (unified semantic) and the second for general symbols (provided to people these semantic intuitive representations). UML scholars promote a development using CASE-driven, modeling-centered and reused programs. UML Outside the UML range is a simplified and standard template instead of an universal language. This gives industries that are easy to use to design a diversified system to cover a multi-industry. Some of the main regions outside the UML range include: 1. Programming language UML is a visual modeling language, rather than extended visualization programming languages, which seems to have the necessary visualization and semantic support instead of programming language, but it can't draw a line as you change the code. UML is only mapped in the OO language family, so you can get the best two worlds (language representation and facilities). 2. Tools are based on tools and procedures, and it is necessary to build a language standardization. OMG REP initial goal is to make the coordination of tools, however, tools and their coordination are cutly relying on fixed semantics and symbol definitions, as UML is provided. UML defines a semantic element model instead of a tool interface, a storage, or running model, although these can be closed (just semantic issues). 3. Many companies will use UML as a general language for their engineering products, they will use the same UML chart type in different programs, because UML has an independence of any program, defines a standard program is not a UML or OMG. The goal. How to make UML becoming an OMG standard confirmation, an object-oriented (OO) template language initiated in the 1970s, in the late 1980s, there are different methodologists to test OO analysis and design in different approximation algorithms. Production a large number of marker templates Language, in previous 1989-1994, from at least 10 to 50. Users in numerous OO methods have been difficult to find 100% satisfaction in a template language. Together, "Method War" is started, in the mid-1990s, due to the repeated use of these methods, there is a technological merger, some of which have obvious advantages, also the head angle.

The development of UML begins in 1994, when Rational Software's Grady Booch and Jim Rumbaugh begin to commit to unified Booch and OMT (Object Template Technology) methods. At the end of 1995, Ivar Jacobson and his Objectory joined Rational and their unified work and fused and OOSE (object-oriented software engineering). As the basic scholar of Booch, OMT and OOSE methods, Grady Booch, Jim Rumbaugh, and Ivar Jacobson are excited to create a unified template language, based on the following three reasons: First, these methods are started and independent, create a development It wins through the development, excluding some atmospheres that do not have the difference and the difference without reason. Second, by defining semantics and symbols, they can bring some stable OO market space, allowing engineering to set up mature model languages ​​and tools to build more useful methods based on inheritance. Third, they hope that their collaboration can improve the above three early methods to help them capture valuable experience and problems in a very good situation that has not been mastered. They have determined four development goals in the period of unity. The system (not software) that is able to model it is OO concept. 2. Establish an external coupling and perform the same concept. 3. Expert system, inherited the confident position inherited in the complexity. 4. Creating a modeling language makes machines and people know. Booch, Rumbaugh and Jacobson efforts were issued in 1996/6 and 1990/10 released UML0.9 and 0.91 editions, in 1996, UML scholars introduced and accepted feedback from the public. When Rational's UML collection, it is dedicated to achieving the purpose of industrial standard template language. As early as 1995, Ivar Jacobson and Richard Soley decided to force the standardization of the market. At 1995/6, OMG hosted all high-level methodologists' meetings. The result is the first time to find a method standard in the world under the support of OMG. During 1996, several organizations have clearly clear UML as their business strategy, and RFP is believed to provide the response force catalyst generated by these organizations through OMG. Rational Company determines UML partners to strengthen UML1.0 through the cooperation with it. Contributions to UML1.0 are: Digital Equipment Corp, HP, I-Logix, Intellicorp, IBM, Icon Computing, MCI Systemhouse, Microsoft, Oracle, Rational Software, TI, and Unisys. This collaborative product version 1.0 is well defined, with powerful and versatile template language. Also, in 1997/1 IBM, Objectime, Platinum Technology, PTECH, Taskon, Reich Technologies and SoftEAM also separately respond to OMG. These companies joined the UML cooperation organization to contribute their talents and cooperate to reform their partner products to UML1.1 to improve 1.0 semantics and transparency contributed from new partnership. UML's status quo and future UML have no copyright and open to everyone, it is engaged in the needs of individuals, scientific groups, and identifies its priority methods. Many methodologists, organizations, and tool suppliers have been committed to developing and using it. UML establishes a simple semantic and symbol from Booch, OMT, OOSE, and some other advanced methods, and it is easy to dissolve in UML from the public and universal opinions. Two aspects of UML "Unified": First, a lot of differences that are effective, often regularly logic, and methods prior to modeling language.

转载请注明原文地址:https://www.9cbs.com/read-545.html

New Post(0)