MIS 315 - Bsharah The project should include the following items 1.Graphical process model containing 3 to 10 activities/process steps. 2.An Entity/Object.

Slides:



Advertisements
Similar presentations
Normalisation.
Advertisements

First Normal Form Second Normal Form Third Normal Form
Chapter Three Objectives Identification of Keys Application of primary and foreign keys Converting a database design to Relational DB. What is a good DBMS.
UNIVERSITY OF PALESTINE business computer application College of Business Instructor: Mr. Ahmed Abumosameh.
Information Technology Foundations-BIT 112 CHAPTER 4 Data and Knowledge Management.
Chapter Information Systems Database Management.
Video Rental Store M.S. Access Module CAS 133 Basic Computer Skills/MS Office Russ Erdman.
Accounting 6500 Relational Databases: Accounting Applications Introduction to Normalization.
Database Design Conceptual –identify important entities and relationships –determine attribute domains and candidate keys –draw the E-R diagram Logical.
The Relational Database Model:
Chapter 12 Information Systems. 2 Chapter Goals Define the role of general information systems Explain how spreadsheets are organized Create spreadsheets.
Case study Lisa’s Bookstore IST210.
Lesson 32: Designing a Relational Database. 2 Lesson Objectives After studying this lesson, you will be able to:  Identify and apply principles for good.
Things are bad. Children no longer obey their parents and everyone is writing a book. -- Marcus Tillius Cicero.
Page 1 ISMT E-120 Desktop Applications for Managers Introduction to Microsoft Access.
Chapter 12 Information Systems. 2 Chapter Goals Define the role of general information systems Explain how spreadsheets are organized Create spreadsheets.
Normalization Rules for Database Tables Northern Arizona University College of Business Administration.
Advanced Entity Relationship Concepts. Advanced Concepts UIDs Intersection Entities Recursive Relationships Roles Subtypes Exclusivity Historical Fan.
Database Design Sections 4 & 5 Subtype, Supertype, Mutually exclusive, non-transferability, transferable, 1:1, 1:M, M:M, Redundant, Intersection entity,
CREATE THE DIFFERENCE Normalisation (special thanks to Janet Francis for this presentation)
1 Advanced Computer Programming Databases. Overview What is a database? Database Basics Database Components Data Models Normalization Database Design.
Practice of ER modeling
Database Design Sections 6 & 7 Second Normal Form (2NF), Unique Identifiers (UID), Third Normal Form (3NF), Arcs, Hierarchies and Recursive relationships.
Information Systems: Databases Define the role of general information systems Describe the elements of a database management system (DBMS) Describe the.
Concepts and Terminology Introduction to Database.
Relational databases and third normal form As always click on speaker notes under view when executing to get more information!
University of Manitoba Asper School of Business 3500 DBMS Bob Travica
Component 4: Introduction to Information and Computer Science Unit 6: Databases and SQL Lecture 4 This material was developed by Oregon Health & Science.
Avoiding Database Anomalies
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
Normalization (Codd, 1972) Practical Information For Real World Database Design.
Concepts of Relational Databases. Fundamental Concepts Relational data model – A data model representing data in the form of tables Relations – A 2-dimensional.
Copyright Ó Oracle Corporation, All rights reserved. Normalization Use the student note section below for further explanation of the slide content.Use.
CORE 2: Information systems and Databases NORMALISING DATABASES.
Normalization Well structured relations and anomalies Normalization First normal form (1NF) Functional dependence Partial functional dependency Second.
© Relational Databases. © Entities Data is stored in tables. Each table is concerned with one entity An entity is a.
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.
CS 1308 Computer Literacy and the Internet
DataBase Management System What is DBMS Purpose of DBMS Data Abstraction Data Definition Language Data Manipulation Language Data Models Data Keys Relationships.
Next Back A-1 Management Information Systems for the Information Age Second Canadian Edition Copyright 2004 The McGraw-Hill Companies, Inc. All rights.
C-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Extended Learning Module.
Unit 4 Normalisationand Relational Database Management Systems.
ITN Table Normalization1 ITN 170 MySQL Database Programming Lecture 3 :Database Analysis and Design (III) Normalization.
Description and exemplification of entity-relationship modelling.
Quiz questions. 1 A data structure that is made up of fields and records? Table.
Database Design Normalisation. Last Session Looked at: –What databases were –Where they are used –How they are used.
Database Design – Lecture 6 Moving to a Logical Model.
Copyright Ó Oracle Corporation, All rights reserved. Assign Unique Identifiers A Unique Identifier (UID) is any combination of attributes and/or.
1 Class Agenda (04/06/2006 and 04/11/2006)  Discuss use of Visio for ERDs  Learn concepts and ERD notation for data generalization  Introduce concepts.
Understand Relational Database Management Systems Software Development Fundamentals LESSON 6.1.
Logical Database Design and the Relational Model.
Sample Table Standard Notation Entity name in uppercase
IST Database Normalization Todd Bacastow IST 210.
Lecture 4: Logical Database Design and the Relational Model 1.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 6 Modeling the Data: Conceptual and Logical Data Modeling.
Microsoft Access CS 110 Fall Entity Relationship Model Entities Entities Principal data object about which information is to be collectedPrincipal.
What Is Normalization  In relational database design, the process of organizing data to minimize redundancy  Usually involves dividing a database into.
Database Planning Database Design Normalization.
DATA SCIENCE MIS0855 | Spring 2016 Designing Data
Normalisation Unit 6: Databases. Just to recap  What is an Entity  What is an Attribute?
G057 - Lecture 05 From Scenario To Design Mr C Johnston ICT Teacher
1 Database Design Sections 6 & 7 First Normal Form (1NF), Second Normal Form (2NF), Unique Identifiers (UID), Third Normal Form (3NF), Arcs, Hierarchies.
Data Base Design Steps 1.Define Entity Classes (Relations/Tables) and Keys. 2.Define Relationships between Entity Classes. Normalization Steps Eliminate.
SEEM3430: Information Systems Analysis and Design
Chapter 12 Information Systems.
Information Systems Database Management
Introduction to Database Systems
Payroll Management System
Week 11: Database Management System
Appendix A Data Modeling MANAGEMENT INFORMATION SYSTEMS 8/E
Presentation transcript:

