DATABASE SYSTEMS. Chapter 5 Entity Relationship (ER) Modelling DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT
|
|
|
- Chastity May
- 7 years ago
- Views:
Transcription
1 DATABASE SYSTEMS DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT Chapter 5 Entity Relationship (ER) Modelling 1
2 (Rob, Coronel & Crockett ) In this chapter, you will learn: The main characteristics of entity relationship components How relationships between entities are defined and refined and how those relationships are incorporated into the database design process How ERD components affect database design and implementation That real-world database design often requires the reconciliation of conflicting goals
3 (Rob, Coronel & Crockett ) The Entity Relationship (ER) Model ER model forms the basis of an ER diagram ERD represents conceptual database as viewed by end user ERDs depict database s main components: Entities Attributes Relationships 3
4 (Rob, Coronel & Crockett ) A Recipe ERD 4
5 (Rob, Coronel & Crockett ) Entities Refers to entity set and not to single entity occurrence Corresponds to table and not to row in relational environment In UML notation, an entity is represented by a box that is subdivided into three parts. Entity name, a noun, is usually written in capital letters 5
6 (Rob, Coronel & Crockett ) Attributes In the UML model, the attributes are written in the attribute box below the entity rectangle 6
7 (Rob, Coronel & Crockett ) Domains Attributes have domain Domain is attribute s set of possible values Attributes may share a domain 7
8 (Rob, Coronel & Crockett ) Identifiers (Primary Keys) Underlined in the ERD Key attributes are also underlined in frequently used table structure shorthand For example, a CAR entity may be represented by: CAR (CAR_REG, MOD_CODE, CAR_YEAR, CAR_COLOUR) 8
9 (Rob, Coronel & Crockett ) Composite Primary Keys Primary keys ideally composed of only single attribute Possible to use a composite key Primary key composed of more than one attribute 9
10 (Rob, Coronel & Crockett ) Composite Primary Keys (continued) 10
11 (Rob, Coronel & Crockett ) Composite and Simple Attributes Composite attribute can be subdivided Simple attribute cannot be subdivided 11
12 (Rob, Coronel & Crockett ) Single and Multi-Valued Attributes Single-value attribute can have only a single value Multi-valued attributes can have many values 1
13 (Rob, Coronel & Crockett ) Multivalued Attributes (continued) 13
14 (Rob, Coronel & Crockett ) Resolving Multivalued Attribute Problems Although conceptual model can handle M:N relationships and multi-valued attributes, you should not implement them in relational DBMS Within original entity, create several new attributes, one for each of the original multi-valued attribute s components Can lead to major structural problems in table Create new entity composed of original multivalued attribute s components 14
15 (Rob, Coronel & Crockett ) Resolving Multivalued Attribute Problems (continued) 15
16 (Rob, Coronel & Crockett ) Resolving Multivalued Attribute Problems (continued) 16
17 (Rob, Coronel & Crockett ) Resolving Multivalued Attribute Problems (continued) 17
18 (Rob, Coronel & Crockett ) Derived Attributes Attribute whose value may be calculated (derived) from other attributes Need not be physically stored within database Can be derived by using an algorithm 18
19 (Rob, Coronel & Crockett ) Derived Attributes (continued) 19
20 (Rob, Coronel & Crockett ) Derived Attributes (continued) 0
21 (Rob, Coronel & Crockett ) Relationships Association between entities Participants are entities that participate in a relationship Relationships between entities always operate in both directions Relationship can be classified as 1:* Relationship classification is difficult to establish if know only one side of the relationship 1
22 (Rob, Coronel & Crockett ) Multiplicity Multiplicity refers to the number of instances of one entity that are associated with one instance of a related entity. Cardinality expresses minimum and maximum number of entity occurrences associated with one occurrence of related entity Participation - determines whether all occurrences of an entity participate in the relationship or not.
23 (Rob, Coronel & Crockett ) Multiplicity(continued) 3
24 (Rob, Coronel & Crockett ) Existence Dependence Existence dependence Exist in database only when it is associated with another related entity occurrence Existence independence Entity can exist apart from one or more related entities Sometimes refers to such an entity as strong or regular entity 4
25 (Rob, Coronel & Crockett ) Relationship Strength Weak (non-identifying) relationships Exists if PK of related entity does not contain PK component of parent entity Strong (Identifying) Relationships Exists when PK of related entity contains PK component of parent entity 5
26 (Rob, Coronel & Crockett ) Weak (Non-Identifying) Relationships 6
27 (Rob, Coronel & Crockett ) Weak (Non-Identifying) Relationships (continued) 7
28 (Rob, Coronel & Crockett ) Weak (Non-Identifying) Relationships (continued) 8
29 (Rob, Coronel & Crockett ) Strong (Identifying) Relationships 9
30 (Rob, Coronel & Crockett ) Weak Entities Weak entity meets two conditions Existence-dependent Cannot exist without entity with which it has a relationship Has primary key that is partially or totally derived from parent entity in relationship Database designer usually determines whether an entity can be described as weak based on business rules 30
31 (Rob, Coronel & Crockett ) Weak Entities (continued) 31
32 (Rob, Coronel & Crockett ) Weak Entities (continued) 3
33 (Rob, Coronel & Crockett ) Relationship Participation Optional participation One entity occurrence does not require corresponding entity occurrence in particular relationship Mandatory participation One entity occurrence requires corresponding entity occurrence in particular relationship 33
34 (Rob, Coronel & Crockett ) Relationship Participation (continued) 34
35 (Rob, Coronel & Crockett ) Relationship Participation (continued) 35
36 (Rob, Coronel & Crockett ) Relationship Participation (continued) 36
37 (Rob, Coronel & Crockett ) Relationship Participation (continued) 37
38 (Rob, Coronel & Crockett ) Relationship Degree Indicates number of entities or participants associated with a relationship Unary relationship Association is maintained within single entity Binary relationship Two entities are associated Ternary relationship Three entities are associated 38
39 (Rob, Coronel & Crockett ) Relationship Degree (continued) 39
40 (Rob, Coronel & Crockett ) Relationship Degree (continued) 40
41 (Rob, Coronel & Crockett ) Relationship Degree (continued) 41
42 (Rob, Coronel & Crockett ) Recursive Relationships Relationship can exist between occurrences of the same entity set Naturally found within unary relationship 4
43 (Rob, Coronel & Crockett ) Recursive Relationships (continued) 43
44 (Rob, Coronel & Crockett ) Recursive Relationships (continued) 44
45 (Rob, Coronel & Crockett ) Recursive Relationships (continued) 45
46 (Rob, Coronel & Crockett ) Recursive Relationships (continued) 46
47 (Rob, Coronel & Crockett ) Recursive Relationships (continued) 47
48 (Rob, Coronel & Crockett ) Recursive Relationships (continued) 48
49 (Rob, Coronel & Crockett ) Composite Entities Also known as bridge entities Composed of primary keys of each of the entities to be connected May also contain additional attributes that play no role in connective process 49
50 (Rob, Coronel & Crockett ) Composite Entities (continued) 50
51 (Rob, Coronel & Crockett ) Composite Entities (continued) 51
52 (Rob, Coronel & Crockett ) Composite Entities (continued) 5
53 (Rob, Coronel & Crockett ) Association Class 53
54 (Rob, Coronel & Crockett ) Developing an ER Diagram Database design is iterative rather than linear or sequential process Iterative process Based on repetition of processes and procedures 54
55 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) Building an ERD usually involves the following activities: Create detailed narrative of organization s description of operations Identify business rules based on description of operations Identify main entities and relationships from business rules Develop initial ERD Identify attributes and primary keys that adequately describe entities Revise and review ERD 55
56 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) Tiny University Tiny University is divided into several schools Each school is composed of several departments Each department may offer courses Each department may have many lecturers assigned to it Each lecturer may teach up to four classes; each class is section of course Student may enroll in several classes, but (s)he takes each class only once during any given enrollment period 56
57 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) Tiny University (continued) Each department has several students Each student has only a single major and is associated with a single department Each student has an advisor in his or her department Each advisor counsels several students The relationship between class is taught in a room and the room in the building 57
58 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 58
59 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 59
60 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 60
61 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 61
62 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 6
63 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 63
64 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 64
65 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 65
66 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 66
67 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 67
68 (Rob, Coronel & Crockett ) Developing an ER Diagram (continued) 68
69 (Rob, Coronel & Crockett ) Database Design Challenges: Conflicting Goals Database design must conform to design standards High processing speeds are often a top priority in database design Quest for timely information might be focus of database design 69
70 (Rob, Coronel & Crockett ) Database Design Challenges: Conflicting Goals (cont.) 70
71 (Rob, Coronel & Crockett ) Database Design Challenges: Conflicting Goals (cont.) 71
72 (Rob, Coronel & Crockett ) Summary Entity relationship (ER) model Uses ERD to represent conceptual database as viewed by end user ERM s main components: Entities Relationships Attributes Includes multiplicity notation. 7
73 (Rob, Coronel & Crockett ) Summary (continued) Multiplicities are based on business rules In ERM, *:* relationship is valid at conceptual level ERDs may be based on many different ERMs Database designers are often forced to make design compromises 73
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,
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 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 SYSTEMS. Chapter 7 Normalisation
DATABASE SYSTEMS DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT Chapter 7 Normalisation 1 (Rob, Coronel & Crockett 978184480731) In this chapter, you will learn: What normalization
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
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
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
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
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
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
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
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
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
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
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
Chapter 6. Database Tables & Normalization. The Need for Normalization. Database Tables & Normalization
Chapter 6 Database Tables & Normalization Objectives: to learn What normalization is and what role it plays in the database design process About the normal forms 1NF, 2NF, 3NF, BCNF, and 4NF How normal
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
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
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
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
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
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:
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
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
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:
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
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 Design. Adrienne Watt. Port Moody
Database Design Database Design Adrienne Watt Port Moody Except for third party materials and otherwise stated, content on this site is made available under a Creative Commons Attribution 2.5 Canada License.
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
Module 5: Normalization of database tables
Module 5: Normalization of database tables Normalization is a process for evaluating and correcting table structures to minimize data redundancies, thereby reducing the likelihood of data anomalies. The
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
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,
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
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
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/
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
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
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
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
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
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
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
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
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
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
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?
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
Chapter 10. Practical Database Design Methodology. The Role of Information Systems in Organizations. Practical Database Design Methodology
Chapter 10 Practical Database Design Methodology Practical Database Design Methodology Design methodology Target database managed by some type of database management system Various design methodologies
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
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
Database Design and the Reality of Normalisation
Proceedings of the NACCQ 2000 Wellington NZ www.naccq.ac.nz Database Design and the Reality of Normalisation Dave Kennedy ABSTRACT Institute of Technology Christchurch Polytechnic Te Whare Runanga O Otautahi
Chapter 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
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
Chapter 10 Practical Database Design Methodology and Use of UML Diagrams
Chapter 10 Practical Database Design Methodology and Use of UML Diagrams Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 10 Outline The Role of Information Systems in
DATABASE INTRODUCTION
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
Review: 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
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
Answers to Review Questions
Tutorial 2 The Database Design Life Cycle Reference: MONASH UNIVERSITY AUSTRALIA Faculty of Information Technology FIT1004 Database Rob, P. & Coronel, C. Database Systems: Design, Implementation & Management,
Object-Oriented Data Modeling
C h a p t e r 1 3 Object-Oriented Data Modeling Learning Objectives After studying this chapter, you should be able to: Concisely define each of the following key terms: class, object, state, behavior,
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
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
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
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
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
Topic 5.1: Database Tables and Normalization
Topic 5.1: Database Tables and Normalization What is Normalization? Normalization is a process for evaluating and correcting table structures to minimize data redundancies, thereby helping to eliminate
COURSE NAME: Database Management. TOPIC: Database Design LECTURE 3. The Database System Life Cycle (DBLC) The database life cycle contains six phases;
COURSE NAME: Database Management TOPIC: Database Design LECTURE 3 The Database System Life Cycle (DBLC) The database life cycle contains six phases; 1 Database initial study. Analyze the company situation.
Major Work of the Grade
Counting and Cardinality Know number names and the count sequence. Count to tell the number of objects. Compare numbers. Kindergarten Describe and compare measurable attributes. Classify objects and count
Chapter 3. Data Analysis and Diagramming
Chapter 3 Data Analysis and Diagramming Introduction This chapter introduces data analysis and data diagramming. These make one of core skills taught in this course. A big part of any skill is practical
Rose Data Modeler (logical)
Rose Data Modeler (logical) Rational Rose uses a data modeler to model the conceptual, logical, and physical database models, but also to generate DDLs commands, such as creating tables following UML methodology.
Normalization. Reduces the liklihood of anomolies
Normalization Normalization Tables are important, but properly designing them is even more important so the DBMS can do its job Normalization the process for evaluating and correcting table structures
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
LiTH, 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
Database 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
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
www.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
A. 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
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
CS 487. Week 8. Reference: 1. Software engineering, roger s. pressman. Reading: 1. Ian Sommerville, Chapter 3. Objective:
CS 487 Week 8 Reading: 1. Ian Sommerville, Chapter 3. Objective: 1. To check the understandibility of the students in life cycle and process model for development of a software product. 2. To check if
BİL 354 Veritabanı Sistemleri. Entity-Relationship Model
BİL 354 Veritabanı Sistemleri Entity-Relationship Model Steps in building a DB application Pick application domain Conceptual design How can I describe that data? What data do I need for my application
Database Concepts II. Top down V Bottom up database design. database design (Cont) 3/22/2010. Chapter 4
Chapter 4 Database Concepts II Prepared by Kent Wilson University of South Australia Top down V Bottom up database design Entity relationship diagram presents top down view Normalisation looks at the bottom
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
Object-oriented design methodologies
Object-oriented design methodologies An object-oriented methodology is defined as the system of principles and procedures applied to object-oriented software development. Five years ago, there was no standard
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
CSE4213 Lecture Notes
CSE4213 Lecture Notes Introduction to B Tools Computer Science and Software Engineering Monash University 20070226 / Lecture 1 ajh 1/15 1 Outline 2 3 4 5 ajh 2/15 In this course we will be introducing
Software Development: An Introduction
Software Development: An Introduction Fact: Software is hard. Imagine the difficulty of producing Windows 2000 29 million lines of code 480,000 pages of listing if printed a stack of paper 161 feet high
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,
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)
Data 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
Lecturer: Sebastian Coope Ashton Building, Room G.18 E-mail: coopes@liverpool.ac.uk. COMP 201 web-page: http://www.csc.liv.ac.
Lecturer: Sebastian Coope Ashton Building, Room G.18 E-mail: coopes@liverpool.ac.uk COMP 201 web-page: http://www.csc.liv.ac.uk/~coopes/comp201 Lecture 18 Introductory Case Study Introduction to UML During
Why Data Flow Diagrams?
Flow Diagrams A structured analysis technique that employs a set of visual representations of the data that moves through the organization, the paths through which the data moves, and the processes that
Software Engineering. System Models. Based on Software Engineering, 7 th Edition by Ian Sommerville
Software Engineering System Models Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To explain why the context of a system should be modeled as part of the RE process To describe
Object-Oriented Design Guidelines
Adaptive Software Engineering G22.3033-007 Session 8 Sub-Topic 3 Presentation Object-Oriented Design Guidelines Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute
11 Tips to make the requirements definition process more effective and results more usable
1 11 Tips to make the s definition process more effective and results more usable This article discusses what I believe are the key techniques for making s definition process repeatable from project to
Databases -Normalization III. (N Spadaccini 2010 and W Liu 2012) Databases - Normalization III 1 / 31
Databases -Normalization III (N Spadaccini 2010 and W Liu 2012) Databases - Normalization III 1 / 31 This lecture This lecture describes 3rd normal form. (N Spadaccini 2010 and W Liu 2012) Databases -
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
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
7. Classification. Business value. Structuring (repetition) Automation. Classification (after Leymann/Roller) Automation.
7. Classification Business Process Modelling and Workflow Management Business value Lecture 4 (Terminology cntd.) Ekkart Kindler kindler@upb.de Structuring (repetition) Automation UPB SS 2006 L04 2 Classification