1 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 Model (ER model) for DB design, enumerate the basic constructs of the ER model, develop ER diagrams (schemas in the ER model) for a given application, translate ER models into equivalent (as far as possible) relational models.
2 The Entity-Relationship Model 222 Overview 1. Database Design Overview 2. Basic ER Constructs 3. Kinds of Relationships (Cardinalities) 4. Keys, Weak Entities 5. Translation into the Relational Model
3 Database Design (1) 223 Overall goal of DBMS usage: Efficiently develop programs to support given real-world tasks. These programs need to store data persistently. To develop these programs, apply proven methods of software engineering specialized to support data-intensive programs. Database Design Database Design is the process of developing a database schema for a given application. DB design is a subtask of the overall software engineering effort.
4 Database Design (2) 224 The specification of programs and data is intertwined: The schema should contain the data needed by the programs. Programs are often easy to develop once the structure of the data to be manipulated has been specified. Data, however, is an independent resource: Typically, additional programs will be developed later based on the collected data. Also, ad-hoc queries will be posed against the DB.
5 Database Design (3) 225 During DB design, a formal model of the relevant aspects of the real world ( mini world, domain of discourse ) must be built. Once the DB is up and running, questions will be posed against the DB. Knowledge of these questions beforehand is important input to the DB design process and helps to identify the relevant parts of the real world. In some sense, the real world is the measure of correctness for the DB schema: the possible DB states should correspond to the states of the real world.
6 Database Design (4) 226 DB design is not easy for a variety of reasons: Expertise: The designer must become an expert for the application domain or needs to talk to such experts. Depending on the domain, these experts might not be used to give a complete and formal account of their field. Flexibility: The real world typically permits exceptions and corner cases. Does the DB schema need to reflect these? Size: Database schemas may become huge (in terms of number of relations, attributes, constraints). Due to this complexity, DB design is a multi-step process.
7 Database Design (5) 227 Three Phases of DB Design 1 Conceptual Database Design. Produces the initial model of the mini world in a conceptual data model (e.g., in the ER model). 2 Logical Database Design. Transforms the conceptual schema into the data model supported by the DBMS (e.g., the relational model). 3 Physical Database Design. Design indexes, table distribution, buffer size, etc., to maximize performance of the final system (subject of Datenbanken II ).
8 Database Design (6) 228 Why multiple design phases? Partition the problem, attack one sub-problem after the other. For example, during conceptual design there is no need to worry about performance aspects or limitations of the specific SQL dialect of the RDBMSs. DBMS features do not influence the conceptual design and only partially influence the logical design. Thus, the conceptual design work is not invalidated, if a different DBMS is used later on.
9 Example (1) 229 ER schema in graphical notation: ER schema in graphical notation: Instructor teaches Course Name Phone No Title This mini world talks about instructors and courses. Instructors teach courses. Instructors have a name and a phone number. Courses are numbered and have titles.
10 Example (2) 230 A possible state of this mini world Grust Name 7111 Phone Instructor Course No Title XML No Title DB1
11 The ER Model (1) 231 The Entity-Relationship Model is often referred to as a semantic data model, because it more closely resembles real world scenarios than, e.g., the relational model. In the ER model, we model the concept of Instructors. In the relational model we deal with names and phone numbers. In the ER model, there is a distinction between entities (objects) and relationships between such entities. In the relational model, both concepts are represented by relations.
12 The ER Model (2) 232 Proposed by Peter Chen (1976), today at Louisiana State University ( chen/chen.html). The ER model comes with a graphical notation which helps to establish quick overviews of database application schemas. Such ER diagrams are also a great way to communicate schemas to non-expert/future DB users. There are no ER Model DBMS. Instead, we will describe a translation of ER model concepts into the relational model.
13 The Entity-Relationship Model 233 Overview 1. Database Design Overview 2. Basic ER Constructs 3. Kinds of Relationships (Cardinalities) 4. Keys, Weak Entities 5. Translation into the Relational Model
14 Basic ER Model Concepts (1) 234 Entities: An object in the mini world about which information is to be stored. Examples: persons, books, courses. Note: entities do not have to correspond to objects of physical existence. Entities may also represent conceptual objects like, e.g., vacations. The mini world that has to be modelled can contain only a finite number of objects. It must be possible to distinguish entities from each other, i.e., objects must have some identity. Examples: entity book identified by ISBN number, entity vacations identified by travel agency booking number.
15 Basic ER Model Concepts (2) 235 Attribute: A property or feature of an entity (or relationship, see below). Example: the title of this course entity is Foundations of Databases. The value of an attribute is an element of a data type like string, integer, date. These values have a printable representation (which entities have not).
16 Basic ER Model Concepts (3) 236 Relationship: A relation not in the strict relational model sense between pairs of entities (a binary relationship). Example: Grust (an entity) teaches (a relationship) the course Foundations of Databases (an entity).
17 ER Diagrams (1) 237 Entity E: E Attribute A of Entity Type E: E A Relationship R between Entity Types E 1 and E 2 : E 1 R E 2
18 ER Diagrams (2) 238 Relationships may also exist entities of the same type ( recursive relationship ): is precondition for Course Precondition requires knowledge of In this case, role names have to be attached to the connecting edges. In the ER model, role names may be attached to any kind of relationship for documentation purposes.
19 ER Diagrams (3) 239 Relationships may have attributes, too: Student solved Exercise points This models the fact that a number of points is stored for every pair of a student X and an exercise Y such that X submitted a solution for Y.
20 Graphical Syntax An ER diagram contains boxes, diamonds, ovals, plus interconnecting lines. 2 Boxes, diamonds, and ovals are each labelled by a string. Box labels are unique in the entire diagram. Oval labels are unique for a single box or diamond. Diamond labels are unique for a pair of connected boxes. 3 Interconnecting lines are only allowed between box diamond, box oval, diamond oval. 4 A diamond has exactly two connecting lines to boxes. There may be any number of connections to ovals. 5 An oval has exactly one connecting line.
21 ER Example 241 Modelling a Mini World: Define an ER Diagram Information about researchers in the database field is to be stored. For each researcher, his/her last name, first name, address, and homepage URI are relevant. Researchers are affiliated with universities and assume a certain position (e.g., professor, lecturer). Relevant university information are the name, homepage URI, and country. Researchers publish articles (of a given title) in journals.
22 The Entity-Relationship Model 242 Overview 1. Database Design Overview 2. Basic ER Constructs 3. Kinds of Relationships (Cardinalities) 4. Keys, Weak Entities 5. Translation into the Relational Model
23 Cardinalities (1) 243 General ER relationship: E 1 R E 2
24 Cardinalities (2) 244 In general, there is no restriction on how often an entity participates in an relationship R. An entity can be connected to one entity of the other type, to more than one, or it can have no R-partner at all. However, specific application semantics dictate to how many E 2 entities an E 1 entity can be related: Man is married to Woman
25 Cardinalities (3) 245 The ER model introduces the (min, max) notation to specify an interval of possible participations in an relationship: E 1 (m 1,n 1 ) R (m 2,n 2 ) E 2 An entity of type E 1 may be related to at least m 1 and at most n 1 entities of type E 2. Likewise, m 2 is the minimum number and n 2 is the maximum number of E 1 entities to which an E 2 entity is related
26 Cardinalities (4) 246 Extensions: may be used as maximum if there is no limit. (0, ) means no restriction at all (general relationship).
27 Cardinalities (5) 247 Marriage Man (0,1) is married to (0,1) Woman A man can be married to at most one woman and vice versa. Airport Locations Airport (1,1) lies in (0,*) Country An airport lies in exactly one country. A country may have arbitrarily many airports (and maybe none at all).
28 Cardinalities (6) 248 Derive cardinalities from verbal specifications Besides normal customers, the database may contain customers who have not yet ordered anything. Order (, ) from (, ) Customer Derive cardinalities from verbal specifications An order can contain several products. Order (, ) for (, ) Product
29 Selecting Cardinalities 249 Sometimes a sketch of a valid database state may help in selecting the right cardinalities, e.g., for the state sketched on slide 243, a viable cardinality for E 1 R may be (0, 3). Application knowledge might lead to weaker restrictions, in this example (0, 5) or (0, ). A cardinality (a, b) is weaker than (c, d) if a c and d b. In real applications, the cardinalities (0, 1), (1, 1), and (0, ) are the most common and especially easy to enforce in the relational model.
30 Common Cases (1) 250 Normally, the minimum cardinality will be 0 or 1, and the maximum cardinality will be 1 or. Thus, only the (0, 1), (1, 1), (0, ), (1, ) cardinalities are common in practice. To understand a relationship, one must know the cardinality specifications on both sides. The maximum cardinalities on each side are used to distinguish between many-to-many, one-to-many / many-to-one, and one-to-one relationships.
31 Common Cases (2) 251 Many-to-many relationships: Both maximum cardinalities are (the minimum cardinalities are 0 or 1): Many-to-many relationship Student (0,*) takes (0,*) Course This is the most general/least restrictive case of a relationship. When translated into the relational model, the representation of many-to-many relationships requires an extra table.
32 One-to-many relationships do not require an extra table in an equivalent representation in the relational model. Common Cases (3) 252 One-to-many relationships: Maximum cardinality 1 on the many side and on the one side: One-to-many relationship Instructor (0,*) teaches (1,1) Course One instructor teaches many courses, but each course is run by exactly one instructor.
33 Common Cases (4) 253 One-to-one relationships: Maximum cardinality 1 on both sides: One-to-one relationship Employee (0,1) is head of (1,1) Department Each department has exactly one department head, some employees are the head of one department. Note how mandatory or optional participation in an relationship determines the minimum cardinalities.
34 Cardinalities: Alternative Notations (1) 254 Widespread variants of notations for cardinalities: Leave particpiation unspecified: Cardinalities are either many-to-many (N:M), one-to-many (1:N), or one-to-one (1:1). One-to-many relationship Instructor 1 teaches N Course
35 Cardinalities: Alternative Notations (2) 255 Sometimes found in software supporting visual ER diagram development (e.g., in Oracle Designer TM ): One-to-many relationship teaches Instructor Course taught by The crow foot indicates the many side. Dashed lines indicate optional participiation. Relationship roles are given (for both sides).
36 The Entity-Relationship Model 256 Overview 1. Database Design Overview 2. Basic ER Constructs 3. Kinds of Relationships (Cardinalities) 4. Keys, Weak Entities 5. Translation into the Relational Model
37 Keys (1) 257 ER Key A key K of an entity type E a is an attribute of E which uniquely identifies the entities of this type. No two different entities share the same value for the key attribute. Composite keys are allowed. K E A 1 A 2 a Only entity types can have key attributes.
38 Keys (2) 258 The translation of ER schemas into relational schemas requires the declaration of ER keys. If there is no natural key, add artificial identifiers (e.g., integers, remember attributes EMPNO, DEPTNO from Chapter 1) which then represent the entities.
39 Weak Entities (1) 259 In many schemas, some entities describe a kind of detail that cannot exist without a master (or owner) entity. In such a case, 1 there is a relationship with cardinality (1, 1) on the detail entity side, and in addition 2 the key of the master is inherited and becomes part of the key of the detail entity. Inv No Date Invoice (1, ) has (1,1) Position Inv No Pos
40 Weak Entities (2) 260 Without a specific ER construct for this case, we would require the following additional constraint: If two entities are in has relationship, then their attribute Inv No are required to have identical values. For example, invoice #12 cannot have position 2 in invoice #42 as detail. Such constraints occur if an entity does not have a key by itself, but it is only unique in the context of some other (master) entity.
41 Weak Entities (3) 261 Note: In such cases, keys are always composite. Examples: A classroom is identified by a building and a room number. A section in a book is identified by a chapter and a section title. A web page URI is composed of a web server DNS address and a path on that server. There is also an existence dependency. If the building is pulled down, the classrooms automatically disappear. If the web server is shut down, all URIs on that server cease to function.
42 Weak Entities (4) 262 In the ER model, such scenarios are modelled via weak entities 3. In ER diagrams, weak entities and their identifying relationships are indicated by double lines: Inv No Date Invoice (1, ) has (1,1) Position Pos For the weak entity, the inherited part of the key is not shown. 3 Non-weak entities are also called strong entities.
43 Weak Entities (5) 263 Modelling with weak entities Model a set of online quizzes (multiple choice tests). Each quiz is identified by a title, each question within a quiz is numbered, and each possible answer to a given question is referenced by a letter. For each question and answer, the associated text is stored. Answers are classified into correct and incorrect ones. What is the complete key for each of the occurring entity types?
44 The Entity-Relationship Model 264 Overview 1. Database Design Overview 2. Basic ER Constructs 3. Kinds of Relationships (Cardinalities) 4. Keys, Weak Entities 5. Translation into the Relational Model
45 ER Diagram Example 265 CustNo Customer (0, ) Name Phone places (1,1) Description Order (0, ) for (0, ) Product OrdNo Date Quantity ProdNo Price
46 Step 1: Entities (1) 266 Transforming an ER entity E: 1 Create a table for each entity. The table name is E (conventionally: E + s ). 2 The columns of this table are the attributes of the entity type. 3 The primary key of the table is the primary key of the entity type. If E s key is composite, so will be the relational key. If E has no key, add an artifical key to the table.
47 Step 1: Entities (2) 267 Customers CustNo Name Phone 10 Jones Smith Products ProdNo Description Price 1 Apple Kiwi Orange 0.60 Orders OrdNo Date 200 2/15/ /16/04
48 Step 1B: Weak Entities 268 Invoice (1, ) has Position Inv No Date Pos When a weak entity is translated, the key attributes of the owner entity are added as a key and foreign key: Position (Pos, Inv No Invoice,...) This automatically implements the relationship. It makes sense to specify DELETE CASCADES for the foreign key: if an invoice is deleted, all its positions will be removed from the DB state, too.
49 Step 2: One-To-Many Relationships (1) 269 Transforming a relationship R: 1 If R has maximum cardinality 1 on one side, R is one-to-many 4. Example: Customer (0, ) places (1, 1) Order, one customer places many orders. 2 In this case, add the key of the one side as a column to the many table to implement R. 3 This column will be a foreign key referencing a row in the table representing the related entity. 4 If R has maximum cardinality 1 on both sides, it is actually one-to-one, see below.
50 Step 2: One-To-Many Relationships (2) 270 Orders (OrdNo, Date, CustNo Customers) Orders OrdNo Date CustNo 200 2/15/ /16/04 11 Customers CustNo Name Phone 10 Jones Smith Convention: use relationship and role to name foreign key column: Orders (OrdNo, Date, placed by Customers)
51 Step 2: One-To-Many Relationships (3) 271 Transforming a one-to-many relationship R: 4 If the minimum cardinality is 1 on the many side (see example), null values are not allowed in the foreign key column (column placed by in example). If the minimum cardinality is 0, null values are allowed in the foreign key column. The foreign key is null for those entities that do not participate in R at all.
52 Step 2: Relationship Attributes 272 To transform one-to-many relationship attribute(s), e.g. Student (0, ) borrowed (0,1) Book Stud ID Date ISBN store the relationship attribute(s) together with the reference to the related entity, e.g. Books (ISBN,..., borrowed by Students, Date)
53 273 Step 2: One-To-Many Relationships: A Variant One-to-many relationships R with cardinality (0,1) can be translated into a table of their own: borrowed by (ISBN Books, Stud ID Students, Date) The extra table holds the key values of the related entities plus the relationship attributes. The key attributes of the side with the (0,1) cardinality become the key of this relation. Each book can be borrowed only once at the same time. This does not model R correctly if the cardinality is (1,1) Why?
54 Step 3: Many-To-Many Relationships (1) 274 Transforming a many-to-many relationship R: 1 If R has maximum cardinality on both sides, R is many-to-many. Example: Order (1, ) for (0, ) Product, an order contains many products, a product may be part of many orders. 2 R becomes its own table. 3 The columns of this table are the keys of both participating entity types. 4 These columns act as foreign keys referencing the entities and, at the same time, together form a composite key for the extra table.
55 Step 3: Many-To-Many Relationships (2) 275 Transforming a many-to-many-relationship R: 5 Relationship attributes are added as columns to the table representing R. for (OrdNo Orders, ProdNo Products, Quantity) Composite key? Is it really necessary that both entity keys (here: OrdNo, ProdNo) form a composite key for the relationship table?
56 Step 3: Many-To-Many Relationships (3) 276 for (OrdNo Orders, ProdNo Products, Quantity) for OrdNo ProdNo Quantity Orders OrdNo Date CustNo 200 2/15/ /16/04 11 Products ProdNo Description Price 1 Apple Kiwi Orange 0.60
57 Step 3: Many-To-Many Relationships (4) 277 Transforming a many-to-many relationship R: Note: Minimum cardinalties other than 0 for R cannot be enforced by the relational model per se, i.e., in terms of key constraints. Order (0, ) for (1, ) Product Every product occurs in at least one order. If this is important to guarantee database consistency (valid DB state), this constraint needs to be checked by the application program or a general RDBMS constraint mechanism.
58 Step 4: One-To-One Relationships (1) 278 Transforming a one-to-one relationship R: Department (1,1) led by (0,1) Employee DName ID 1 If R has maximum cardinality 1 on both sides, R is one-to-one. 2 We can essentially transform as if R were one-to-many, but additional key constraints are generated.
59 Step 4: One-To-One Relationships (2) 279 To which entity table shall we add the led by attribute to represent the relationship? Department (1,1) led by (0,1) Employee DName ID Since we have Department (1, 1) led by ( every department is led by exactly one employee ), it makes sense to host the relationship in the Department table: Department (DName,..., led by Employee) We may declare the foreign key led by as NOT NULL. (This is not possible if led by is hosted in the Employee table.)
60 Step 4: One-To-One Relationships (3) 280 Department (1,1) led by (0,1) Employee DName ID Department (DName,..., led by Employee) Note: led by now also is a key for the Department table. led by is a key for table Department Why is this the case in this example? This key constraint enforces the maximum cardinality of 1 (on the Employee side).
61 Step 4: One-To-One Relationships (4) 281 Man (0,1) married (0,1) Woman MName Born WName Born Two variants: 1 Any of the two (not both!) entity tables may host the married foreign key (null values allowed). 2 Translate the relationship into a table of its own: married (MName Man, WName Woman) A one-to-one relationship in an extra table What would be the correct key(s) for table married?
62 Step 4: One-To-One Relationships (5) 282 Customer (1,1) has (1,1) Card SSN Name CardNo CreditLimit In order to enforce the minimum cardinality 1 on both sides, the entity tables need to be merged: CustomerCard (SSN, Name, CardNo, CreditLimit) No null values are allowed. Both, SSN and CardNo, are keys of this table. One is selected as primary key, the other is an secondary key.
63 Limitations (1) 283 The following ER relationship cardinalities can be faithfully represented in the relational model: E 1 (1,1) R (0, ) E 2 E 1 (1,1) R (0,1) E 2 E 1 (0,1) R (0, ) E 2 E 1 (0,1) R (0,1) E 2 E 1 (0, ) R (0, ) E 2 E 1 (1,1) R (1,1) E 2
64 Limitations (2) 284 For all other cardinalities, the constraint mechanisms of the relational model will not suffice. Order (1, ) for (0, ) Product No ID Every purchase order includes at least one product item. Relational (foreign) key constraints cannot enforce the minimum cardinality 1. Apply the translation method for (0, ) cardinalities and enforce the constraint in the application (or via an RDBMS trigger whenever a tuple in table Order is inserted).
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
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
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:
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,
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,
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?
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
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
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
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
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
Lecture 12: Entity Relationship Modelling The Entity-Relationship Model Entities Relationships Attributes Constraining the instances Cardinalities Identifiers Generalization 2004-5 Steve Easterbrook. This
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
Process Databases - Entity-Relationship Modelling Ramakrishnan & Gehrke identify six main steps in designing a database Requirements Analysis Conceptual Design Logical Design Schema Refinement Physical
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
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
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
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
IV. The (Extended) Entity-Relationship Model The Extended Entity-Relationship (EER) Model Entities, Relationships and Attributes Cardinalities, Identifiers and Generalization Documentation of EER Diagrams
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
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
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
Eduardo Cunha de Almeida email@example.com Outline of the course Introduction Database Systems (E. Almeida) Distributed Hash Tables and P2P (C. Cassagnes) NewSQL (D. Kim and J. Meira) NoSQL (D. Kim)
Database Systems Lecture 1: Introduction General Information Professor: Leonid Libkin Contact: firstname.lastname@example.org Lectures: Tuesday, 11:10am 1 pm, AT LT4 Website: http://homepages.inf.ed.ac.uk/libkin/teach/dbs09/index.html
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
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
Databasesystemer, forår 2005 IT Universitetet i København Forelæsning 3: Business rules, constraints & triggers. 3. marts 2005 Forelæser: Rasmus Pagh Today s lecture Constraints and triggers Uniqueness
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
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
ECS-165A WQ 11 36 3. Relational Model and Relational Algebra Contents Fundamental Concepts of the Relational Model Integrity Constraints Translation ER schema Relational Database Schema Relational Algebra
Relational Databases IST400/600 Jian Qin Database A collection of data? Everything you collected for your group project? A computer system? File? Spreadsheet? Information system? Date s criteria: Integration
Data Modeling: Part 1 Entity Relationship (ER) Model MBA 8473 1 Cognitive Objectives (Module 2) 32. Explain the three-step process of data-driven information system (IS) development 33. Examine the purpose
AVOIDANCE OF CYCLICAL REFERENCE OF FOREIGN KEYS IN DATA MODELING USING THE ENTITY-RELATIONSHIP MODEL Ben B. Kim, Seattle University, email@example.com ABSTRACT The entity-relationship (ER model is clearly
2. Designing XML DTDs 2-1 Chapter 2: Designing XML DTDs References: Tim Bray, Jean Paoli, C.M. Sperberg-McQueen: Extensible Markup Language (XML) 1.0, 1998. [http://www.w3.org/tr/rec-xml] See also: [http://www.w3.org/xml].
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
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
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
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
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
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
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
Designing Databases C Introduction Businesses rely on databases for accurate, up-to-date information. Without access to mission critical data, most businesses are unable to perform their normal daily functions,
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
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
Data Modeling Windows Enterprise Support Database Services provides the following documentation about relational database design, the relational database model, and relational database software. Introduction
Database Fundamentals Robert J. Robbins Johns Hopkins University firstname.lastname@example.org Database Fundamentals: 1 What is a Database? General: A database is any collection of related data. Restrictive: A database
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/
The Relational Model Chapter 3 Instructor: Vladimir Zadorozhny email@example.com Information Science Program School of Information Sciences, University of Pittsburgh 1 Why Study the Relational Model?
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:
COS 597A: Principles of Database and Information Systems elational model elational model A formal (mathematical) model to represent objects (data/information), relationships between objects Constraints
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
Entity/Relationship Modelling Database Systems Lecture 4 Natasha Alechina In This Lecture Entity/Relationship models Entities and Attributes Relationships Attributes E/R Diagrams For more information Connolly
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?
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
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
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
EECS 647: Introduction to Database Systems Instructor: Luke Huan Spring 2013 Administrative Take home background survey is due this coming Friday The grader of this course is Ms. Xiaoli Li and her email
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.
CS2Bh: Current Technologies Introduction to XML and Relational Databases Spring 2005 Introduction to Databases CS2 Spring 2005 (LN5) 1 Why databases? Why not use XML? What is missing from XML: Consistency
Introduction The history of database system research is one of exceptional productivity and startling economic impact. We have learnt that from the days of file-based systems there are better ways to handle
SQL DATA DEFINITION: KEY CONSTRAINTS CS121: Introduction to Relational Database Systems Fall 2015 Lecture 7 Data Definition 2 Covered most of SQL data manipulation operations Continue exploration of SQL
: 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
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
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
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
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
Relational Databases Christopher Simpkins firstname.lastname@example.org Relational Databases A relational database is a collection of data stored in one or more tables A relational database management system
C H A P T E R 7 Database Design and the E-R Model Practice Exercises 7.1 Answer: The E-R diagram is shown in Figure 7.1. Payments are modeled as weak entities since they are related to a specific policy.
Chapter 2 Data Model Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel 1 In this chapter, you will learn: Why data models are important About the basic data-modeling
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
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
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
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
CMPT 354 Database Systems Simon Fraser University Summer 2016 Instructor: Oliver Schulte Assignment 1: Entity-Relationship Modeling. The Relational Model. MS SQL Server. Instructions: Check the instructions
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
Information Systems 2 Information Systems 2 1. Modelling Information Systems I: Databases Lars Schmidt-Thieme Information Systems and Machine Learning Lab (ISMLL) Institute for Business Economics and Information
The Relational Data Model and Relational Database Constraints Chapter Outline Relational Model Concepts Relational Model Constraints and Relational Database Schemas Update Operations and Dealing with Constraint
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
Databases and DBMS Eric Lew (MSc, BSc) SeconSys Inc. Nov 2003 What is a Database? Data (singular: datum) Factual Information Database Organized body of related information Repository / storage of information
Data Modelling and E-R Diagrams So far we have considered some of the basic ideas behind relational theory, and we will continue with this in subsequent sections. In this section we look at the processes
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
CSC 443 Data Base Management Systems Lecture 6 SQL As A Data Definition Language Basic SQL SQL language Considered one of the major reasons for the commercial success of relational databases SQL Structured
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