World Library  
Flag as Inappropriate
Email this Article
 

Unified Modeling Language

UML logo

The Unified Modeling Language (UML) is a general-purpose modeling language in the field of software engineering, which is designed to provide a standard way to visualize the design of a system.[1]

It was created and developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software during 1994–95 with further development led by them through 1996.[1]

In 1997 it was adopted as a standard by the


  • Official website

External links

  • Ambler, Scott William (2004). The Object Primer: Agile Model Driven Development with UML 2. Cambridge University Press.  
  • Chonoles, Michael Jesse; James A. Schardt (2003). UML 2 for Dummies. Wiley Publishing.  
  •  
  •  
  •  
  • Noran, Ovidiu S. "Business Modelling: UML vs. IDEF" (PDF). Retrieved 2005-12-28. 
  • Penker, Magnus; Hans-Erik Eriksson (2000). Business Modeling with UML. John Wiley & Sons.  

Further reading

  1. ^ a b c d e Unified Modeling Language User Guide, The (2 ed.). Addison-Wesley. 2005. p. 496.   , See the sample content, look for history
  2. ^ "ISO/IEC 19505-1:2012 - Information technology - Object Management Group Unified Modeling Language (OMG UML) - Part 1: Infrastructure". Iso.org. 2012-04-20. Retrieved 2014-04-10. 
  3. ^ a b c d "OMG Unified Modeling Language (OMG UML), Superstructure. Version 2.4.1". Object Management Group. Retrieved 9 April 2014. 
  4. ^ Satish Mishra (1997). "Visual Modeling & Unified Modeling Language (UML) : Introduction to UML". Rational Software Corporation. Accessed 9 November 2008.
  5. ^ a b "UML, Success Stories". Retrieved 9 April 2014. 
  6. ^ Andreas Zendler (1997) Advanced Concepts, Life Cycle Models and Tools for Objeckt-Oriented Software Development. p.122
  7. ^ "UML Specification version 1.1 (OMG document ad/97-08-11)". Omg.org. Retrieved 2011-09-22. 
  8. ^ "UML". Omg.org. Retrieved 2014-04-10. 
  9. ^ Génova et alia 2004 "Open Issues in Industrial Use Case Modeling"
  10. ^ "Will UML 2.0 Be Agile or Awkward?" (PDF). Retrieved 2011-09-22. 
  11. ^ "UML 2.0". Omg.org. Retrieved 2011-09-22. 
  12. ^ "UML". Omg.org. Retrieved 2011-09-22. 
  13. ^ "UML". Omg.org. Retrieved 2012-02-21. 
  14. ^ "UML". Omg.org. Retrieved 2013-08-07. 
  15. ^ OMG. "Catalog of OMG Modeling and Metadata Specifications". Retrieved 2012-02-21. 
  16. ^ "Issues for UML 2.6 Revision task Force mailing list". Omg.org. Retrieved 2014-04-10. 
  17. ^ John Hunt (2000). The Unified Process for Practitioners: Object-oriented Design, UML and Java. Springer, 2000. ISBN 1-85233-275-1. p.5.door
  18. ^ Jon Holt Institution of Electrical Engineers (2004). UML for Systems Engineering: Watching the Wheels IET, 2004, ISBN 0-86341-354-4. p.58
  19. ^ Iman Poernomo (2006) "The Meta-Object Facility Typed" in: Proceeding SAC '06 Proceedings of the 2006 ACM symposium on Applied computing. pp. 1845-1849
  20. ^ "UML 2.4.1 Infrastructure". Omg.org. 2011-08-05. Retrieved 2014-04-10. 
  21. ^ B. Henderson-Sellers; C. Gonzalez-Perez (2006). "Uses and Abuses of the Stereotype Mechanism in UML 1.x and 2.0". in: Model Driven Engineering Languages and Systems. Springer Berlin / Heidelberg.
  22. ^ "UML 2.5: Do you even care?".  "UML truly is ubiquitous"
  23. ^ "Death by UML Fever". 
  24. ^ "Ivar Jacobson on UML, MDA, and the future of methodologies". 
  25. ^ Hubert Tardieu, Arnold Rochfeld and René Colletti La methode MERISE: Principes et outils (Paperback - 1983)
  26. ^ Elmasri, Ramez, B. Shamkant, Navathe, Fundamentals of Database Systems, third ed., Addison-Wesley, Menlo Park, CA, USA, 2000.
  27. ^ ER 2004 : 23rd International Conference on Conceptual Modeling, Shanghai, China, 8-12 November 2004
  28. ^ "A Formal Treatment of UML Class Diagrams as an Efficient Method for Configuration Management 2007" (PDF). Retrieved 2011-09-22. 
  29. ^ "James Dullea, Il-Yeol Song, Ioanna Lamprou - An analysis of structural validity in entity-relationship modeling 2002" (PDF). Retrieved 2011-09-22. 
  30. ^ Reasoning about participation constraints and Chen's constraints" S Hartmann - 2003""" (PDF). Retrieved 2013-08-17. 

