Logical Design. Readings: Elmasri&Navathe: Chapter Relational Database Design by ER- and EER-to-relational mapping
|
|
- Lillian Sullivan
- 7 years ago
- Views:
Transcription
1 Logical Design Readings: Elmasri&avathe: Chapter Relational Database Design by ER- and EER-to-relational mapping (Chapter 7 in the 7th and 5th edition, Chapter 9 in the 6th edition)
2 Conceptual Design Logical Design DMBS specific DBMS independent Physical Design
3 Aims of Logical Design the aim of this phase is to construct a logical schema, that correctly and efficiently represents all of the information described by the conceptual (e.g. ER) schema this is not always just a simple translation: in some cases there it no close correspondence between conceptual and logical schema e.g. if the conceptual schema is EER, and the logical schema is relational, a generalisation cannot be directly translated this is because the aim of conceptual design is to represent data accurately and naturally from a high level, computer-independent point of view, whereas logical design has to consider the performances of the final, computer based product
4 Decisions to take Analysis of redundancies decide whether to delete or retain possible redundancies Removing unsupported concepts e.g. replace all generalisations with other constructs (such as IS- A relationships) when using a relational logical model Partitioning and Merging partition of entity Employee to distinguish between Personal data (ame, YearOfBirth etc) and Professional data (Level, Salary, etc.) on the basis of frequency of access/modification Selection of Primary Identifiers e.g. adding new attributes to entities which do not have a natural primary key
5 Decisions to take decide how to deal with derived notions: e.g. derived attributes can be represented as virtual fields, as part of a form (visualisation phase), implemented as a query, or just ignored sometimes relations can be derived (cyclic relations) such as: TRAIEE ATTEDS COURSE TEACHES ISTRUCTOR ASSIGED TO need to decide whether ASSIGED TO can be derived from the other relationships, or is a relationship of its own
6 Step by step process After restructuring, it s just a straightforward process, which considers each concept in turn and with a specific order:. regular entities 2. weak entities 3. binary one-to-one relationships 4. binary one-to-many relationships 5. binary many-to-many relationships 6. multi-valued attributes 7. -ary relationships. (generalisations/specifications)
7 STEP : Regular entity types For each regular (non weak) entity type E in the ER schema, create a relation (table) that includes all the simple, primitive attributes of E all the simple components of composite attributes of E and choose one of the candidate key attributes as primary key YearBirth Code Age I ignore derived ISTRUCTOR Telephone umber ignore multivalued ame Firstame only consider components ISTRUCTOR I Firstame YearBirth
8 STEP 2: Weak entity types For each weak entity type W, create a relation (table) that includes all the simple, primitive attributes and all the simple components of composite attributes of W the primary key attribute(s) of the table T that corresponds to W s owner entity type and choose as primary key the combination of all attributes taken from T and the partial key of W (if any) Code I Age TRAIEE TRAIEE I Sex Age Sex IS A PROFESSIOAL PROFESSIOAL Area Title Area Title
9 STEP 3: Binary one-to-one rel. For each binary : relationship type R in the ER schema: identify T and S, relations corresponding to the entity types participating to R consider the relation T whose entity type has a total participation to R, if any, or choose any of the two if both have partial participation to R include the attribute(s) forming the primary key of S as foreign key in T include all the simple, primitive attributes and the simple components of attributes of R in T S ISTRUCTOR I Firstame YearBirth Telephone umber T COURSE TYPE ame StartDate I YearBirth Age DIRECTOR ISTRUCTOR Code ame COURSE TYPE Code COURSE TYPE ame DirectorCode StartDate Firstname ame
10 STEP 4: Regular Binary one-to-many rel. For each regular (non weak) binary : relationship type R: identify relation S that corresponds to the entity type at the Many side identify relation T that corresponds to the entity type at the One side include as foreign key in S the primary key of T include all the simple, primitive attributes and the simple components of attributes of R in S StartDate Code ame Address Telephone umber WORKS FOR EMPLOYER Level EMPLOYEE T S EMPLOYER ame Address Telephone umber EMPLOYEE Level EMPLOYEE Level EmployerCode StartDate
11 STEP 5: Binary many-to-many rel. For each binary :M relationship type R in the ER schema: identify the relations S and T that correspond to the entity types participating to R create a new relation and include as foreign keys all the attributes forming the primary key of S and all the attributes forming the primary key of T include in the new relation all the simple, primitive attributes and the simple components of attributes of R Code I TRAIEE Age TRAIEE I PAST EDITIO Sex Age Sex StartDate* EndDate HAS ATTEDED PAST EDITIO Mark HAS ATTEDED StartDate EndDate Participants CodeTrainee* CodeCourse* StartDate* Mark
12 STEP 6: Multivalued attributes For each multivalued attribute A of an entity type E in the ER schema: identify the relation T that correspond to E create a new relation S that include an attribute corresponding to A and all the attributes forming the primary key of T if the multivalued attribute is composite, include the simple components ISTRUCTOR I Firstame YearBirth YearBirth Code Age I ISTRUCTOR Telephone umber Firstame ame ISTR-TELEPHOE Telephone umber*
13 STEP 7: -ary relationships For each n-ary (n > 2) relationship type R in the ER schema: identify relations T, T 2,... T n that correspond to the entity types participating to R create a new relation including as foreign key the attributes forming the primary key of each of the tables T, T 2,... T n include all the simple, primitive attributes and the simple components of attributes of R Capacity Location Telephone umber StartDate Day Time Class EDITIO CLASSROOM TEACHES I YearBirth Age CLASSROOM Location* Capacity ISTRUCTOR I Firstame EDITIO StartDate* YearBirth ISTRUCTOR Code ame TEACHES Instructor Course StartDate* Location* Firstname
14 ame Address StartDate Code Telephone umber WORKS FOR EMPLOYER EndDate Code Age Sex Area Level I EMPLOYEE TRAIEE IS A IS A PROFESSIOAL Title Mark HAS WORKED FOR Date ATTEDS EDITIO Code ame HAS ATTEDED Class StartDate Time HELD I COURSE TYPE PAST EDITIO CLASSROOM TEACHES HAS BEE HELD I QUALIFIES Location HAS TAUGHT Telephone umber ISTRUCTOR Age Code StartDate EndDate Participants
15 TRAIEE I Sex Age HAS WORKED FOR Employer StartDate EndDate EMPLOYER ame Address Telephone umber ATTEDS PROFESSIOAL Area Title CodeTrainee* CodeCourse* StartDate* EMPLOYEE Level EmployerCode StartDate EDITIO CLASSES StartDate* Day Time HAS ATTEDED EDITIO StartDate* CodeTrainee* CodeCourse* StartDate* Mark COURSE TYPE ame DirectorCode StartDate PAST EDITIO StartDate* EndDate CLASSROOM Location* Capacity TEACHES Instructor Course StartDate* Location* QUALIFIES HAS TAUGHT CodeInstructor* CodeCourse* CodeInstructor* CodeCourse* StartDate* ISTRUCTOR I Firstame YearBirth ISTR-TELEPHOE Telephone umber*
16 TRAIEE I Sex Age (is a) ATTEDS (is a) PROFESSIOAL Area CodeTrainee* CodeCourse* StartDate* Title HAS WORKED FOR Employer StartDate EndDate EMPLOYEE Level EmployerCode StartDate EDITIO CLASSES StartDate* Day Time EMPLOYER ame Address Telephone umber (works for) HAS ATTEDED CodeTrainee* CodeCourse* StartDate* PAST EDITIO StartDate* EndDate TEACHES Mark (has been held in) EDITIO StartDate* (held in) CLASSROOM Location* Instructor Course StartDate* Location* COURSE TYPE ame DirectorCode StartDate Capacity (director) QUALIFIES HAS TAUGHT CodeInstructor* CodeCourse* StartDate* ISTRUCTOR I Firstame CodeInstructor* CodeCourse* YearBirth ISTR-TELEPHOE Telephone umber*
17 recursive relation
18 recursive relation
19 Remarks an alternative mapping of a One-to-One relationship type is possible by merging the two entity types and the relationship into a single relation (table) particularly appropriate when both participations are total the two entity types should not participate to other relationship types a One-to-One or a One-to-Many relationship type can always be mapped similarly to the method for Many-to-Many relationship types particularly useful when few relationship instances exist in order to avoid null values in foreign key
20 ER to Relational Mapping: Summary ER Entity Type Relational DB Relation (table) : relationship type foreign key or relationship relation : relationship type foreign key or relationship relation :M relationship type n-ary relationship type simple attribute composite attribute multivalued attribute key attribute relationship relation and two foreign keys relationship relation and n foreign keys attribute (column, field) set of attributes (fields) relation and foreign key primary key
21 Relational vs ER relational model does not allow relationship types to be represented explicitly: relationships are represented using primary keys and foreign keys as attributes in relations an operation called natural join allows combinations of all record pairs in order to materialise the relationship: binary : or : relationships require one join binary :M relationships require two joins n-ary relationships require n joins
22 Relational vs ER relational model does not allow multivalued attributes in relational schemas we create separate relations for each multivalued attribute key attribute of the relevant entity is repeated for each value need a join to relate the values of the multivalued attribute to values of other attributes of the entity or to relationship instances relational languages (e.g. SQL) also cannot explicitly handle set of values object-oriented, network and hierarchical models do support multivalued attributes seen as a flaw in normalised relational models
23 Mapping of EER constructs Extending ER-to-relational mapping algorithm with a STEP basically converting each specialisation with m subclasses S, S 2,... S m of a generalised superclass C into relation schemas several options available depending on the nature of the specialisation
24 STEP a: Multiple relations: superclass and subclasses works for any specialisation S, S 2,... S m of a class C (total or partial, disjoint or overlapping) create a relation for each subclass S and add the primary key of C to each equivalent to representing classes via weak entities ( IS-A rel.) Code I Sex Age TRAIEE Level U EMPLOYEE U Area PROFESSIOAL Title
25 STEP b: Multiple relations: Salary subclasses relations only only if: "Salaried" Subclasses are total Specialisation has disjointedness constraint DO T create a relation for the superclass, BUT add all of the superclass attributes to each subclass relations Level U "Employee" U EMPLOYEE d U o "Hourly" U Salaried "Professiona PROFESSIO PayScale Level Salary Hourly-paid Level Payscale SALARIED HOURLY-PAID can actually eliminate this
26 STEP c: single relation with one type attribute Salary only if: Specialisation has disjointedness constraint add all attributes to the superclass relation PROBLEM: many ULL values can be created "Salaried" Level U SALARIED "Employee" U EMPLOYEE d U o "Hourly" U HOURLY-PAID Employee "Professiona Level Salary Payscale PROFESSIO PayScale this will be empty if =Hourly this will be empty if =Salaried
27 STEP d: single relation with multiple type attributes to model overlapping subclasses (but also OK for disjoint) add all attributes to the superclass relation add a Boolean (flag) attribute for each subclass Code I Sex Level Age Trainee JobType = "Employee" U EMPLOYEE TRAIEE o U YOUG U Age < 30 JobType JobType = "Professional" PROFESSIOAL... EmplFlag Level YoungFlag ProfFlag Area Title Area Title Flags many empty/null fields, but controlled by the flags
28
29 Different tables for the upper classification Multiple strategies Flags for the lower classifications
not necessarily strictly sequential feedback loops exist, i.e. may need to revisit earlier stages during a later stage
Database Design Process there are six stages in the design of a database: 1. requirement analysis 2. conceptual database design 3. choice of the DBMS 4. data model mapping 5. physical design 6. implementation
More informationDesigning a Database Schema
Week 10: Database Design Database Design From an ER Schema to a Relational One Restructuring an ER schema Performance Analysis Analysis of Redundancies, Removing Generalizations Translation into a Relational
More informationChapter 2: Entity-Relationship Model. Entity Sets. " Example: specific person, company, event, plant
Chapter 2: Entity-Relationship Model! Entity Sets! Relationship Sets! Design Issues! Mapping Constraints! Keys! E-R Diagram! Extended E-R Features! Design of an E-R Database Schema! Reduction of an E-R
More information2. Conceptual Modeling using the Entity-Relationship Model
ECS-165A WQ 11 15 Contents 2. Conceptual Modeling using the Entity-Relationship Model Basic concepts: entities and entity types, attributes and keys, relationships and relationship types Entity-Relationship
More informationChapter 2: Entity-Relationship Model. E-R R Diagrams
Chapter 2: Entity-Relationship Model What s the use of the E-R model? Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of an E-R Database Schema
More informationER modelling, Weak Entities, Class Hierarchies, Aggregation
CS344 Database Management Systems ER modelling, Weak Entities, Class Hierarchies, Aggregation Aug 2 nd - Lecture Notes (Summary) Submitted by - N. Vishnu Teja Saurabh Saxena 09010125 09010145 (Most the
More informationRelational Schema Design
Relational Schema Design Using ER Methodology to Design Relational Database Schemas The Development Process Collect requirements. Analyze the requirements. Conceptually design the data (e.g., draw an ER
More informationChapter 2: Entity-Relationship Model
Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E R Diagram Extended E-R Features Design of an E-R Database Schema Reduction of an E-R Schema to
More informationCSC 742 Database Management Systems
CSC 742 Database Management Systems Topic #4: Data Modeling Spring 2002 CSC 742: DBMS by Dr. Peng Ning 1 Phases of Database Design Requirement Collection/Analysis Functional Requirements Functional Analysis
More informationInformation Systems Analysis and Design CSC340. 2004 John Mylopoulos Database Design -- 2. Information Systems Analysis and Design CSC340
XX. Database Design Databases Databases and DBMS Data Models, Hierarchical, Network, Relational Database Design Restructuring an ER schema Performance analysis Analysis of Redundancies, Removing generalizations
More informationDatabase Design Methodology
Database Design Methodology Three phases Database Design Methodology Logical database Physical database Constructing a model of the information used in an enterprise on a specific data model but independent
More informationReview: Participation Constraints
Review: Participation Constraints Does every department have a manager? If so, this is a participation constraint: the participation of Departments in Manages is said to be total (vs. partial). Every did
More informationThe Entity-Relationship Model
The Entity-Relationship Model 221 After completing this chapter, you should be able to explain the three phases of database design, Why are multiple phases useful? evaluate the significance of the Entity-Relationship
More informationIV. The (Extended) Entity-Relationship Model
IV. The (Extended) Entity-Relationship Model The Extended Entity-Relationship (EER) Model Entities, Relationships and Attributes Cardinalities, Identifiers and Generalization Documentation of EER Diagrams
More informationXV. The Entity-Relationship Model
XV. The Entity-Relationship Model The Entity-Relationship Model Entities, Relationships and Attributes Cardinalities, Identifiers and Generalization Documentation of E-R Diagrams and Business Rules The
More informationDatabases Model the Real World. The Entity- Relationship Model. Conceptual Design. Steps in Database Design. ER Model Basics. ER Model Basics (Contd.
The Entity- Relationship Model R &G - Chapter 2 A relationship, I think, is like a shark, you know? It has to constantly move forward or it dies. And I think what we got on our hands is a dead shark. Woody
More informationCOMP 378 Database Systems Notes for Chapter 7 of Database System Concepts Database Design and the Entity-Relationship Model
COMP 378 Database Systems Notes for Chapter 7 of Database System Concepts Database Design and the Entity-Relationship Model The entity-relationship (E-R) model is a a data model in which information stored
More informationER & EER to Relational Mapping. Chapter 9 1
ER & EER to Relational Mapping Chapter 9 1 Figure 3.2 ER schema diagram for the company database. Fname Minit Lname Number Name Address N 1 WORKS_FOR Name Locations Sex Salary Ssn Bdate EMPLOYEE NumberOfEmployees
More informationChapter 7 Data Modeling Using the Entity- Relationship (ER) Model
Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Outline Using High-Level Conceptual Data Models for
More informationTHE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E)
THE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E) 2 LECTURE OUTLINE Using High-Level, Conceptual Data Models for Database Design Entity-Relationship (ER) model Popular high-level conceptual
More informationBridge from Entity Relationship modeling to creating SQL databases, tables, & relations
1 Topics for this week: 1. Good Design 2. Functional Dependencies 3. Normalization Readings for this week: 1. E&N, Ch. 10.1-10.6; 12.2 2. Quickstart, Ch. 3 3. Complete the tutorial at http://sqlcourse2.com/
More informationDATABASE MANAGEMENT SYSTEMS. Question Bank:
DATABASE MANAGEMENT SYSTEMS Question Bank: UNIT 1 1. Define Database? 2. What is a DBMS? 3. What is the need for database systems? 4. Define tupule? 5. What are the responsibilities of DBA? 6. Define schema?
More informationConceptual Design Using the Entity-Relationship (ER) Model
Conceptual Design Using the Entity-Relationship (ER) Model Module 5, Lectures 1 and 2 Database Management Systems, R. Ramakrishnan 1 Overview of Database Design Conceptual design: (ER Model is used at
More informationThe Relational Model. Why Study the Relational Model? Relational Database: Definitions. Chapter 3
The Relational Model Chapter 3 Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase,
More informationLecture 12: Entity Relationship Modelling
Lecture 12: Entity Relationship Modelling The Entity-Relationship Model Entities Relationships Attributes Constraining the instances Cardinalities Identifiers Generalization 2004-5 Steve Easterbrook. This
More informationLesson 8: Introduction to Databases E-R Data Modeling
Lesson 8: Introduction to Databases E-R Data Modeling Contents Introduction to Databases Abstraction, Schemas, and Views Data Models Database Management System (DBMS) Components Entity Relationship Data
More informationDatabase Management Systems
Database Management Systems Database Design (1) 1 Topics Information Systems Life Cycle Data Base Design Logical Design Physical Design Entity Relationship (ER) Model Entity Relationship Attributes Cardinality
More informationA Tool for Generating Relational Database Schema from EER Diagram
A Tool for Generating Relational Schema from EER Diagram Lisa Simasatitkul and Taratip Suwannasart Abstract design is an important activity in software development. EER diagram is one of diagrams, which
More informationIntroduction to Computing. Lectured by: Dr. Pham Tran Vu t.v.pham@cse.hcmut.edu.vn
Introduction to Computing Lectured by: Dr. Pham Tran Vu t.v.pham@cse.hcmut.edu.vn Databases The Hierarchy of Data Keys and Attributes The Traditional Approach To Data Management Database A collection of
More informationDATABASE DESIGN. - Developing database and information systems is performed using a development lifecycle, which consists of a series of steps.
DATABASE DESIGN - The ability to design databases and associated applications is critical to the success of the modern enterprise. - Database design requires understanding both the operational and business
More informationData Modeling. Database Systems: The Complete Book Ch. 4.1-4.5, 7.1-7.4
Data Modeling Database Systems: The Complete Book Ch. 4.1-4.5, 7.1-7.4 Data Modeling Schema: The structure of the data Structured Data: Relational, XML-DTD, etc Unstructured Data: CSV, JSON But where does
More informationConcepts of Database Management Seventh Edition. Chapter 6 Database Design 2: Design Method
Concepts of Database Management Seventh Edition Chapter 6 Database Design 2: Design Method Objectives Discuss the general process and goals of database design Define user views and explain their function
More informationConverting E-R Diagrams to Relational Model. Winter 2006-2007 Lecture 17
Converting E-R Diagrams to Relational Model Winter 2006-2007 Lecture 17 E-R Diagrams Need to convert E-R model diagrams to an implementation schema Easy to map E-R diagrams to relational model, and then
More informationChapter 3. Data Modeling Using the Entity-Relationship (ER) Model
Chapter 3 Data Modeling Using the Entity-Relationship (ER) Model Chapter Outline Overview of Database Design Process Example Database Application (COMPANY) ER Model Concepts Entities and Attributes Entity
More informationIntroduction to normalization. Introduction to normalization
Introduction to normalization Lecture 4 Instructor Anna Sidorova Agenda Presentation Review of relational models, in class exersise Introduction to normalization In-class exercises Discussion of HW2 1
More informationDatabase Design Overview. Conceptual Design ER Model. Entities and Entity Sets. Entity Set Representation. Keys
Database Design Overview Conceptual Design. The Entity-Relationship (ER) Model CS430/630 Lecture 12 Conceptual design The Entity-Relationship (ER) Model, UML High-level, close to human thinking Semantic
More informationThe Entity-Relationship Model
The Entity-Relationship Model Chapter 2 Slides modified by Rasmus Pagh for Database Systems, Fall 2006 IT University of Copenhagen Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Today
More information7.1 The Information system
Chapter 7. Database Planning, Design and Administration Last few decades have seen proliferation of software applications, many requiring constant maintenance involving: correcting faults, implementing
More informationthree Entity-Relationship Modeling chapter OVERVIEW CHAPTER
three Entity-Relationship Modeling CHAPTER chapter OVERVIEW 3.1 Introduction 3.2 The Entity-Relationship Model 3.3 Entity 3.4 Attributes 3.5 Relationships 3.6 Degree of a Relationship 3.7 Cardinality of
More informationLiTH, Tekniska högskolan vid Linköpings universitet 1(7) IDA, Institutionen för datavetenskap Juha Takkinen 2007-05-24
LiTH, Tekniska högskolan vid Linköpings universitet 1(7) IDA, Institutionen för datavetenskap Juha Takkinen 2007-05-24 1. A database schema is a. the state of the db b. a description of the db using a
More informationEntity-Relationship Model
UNIT -2 Entity-Relationship Model Introduction to ER Model ER model is represents real world situations using concepts, which are commonly used by people. It allows defining a representation of the real
More informationCIS 631 Database Management Systems Sample Final Exam
CIS 631 Database Management Systems Sample Final Exam 1. (25 points) Match the items from the left column with those in the right and place the letters in the empty slots. k 1. Single-level index files
More informationA. TRUE-FALSE: GROUP 2 PRACTICE EXAMPLES FOR THE REVIEW QUIZ:
GROUP 2 PRACTICE EXAMPLES FOR THE REVIEW QUIZ: Review Quiz will contain very similar question as below. Some questions may even be repeated. The order of the questions are random and are not in order of
More informationFoundations of Information Management
Foundations of Information Management - WS 2012/13 - Juniorprofessor Alexander Markowetz Bonn Aachen International Center for Information Technology (B-IT) Data & Databases Data: Simple information Database:
More informationRelational Databases
Relational Databases Jan Chomicki University at Buffalo Jan Chomicki () Relational databases 1 / 18 Relational data model Domain domain: predefined set of atomic values: integers, strings,... every attribute
More informationDatabase Design Process
Entity-Relationship Model Chapter 3, Part 1 Database Design Process Requirements analysis Conceptual design data model Logical design Schema refinement: Normalization Physical tuning 1 Problem: University
More informationThe Entity-Relationship Model
The Entity-Relationship Model Overview of Database Design Requirements analysis Conceptual design data model Logical design Schema refinement: Normalization Physical tuning Conceptual Design Entities Conceptual
More informationPhysical Database Design Process. Physical Database Design Process. Major Inputs to Physical Database. Components of Physical Database Design
Physical Database Design Process Physical Database Design Process The last stage of the database design process. A process of mapping the logical database structure developed in previous stages into internal
More informationRelational Database Basics Review
Relational Database Basics Review IT 4153 Advanced Database J.G. Zheng Spring 2012 Overview Database approach Database system Relational model Database development 2 File Processing Approaches Based on
More informationUnit 2.1. Data Analysis 1 - V2.0 1. Data Analysis 1. Dr Gordon Russell, Copyright @ Napier University
Data Analysis 1 Unit 2.1 Data Analysis 1 - V2.0 1 Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is a relationship? Entities, attributes,
More informationLecture 6. SQL, Logical DB Design
Lecture 6 SQL, Logical DB Design Relational Query Languages A major strength of the relational model: supports simple, powerful querying of data. Queries can be written intuitively, and the DBMS is responsible
More informationHow To Write A Diagram
Data Model ing Essentials Third Edition Graeme C. Simsion and Graham C. Witt MORGAN KAUFMANN PUBLISHERS AN IMPRINT OF ELSEVIER AMSTERDAM BOSTON LONDON NEW YORK OXFORD PARIS SAN DIEGO SAN FRANCISCO SINGAPORE
More informationDatabase Design. Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB
Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB Outline Database concepts Conceptual Design Logical Design Communicating with the RDBMS 2 Some concepts Database: an
More informationDatabase Design Methodology
Topic 7 Database Design Methodology LEARNING OUTCOMES When you have completed this Topic you should be able to: 1. Discuss the purpose of a design methodology. 2. Explain three main phases of design methodology.
More informationDatabase Design Process. Databases - Entity-Relationship Modelling. Requirements Analysis. Database Design
Process Databases - Entity-Relationship Modelling Ramakrishnan & Gehrke identify six main steps in designing a database Requirements Analysis Conceptual Design Logical Design Schema Refinement Physical
More informationOutline. Data Modeling. Conceptual Design. ER Model Basics: Entities. ER Model Basics: Relationships. Ternary Relationships. Yanlei Diao UMass Amherst
Outline Data Modeling Yanlei Diao UMass Amherst v Conceptual Design: ER Model v Relational Model v Logical Design: from ER to Relational Slides Courtesy of R. Ramakrishnan and J. Gehrke 1 2 Conceptual
More informationData Analysis 1. SET08104 Database Systems. Copyright @ Napier University
Data Analysis 1 SET08104 Database Systems Copyright @ Napier University Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is a relationship?
More informationThe Relational Model. Ramakrishnan&Gehrke, Chapter 3 CS4320 1
The Relational Model Ramakrishnan&Gehrke, Chapter 3 CS4320 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase, etc. Legacy systems in older models
More informationWe know how to query a database using SQL. A set of tables and their schemas are given Data are properly loaded
E-R Diagram Database Development We know how to query a database using SQL A set of tables and their schemas are given Data are properly loaded But, how can we develop appropriate tables and their schema
More informationIT2304: Database Systems 1 (DBS 1)
: Database Systems 1 (DBS 1) (Compulsory) 1. OUTLINE OF SYLLABUS Topic Minimum number of hours Introduction to DBMS 07 Relational Data Model 03 Data manipulation using Relational Algebra 06 Data manipulation
More informationAVOIDANCE OF CYCLICAL REFERENCE OF FOREIGN KEYS IN DATA MODELING USING THE ENTITY-RELATIONSHIP MODEL
AVOIDANCE OF CYCLICAL REFERENCE OF FOREIGN KEYS IN DATA MODELING USING THE ENTITY-RELATIONSHIP MODEL Ben B. Kim, Seattle University, bkim@seattleu.edu ABSTRACT The entity-relationship (ER model is clearly
More informationRelational Database Concepts
Relational Database Concepts IBM Information Management Cloud Computing Center of Competence IBM Canada Labs 1 2011 IBM Corporation Agenda Overview Information and Data Models The relational model Entity-Relationship
More informationModern Systems Analysis and Design
Modern Systems Analysis and Design Prof. David Gadish Structuring System Data Requirements Learning Objectives Concisely define each of the following key data modeling terms: entity type, attribute, multivalued
More informationTIM 50 - Business Information Systems
TIM 50 - Business Information Systems Lecture 15 UC Santa Cruz March 1, 2015 The Database Approach to Data Management Database: Collection of related files containing records on people, places, or things.
More informationCS 377 Database Systems. Database Design Theory and Normalization. Li Xiong Department of Mathematics and Computer Science Emory University
CS 377 Database Systems Database Design Theory and Normalization Li Xiong Department of Mathematics and Computer Science Emory University 1 Relational database design So far Conceptual database design
More informationDatabase Design. Database Design I: The Entity-Relationship Model. Entity Type (con t) Chapter 4. Entity: an object that is involved in the enterprise
Database Design Database Design I: The Entity-Relationship Model Chapter 4 Goal: specification of database schema Methodology: Use E-R R model to get a high-level graphical view of essential components
More informationIT2305 Database Systems I (Compulsory)
Database Systems I (Compulsory) INTRODUCTION This is one of the 4 modules designed for Semester 2 of Bachelor of Information Technology Degree program. CREDITS: 04 LEARNING OUTCOMES On completion of this
More informationChapter 8 The Enhanced Entity- Relationship (EER) Model
Chapter 8 The Enhanced Entity- Relationship (EER) Model Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 8 Outline Subclasses, Superclasses, and Inheritance Specialization
More informationGraham Kemp (telephone 772 54 11, room 6475 EDIT) The examiner will visit the exam room at 15:00 and 17:00.
CHALMERS UNIVERSITY OF TECHNOLOGY Department of Computer Science and Engineering Examination in Databases, TDA357/DIT620 Tuesday 17 December 2013, 14:00-18:00 Examiner: Results: Exam review: Grades: Graham
More informationFiles. Files. Files. Files. Files. File Organisation. What s it all about? What s in a file?
Files What s it all about? Information being stored about anything important to the business/individual keeping the files. The simple concepts used in the operation of manual files are often a good guide
More informationDatabases What the Specification Says
Databases What the Specification Says Describe flat files and relational databases, explaining the differences between them; Design a simple relational database to the third normal form (3NF), using entityrelationship
More informationFundamentals of Database Design
Fundamentals of Database Design Zornitsa Zaharieva CERN Data Management Section - Controls Group Accelerators and Beams Department /AB-CO-DM/ 23-FEB-2005 Contents : Introduction to Databases : Main Database
More informationA brief overview of developing a conceptual data model as the first step in creating a relational database.
Data Modeling Windows Enterprise Support Database Services provides the following documentation about relational database design, the relational database model, and relational database software. Introduction
More informationDatabase Design Methodologies
Critical Success Factors in Database Design Database Design Methodologies o Work interactively with the users as much as possible. o Follow a structured methodology throughout the data modeling process.
More informationHow To Improve Performance In A Database
Some issues on Conceptual Modeling and NoSQL/Big Data Tok Wang Ling National University of Singapore 1 Database Models File system - field, record, fixed length record Hierarchical Model (IMS) - fixed
More informationRequirement Analysis & Conceptual Database Design. Problem analysis Entity Relationship notation Integrity constraints Generalization
Requirement Analysis & Conceptual Database Design Problem analysis Entity Relationship notation Integrity constraints Generalization Introduction: Lifecycle Requirement analysis -> Text Conceptual Design
More informationDatabase Design Process
Database Design Process Entity-Relationship Model From Chapter 5, Kroenke book Requirements analysis Conceptual design data model Logical design Schema refinement: Normalization Physical tuning Problem:
More informationFundamentals of Database System
Fundamentals of Database System Chapter 4 Normalization Fundamentals of Database Systems (Chapter 4) Page 1 Introduction To Normalization In general, the goal of a relational database design is to generate
More informationCHAPTER 6 DATABASE MANAGEMENT SYSTEMS. Learning Objectives
CHAPTER 6 DATABASE MANAGEMENT SYSTEMS Management Information Systems, 10 th edition, By Raymond McLeod, Jr. and George P. Schell 2007, Prentice Hall, Inc. 1 Learning Objectives Understand the hierarchy
More informationAS LEVEL Computer Application Databases
AS LEVEL Computer Application Databases YLLSS In the syllabus, we have Applications of databases in society Students should be aware of the uses and applications of databases in everyday life (e.g. the
More informationThe Relational Model. Why Study the Relational Model? Relational Database: Definitions
The Relational Model Database Management Systems, R. Ramakrishnan and J. Gehrke 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Microsoft, Oracle, Sybase, etc. Legacy systems in
More informationSAMPLE FINAL EXAMINATION SPRING SESSION 2015
SAMPLE FINAL EXAMINATION SPRING SESSION 2015 School of Computing, Engineering and Mathematics Student family name: Student given name/s: Student ID number: Course: Unit Name (In Full): Database Design
More informationOnce the schema has been designed, it can be implemented in the RDBMS.
2. Creating a database Designing the database schema... 1 Representing Classes, Attributes and Objects... 2 Data types... 5 Additional constraints... 6 Choosing the right fields... 7 Implementing a table
More informationChapter 5: Logical Database Design and the Relational Model Part 2: Normalization. Introduction to Normalization. Normal Forms.
Chapter 5: Logical Database Design and the Relational Model Part 2: Normalization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Robert C. Nickerson ISYS
More informationExercise 1: Relational Model
Exercise 1: Relational Model 1. Consider the relational database of next relational schema with 3 relations. What are the best possible primary keys in each relation? employ(person_name, street, city)
More informationEntity Relationship Diagram
Yufei Tao Department of Computer Science and Engineering Chinese University of Hong Kong A primary goal of database design is to decide what tables to create. Usually, there are two principles: 1 Capture
More informationFoundations of Information Management
Foundations of Information Management - WS 2009/10 Juniorprofessor Alexander Markowetz Bonn Aachen International Center for Information Technology (B-IT) Alexander Markowetz Born 1976 in Brussels, Belgium
More informationThe Relational Data Model: Structure
The Relational Data Model: Structure 1 Overview By far the most likely data model in which you ll implement a database application today. Of historical interest: the relational model is not the first implementation
More informationA Comparative Analysis of Entity-Relationship Diagrams 1
A Comparative Analysis of Entity-Relationship Diagrams 1 Il-Yeol Song Drexel University Mary Evans USConnect E.K. Park U.S. Naval Academy The purpose of this article is to collect widely used entity-relationship
More informationData Modeling Basics
Information Technology Standard Commonwealth of Pennsylvania Governor's Office of Administration/Office for Information Technology STD Number: STD-INF003B STD Title: Data Modeling Basics Issued by: Deputy
More informationSection of DBMS Selection & Evaluation Questionnaire
Section of DBMS Selection & Evaluation Questionnaire Whitemarsh Information Systems Corporation 2008 Althea Lane Bowie, Maryland 20716 Tele: 301-249-1142 Email: mmgorman@wiscorp.com Web: www.wiscorp.com
More informationObject Oriented Databases. OOAD Fall 2012 Arjun Gopalakrishna Bhavya Udayashankar
Object Oriented Databases OOAD Fall 2012 Arjun Gopalakrishna Bhavya Udayashankar Executive Summary The presentation on Object Oriented Databases gives a basic introduction to the concepts governing OODBs
More informationOVERVIEW 1.1 DATABASE MANAGEMENT SYSTEM (DBMS) DEFINITION:-
1 1 OVERVIEW Topics Covered: 1.1 Database management system 1.2 Data Independence 1.3 Data Abstraction 1.4 Data Models 1.5 DBMS Architecture 1.6 Users of DBMS 1.7 Overview of Conventional Data Models 1.1
More informationImplementing evolution: Database migration
2IS55 Software Evolution Sources Implementing evolution: Database migration Alexander Serebrenik / SET / W&I 7-6-2010 PAGE 1 Last week Recapitulation Assignment 8 How is it going? Questions to Marcel:
More informationwww.gr8ambitionz.com
Data Base Management Systems (DBMS) Study Material (Objective Type questions with Answers) Shared by Akhil Arora Powered by www. your A to Z competitive exam guide Database Objective type questions Q.1
More informationCS2Bh: Current Technologies. Introduction to XML and Relational Databases. The Relational Model. The relational model
CS2Bh: Current Technologies Introduction to XML and Relational Databases Spring 2005 The Relational Model CS2 Spring 2005 (LN6) 1 The relational model Proposed by Codd in 1970. It is the dominant data
More informationTutorial on Relational Database Design
Tutorial on Relational Database Design Introduction Relational database was proposed by Edgar Codd (of IBM Research) around 1969. It has since become the dominant database model for commercial applications
More informationThe E-R èentity-relationshipè data model views the real world as a set of basic objects èentitiesè and
CMPT-354-Han-95.3 Lecture Notes September 20, 1995 Chapter 2 The Entity-Relationship Model The E-R èentity-relationshipè data model views the real world as a set of basic objects èentitiesè and relationships
More informationSCHEMAS AND STATE OF THE DATABASE
SCHEMAS AND STATE OF THE DATABASE Schema the description of a database specified during database design relatively stable over time Database state the data in a database at a particular moment the set
More information