Department of Computer Science and Engineering, HKUST Slide 1 Multivalue attribute: contains more than one value Employee Phone Email Employee Mobile PhoneHome.

Slides:



Advertisements
Similar presentations
DFD, LDS, ELH Inter-Relationships
Advertisements

1 Database Design I: The Entity- Relationship Model Chapter 5.
 Chase Banking Maci Lemons. Getting Started  All you need to get started is a bank account with Chase  You can download the app on your smartphone.
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
E/R Exercises – Part I April 16, 2017.
Entity - Relationship Modelling Exercises by Artem Chebotko
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Department of Computer Science and Engineering, HKUST Slide 1 Notation Summary R, S: table schemas such as Branch (branch-name, branch-city, assets) Account.
Project 1 Assignment Building a mini-database for CCI in UNCC which includes entity sets: departments (CS,SIS, bioinformatics), faculties, courses given.
Information Resources Management February 6, 2001.
Data Modeling with ERD ISYS 363. Entity-Relationship Diagram An entity is a “thing” in the real world, such as a person, place, event for which we intend.
ER-to-Relational Mapping Jan. 2012ACS-3902 Yangjun Chen1 ER-to-Relational Mapping Principles Specialization/Generalization -Superclass/Subclass Relationship.
Data Modeling ISYS 464. Database Design Process Conceptual database design: –The process of creating a data model independent of implementation details.
Database Design Concepts Info 1408 Lecture 2 An Introduction to Data Storage.
Information Resources Management January 30, 2001.
Carnegie Mellon Carnegie Mellon Univ. Dept. of Computer Science Database Applications C. Faloutsos E-R diagrams.
Department of Computer Science and Engineering, HKUST Slide 1 7. Relational Database Design.
Department of Computer Science and Engineering, HKUST Slide 1 Finding All the Keys Computationally, finding all the keys can be done by exhaustive search:
APPENDIX C DESIGNING DATABASES
Computer Science & Engineering 2111 Introduction to Database Management Systems Relationships and Database Creation 1 CSE 2111 Introduction to Database.
COURSE REGISTRATION SYSTEM Case study IST2101. Case Study: Course Registration (1) IST2102 You are helping Penn State create a course registration system.
Computing & Information Sciences Kansas State University Wednesday, 01 Oct 2008CIS 560: Database System Concepts Lecture 15 of 42 Wednesday, 01 October.
Dr. Mohamed Osman Hegaz1 Conceptual data base design: The conceptual models: The Entity Relationship Model.
Converting ER model Into Relational Table
ICT in Banking.
Glenn David Blank Computer Science & Engineering Department Lehigh University, Bethlehem, PA, USA With support from the National Science Foundation (Grants.
Big Java Chapter 12. Software Process - Waterfall Analysis Design Implementation Testing Deployment Does not work well when rigidly applied! established.
© 2005 course technology1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard Podeswa.
Relational databases and third normal form As always click on speaker notes under view when executing to get more information!
HNDComputing – DeMontfort University  DeMontfort University 2011 Database Fundamentals wk2 Database Design ConceptsDatabase Design Concepts Database Design.
Database R.Fröhlich, M. Schaffer, J. Konicek Database Relationship Types Different Relationship Types in a Logical Relational Model.
Requirements Determining the requirements of software involves determining the needs of the users of the software. Determining the requirements of software.
Kardashian Kard “Take Us With You Everywhere”. What is It? Credit Card/ Debit Card Pre-Paid Both Online (Mobile) and Offline Payments.
Copyright Ó Oracle Corporation, All rights reserved. Normalization Use the student note section below for further explanation of the slide content.Use.
Chapter 3, Section 3 ELECTRONIC BANKING.
1 CSE 480: Database Systems Lecture 4: Enhanced Entity-Relationship Modeling Reference: Read Chapter 8.1 – 8.5 of the textbook.
MIS 3053 Database Design & Applications The University of Tulsa Professor: Akhilesh Bajaj ER Model Lecture 1 © Akhilesh Bajaj, 2000, 2002, 2003, 2004.
1–1 McQuaig Bille 1 College Accounting 10 th Edition McQuaig Bille Nobles © 2011 Cengage Learning PowerPoint presented by Douglas Cloud Professor Emeritus.
Today’s Tasks Open your notebook and put the title “Today’s Tasks” September 24, 2015 Now, write down this list of things we are doing today in your notebook.
Database Design 3: Advanced Data Modeling Concepts CS 320.
The Hong Kong University of Science and Technology COMP3311 Spring 2013 Tutorial 1 ER Diagrams.
1 Translating ER Schema to Relational Model Instructor: Mohamed Eltabakh
COMP231 Tutorial 1 ER Model and ER to Relational Schema.
Project Name:- Acknowledgement  First of all we deeply acknowledge our gratitude to our guide Mr. Dibyendu Kumar Pal(Guide ) for being kind enough.
© 2013 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Object Oriented Analysis: Associations. 2 Object Oriented Modeling BUAD/American University Class Relationships u Classes have relationships between each.
Weak Entity Sets A weak entity is an entity that cannot exist in a database unless another type of entity also exists in that database. Weak entity meets.
Data Modeling with ERD BUS 782. Entities An entity is a person, place, object, event, or concept in the user environment about which the organization.
Chapter 4 The Semantic Object Model David M. Kroenke Database Processing © 2000 Prentice Hall.
Reconcile a Bank Statement UNIT 1 LESSON 2. First… some definitions  Bank statement  Shows all transactions that have occurred during the month  Statement.
Rensselaer Polytechnic Institute CSCI-4380 – Database Systems David Goldschmidt, Ph.D.
1 10/15/04CS150 Introduction to Computer Science 1 Reading from and Writing to Files Part 2.
Sample Table Standard Notation Entity name in uppercase
Database Design. Database Design Process Data Model Requirements Application 1 Database Requirements Application 2 Requirements Application 4 Requirements.
Howard Paul. Sequential Access Index Files and Data File Random Access.
BIS 360 – Lecture Six (Part 1) Conceptual Data Modeling (Chapter 10 and partial Chapter 12)
CS3431: C-Term Translating ER Schema to Relational Model Instructor: Mohamed Eltabakh
Data Modeling with ERD ISYS 363.
Designing Classes Lab. The object that you brought to class Put it in the basket we will exchange them now.
DATA MODELING AND ENTITY-RELATIONSHIP MODEL II IST 210: Organization of Data IST210 1.
The Entity-Relationship Model
ER model Ashima Wadhwa.
Rogers customer service Rogers support number
Entity Relationship Diagrams
Teaching slides Chapter 8.
Data Modeling with Entity Relationship Diagrams (Cont.)
Example A university registrar’s office maintains data about the following entities: (a) courses, including number, title, credits, syllabus, and prerequisites;
First and last name D E P T O F L First and last name A B R Y M
Mobile Robot Kinematics
Databases and Information Management
Presentation transcript:

Department of Computer Science and Engineering, HKUST Slide 1 Multivalue attribute: contains more than one value Employee Phone Employee Mobile PhoneHome Phone Personal Business Contrast with: What are the pros and cons in terms of flexibility and preciseness in meaning?

Department of Computer Science and Engineering, HKUST Slide 2 Take Home Messages from the Customer- Depositor-Account Example The exact meaning of a word may be ambiguous –What does “Amount” mean? –What does “Name” (of Customer and Account) mean? Are they the same? Whether to put an attribute to an entity or a relationship is not easy to determine –In the example, we try to argue that if “Amount” represents the deposit amount of EACH transaction, it should be associated with the relationship, because “Amount” is a property of the “deposit” action which is represented by the relationship between customer and account If we associate the “Amount” of each deposit to the account or to the customer, then multi-value attributes must be used, which is discouraged (you would know why when we study the relational data model)

Department of Computer Science and Engineering, HKUST Slide 3 Take Home Messages from the Customer- Depositor-Account Example –We further argue that if “Amount” is the balance of an account, there is always only one single balance for an account. It should be a property of account, not a property of the act of “depositing” money (though the act changes the balance)

Department of Computer Science and Engineering, HKUST Slide 4 ISA (“is a”) Relationship +A university has both part-time and full-time students. They are largely the same but with some differences: Student takes Course Grade Student-No Name Course-No Title FT/PT Emp-Name Advisor +Problem: If only FT students have advisors and only PT students have employer names, there are lots of empty values in the database

Department of Computer Science and Engineering, HKUST Slide 5 Separating the Students takes Course Grade Course-No Title FT Student Student-No Name Advisor +Other problems are introduced +If a student changes from FT to PT, he will exist in both entities PT Student Student-No Name Emp-Name takes Grade

Department of Computer Science and Engineering, HKUST Slide 6 Introduce a new Relationship: ISA takes Course Grade Course-No Title Student Student-No Name +A PT student “IS-A” Student +A FT student “IS-A” Student +A Professor “IS-A” Student PT Student Emp-Name PT Student Advisor ISA