MIS3500 * Asper School of Business * Travica

Slides:



Advertisements
Similar presentations
Normalisation.
Advertisements

Database Fundamentals Lecture 5. The Design Process continued.
Class diagram II Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: October 2014.
Terms - data,information, file record, table, row, column, transaction, concurrency Concepts - data integrity, data redundancy, Type of databases – single-user,
MIS2502: Data Analytics Relational Data Modeling
Introduction to Databases
Bob Travica MIS 2000 Bob Travica Class 5 More on Data Analysis Updated Jan
Database Design Sections 6 & 7 Second Normal Form (2NF), Unique Identifiers (UID), Third Normal Form (3NF), Arcs, Hierarchies and Recursive relationships.
Bob Travica MIS 2000 Bob Travica Class 5 More on Data Analysis Updated May 2015.
University of Manitoba Asper School of Business 3500 DBMS Bob Travica
Avoiding Database Anomalies
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
Normalisation Mia’s Sandwich Shop The Process Explained.
SALINI SUDESH. Primarily a tool to validate and improve a logical design so that it satisfies certain constraints that avoid unnecessary duplication of.
DBSYSTEMS Chapter 3 Data Normalization Get data properly tabled! Based on G. Post, DBMS: Designing & Building Business Applications University of Manitoba.
SQL Schemas DATA SCIENCE BOOTCAMP. Schema The structure of the database (relationships between tables)
Customer Order Order Number Date Cust ID Last Name First Name State Amount Tax Rate Product 1 ID Product 1 Description Product 1 Quantity Product 2 ID.
1 5 Chapter 5 Database Design 1: Some Normalization Examples Spring 2006.
PMIT-6102 Advanced Database Systems By- Jesmin Akhter Assistant Professor, IIT, Jahangirnagar University.
MIS 301 Information Systems in Organizations Dave Salisbury ( )
MIS2502: Data Analytics Relational Data Modeling
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Normalization Hour1,2 Presented & Modified by Mahmoud Rafeek Alfarra.
MIS2502: Data Analytics Relational Data Modeling David Schuff
Lecture # 17 Chapter # 10 Normalization Database Systems.
Copyright © 2016 Pearson Education, Inc. Modern Database Management 12 th Edition Jeff Hoffer, Ramesh Venkataraman, Heikki Topi CHAPTER 4: PART C LOGICAL.
1 Database Design Sections 6 & 7 First Normal Form (1NF), Second Normal Form (2NF), Unique Identifiers (UID), Third Normal Form (3NF), Arcs, Hierarchies.
Functional Dependencies and Normalization 1 Instructor: Mohamed Eltabakh Part 2.
Order Database – ER Diagram
Database, tables and normal forms
Revised: 2 April 2004 Fred Swartz
Order Database – ER Diagram
Get data properly tabled!
SEEM3430: Information Systems Analysis and Design
Basic Database Design COSC 2328 – Web Programming.
MIS2502: Data Analytics Relational Data Modeling
Normalization DBS201.
Order Database – ER Diagram
Order Database – ER Diagram
MIS5101: Business Intelligence Relational Data Modeling
Example Question–Is this relation Well Structured? Student
Unit 4: Normalization of Relations
Normalisation Exercise
Entity relationship diagrams
MIS2502: Data Analytics Relational Data Modeling
MIS2502: Review for Exam 1 JaeHwuen Jung
Functional Dependencies and Normalization
MIS2502: Data Analytics Converting ERDs to Schemas
Normalization and Databases
Some Normalization Examples
Aggregations Various Aggregation Functions GROUP BY HAVING.
Customer Order Entry Database Version: 1.1 by: R. Holowczak
MIS2502: Data Analytics Relational Data Modeling
Schema Template Employee Office EmployeeOffice EmployeeID OfficeID
Order Database – ER Diagram
MIS2502: Data Analytics Relational Data Modeling
CSE2DBF – CSE4DBF Normalization 20/03/2017
Database Normalisation
CHAPTER 4: LOGICAL DATABASE DESIGN AND THE RELATIONAL MODEL
MIS2502: Review for Exam 1 Aaron Zhi Cheng
Chapter 8 – Part2 Database Design.
Order Database – ER Diagram
Chapter 8 – Part2 Database Design.
A relation is in first normal form if it does not contain repeating groups.
Class11 Introduction to relational databases and MySQL
ER Diagram Master How to use this template
MIS2502: Data Analytics Relational Data Modeling 2
MIS2502: Data Analytics Relational Data Modeling 3
Normalization DBS201.
Some Normalization Examples
Presentation transcript:

MIS3500 * Asper School of Business * Travica Exercise on Normalization - Solution (a) Class diagram for Customer Order Management System _OrderProduct__ Quantity Discount _Customer_ CustomerID CLastName CFirstName Address City State PostCode CTel ___Order___ OrderNumber OrderDate EstRecDate ActDecDate __Product__ ProductID PName ListPrice _Manufacturer_ ManufacturerID MName MTel __Fabric___ FabricID FabName FabDescription _Category__ CategoryID CatName CatDescription 1 places * * is for * 1 * * made of 1 * belongs to 1 made by Alternatives: Product : Fabric = M:M, association class needed Product : Manufacturer = M:M Business rule on multiplicity: 1. Each customer places a number of orders while each order is placed by only one customer. 2. An Order can have many products, and each product can be ordered many times. 3. A product is made of one main fabric (alt.: many), and a particular fabric can be used in many products. 4. A product belongs to one category, and each category can have many products 5. A product is made by one manufacturer (alt.: many), and a manufacturer can make many products.

(b) Schema for Customer Order Management System _OrderProduct__ OrderNumber ProductID Quantity Discount _Customer_ CustomerID CLastName CFirstName Address City State PostCode CTel ___Order___ OrderDate EstRecDate ActDecDate __Product__ PName CategoryID FabricID ListPrice ManufactD _Manufacturer_ ManufacturerID MName MTel __Fabric___ FabName FabDescription _Category__ CatName CatDescription 1 * 1 * * 1 * 1 Study carefully similarities and differences between (a) and (b). Run normalization test: 1NF – are there repeating sections in any table? 2 NF – in tables with combined keys (OrderProduct), do non-key attributes depend on the entire key? Is there a partial functional dependence on the key? If yes, it’s not in 2NF. 3 NF – do non-key attributes depend on the key only? Is there any dependence between non-key attributes (transitive dependence)?