MIS Bsharah The project should include the following items 1.Graphical process model containing 3 to 10 activities/process steps. 2.An Entity/Object Pool with 3 to 5 entities. 3.An Entity Relationship Matrix for the entities identified in step 2. 4.A fully refined or attributed Logical Data Model normalized to third normal form. 5.A data dictionary for the logical model created in step 4. 6.An Access 2007 Database created by transforming the logical model in step 4 into a physical design. Each table in the database should contains at least 4 records. 7.At least two Forms for the database created in step 6. The forms at a minimum should enable record addition, deletion, modification. 8.At least two Queries for the database created in step 6. 9.At least two Reports for the database created in step 6.

MIS Bsharah 1. Graphical process model containing 3 to 10 activities/process steps. 1.0 Input Customer Information Manage Video Rental Business 2.0 Manage Video Inventory 3.0 Track Customer Rentals 4.0 Order New Movies 5.0 Advertise and Track Specials to New and Repeat Customers Customer data collection form Customer address and preference information Movie order form New movies Returned movies Customer history and status s Studio movie release info Postal mailing Inventory with shelf location

MIS Bsharah 2. An Entity/Object Pool with 3 to 5 entities. Movie Western Action and Adventure Comedy Documentary Movie Studio Customer Movie Rating

MIS Bsharah 3. An Entity Relationship Matrix for the entities identified in step 2.

MIS Bsharah Fully Attributed/Refined Model Example Makes Movie # Title Length Movie Type MPAA Rating MOVIE Customer # Last Name First Name Cust Address Cust Phone # Studio Name Address CUSTOMER MOVIE STUDIO Is Distributed by Movie # (Fk1) Copy # Customer # (Fk2) Rent Date Return Date Late Status MOVIE RENTAL Is Rented By Rents Distributor Name Movie # (Fk1) Studio Name(Fk2) Release Date Contact Name Contact Phone # MOVIE DISTRIBUTOR Movie # ASPCA Rating WESTERN (TYPE)

MIS Bsharah 5.0 A data dictionary for the logical model created in step 4. Movie-An item that is available to rent, a motion picture or television production. –Movie #-Unique identifier of the item available for rent. –Title-The name of the item available for rent. –Length-The running time in minutes of the item available for rent. –Movie Type-The genre or classification associated with the items available for rent. Valid values are: Action and Adventure, Animation, Christmas, Comedy, Comic Book-Based, Documentary, Drama, Family, Horror, Martial Arts, Musical, Science Fiction and Fantasy, Silent Movie, Sports, War Movie, and Western. –MPAA Rating-Motion Picture Association of America evaluation. Valid values are: G, PG, PG-13 R, and NC-17. Western-A genre or type of Movie/Television production. –ASPCA Rating-American Society for the Prevention of Cruelty to Animals evaluation. Movie Rental-An instance of a Movie being rented by a customer. –Movie # (Fk1)- Unique identifier of the item available for rent. –Copy #-The sequence number of the item available for rent. Used to differentiate multiple copies of a Movie. –Customer # (Fk2)-Unique identifier of an individual authorized to rent a Movie. –Rent Date-The date a Movie is rented by a Customer. –Return Date-The date a rented Movie is to be returned to the store for restocking. –Late Status-A status code identifying if the rental item has not been returned by the Return Date.

MIS Bsharah 5.0 A data dictionary for the logical model created in step 4. (con’t) Customer-the patron who rents Movies. –Customer #-Unique identifier of a customer. –Last Name-the Customer’s surname. –First Name-the Customer’s given name. –Customer Address-the location (postal) where a Customer may be communicated with. –Cust Phone #-the area code and telephone number of the Customer. If Address is outside of the USA, then a country code is required. Movie Studio-a company that makes and produces motion pictures/television shows. –Studio Name-Unique identifier of a Movie Studio. –Address-the location (postal) where a Movie Studio may be communicated with.

