1. Logical Database Design Transparencies 1

2. ©Pearson Education 2009 Objectives How to create a set of tables from an ER model. How to check that the tables are well-structured using normalization. How to check that the tables are capable of supporting the required transactions. How to define and document integrity constraints on the tables. 2

3. ©Pearson Education 2009 Overview of the database design methodology 3

4. ©Pearson Education 2009 Step 2: Logical database design (Map ER model to tables) Step 2.1Create tables Step 2.2Check table structures using normalization Step 2.3Check tables support user transactions Step 2.4Check integrity constraints Step 2.5 Review logical database design with users 4

5. ©Pearson Education 2009 Initial table structures for StayHome Online Rentals 5

6. ©Pearson Education 2009 1:* relationship (a) ER diagram (b) tables 6

7. ©Pearson Education 2009 1:* recursive relationship (a) ER diagram (b) table 7

8. ©Pearson Education 2009 1:1 relationship mandatory both entities (a) ER diagram (b) table 8

9. ©Pearson Education 2009 1:1 relationship mandatory one entity only (a) ER diagram (b) tables 9

10. ©Pearson Education 2009 1:1 relationship mandatory one entity only (a) ER diagram (b) tables 10

11. ©Pearson Education 2009 1:1 relationship optional both entities (a) ER diagram (b) tables 11

12. ©Pearson Education 2009 *:* relationship (a) ER diagram (b) tables 12

13. ©Pearson Education 2009 Complex (ternary) relationship (a) ER diagram (b) tables 13

14. ©Pearson Education 2009 Multi-valued attribute (a) ER diagram (b) tables 14

15. ©Pearson Education 2009 Summary of mapping rules 15

16. ©Pearson Education 2009 Representation of superclass/subclasses relationships 16

17. ©Pearson Education 2009 Tables to represent Staff specialization/generalization 17

18. ©Pearson Education 2009 Tables to represent Vehicle specialization/generalization 18

19. ©Pearson Education 2009 Tables for StayHome Online Rentals 19

20. ©Pearson Education 2009 Tables for StayHome Online Rentals with referential integrity constraints 20