This article is based on material taken from the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the "relicensing" terms of the GFDL, version 1.3 or later.

References

See also

In Feinerer it says "Problems arise if we operate under the look-across semantics as used for UML associations. Hartmann[30] investigates this situation and shows how and why different transformations fail." (Although the "reduction" mentioned is spurious as the two diagrams 3.4 and 3.5 are in fact the same) and also "As we will see on the next few pages, the look-across interpretation introduces several difficulties which prevent the extension of simple mechanisms from binary to n-ary associations."
Cardinality notation
As with database Chen, Bachman, and ISO ER diagrams, class models are specified to use "look-across" cardinalities, even though several authors (Merise,[25] Elmasri & Navathe[26] amongst others[27]) prefer same-side or "look-here" for roles and both minimum and maximum cardinalities. Recent researchers (Feinerer,[28] Dullea et. alia[29]) have shown that the "look-across" technique used by UML and ER diagrams is less effective and less coherent when applied to n-ary relationships of order >2.

Critique of UML 1.x

Criticisms

It is seen to be a large language, with many constructs in it. Some (including Jacobson) feel that there are too many and that this hinders the learning (and therefore usage) of it.[24]

It has been treated, at times, as a design silver bullet, which has led to problems in its usage. Misuse of it includes excessive usage of it (design every little part of the system's code with it, which is unnecessary) and assuming that anyone can design anything with it (even those who haven't programmed).[23]

UML has been found useful in many design contexts,[5] so much so that is has become ubiquitous in its field.[22]

Adoption

The meta-model can be extended using a mechanism which is called stereotyping. This has been criticised as being insufficient/untenable by Brian Henderson-Sellers and Cesar Gonzalez-Perez in "Uses and Abuses of the Stereotype Mechanism in UML 1.x and 2.0".[21]

The most prominent example of a Layer 2 Meta-Object Facility model is the UML metamodel, the model that describes the UML itself. These M2-models describe elements of the M1-layer, and thus M1-models. These would be, for example, models written in UML. The last layer is the M0-layer or data layer. It is used to describe runtime instances of the system.[20]

The Object Management Group (OMG) has developed a metamodeling architecture to define the Unified Modeling Language (UML), called the Meta-Object Facility (MOF).[19] The Meta-Object Facility is designed as a four-layered architecture, as shown in the image at right. It provides a meta-meta model at the top layer, called the M3 layer. This M3-model is the language used by Meta-Object Facility to build metamodels, called M2-models.

Illustration of the Meta-Object Facility

Meta modeling

Interaction diagrams, a subset of behavior diagrams, emphasize the flow of control and data among the things in the system being modeled. For example, the sequence diagram which shows how objects communicate with each other in terms of a sequence of messages.

Interaction diagrams

Behavior diagrams emphasize what must happen in the system being modeled. Since behavior diagrams illustrate the behavior of a system, they are used extensively to describe the functionality of software systems. As an example, the activity diagram describes the business and operational step-by-step activities of the components in a system.

Behavior diagrams

Structure diagrams emphasize the things that must be present in the system being modeled. Since structure diagrams represent the structure, they are used extensively in documenting the software architecture of software systems. For example, the component diagram which describes how a software system is split up into components and shows the dependencies among these components.

Structure diagrams

These diagrams may all contain comments or notes explaining usage, constraint, or intent.

Hierarchy of UML 2.2 Diagrams, shown as a class diagram

UML 2 has many types of diagrams which are divided into two categories.[3] Some types represent structural information, and the rest represent general types of behavior, including a few that represent different aspects of interactions. These diagrams can be categorized hierarchically as shown in the following class diagram:[3]

Diagrams

