Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Reference Hub36
Data Modeling in UML and ORM: A Comparison

Data Modeling in UML and ORM: A Comparison

Terry Halpin, Anthony Bloesch
Copyright: © 1999 |Volume: 10 |Issue: 4 |Pages: 10
ISSN: 1063-8016|EISSN: 1533-8010|EISBN13: 9781466638112|DOI: 10.4018/jdm.1999100101
Cite Article Cite Article

MLA

Halpin, Terry, and Anthony Bloesch. "Data Modeling in UML and ORM: A Comparison." JDM vol.10, no.4 1999: pp.4-13. http://doi.org/10.4018/jdm.1999100101

APA

Halpin, T. & Bloesch, A. (1999). Data Modeling in UML and ORM: A Comparison. Journal of Database Management (JDM), 10(4), 4-13. http://doi.org/10.4018/jdm.1999100101

Chicago

Halpin, Terry, and Anthony Bloesch. "Data Modeling in UML and ORM: A Comparison," Journal of Database Management (JDM) 10, no.4: 4-13. http://doi.org/10.4018/jdm.1999100101

Export Reference

Mendeley
Favorite Full-Issue Download

Abstract

The Unified Modeling Language (UML) is becoming widely used for software and database modeling, and has been accepted by the Object Management Group as a standard language for object-oriented analysis and design. For data modeling purposes, UML includes class diagrams, that may be annotated with expressions in a textual constraint language. Although facilitating the transition to object-oriented code, UML’s implementation concerns render it less suitable for developing and validating a conceptual model with domain experts. This defect can be remedied by using a fact-oriented approach for the conceptual modeling, from which UML class diagrams may be derived. Object-Role Modeling (ORM) is currently the most popular fact-oriented approach to data modeling. This paper examines the relative strengths and weaknesses of ORM and UML for data modeling, and indicates how models in one notation can be translated into the other.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.