1 / 25

Lecture 07: Conceptual Database Design

Lecture 07: Conceptual Database Design. Building an Application with a DBMS. Requirements modeling (conceptual) Decide what entities should be part of the application and how they should be linked. Schema design and implementation Decide on a set of tables, attributes.

hanzila
Download Presentation

Lecture 07: Conceptual Database Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lecture 07: Conceptual Database Design

  2. Building an Application with a DBMS • Requirements modeling (conceptual) • Decide what entities should be part of the application and how they should be linked. • Schema design and implementation • Decide on a set of tables, attributes. • Define the tables in the database system. • Populate database (insert tuples). • Write application programs using the DBMS • Way easier now that the data management is taken care of.

  3. Database Design • Why do we need it? • Agree on structure of the database before deciding on a particular implementation. • Consider issues such as: • What entities to model • How entities are related • What constraints exist in the domain • How to achieve good designs

  4. Database Design Formalisms 1. Object Definition Language (ODL): • Closer in spirit to object-oriented models • Not in the scope of this course 2. Entity/Relationship model (E/R): • More relational in nature. • Related to the EER modeling in the MySQL workbench but we use different conventions here! • Both can be translated to relational schemas

  5. Entity / Relationship Diagrams Entity sets Attributes Relationships between entities Product address buys

  6. Keys in E/R Diagrams • Every entity set must have a key name category price Product

  7. name category stockprice name price makes Company Product buys employs Person address name ssn

  8. makes Company Product 1 a b 2 A= =B c 3 d What is a Relation ? • A mathematical definition: • if A, B are sets, then a relation R is a subset of A  B • A={1,2,3}, B={a,b,c,d}, R = {1,a, 1,c, 3,b} - makes is a subset of ProductCompany:

  9. 1 2 3 1 2 3 1 2 3 a b c d a b c d a b c d Multiplicity of E/R Relations • one-one: • many-one • many-many

  10. name category stockprice name price makes Company Product What doesit mean? buys employs Person address name ssn

  11. Multi-way Relationships How do we model a purchase relationship between buyers, products and stores? Product Store Purchase Person Can still model as a mathematical set (how?)

  12. Role Movie Plays Salary Actor Arrows in Multiway Relationships Q: what does the arrow mean ? A: if I know the movie, role and actor, I know the salary too

  13. Arrows in Multiway Relationships Q: what do these arrow mean ? A: store, person, invoice determines movie and store, invoice, movie determines person Invoice VideoStore Rental Movie Person

  14. Invoice VideoStore Rental Movie Person Arrows in Multiway Relationships Q: how do I say: “invoice determines store” ? A: no good way; best approximation: Q: Why is this incomplete ?

  15. Roles in Relationships What if we need an entity set twice in one relationship? Product Purchase Store buyer seller Person

  16. Attributes on Relationships date Product Purchase Store Person

  17. Converting Multi-way Relationships to Binary ProductOf date Product StoreOf Purchase Store BuyerOf Person

  18. From E/R Diagramsto Relational Schema • Entity  relation • Relationship  relation

  19. Entity Set to Relation name category price Product Product(name,category, price) name category price gizmo gadgets $19.99

  20. Relationships to Relations price name category Start Year name makes Company Product Stock price Makes(product-name,product-category,company-name, year)Product-name Product-Category Company-name Starting-year gizmo gadgets gizmoWorks 1963 (watch out for attribute name conflicts)

  21. Relationships to Relations price name category Start Year name makes Company Product Stock price No need for Makes. Modify Product: name category price StartYear companyName gizmo gadgets 19.99 1963 gizmoWorks

  22. Multi-way Relationships to Relations name address Product Purchase Store name price Person Purchase( , , ) ssn name

  23. 3. Design Principles What’s wrong? Purchase Product Person President Country Person

  24. Design Principles:What’s Wrong? date Product Purchase Store Moral: pick the right kind of entities. personName personAddr

  25. Design Principles:What’s Wrong? date Dates Product Purchase Store Moral: don’t complicate life more than it already is. Person

More Related