![]() |
|
|
| |
|
||||
In software engineering, Unified Modeling Language (UML) is a non-proprietary, third generation modeling and specification language. The UML is an open method used to specify, visualize, 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 modeling large, complex systems, especially at the architectural level. UML integrates the concepts of Booch, OMT, OOSE and Class-Relation by fusing them into a single, common and widely usable modeling language. UML aims to be a standard modeling language which can model concurrent and distributed systems. UML is an industry standard, created under the auspices of the Object Management Group (OMG). OMG had called for information on object-oriented methodologies, that might create a rigorous software modeling language. Many industry leaders had responded in earnest to help create the standard. There are three prominent models of the UML system development:
It is important to distinguish between a UML model, and a UML diagram, or set of diagrams, including Use Case Diagram, Collaboration Diagram, Activity Diagram, Sequence Diagram, Deployment Diagram, Component Diagram, Class Diagram, StateChart Diagram—a UML diagram is a graphical representation of the information in the model, but the model exists independently. XMI in its current version provides interchange for the model, but not for the diagrams. UML uses a graphical notation which has text equivalents in Java and other object-oriented languages, and also ontological equivalents which are high-level enough to merit articles in Wikipedia. To show the degree of development of this language, it is possible to state concepts such as political processes in UML notation. Thus, it is possible to translate these schemas into executable programming languages. UML is not a methodology and does not force one, but it is a requisite for the Rational Unified Process.
UML specification versionsThere are several versions of UML specification. The current official version is UML 1.5 (http://www.omg.org/technology/documents/formal/uml.htm). OMG is currently upgrading UML to Version 2.0 which differs from version 1.5 very much. UML 2.0 is in finalization stage (http://www.omg.org/gettingstarted/process4-Finalize.htm) and is expected to be released soon. Many modeling tools vendors already support, up to some extent, UML 2.0 UML Use Case DiagramThis diagram describes the functionality of the (simple) Restaurant System. The Food Critic actor can Eat Food, Pay for Food, or Drink Wine. Only the Chef Actor can Cook Food. Use Cases are represented by an oval and Actors are stick figures. The box defines the boundaries of the Restaurant System, i.e. the use cases shown are part of the system being modelled, the actors are not. The OMG defines a graphical notation for use cases; but it refrains from defining any written format for describing use cases in detail. Many people thus suffer under the misapprehension that a use case is its graphical notation; when in fact it is the written description of scenarios regarding a business task which provides the true value of a use case. UML Class DiagramThis diagram describes the structure of a simple Restaurant System. UML shows is_a relationships with a triangle; and containers with diamond shape. Additionally, the role of the relationship may be specified as well as the cardinality (in the diagram above, the roles are accidentally on the wrong end of the lines --- for example, seats should be at the association end that terminates on Patrons --- see Fowler and Scott, UML Distilled, 2nd Edition, page 56 or Mellor and Balcer, Executable UML, page 214). The Restaurant System has any number of Food dishes, and one Kitchen, Dining Area, and any number of staff. All of these objects are associated to one Restaurant. (This model did not include a washroom.) UML Sequence DiagramThis diagram describes the sequences of messages of the (simple) Restaurant System. This diagram represents a Patron ordering food, eating the food, drinking wine, then paying for the food. The dotted lines extending downwards indicate the timeline. The arrows represent messages (stimuli) from an actor or object to other objects. For example, the Patron sends message 'pay' to the Cashier.
UML Collaboration DiagramUML Statechart DiagramSee Harel Statechart. UML Activity DiagramUML Deployment DiagramExtensions to UML
See also
Open Source and Free Software UML programs
Proprietary UML programs
External links
This article was originally based on material from the Free On-line Dictionary of Computing, which is licensed under the GFDL.
de:Unified Modeling Language es:Lenguaje Unificado de Modelado fr:Unified modeling language lt:Unified Modeling Language nl:Unified Modeling Language ja:統一モデリング言語 pl:UML pt:UML sv:UML uk:UML zh:统一建模语言 |
||
|
|
|
|
|
|
Copyright 2008 WordIQ.com - Privacy Policy
::
Terms of Use
:: Contact Us
:: About Us This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "Unified Modeling Language". |