• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Database Modelling using UML

 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
How can a database design be modelled using UML ?
My thoughts on this :
1) Using Class Diagrams for representing Tables, views etc, and
2) Using Deployment Diagrams for representing Physical Structure
Please let me know your comments
Thanks,
Rupesh
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sounds good. If you're serious about database modeling, there's a book called Agile Database Techniques from Scott Ambler, which contains a lot of useful information on how to model a database schema with UML.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
See also http://www.agiledata.org/essays/umlDataModelingProfile.html
 
mister krabs
Posts: 13974
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Logical database design is done using class diagrams. The UML calls for using the {persistent} tag to identify the objects as logical database entries. Then design the associations for the objects. This is extremely useful because potential design flaws such as one-to-one, cyclic, and n-ary associations will become quite obvious.
Mapping your logical design to a physical design is done with standard UML component diagrams. You will want to take into account the physical distribution of your database at this point. (It may be that your logical tables will live in different databases on different servers.)
 
Peter Chang
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks a lot all of you for your support and pointers.
BTW, here is one more link, that might be helpful to you.
http://www.martinig.ch/mt/spring01.html
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic