Database Systems - Introduction to Databases and Data Warehouses. Copyright (c) 2014 Pearson Education, Inc.
|
|
|
- Jessie Garrison
- 7 years ago
- Views:
Transcription
1 Database Systems - Introduction to Databases and Data Warehouses Copyright (c) 2014 Pearson Education, Inc.
2 INTRODUCTION Entity-relationship (ER) modeling - conceptual database modeling technique Enables the structuring and organizing of the requirements collection process Provides a way to graphically represent the requirements ER diagram (ERD) - the result of ER modeling Serves as a blueprint for the database
3 ENTITIES Entities - constructs that represent what the database keeps track of The basic building blocks of an ER diagram Represent various real world notions, such as people, places, objects, events, items, and other concepts Within on ERD each entity must have a different name
4 ENTITIES Two entities
5 ENTITIES Entity instances (entity members) - occurrences of an entity Entities themselves are depicted in the ER diagrams while entity instances are not Entity instances are eventually recorded in the database that is created based on the ER diagram
6 ATTRIBUTES Attribute - depiction of a characteristic of an entity Represents the details that will be recorded for each entity instance Within one entity, each attribute must have a different name Unique Attribute - attribute whose value is different for each entity instance Every regular entity must have at least one unique attribute
7 ATTRIBUTES An entity with attributes
8 RELATIONSHIPS Relationship - ER modeling construct depicting how entities are related Within an ER diagram, each entity must be related to at least one other entity via a relationship
9 RELATIONSHIPS Cardinality constraints - depict how many instances of one entity can be associated with instances of another entity Maximum cardinality o One (represented by a straight bar: I) o Many (represented by a crow s foot symbol) Minimum cardinality (participation) o Optional (represented by a circular symbol: 0) o Mandatory (represented by a straight bar: I)
10 RELATIONSHIPS A relationship between two entities
11 RELATIONSHIPS Four possible cardinality constraints
12 RELATIONSHIPS Several possible versions of the relationship ReportsTo
13 RELATIONSHIPS Types of Relationships (maximum cardinality-wise) One-to-one relationship (1:1) One-to-many relationship (1:M) Many-to-many relationship (M:N)
14 RELATIONSHIPS Three types of relationships (maximum cardinality-wise)
15 RELATIONSHIPS A 1:M Relationship A M:N Relationship A 1:1 Relationship
16 RELATIONSHIPS Relationship instances - occurrences of a relationship Occur when an instance of one entity is related to an instance of another entity via a relationship Relationship themselves are depicted in the ER diagrams while relationship instances are not Relationship instances are eventually recorded in the database that is created based on the ER diagram
17 RELATIONSHIPS A relationship and its instances
18 RELATIONSHIPS Relationship attributes In some cases M:N relationships can actually have attributes of their own
19 RELATIONSHIPS A M:N relationship with an attribute
20 RELATIONSHIPS A 1:M relationship with and without an attribute
21 ER diagram example: ZAGI Retail Company Sales Department Database
22 ATTRIBUTES Composite attribute attribute that is composed of several attributes Not an additional attribute of an entity Its purpose is to indicate a situation in which a collection of attributes has an additional meaning, besides the individual meanings of each attribute
23 ATTRIBUTES An entity with a composite attribute
24 ATTRIBUTES Another entity with a composite attribute
25 ATTRIBUTES Composite attributes sharing components
26 ATTRIBUTES Composite unique attribute attribute that is composed of several attributes and whose value is different for each entity instance
27 ATTRIBUTES An entity with a unique composite attribute
28 ATTRIBUTES Multiple unique attributes (candidate keys) - when an entity has more than one unique attribute each unique attribute is also called a candidate key
29 ATTRIBUTES An entity with multiple unique attributes (candidate keys)
30 ATTRIBUTES An entity with a regular and composite candidate key
31 ATTRIBUTES Multivalued attribute - attribute for which instances of an entity can have multiple values for the same attribute
32 ATTRIBUTES A multivalued attribute
33 ATTRIBUTES A scenario that does not use multivalued attributes
34 ATTRIBUTES Derived attribute - attribute whose values are calculated and not permanently stored in a database
35 ATTRIBUTES A derived attribute example
36 ATTRIBUTES Another derived attribute example
37 ATTRIBUTES Optional attribute - attribute that is allowed to not have a value
38 ATTRIBUTES An optional attribute example
39 ATTRIBUTES EXAMPLE: An entity with various types of attributes
40 RELATIONSHIPS Exact minimum and maximum cardinality in relationships In some cases the exact minimum and/or maximum cardinality in relationships is known in advance Exact minimum/and or maximum cardinalities can be depicted in ER diagrams
41 RELATIONSHIPS A relationship with specific minimum and maximum cardinalities
42 RELATIONSHIPS A relationship with a mixture of specific and non-specific cardinalities
43 RELATIONSHIPS Degree of a relationship - reflects how many entities are involved in the relationship Binary relationship - relationship between two entities (degree 2 relationship) Unary relationship (recursive relationship) - occurs when an entity is involved in a relationship with itself (degree 1 relationship)
44 RELATIONSHIPS Unary relationship examples
45 RELATIONSHIPS Relationship roles - additional syntax that can be used in ER diagrams at the discretion of a data modeler to clarify the role of each entity in a relationship
46 RELATIONSHIPS Unary relationships with role names
47 RELATIONSHIPS A binary relationship with role names
48 RELATIONSHIPS Multiple relationships between same entities Same entities in an ER diagram can be related via more than one relationship
49 RELATIONSHIPS Multiple relationships between the same entities
50 WEAK ENTITY Weak entity - ER diagram construct depicting an entity that does not have a unique attribute of its own Owner entity - entity whose unique attribute provides a mechanism for identifying instances of a weak entity Identifying relationship - relationship between a weak entity and its owner entity in which each instance of a weak entity is associated with exactly one instance of an owner entity Each weak entity must be associated with its owner entity via an identifying relationship Unique attribute from the owner entity uniquely identifies every instance of the weak entity via an identifying relationship
51 WEAK ENTITY Partial key - attribute of a weak entity that combined with the unique attribute of the owner entity uniquely identifies the weak entity's instances Combination of the partial key and the unique attribute from the owner entity uniquely identifies every instance of the weak entity
52 WEAK ENTITY A weak entity example with entity instances
53 WEAK ENTITY A weak entity versus a multivalued composite attribute
54 WEAK ENTITY A weak entity with an identifying and regular relationship
55 WEAK ENTITY Identifying relationship is either 1:M or 1:1 relationship In case of 1:M identifying relationship, a weak entity must have a partial key attribute In case of 1:1 identifying relationship, a weak entity doesn t need to have a partial key attribute
56 WEAK ENTITY A weak entity with a 1:1 identifying relationship
57 NAMING CONVENTIONS FOR ER DIAGRAMS Entities and attributes Use singular (rather than plural) nouns Relationships Use verbs or verb phrases, rather than nouns
58 NAMING CONVENTIONS FOR ER DIAGRAMS Names should be as brief as possible, without being too condensed as to obscure the meaning of the construct If possible, give all attributes in the entire ER diagram different names
59 MULTIPLE ER DIAGRAMS When depicting multiple ER diagrams, each diagram should be visualized separately Instead of multiple ER diagrams in one schema a better choice is to present each ER diagram separately
60 MULTIPLE ER DIAGRAMS A schema with two separate ER diagrams (potentially misleading)
61 MULTIPLE ER DIAGRAMS Separate ER diagrams in separate schemas
62 MULTIPLE ER DIAGRAMS Separate ER diagrams in separate schemas
63 Another ER diagram example: HAFH Realty Company Property Management Database
64 DATABASE REQUIREMENTS AND ER MODEL USAGE ER modeling provides a straightforward technique for collecting, structuring, and visualizing requirements An understanding of ER modeling is crucial, not just for creating ER models based on the requirements, but also during the requirements collection process itself It helps keep the focus on asking or seeking answers to the right questions in order to establish the relevant facts about entities, attributes, and relationships
65 DATABASE REQUIREMENTS AND ER MODEL USAGE One of the common mistakes that beginners make when engaging in ER modeling for the first time is not recognizing the difference between an entity and the ER diagram itself
66 DATABASE REQUIREMENTS AND ER MODEL USAGE An ER diagram incorrectly and correctly interpreting requirements
67 DATABASE REQUIREMENTS AND ER MODEL USAGE An ER diagram incorrectly and correctly interpreting requirements
68 DATABASE REQUIREMENTS AND ER MODEL USAGE Another common database requirements collection and ER modeling mistake made by novices is not distinguishing between: Modeling of the data that is wanted and can be kept track of versus Modeling of everything that takes place in an organization
69 DATABASE REQUIREMENTS AND ER MODEL USAGE An ER diagram based on unfeasible and proper requirements
70 VARIOUS ER NOTATIONS There is no universally adopted ER notation to which all database projects conform Instead, there is a variety of available ER notations in use However, if a designer is familiar with one ER notation, other alternative ER notations are easy to understand and use
71 VARIOUS ER NOTATIONS Examples of various ER notations
72 M:N RELATIONSHIPS WITH MULTIPLE INSTANCES BETWEEN THE SAME ENTITIES In some cases, M:N relationships can have multiple occurrences between the same instances of involved entities The following examples illustrates such cases
73 M:N RELATIONSHIPS WITH MULTIPLE INSTANCES BETWEEN THE SAME ENTITIES An ER diagram for an M:N relationship depicting students completing classes
74 M:N RELATIONSHIPS WITH MULTIPLE INSTANCES BETWEEN THE SAME ENTITIES Instances of the M:N relationship Completes
75 M:N RELATIONSHIPS WITH MULTIPLE INSTANCES BETWEEN THE SAME ENTITIES Instances of the M:N relationship Completes with an additional requirement
76 M:N RELATIONSHIPS WITH MULTIPLE INSTANCES BETWEEN THE SAME ENTITIES An ER diagram for an M:N relationship represented as a weak entity
77 M:N RELATIONSHIPS WITH MULTIPLE INSTANCES BETWEEN THE SAME ENTITIES Another M:N relationship represented as a weak entity
78 M:N RELATIONSHIPS WITH MULTIPLE INSTANCES BETWEEN THE SAME ENTITIES A regular entity, instead of an M:N relationship represented as a weak entity
79 ASSOCIATIVE ENTITY Associative entity - construct used as an alternative way of depicting M:N relationships Associative entities do not have unique or partially unique attributes, and often do not have any attributes at all
80 ASSOCIATIVE ENTITY An identical relationship represented as a M:N relationship and as an associative entity
81 ASSOCIATIVE ENTITY An identical relationship represented as a unary M:N relationship and as an associative entity
82 ASSOCIATIVE ENTITY An identical relationship represented as an M:N relationship with an attribute and as an associative entity with an attribute
83 ASSOCIATIVE ENTITY For relationships with a degree higher than 2 such as ternary relationships, associative entities provide a way to eliminate potential ambiguities in the ER diagrams
84 TERNARY RELATIONSHIP Ternary relationship - relationship involving three entities (degree 3 relationship)
85 TERNARY RELATIONSHIP Three binary relationships that are insufficient for depicting given requirements
86 TERNARY RELATIONSHIP A ternary relationship
87 TERNARY RELATIONSHIP A ternary relationship via associative entity
88 TERNARY RELATIONSHIP A regular entity replacing a ternary relationship
89 TERNARY RELATIONSHIP A many-to-many-to-one ternary relationship
90 TERNARY RELATIONSHIP A many-to-many-to-one ternary relationship
91 TERNARY (AND HIGHER DEGREE) RELATIONSHIPS In practice, ternary relationships are relatively rare, and relationships of degree higher than 3 are rarer still
Chapter 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
DATABASE 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
Unit 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,
THE 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
Modern 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
Lecture 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
RELATIONSHIP STRENGTH
Connectivity and Cardinality The term connectivity is used to describe the relationship classification. Cardinality expresses the minimum and maximum number of entity occurrences associated with one occurrence
Data 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?
Chapter 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
Database 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
Entity-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
A 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
ComponentNo. C_Description UnitOfMeasure. C_Quantity
MIS 322: ERD Exercises Student Name: 1. Assume that at Pine Valley Furniture each product (described by Product No., Description, and Cost) is comprised of at least three components (described by Component
7.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
Database 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:
Database 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
Entity - Relationship Modelling
Topic 5 Entity - Relationship Modelling LEARNING OUTCOMES When you have completed this Topic you should be able to: 1. Acquire the basic concepts of the Entity-Relationship (ER) model. 2. Discuss how to
three 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
Chapter 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
Foundations 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:
The 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
Database 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
Why & How: Business Data Modelling. It should be a requirement of the job that business analysts document process AND data requirements
Introduction It should be a requirement of the job that business analysts document process AND data requirements Process create, read, update and delete data they manipulate data. Process that aren t manipulating
XV. 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
2. 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
Lesson 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
Chapter 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
Data Modeling: Part 1. Entity Relationship (ER) Model
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
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
Database 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
ER 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
CSC 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
1 Class Diagrams and Entity Relationship Diagrams (ERD)
1 Class Diagrams and Entity Relationship Diagrams (ERD) Class diagrams and ERDs both model the structure of a system. Class diagrams represent the dynamic aspects of a system: both the structural and behavioural
Bridge 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/
Chapter 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
Designing 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
Conceptual Design: Entity Relationship Models. Objectives. Overview
Conceptual Design: Entity Relationship Models Craig Van Slyke, University of Central Florida cvanslyke@bus.ucf.edu John Day, Ohio University Objectives Define terms related to entity relationship modeling,
Fundamentals 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
IV. 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
Data 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
Lecture Notes INFORMATION RESOURCES
Vilnius Gediminas Technical University Jelena Mamčenko Lecture Notes on INFORMATION RESOURCES Part I Introduction to Dta Modeling and MSAccess Code FMITB02004 Course title Information Resourses Course
The 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
6-1. Process Modeling
6-1 Process Modeling Key Definitions Process model A formal way of representing how a business system operates Illustrates the activities that are performed and how data moves among them Data flow diagramming
A 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
Concepts 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
Foundations 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
We 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
How 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
SCHEMAS 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
Chapter 2. Data Model. Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel
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
A Short Tutorial on Using Visio 2010 for Entity-Relationship Diagrams
A Short Tutorial on Using Visio 2010 for Entity-Relationship Diagrams by Nezar Hussain Microsoft Visio 2010 is a flexible software tool that allows users to create some diagrams and charts, providing an
COMP 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
Designing Databases. Introduction
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,
Entity 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
USING UML FOR OBJECT-RELATIONAL DATABASE SYSTEMS DEVELOPMENT: A FRAMEWORK
USING UML FOR OBJECT-RELATIONAL DATABASE SYSTEMS DEVELOPMENT: A FRAMEWORK Ming Wang, California State University, ming.wang@calstatela.edu ABSTRACT Data model of object-relational databases (ORDBs) is
Database 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.
Database IST400/600. Jian Qin. A collection of data? A computer system? Everything you collected for your group project?
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
An Experimental Comparison of ER and UML Class Diagrams
Vol.8, No.2 (205), pp.279-288 http://dx.doi.org/0.4257/ijhit.205.8.2.26 An Experimental Comparison of ER and UML Class Diagrams Ahmad Al- Shamailh Mutah University, Jordan Ahmadsham03@gmail.com Abstract
Relational 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
DATABASE 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?
An analysis of structural validity in entity-relationship modeling
Data & Knowledge Engineering 47 (2003) 67 205 www.elsevier.com/locate/datak An analysis of structural validity in entity-relationship modeling James Dullea a, Il-Yeol Song b, *, Ioanna Lamprou b a The
The 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
Hotel Management System
A Seminar report On Hotel Management System Submitted in partial fulfillment of the requirement for the award of degree Of MBA SUBMITTED TO: SUBMITTED BY: Preface I have made this report file on the topic
SQL AND DATA. What is SQL? SQL (pronounced sequel) is an acronym for Structured Query Language, CHAPTER OBJECTIVES
C H A P T E R 1 SQL AND DATA CHAPTER OBJECTIVES In this chapter, you will learn about: Data, Databases, and the Definition of SQL Page 3 Table Relationships Page 15 The STUDENT Schema Diagram Page 37 What
Outline. 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
Converting 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
Database 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
Doing database design with MySQL
Doing database design with MySQL Jerzy Letkowski Western New England University ABSTRACT Most of the database textbooks, targeting database design and implementation for information systems curricula support
Preview DESIGNING DATABASES WITH VISIO PROFESSIONAL: A TUTORIAL
DESIGNING DATABASES WITH VISIO PROFESSIONAL: A TUTORIAL A Microsoft Visio Professional is a powerful database design and modeling tool. The Visio software has so many features that it is impossible to
Conceptual 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
Developing Entity Relationship Diagrams (ERDs)
Developing Entity Relationship Diagrams (ERDs) Introduction This document seeks to give expanded explanation and examples of how to produce entity relationship diagrams. It is based on material adapted
Databases 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
SOFTWARE ENGINEERING IT 0301 Semester V B.Nithya,G.Lakshmi Priya Asst Professor SRM University, Kattankulathur. School of Computing, Department of IT
SOFTWARE ENGINEERING IT 0301 Semester V B.Nithya,G.Lakshmi Priya Asst Professor SRM University, Kattankulathur School of Computing, Department of IT 1 Analysis Modeling Cardinality and Modality Cardinality
The 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
TIM 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.
A Tutorial on Quality Assurance of Data Models 1. QA of Data Models. Barry Williams. tutorial_qa_of_models.doc Page 1 of 17 31/12/2012 00:18:36
A Tutorial on Quality Assurance of Data Models 1 QA of Data Models Barry Williams tutorial_qa_of_models.doc Page 1 of 17 31/12/2012 00:18:36 A Tutorial on Quality Assurance of Data Models 2 List of Activities
Welcome to the Data Analytics Toolkit PowerPoint presentation on EHR architecture and meaningful use.
Welcome to the Data Analytics Toolkit PowerPoint presentation on EHR architecture and meaningful use. When data is collected and entered into the electronic health record, the data is ultimately stored
Lecture 1. Basic Concepts of Set Theory, Functions and Relations
September 7, 2005 p. 1 Lecture 1. Basic Concepts of Set Theory, Functions and Relations 0. Preliminaries...1 1. Basic Concepts of Set Theory...1 1.1. Sets and elements...1 1.2. Specification of sets...2
D6 INFORMATION SYSTEMS DEVELOPMENT. SOLUTIONS & MARKING SCHEME. June 2013
D6 INFORMATION SYSTEMS DEVELOPMENT. SOLUTIONS & MARKING SCHEME. June 2013 The purpose of these questions is to establish that the students understand the basic ideas that underpin the course. The answers
EXTENDED LEARNING MODULE A
EXTENDED LEARNING MODULE A DESIGNING DATABASES AND ENTITY- RELATIONSHIP DIAGRAMMING Student Learning Outcomes 1. Identify how databases and spreadsheets are both similar and different. 2. List and describe
Using UML Part One Structural Modeling Diagrams
UML Tutorials Using UML Part One Structural Modeling Diagrams by Sparx Systems All material Sparx Systems 2007 Sparx Systems 2007 Page 1 Trademarks Object Management Group, OMG, Unified Modeling Language,
Announcements. SE 1: Software Requirements Specification and Analysis. Review: Use Case Descriptions
Announcements SE 1: Software Requirements Specification and Analysis Lecture 4: Basic Notations Nancy Day, Davor Svetinović http://www.student.cs.uwaterloo.ca/ cs445/winter2006 uw.cs.cs445 Send your group
The 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
Higher National Unit specification: general information. Relational Database Management Systems
Higher National Unit specification: general information Unit code: H16W 35 Superclass: CB Publication date: March 2012 Source: Scottish Qualifications Authority Version: 01 Unit purpose This Unit is designed
Data Modeling with Entity-Relationship Diagrams
Riccardi04 6/28/02 0:20 P Page 6 CHAPTER4 Data odeling with Entity-Relationship Diagrams In this chapter, you will learn: What entity-relationship data modeling is How to read and draw entity-relationship
Principles of Data-Driven Instruction
Education in our times must try to find whatever there is in students that might yearn for completion, and to reconstruct the learning that would enable them autonomously to seek that completion. Allan
Animated Courseware Support for Teaching Database Design
Issue s in Informing Science and Information Technology Volume 6, 2009 Animated Courseware Support for Teaching Database Design Meg Murray and Mario Guimaraes Kennesaw State University, Kennesaw, GA, USA
NATIONAL OPEN UNIVERSITY OF NIGERIA
NATIONAL OPEN UNIVERSITY OF NIGERIA SCHOOL OF SCIENCE AND TECHNLOGY COURSE CODE: CIT 843 COURSE TITLE: INTRODUCTION TO DATABASE MANAGEMENT SYSTEM 1 COURSE GUIDE Course Code CIT 843 Course Title Introduction
An Example: Video Rental System
An Example: Video Rental System Video Rental Database Customers Rentals Videos E-R Analysis ERD Example CUSTOMER PRODUCER E-R Analysis Attributes Attribute - property or characteristic of an entity type
Database Systems. Session 3 Main Theme. Enterprise Data Modeling Using The Entity/Relationship (ER) Model. Dr. Jean-Claude Franchitti
Database Systems Session 3 Main Theme Enterprise Data Modeling Using The Entity/Relationship (ER) Model Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical
Access Tutorial 3: Relationships
Access Tutorial 3: Relationships 3.1 Introduction: The advantage of using tables and relationships A common mistake made by inexperienced database designers (or those who have more experience with spreadsheets
Data Modelling and E-R Diagrams
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
2.0 Welcome...2. 2.1 Introduction... 2. 2.2 What is the Scope?...3. 2.3 What are the Things of Interest?... 4. 2.4 Creating Entities...
2. Some Basic Concepts...2 2.0 Welcome...2 2.1 Introduction... 2 2.2 What is the Scope?...3 2.3 What are the Things of Interest?... 4 2.4 Creating Entities... 4 2.5 Primary Keys... 5 2.6 Foreign Keys...
A candidate following a programme of learning leading to this unit will be able to:
Unit 42: Database Design Learning Outcomes A candidate following a programme of learning leading to this unit will be able to: Analyse a business for its business rules Create and produce supporting documentation
Databases 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
CHAPTER 3: DATA MODELING USING THE ENTITY-RELATIONSHIP MODEL
Chapter 3: Data Modeling Using the Entity-Relationship Model 1 CHAPTER 3: DATA MODELING USING THE ENTITY-RELATIONSHIP MODEL Answers to Selected Exercises 3.16 Consider the following set of requirements
Select the Crow s Foot entity relationship diagram (ERD) option. Create the entities and define their components.
Α DESIGNING DATABASES WITH VISIO PROFESSIONAL: A TUTORIAL Microsoft Visio Professional is a powerful database design and modeling tool. The Visio software has so many features that we can t possibly demonstrate
AS 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
Databases and BigData
Eduardo Cunha de Almeida eduardo.almeida@uni.lu 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)