Encyclopedia of Database Systems

2018 Edition
| Editors: Ling Liu, M. Tamer Özsu

Unified Modeling Language

  • Martin GogollaEmail author
Reference work entry
DOI: https://doi.org/10.1007/978-1-4614-8265-9_440


UML; Unified modeling language


The Unified Modeling Language (UML) is a graphical language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system. UML offers a standard way to write a system’s blueprints, including conceptual things such as business processes and system functions as well as concrete things such as programming language statements, database schemas, and reusable software components [8].

Historical Background

The UML is based on earlier software design approaches, among them the Object Modeling Technique (OMT) [9], Object-Oriented Analysis and Design (OOAD) [1], and Object-Oriented Software Engineering (OOSE) [6] and other important techniques [5]. The UML was standardized in various versions by the Object Modeling Group (OMG) [8]. Authors of the predecessor techniques have published a comprehensive description of the UML [10]. Questions strongly related to UML are discussed at the UML and MODELS...

This is a preview of subscription content, log in to check access.

Recommended Reading

  1. 1.
    Booch G. Object-oriented design with applications. Menlo Park: Benjamin-Cummings; 1991.zbMATHGoogle Scholar
  2. 2.
    Chen PP. The entity-relationship model – toward a unified view of data. ACM Trans Database Syst. 1976;1(1):9–36.CrossRefGoogle Scholar
  3. 3.
    Gogolla M, Büttner F, Richters M. USE: a UML-based specification environment for validating UML and OCL. Sci Comput Program. 2007;69(1–3):27–34.MathSciNetzbMATHCrossRefGoogle Scholar
  4. 4.
    Gogolla M, Richters M. Expressing UML class diagrams properties with OCL. In: Clark T, Warmer J, editors. Advances in object modelling with the OCL. Berlin/Heidelberg/New York: Springer; 2001. p. 86–115.Google Scholar
  5. 5.
    Harel D. Statecharts: a visual formalism for complex systems. Sci Comput Program. 1987;8(3):231–74.MathSciNetzbMATHCrossRefGoogle Scholar
  6. 6.
    Jacobson I, Christenson M, Jonsson P, Oevergaard G. Object-oriented software engineering: a use case driven approach. Reading: Addison-Wesley; 1992.Google Scholar
  7. 7.
    Marcos E, Vela B, Cavero JM. A methodological approach for object-relational database design using UML. Softw Syst Model. 2003;2(1):59–75.CrossRefGoogle Scholar
  8. 8.
    OMG. OMG unified modeling language specification. Needham: OMG; 2007 .www.omg.org
  9. 9.
    Rumbaugh J, Blaha M, Premerlani W, Eddy F, Lorensen W. Object-oriented modeling and design. Englewood Cliffs: Prentice-Hall; 1991.zbMATHGoogle Scholar
  10. 10.
    Rumbaugh J, Booch G, Jacobson I. The unified modeling language reference manual. 2nd ed. Reading: Addison-Wesley; 2005.Google Scholar
  11. 11.
    SOSYM Editorial Board. Software and Systems Modeling. Berlin/Heidelberg/New York: Springer; 2007.Google Scholar
  12. 12.
    Toval JA, Requena V, Fernandez JL. Emerging OCL tools. Softw Syst Model. 2003;2(4):248–61.CrossRefGoogle Scholar
  13. 13.
    UML and MODELS Steering Committee. International ACM/IEEE conference on Model Driven Engineering Languages and Systems MODELS (previously ACM/IEEE international conference on the Unified Modeling Language UML). http://www.modelsconference.org/.
  14. 14.
    Urban SD, Dietrich SW. Using UML class diagrams for a comparative analysis of relational, object-oriented, and object-relational database mappings. In: Proceedings of the 34th SIGCSE Technical Symposium on Computer Science Education; 2003. p. 21–5.Google Scholar

Copyright information

© Springer Science+Business Media, LLC, part of Springer Nature 2018

Authors and Affiliations

  1. 1.University of BremenBremenGermany

Section editors and affiliations

  • David W. Embley
    • 1
  1. 1.Brigham Young UniversityProvoUSA