Section 11 : Normalisation

Slides:



Advertisements
Similar presentations
Three-Step Database Design
Advertisements

Chapter 10: Designing Databases
C6 Databases.
Supplement 01a Database-Introduction-1
Section 07 (a)DFD to ERD Link1 HSQ - DATABASES & SQL By MANSHA NAWAZ 07 (a) - DFD to ERD Link And Franchise Colleges.
Section 08Data Dictionary - Structures & Elements 1 08 THE DATA DICTIONARY Structures & Elements And Franchise Colleges By MANSHA NAWAZ.
Section 11 : Normalisation - A Worked Example
The Relational Model System Development Life Cycle Normalisation
Chapter 6 Methodology Conceptual Databases Design Transparencies © Pearson Education Limited 1995, 2005.
Data Management Design
Normalisation up to 1NF Bottom-up Approach to Data Modelling.
1 NORMALISATION. 2 Introduction Overview Objectives Intro. to Subject Why we normalise 1, 2 & 3 NF Normalisation Process Example Summary.
Lecture Fourteen Methodology - Conceptual Database Design
WELL-DESIGNED DATABASES Process faster Easy to develop and maintain Easy to read and write code.
Database Systems Design, Implementation, and Management Coronel | Morris 11e ©2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 4-1.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
System Analysis and Design
Week 2 Lecture 2 Structure of a database. External Schema Conceptual Schema Internal Schema Physical Schema.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
LOGICAL DATABASE DESIGN
Section 01Resources1 HSQ - DATABASES & SQL 01 Resources And Franchise Colleges Name :MANSHA NAWAZ room :G 0/32
Michael F. Price College of Business Chapter 6: Logical database design and the relational model.
Chapter 14 & 15 Conceptual & Logical Database Design Methodology
Chapter 6 Data Flow Diagramming Copyright © 2010 by The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/Irwin.
Daniel AdinugrohoDatabase Programming 1 DATABASE PROGRAMMING Lecture on 29 – 04 – 2005.
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Methodology - Conceptual Database Design Transparencies
1 Chapter 1 Overview of Database Concepts. 2 Chapter Objectives Identify the purpose of a database management system (DBMS) Distinguish a field from a.
Software School of Hunan University Database Systems Design Part III Section 5 Design Methodology.
Methodology Conceptual Databases Design
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
CSCI 3140 Module 2 – Conceptual Database Design Theodore Chiasson Dalhousie University.
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Concepts and Terminology Introduction to Database.
Lecture 2 An Overview of Relational Database IST 318 – DB Admin.
CORE 2: Information systems and Databases NORMALISING DATABASES.
MS Access: Creating Relational Databases Instructor: Vicki Weidler Assistant: Joaquin Obieta.
Section 05Concepts Of DBMS1 HSQ - DATABASES & SQL And Franchise Colleges 05 Concepts of DBMS By MANSHA NAWAZ.
Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.
1/26/2004TCSS545A Isabelle Bichindaritz1 Database Management Systems Design Methodology.
Methodology: Conceptual Databases Design
Lecture2: Database Environment Prepared by L. Nouf Almujally & Aisha AlArfaj 1 Ref. Chapter2 College of Computer and Information Sciences - Information.
Database A database is a collection of data organized to meet users’ needs. In this section: Database Structure Database Tools Industrial Databases Concepts.
C6 Databases. 2 Traditional file environment Data Redundancy and Inconsistency: –Data redundancy: The presence of duplicate data in multiple data files.
Lecture2: Database Environment Prepared by L. Nouf Almujally 1 Ref. Chapter2 Lecture2.
Methodology - Conceptual Database Design
CIS 210 Systems Analysis and Development Week 6 Part II Designing Databases,
Databases Shortfalls of file management systems Structure of a database Database administration Database Management system Hierarchical Databases Network.
IFS310: Module 6 3/1/2007 Data Modeling and Entity-Relationship Diagrams.
Database Design – Lecture 4 Conceptual Data Modeling.
Foundations of Business Intelligence: Databases and Information Management.
Lection №4 Development of the Relational Databases.
BSA206 Database Management Systems Lecture 2: Introduction to Oracle / Overview of Database Concepts.
1 DATABASE TECHNOLOGIES (Part 2) BUS Abdou Illia, Fall 2015 (September 9, 2015)
Understand Relational Database Management Systems Software Development Fundamentals LESSON 6.1.
1 Information Retrieval and Use De-normalisation and Distributed database systems Geoff Leese September 2008, revised October 2009.
NORMALIZATION Handout - 4 DBMS. What is Normalization? The process of grouping data elements into tables in a way that simplifies retrieval, reduces data.
IT 5433 LM3 Relational Data Model. Learning Objectives: List the 5 properties of relations List the properties of a candidate key, primary key and foreign.
NORMALISATION OF DATABASES. WHAT IS NORMALISATION? Normalisation is used because Databases need to avoid have redundant data, which makes it inefficient.
Methodology Conceptual Databases Design
Databases – Exam questions
SEEM3430: Information Systems Analysis and Design
Methodology Conceptual Database Design
Data Dictionary : Store & Flow
Normalization Referential Integrity
Methodology Conceptual Databases Design
Review of Week 3 Relation Transforming ERD into Relations
Presentation transcript:

Section 11 : Normalisation And Franchise Colleges 11 NORMALISATION By MANSHA NAWAZ Section 11 : Normalisation