MIS Bsharah 5.0 A data dictionary for the logical model created in step 4. (con’t) Movie Distributor –Distributor Name- Unique identifier of the company that distributes movies for the Studios. –Movie # (Fk1)-Unique identifier of the item available for rent. –Release Date-The date that the rental item is available for rent. –Studio Name(Fk2)-Unique identifier of a Movie Studio. –Contact Name-the identification of a person at a Movie Studio to whom communication should be directed. –Contact Phone #-the area code and telephone number of the Movie Studio Contact. If Address is outside of the USA, then a country code is required.

MIS Bsharah 6.0 An Access 2007 Database created by transforming the logical model in step 4 into a physical design See Access File: Manage Video Rental v1.accdb

MIS Bsharah First Normal Form - (1NF) Every key and non-key attribute of an entity must be single valued No entity instance can have multiple values for a given attribute i.e., The No Repeat Rule A violating entity is corrected by removing repeating or multivalued attributes to another, dependent (child) entity

MIS Bsharah First Normal Form - Example RESTAURANT REST NAME ADDRESS PHONE # EMPLOYEE NAME BURGER KING TACO HOUSE FISH COMPANY 123 NORTH ST TH PLACE 77 SUNSET AVE JOHN, SUE, LISA MARY, BILL ED, SAM, JOSE, RICK REST NAME ADDRESS PHONE # EMPLOYEE NAME RESTAURANT REST NAME ADDRESS PHONE # EMPLOYEE EMPLOYEE NAME REST NAME POSITION employs

MIS Bsharah Second Normal Form - (2NF) An entity that is in first normal form and each non- key attribute is dependent on the entire primary key No non-key attribute instance can be determined by knowing just part of an entity instances key A violating entity is corrected by removing to a parent entity any attributes that depend on only a subset of the primary key

MIS Bsharah Second Normal Form - Example RESTAURANT ORDER REST NAME SUPPLIER NAME ORDER ITEM SUPPLIER PHONE # BURGER KING TACO HOUSE FISH COMPANY SAM'S PRODUCE SALSA INC. SAM'S PRODUCE BEEF PEPPERS SNAPPER REST NAME SUPPLIER NAME ORDER ITEM SUPPLIER PHONE # fills RESTAURANT ORDER REST NAME ORDER ITEM SUPPLIER NAME (FK1) SUPPLIER SUPPLIER NAME PHONE #

MIS Bsharah Third Normal Form - (3NF) An entity that is in second normal form and each non- key attribute is only dependent on the entire primary key and nothing other than the key No non-key attribute instance can be determined by knowing the value of another non-key attribute for the same instance A violating entity is corrected by removing to a parent entity any attributes exhibiting transitive dependencies (non-key attributes that not only depend on the whole key but also on other non-key attributes)

MIS Bsharah Sample Information Model

MIS Bsharah Categorization Example COMPLETE CATEGORIZATION WESTERNSUSPENSECOMEDYMALEFEMALE (SEX) MOVIEPERSON INCOMPLETE CATEGORIZATION (there are other movie types such as Documentary) (MOVIETYPE)

MIS Bsharah Planning Model Example Is Rented By / Rents MOVIECUSTOMER STUDIO Is Produced In/ Produces WESTERN (TYPE)

MIS Bsharah Key-Based Model Example Funds MOVIECUSTOMER STUDIO Is Produced by MOVIE # CUSTOMER # STUDIO ID MOVIE # (FK1) CUSTOMER # (FK2) DATE MOVIE RENTAL Is Rented By Rents STUDIO ID (FK2) MOVIE # (FK1) MOVIE PRODUCTION WESTERN (TYPE) MOVIE #

MIS Bsharah Non-Specific Connection Relationships A relationship where one instance of an entity may relate to 0, 1, M instances of a second entity; and one instance of the second entity may relate to 0, 1, M instances of the first entity For Example: –A Customer Rents at 0,1,M Movies, and Each Movie is Rented by 0, 1, M Customers rents/is rented by MOVIE Movie Number Name Rating Rental Rate CUSTOMER Cust Number Name Address Status Code

MIS Bsharah Specific Connection Relationships A Parent - Child relationship that resolves a non- specific relationship to capture additional detail A relationship where one instance of an entity (Parent) may relate to 0, 1, M instances of the second entity (Child), and the Child entity is related to one and only one instance of the Parent entity For Example: - A CUSTOMER Rents a specific copy of a MOVIE rents according to Customer Cust Number Name Address Status Code Movie Rental Record Movie Number Movie Copy Id Rental Date Cust Number (FK)

MIS Bsharah Movie Genres Action and Adventure Animation Christmas Comedy Comic Book-Based Documentary Drama Family Horror Martial Arts Musicals Science Fiction and Fantasy Silent Movies Sports War Movies Westerns