Database design using UML Class Diagram

Question

I would like to design a database using UML class diagrams but I dont know how. Can someone help me. How can I design a database using UML class diagrams?

Solution 1

Making an SQL database model in the form of a UML class diagram from a general information design model essentially requires to

1. Represent all entity types (or better: classes representing object types) as classes stereotyped as «object table» using SQL datatype names and replacing the UML {id} property modifier with a «pkey» stereotype:

   

2. Eliminate enumeration attributes for DBMS that do not support enumerations by connecting the object table with a corresponding enum table via a foreign key dependency arrow (a UML dependency stereotyped «fkey»): Otherwise, as in the case of MySQL, you can use their syntax in the model like so:

3. Eliminate multi-valued attributes:

   

4. Eliminate associations:

   1. Replace any functional association with a foreign key dependency:
   2. Replace any many-to-many association (relationship type) with a class stereotyped as «association table» and two foreign key dependencies:

5. Eliminate generalization/inheritance relationships:

   

See this book chapter for more information.

Solution 2

you may try to start with a UML class diagram. Maybe you can find this tutorial useful - http://argouml-db.tigris.org/documentation/DB_UML_Guide.htm

Solution 3

You can additionally use "Relation scheme diagram" to design table relationship and clearly represent primary key / foreign key dependencies.

see this tutorial.

Comments

[Rolf Schorpion]

possible duplicate of UML class diagram for database

[whytheq]

great link - I found that tutorial very useful