Unified Modeling Language


Also found in: Dictionary, Acronyms, Wikipedia.

Unified Modeling Language

(language)
(UML) A non-proprietary, third generation modelling language. The Unified Modeling Language is an open method used to specify, visualise, construct and document the artifacts of an object-oriented software-intensive system under development. The UML represents a compilation of "best engineering practices" which have proven successful in modelling large, complex systems.

UML succeeds the concepts of Booch, OMT and OOSE by fusing them into a single, common and widely usable modelling language. UML aims to be a standard modelling language which can model concurrent and distributed systems.

UML is not an industry standard, but is taking shape under the auspices of the Object Management Group (OMG). OMG has called for information on object-oriented methodologies, that might create a rigorous software modelling language. Many industry leaders have responded in earnest to help create the standard.

See also: STP, IDE.

OMG UML Home.

Rational UML Resource Center.

UML

(Unified Modeling Language) An object-oriented analysis and design language from the Object Management Group (OMG). Many design methodologies for describing object-oriented systems were developed in the late 1980s. UML standardizes several diagramming methods, including Grady Booch's work at Rational Software, Rumbaugh's Object Modeling Technique and Ivar Jacobson's work on use cases.

There are twelve diagrams supported under UML. Four are structural, five are behavioral and three are used for model management, which include packages, subsystems and models. See XMI.

Structural Diagrams
The four structural diagrams are class, object, component and deployment. Following is an example of the class diagram:


Class Diagram
This is one of the structural diagrams. User, User Terminal and Server are three classes that have attributes and operations. An actor is a UML "stereotype" that is external to the system. Lines between classes are "associations." The asterisk means "many," in this case, a many-to-one relationship between client and server.







Behavioral Diagrams
There are five behavioral diagrams: use case, sequence, activity, collaboration and state chart. Following are examples of all but the activity diagram:



Use Case Diagram
This diagram shows a system's functions from a user's point of view, which in this case is pretty simple. All the following diagrams were created in the Telelogic Tau UML suite by Telelogic for this same example. Five of the nine possible diagrams available in UML are shown below. The Component Diagram (software module interaction), Deployment Diagram (hardware nodes) and the Activity Diagram (tasks) are not included. The Object Diagram (instantiations of classes) is rarely used. (All diagrams courtesy of Telelogic, AB, www.telelogic.com)








Sequence Diagram
Like an MSC (Message Sequence Diagram), the Sequence Diagram depicts the message flow between entities in the system. The items between double left/right arrows are UML "stereotypes." See MSC.








Collaboration Diagram
This diagram emphasizes the structure of the relationships between entities. Note that the user is associated with the user terminal in a session, and the terminal is associated with the server in a connection. The order of messages can be read by interpreting the numbers prefixes.








State Chart
This describes the finite states that take place in the system. The rectangles are the states, and the lines between them are the transitions. The connection state shows three substates. The single circles are starting points, and the double circles are the ends.
Mentioned in ?
References in periodicals archive ?
[2] OMG, OMG Unified Modeling Language (OMGUML): Superstructure, Version 2.3,2010, http://www.omg.org/spec/UML/2.3/Superstructure/
The most popular modeling tools are Petri Nets (PN) (Dicesare et al., 1993; MengChu Zhou & Zurawski R., 1995) and Unified Modeling Language (UML) (Booch et al., 1999).
Additionally, it introduces the LabVIEW Statechart Module for higher-level designs to run on targets including FPGAs, real-time systems, PDAs, touch panels and a variety of microprocessors, via add-on functionality giving engineers an alternative to designing systems with a high-level diagram based on the Unified Modeling Language (UML) standard.
New features include automatic generation of logic and code, such as analog and digital measurements with direct memory access using a configuration-based FPGA project wizard; high-level design using a statechart approach based on the Unified Modeling Language specification with the Statechart Module; new intellectual property for multichannel operations including PID control for more efficient FPGA gate usage; and simulation of FPGA functions on windows before compiling for FPGA targets to speed design.
The object-oriented real-time image processing software was developed by using Unified Modeling Language (UML).
The generally accepted best practice for translating system requirements into a system model is through the use of the Unified Modeling Language (UML).
Business process management provides process diagrams that are drawn using standard notations such as Unified Modeling Language and Business Processing Modeling Notation.
The comprehensive contents of this book is arranged in nine different chapters, each describes the design as well as other database technologies such as Unified Modeling Language, business intelligence etc.
The Unified Modeling Language, Second International Conference, volume 1723 of Lecture Notes in Computer Science, pages 32-48.

Full browser ?