UML models can be exchanged among UML tools by using the XML Metadata Interchange (XMI) interchange format.

UML diagrams represent two different views of a system model:[18]

It is important to distinguish between the UML model and the set of diagrams of a system. A diagram is a partial graphic representation of a system's model. The set of diagrams need not completely cover the model and deleting a diagram does not change the model. The model may also contain documentation that drives the model elements and diagrams (such as written use cases).

Modeling

UML is not a development method by itself;[17] however, it was designed to be compatible with the leading object-oriented software development methods of its time (for example OMT, Booch method, Objectory).

Software development methods

Design/Usage

The current versions of these standards follow: UML Superstructure version 2.4.1, UML Infrastructure version 2.4.1, OCL version 2.3.1, and UML Diagram Interchange version 1.0.[15] It continues to be updated and improved by the revision task force, who resolve any issues with the language.[16]

  1. The Superstructure that defines the notation and semantics for diagrams and their model elements
  2. The Infrastructure that defines the core metamodel on which the Superstructure is based
  3. The Object Constraint Language (OCL) for defining rules for model elements
  4. The UML Diagram Interchange that defines how UML 2 diagram layouts are exchanged

There are four parts to the UML 2.x specification:

Although UML 2.1 was never released as a formal specification, versions 2.1.1 and 2.1.2 appeared in 2007, followed by UML 2.2 in February 2009. UML 2.3 was formally released in May 2010.[12] UML 2.4.1 was formally released in August 2011.[13] UML 2.5 was released in October 2012 as an "In process" version and has yet to become formally released.[14]

The UML 2.0 major revision replaced version 1.5 in 2005, which was developed with an enlarged consortium to improve the language further to reflect new experience on usage of its features.[11]

UML 2.x

The standards it produced (as well as the original standard) have been noted as being ambiguous and inconsistent.[9][10]

After the first release a task force was formed[1] to improve the language, which released several minor revisions, 1.3, 1.4, and 1.5.[8]

UML 1.x

Under the technical leadership of those three (Rumbaugh, Jacobson and Booch), a consortium called the HP, DEC, IBM and Microsoft). The UML Partners' UML 1.0 draft was proposed to the OMG in January 1997 by the consortium. During the same month the UML Partners formed a group, designed to define the exact meaning of language constructs, chaired by Cris Kobryn and administered by Ed Eykholt, to finalize the specification and integrate it with other standardization efforts. The result of this work, UML 1.1, was submitted to the OMG in August 1997 and adopted by the OMG in November 1997.[1][7]

Rational Software Corporation hired James Rumbaugh from General Electric in 1994 and after that the company became the source for two of the most popular object-oriented modeling approaches of the day:[6] Rumbaugh's Object-modeling technique (OMT) and Grady Booch's method. They were soon assisted in their efforts by Ivar Jacobson, the creator of the object-oriented software engineering (OOSE) method, who joined them at Rational in 1995.[1]

Before UML 1.x

It is originally based on the notations of the Booch method, the Object-modeling technique (OMT) and Object-oriented software engineering (OOSE), which it has integrated into a single language.[3]

UML has been evolving since the second half of the 1990s and has its roots in the object-oriented methods developed in the late 1980s and early 1990s. The timeline (see image) shows the highlights of the history of object-oriented modeling methods and notation.

History of object-oriented methods and notation

History

Although originally intended solely for object-oriented design documentation, the Unified Modeling Language (UML) has been extended to cover a larger set of design documentation (as listed above),[4] and been found useful in many contexts.[5]

The Unified Modeling Language (UML) offers a way to visualize a system's architectural blueprints in a diagram (see image), including elements such as:[3]

A collage of UML diagrams

Overview

Contents

  • Overview 1
  • History 2
    • Before UML 1.x 2.1
    • UML 1.x 2.2
    • UML 2.x 2.3
  • Design/Usage 3
    • Software development methods 3.1
    • Modeling 3.2
    • Diagrams 3.3
      • Structure diagrams 3.3.1
      • Behavior diagrams 3.3.2
      • Interaction diagrams 3.3.3
    • Meta modeling 3.4
  • Adoption 4
  • Criticisms 5
    • Critique of UML 1.x 5.1
  • See also 6
  • References 7
  • Further reading 8
  • External links 9

[2]

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 



Copyright © World Library Foundation. All rights reserved. eBooks from Hawaii eBook Library are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.