What is better for DB design - UML or ERM ? - 08-22-2005 , 01:37 AM
I know some SQL, but the project I am working on is getting to complex
for me to just wing it.
What is better for DB design - UML or ERM ?
Thank you for your opinion.
Re: What is better for DB design - UML or ERM ? - 08-22-2005 , 02:46 AM
There is no *fundamanetal* difference between UML *class* diagrams and
ER models. Most good ER design apps can export to UML and import from
UML(The same goes for UML apps).
I would then go for ERM because ER apps have a better focus on the
It would be better to choose between ER(UML) and ORM (Object Role
Modelling). ORM btw has nothing to do with OO langauages.(see
www.orm.net) ORM is far better that ERM but you need to learn a new way
to design databases.
Re: What is better for DB design - UML or ERM ? - 08-22-2005 , 09:34 AM
Thanks for the advices DM.
I just noticed Visio has four templates listed under database: Entity
Relationships, Express-G, Object Relational, ORM.
1) Entity Relationships,
3) Object Relational,
Which one is best for modeling a database?
Re: What is better for DB design - UML or ERM ? - 08-23-2005 , 03:15 AM
My suggestion would be ORM, and if you're not going to learn a new way
to design, stick to Entity Relationanships
Express-G is an ISO standard, but for the rest just ER, Object
Relational(sometimes also called ORM!) is a method of mapping objects
to tables. This is not really useful for designing data models (IMO)