Unified Modeling Language
A set picture of UML figure
Unified Modeling Language (UML) software is a standardized general-purpose modeling language of the field of engineering. The standard is created by the management of the object management and is handled by this.
UML software incorporates a set of graphical notation techniques to create visual models of the enhanced system.
Analysis
Unified Modeling Language (UML) is used to describe, adapt, construct, and document the artifact of an object-oriented software intensive system under development. UML provides a standard way of looking at the architectural framework of a system, which includes the following elements:
UML combines the best techniques from data modeling (entity relationship diagram), business modeling (work flow), object modeling and component modeling. In the life cycle of software development and across various implementation technologies, it can be used with all processes. UML synthesized their notation by adding booch method, object modeling technique {OMT} and {0} object-oriented software engineering (OOSE) as a normal, single, and more usable modeling language. The purpose of UML is to create a standard modeling language that can model concurrent and delivery system. UML is a real industry standard and is under the auspices of the Object Management Group (OMG). OMG initially sought information on object-oriented methods that could make a harsh software modeling language. Many industry leaders have responded to help in making the UML standard.
UML models can be automatically converted to other reports (such as Java) through QVT-like conversion languages, supported by OMG. UML is extensible and offers the following mechanisms for optimization: Template and Image. The semantics of expansion through profiles have been improved with UML 2.0 major modification. History History of object-oriented methods and notation. 1.x Before UML
Rational software corporation became the source of today's two most popular object-oriented modeling approaches, after renting services of James Roombog from General Electric in 1994: The OMT of Roombog, which is the object It was better for Oriental Analysis (OO), and Gruchy Booch's BOOP method, which was better for object-oriented design (OOD). In his efforts, he received help from Iver Jacobson, the creator of object-oriented software engineering (OOSE). JackBusan took charge of Rational in the year 1995 after taking possession of Company Objector AB Rational. The three mechanisms were collectively known as Three Amigos, because they used to be often used to argue about the practice of behavioral practice.
In the year 1996, Rational saw that the abundance of modeling languages was slowing down the rate of adoption of object technology, thus rearranging the work in a unified manner, they gave three amigos a non proprietary Unified Modeling Assigned the task of developing the Language The representatives of the Competitive Object Technology companies were consulted during the OPSLA '96 (OOPSLA '96); He selected boxes to show the categories instead of the Grade Bouch's marking method of method, in which the clouds were used. In the technical leadership of
Three Amigos "to complete the Unified Modeling Language (UML) classifications and to offer it as an answer to the OMGRPP, in the year 1996, UML Partners , An UML Partners' UML 1.0 classification draft was proposed to OMG in January 1997. In the same month, UML Partners, of Chris Cobarayan In the Administration of Vision and Ed Aykholt formed a semantics task force to finalize the semantics of classifications and integrate it with other standard efforts. The result of this work, UML 1.1, was released in August 1997 by OMG Was presented and it was adopted by OMG in November 1997. They 1.x UML
As a modeling notation, the effect of OMT notation dominates (e.g., the use of rectangles for classes and objects). Although the Booch "Cloud" marking was removed, the ability to specify the bout's low-level design report was embraced. Usage case marking from Objective and component marking with bouch were organized with other signals, but Semantics integration was relatively weak in UML 1.1 and was not actually fixed until the UML 2.0 major modification was fixed.
With many other OO approaches, the concepts were grouped jointly with UML, with this objective, UML will support all OO methods. As soon as the group tried to ensure comprehensive coverage in the real-time system domain, many others also contributed, whose access, "Object-Oriented Structured Design (OOSD)" notation of Tony Wassermann and Peter Russell ), Today with the "System Design with Ada" of Ray Bahar, Archie Bowen's use case and timing analysis, data analysis of Paul Ward and "Statchart" of David Harel. He reflected on many models. As a result, UML is useful in many varieties of engineering problems, single process, concurrently with single user applicability, distribution system, which enrich UML but also bigger.
Unified modeling language is an international standard: ISO / IEC 19501: 2005 Information Technology - Open Distributed Process - Unified Modeling Language (UML) Version 1.4.2 2.0 Development towards UML
UML has matured significantly since UML 1.1. Many minor modifications (UML 1.3, 1.4 and 1.5) corrected the drawbacks and bugs of the first version of UML, after which UML 2.0 major modification was accepted by OMG in 2005.
The UML 2.x specification has four parts:
The current versions of these standards follow UML Superstructure version 2.2, UML Infrastructure version 2.2, OCL Version 2.0 and UML Diagram Exchanges Version 1.0.
Although many UML tools support some of the new features of UML 2.x, OMG does not provide any testing place to test compliance normally with their specifications. Unified Modeling Language Theme Software development methods
UML is not a growing method in itself, however, it was designed to be compatible with the key objectives of its time in terms of software development methods (for example OMT, Booch Method, Objectory). Since UML has evolved, some of these methods have been re-molded to take advantage of new marking and new modes have been built on the basis of UML. The best known is the IBM Rational Unified Process (RUP). There are many other UML-based methods such as the condensation method, the dynamic system development method, and others designed to provide more specific solutions, or to achieve various objectives. Modeling
It is very important to differentiate between the set of images and the UML model of a system. A diagram is a partial graphical representation of a system's model. The model also contains a 'post-semantics backstage' - documentation type written in the form of documents that give power to model elements and diagrams.
UML diagrams represent two different ideas of a model system.
Using the XMI exchange format, UML models can be swapped between UML devices. Picture overview
UML 2.2 has 14 types of pictures which are divided into two categories. Seven diagram types show structural information and other seven general types of behaviors show, four of which show different aspects of the conversation. This image can be categorized as shown in the following category picture:
UML does not limit UML element type to a certain diagram type. Generally, every UML element can appear on almost all types of images, this flexibility is partially restricted in UML 2.0. UML profiles can define additional diagram types or extend existing pictures with additional marking.
In view of the tradition of engineering drawing, a comment or article is allowed in the UML diagram to clarify the use, constraint, or intent. Structure diagram
Structure diagrams emphasize what will happen in the modeled system.
Since structure pictures represent the structure of a system, they are used extensively for documenting the architecture of the software system. Behavioral picture
Behavioral painting emphasizes what should be done in the system to be modeled:
Because behavioral pictures describe the behavior of a system, they are used extensively to describe the functionality of the software system. Contact picture
A contact picture, a subset of behavioral pictures, which emphasizes the flow of data and control between things to be done in the model:
Protocol state machine is a sub-version of a state machine. This can be used to model a network communication protocol. Meta modeling Description of the Meta-Item Facility
Object Management Group (OMG) has developed a meta-modeling architecture named Meta-Object Facility, to define Unified Modeling Language (UML). The Meta-commodity facility is a standard for model-driven engineering, designed as a four-layer architecture, as shown in the image given on the right. It offers a meta-meta model named M3 layer, at the top level. This M3 language is being used by meta-object facility to create a metamodel called M2 model. The most prominent example of a layer 2 meta-object feature model is UML, a model that describes itself as UML. This M2 model describes the elements of the M1 layer and thus the M1 model. These, for example, will be models written in UML. The last layer is the M0-layer or the data layer. It is used to describe real world objects.
The Meta-Object Facility beyond the M3 model, describes the design and manipulation of metamodels and models defining the COBRA interface, which describes those operations. Due to the similarity between the Mentor-Object Facility M3-model and UML structure model, Meta-Object Facility Meta Models are usually modeled as UML class diagrams. XMI is a support standard of the Meta-Object feature, which defines an XML-based exchange format for modal on the M3-, M2- or M1-layer. Criticisms
Although UML is a widely recognized and used modeling standard, it has often been criticized for: Standard bloat In a satirical essay prepared for the request of changing the grade of a student, Bertrand Mayer criticized UML as being unrelated to the Object-oriented development software in 1997; Later a disclaimer was added, indicating that his company still supports UML. Ivar Jacobson, a co-architect of UML, said that the protests on the size of UML 2.0 are valid for considering the application of the intelligent agent problem. It includes many unnecessary or less used images and compositions. Problems learning and adopting Problems described in this section become complicated in learning and adopting UML, especially when it comes to pre-requisite engineering engineers. In practice, people often draw sketches with the symbol given in their CASE tool, but without the meaning that they are made symbols for the purpose of making available. Linguistic incoherence Writing of UML standards itself as a result of being a non-native English speaker - seriously reduces their standard value. Standards have been widely quoted in this regard, and in fact, they have been clamped as the main example of the obscure geek speaker. Cumulative impedance / impedance mismatch As with any marking system, UML can represent some systems in a more precise or more efficient way than others. Thus, a developer is attracted towards the solution that remains on the intersection of UML's capabilities and implementation language. If the implementation language does not follow conservative object oriented theory, then this problem is especially pronounced because the intersection established between UML and the implementation language can be quite small. Useless exchange format While XMI (XML Metadata Return) is designed to facilitate the exchange of standard UML models, it has been largely ineffective in the practical exchange of UML 2.x models. Two causes of this interoperability failure are reported. First, 2.x XMI is bigger and complex in its own right, as it wishes to address a more technical problem than the UML 2.x model exchanges. In particular, it attempts to provide a system to facilitate the exchange of any unitary modeling language defined by OMG's Meta-Object Facility (MOF). Second, there is a lack of enough information to facilitate reliable exchange of UML 2.x marking between modeling tools in the UML 2.x diagram regulation specification. Since UML is a visual modeling language, this reduction is fundamental for those modelers who do not want to repaint their diagram.
Modeling experts, including Brian Henderson-Sellers, in the "UML: The Positive Spin", and "Usage and Abuse of the Stereotype Mechanism in UML 1.x and 2.0" by Brentand Meyer, have written UML's severe criticism. Read further
wiki
Comments
Post a Comment