Section 11 : Normalisation SAD Overview Systems development undertaken by using Case Tools used early in development life cycle Provide requirements and design in terms of Systems Model and Data Model Case Tools for Systems Modelling: Dataflow Diagrams (DFD) Data Dictionary (DD) Case Tools for Data Modelling: Normalisation (NF) A rules based technique undertaken to produce the data model for a system Entity Relationship Model (ER) A diagrammatic based technique undertaken to produce the data model for a system Data Model Can be implemented on a DBMS such as MS SQL Server, MS Access, etc Consists of logical and physical view of the proposed systems data. Section 11 : Normalisation

Section 11 : Normalisation DFD DDS Normalised Tables E-R Model DBMS PHYSICAL VIEW OF DATA TABLES LOGICAL VIEW OF DATA FORMS Section 11 : Normalisation

DBMS NF DATAFLOW DIAGRAMS DataStores, DataFlows and Data Dictionary DATA MODEL TABLE SET NF E-R Model DBMS PHYSICAL VIEW OF DATA TABLES LOGICAL VIEW OF DATA FORMS Database connectivity via websites www .net technology Macromedia Dreamweaver MS Visual Studio Database connectivity via desktop DBMS such as MS Access Database connectivity via programming languages such as MS Visual Basic Section 11 : Normalisation Area of Interest

Systems Analysis and Design DFDs can provides the base for database development Used to derive our data model Datastores Decompose into a number of related tables provide the TABLE views for the database Physical View of data (Internal Schema) Datastores & Dataflows provide the FORM views Logical View of data (External Schema) Process reports, queries, functions & procedures Section 11 : Normalisation

Section 11 : Normalisation Data Model Also referred to as Conceptual Model A Data Model is the representation of a proposed systems database requirements Data Model provides a full set of related tables and data Able to derive physical views (internal schema) of data Able to derive logical views (external schema) of data Data Model produced by Case Tools techniques of Normalisation and/or Entity Relationship Modelling. Proposed processes that operate on the data and/or produce data (process view) Making sure these tally (event/transaction view?) Section 11 : Normalisation

Section 11 : Normalisation Logical View - for User External Schema View Form or Screen views provided to the end user. Datastore & Dataflows represent as logical views in Data Dictionary Contained in Data Dictionary - Structure and Element view Physical View - for Designers Internal Schema View database structure view that a DBMS requires. in terms of Tables, Attributes (data fields) and Types (data defn.) linkage between tables via primary and foreign keys Datastore decomposed to a set of normalised tables Normalised datastore represent physical view Normalisation takes the logical view and produces the physical view Take the datastore and produce the tables Section 11 : Normalisation

Normalisation (NF). Entity Relationship Modelling (ERM). Provide us with a Bottom Up approach to producing the database tables Technique covered in other modules Entity Relationship Modelling (ERM). Covered in HSQ Databases & SQL Module Section 11 : Normalisation

Section 11 : Normalisation Logical View - for User Form or Screen views provided to the end user. Datastore structure and element view Physical View - for Designers database structure view that a DBMS requires. in terms of Tables, Attributes (data fields) and Types (data defn.) linkage between tables via primary and foreign keys Datastore decomposed to a set of normalised tables Normalisation takes the logical view and produces the physical view Take the datastore and produce the tables Section 11 : Normalisation

Section 11 : Normalisation Normalisation Rules 0NF Zero Normal Form or Unnormalised data Data Dictionary Structure and Elements of a datastore List datastore data: identify key(s) and repeating group of data represents the logical form view of a datastore 1NF first Normal Form or first normalised data Remove repeating group(s) to new table(s) 2NF second Normal Form or second normalised data Remove partial key dependency data to new table(s) 3NF third Normal Form or third normalised data Remove non key dependency data to new table(s) represents the physical tables view of a datastore Section 11 : Normalisation

Normalisation Rational The normalisation process also ensures there must be no repeating groups of data in a table all attributes in a table must be atomic cannot be broken down into any smaller components all primary keys must remain unique every foreign key must have a matching primary key in its related table. Normalisation is a process that reduces errors due to badly designed data structures (entities, attributes, and relationships). Normalisation can be carried out at various levels of complexity. You will need to understand the purpose of normalisation and the methods used to normalise each datastore Section 11 : Normalisation

Section 11 : Normalisation Summary Rules to assist in the creation of a DATA MODEL A step by step technique which restructures the data of a system into a more efficient and desirable form. Takes logical datastore view to physical table view Makes improvements in terms of : NO DUPLICATION NO REDUNDANT NO NULL REDUCTION IN PHYSICAL SIZE QUICKER INFORMATION RETRIVAL LEADS TO A FULLY OPTIMISED SET OF TABLES Section 11 : Normalisation

Document : Design Specification Data Dictionary lecture 08 Data Stores - Structures & Elements lecture 08 Data Flow - Structures & Elements lecture 08 Data Stores and Flow Usage lecture 09 Process Descriptions lecture 10 NORMALISATION lecture 11 Database Tables derived from Data Store Descriptions ONF - Logical View of Datastores 1NF 2NF 3NF - Physical View of Tables Section 11 : Normalisation

Further Reading Why Normalisation or ER Modelling? www Online Tutorial Supplement Notes on Why Normalisation or ER Modelling? www Online Tutorial Normalisation NORMALISATION - Worked Example - - Problems - -  Answers  - > Normalisation Video Section 11 : Normalisation