Lecture 2 ISM - © 2010 Houman Younessi Convener: Houman Younessi 1-860-548-7880 Information Systems Spring 2011.

Slides:



Advertisements
Similar presentations
CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
Advertisements

Database Management3-1 L3 Database Management Santa R. Susarapu Ph.D. Student Virginia Commonwealth University.
Extended Learning Module C
Lecture 1 ISM- © 2010 Houman Younessi Information Systems Summer 2010 Convener: Houman Younessi
Database Design Conceptual –identify important entities and relationships –determine attribute domains and candidate keys –draw the E-R diagram Logical.
Database management concepts Database Management Systems (DBMS) An example of a database (relational) Database schema (e.g. relational) Data independence.
Data Management Design
Chapter 11 Data Management Layer Design
1ISM - © 2010 Houman Younessi Lecture 4 Convener: Houman Younessi Information Systems Spring 2011.
Recording / Financing Fixed Asset Acquisition Human Resources Purchasing Revenue Traditional files approach: separate systems (Legacy Systems) Expenditure.
Chapter 4: Database Management. Databases Before the Use of Computers Data kept in books, ledgers, card files, folders, and file cabinets Long response.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 4-1.
Terms - data,information, file record, table, row, column, transaction, concurrency Concepts - data integrity, data redundancy, Type of databases – single-user,
Bad DB Design Duplicate of data Duplicate of data Updating Updating Deleting Deleting.
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
Copyright © 2016 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Normalization: A workshop for everybody! Database Normalization: A workshop for everybody! Part 2 Contents copyright Brent Friedman, Released under.
IST Databases and DBMSs Todd S. Bacastow January 2005.
Daniel AdinugrohoDatabase Programming 1 DATABASE PROGRAMMING Lecture on 29 – 04 – 2005.
1 DATABASE TECHNOLOGIES BUS Abdou Illia, Fall 2007 (Week 3, Tuesday 9/4/2007)
DBMS By Narinder Singh Computer Sc. Deptt. Topics What is DBMS What is DBMS File System Approach: its limitations File System Approach: its limitations.
ASP.NET Programming with C# and SQL Server First Edition
CSC271 Database Systems Lecture # 30.
1 © Prentice Hall, 2002 Physical Database Design Dr. Bijoy Bordoloi.
Lecture 4 MGMT © 2012 Houman Younessi Strategic Planning for IS and IS toolkit.
CHAPTER 8: MANAGING DATA RESOURCES. File Organization Terms Field: group of characters that represent something Record: group of related fields File:
Module III: The Normal Forms. Edgar F. Codd first proposed the process of normalization and what came to be known as the 1st normal form. The database.
Lecture 6 Normalization: Advanced forms. Objectives How inference rules can identify a set of all functional dependencies for a relation. How Inference.
Database Normalization Lynne Weldon July 17, 2000.
M Taimoor Khan Course Objectives 1) Basic Concepts 2) Tools 3) Database architecture and design 4) Flow of data (DFDs)
GUS: 0262 Fundamentals of GIS Lecture Presentation 3: Relational Data Model Jeremy Mennis Department of Geography and Urban Studies Temple University.
CORE 2: Information systems and Databases NORMALISING DATABASES.
MS Access: Creating Relational Databases Instructor: Vicki Weidler Assistant: Joaquin Obieta.
Object Persistence (Data Base) Design Chapter 13.
Object Persistence Design Chapter 13. Key Definitions Object persistence involves the selection of a storage format and optimization for performance.
CS370 Spring 2007 CS 370 Database Systems Lecture 4 Introduction to Database Design.
5. Database Design Lingma Acheson Department of Computer and Information Science IUPUI CSCI N207 Data Analysis Using Spreadsheets 1.
DataBase Management System What is DBMS Purpose of DBMS Data Abstraction Data Definition Language Data Manipulation Language Data Models Data Keys Relationships.
Databases Shortfalls of file management systems Structure of a database Database administration Database Management system Hierarchical Databases Network.
Lecture 5 Normalization. Objectives The purpose of normalization. How normalization can be used when designing a relational database. The potential problems.
Chapter 10 Normalization Pearson Education © 2009.
The University of Akron Dept of Business Technology Computer Information Systems The Relational Model: Concepts 2440: 180 Database Concepts Instructor:
Normalization Is the gradual and sequential process of efficiently organizing data in a database that follows the rules listed in the previous slide –
GIS Data Models GEOG 370 Christine Erlien, Instructor.
McGraw-Hill/Irwin ©2009 The McGraw-Hill Companies, All Rights Reserved CHAPTER 6 DATABASES AND DATA WAREHOUSES CHAPTER 6 DATABASES AND DATA WAREHOUSES.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 16 Using Relational Databases.
A337 - Reed Smith1 Structure What is a database? –Table of information Rows are referred to as records Columns are referred to as fields Record identifier.
Database Management Supplement 1. 2 I. The Hierarchy of Data Database File (Entity, Table) Record (info for a specific entity, Row) Field (Attribute,
Lection №4 Development of the Relational Databases.
1 DATABASE TECHNOLOGIES (Part 2) BUS Abdou Illia, Fall 2015 (September 9, 2015)
Normalisation RELATIONAL DATABASES.  Last week we looked at elements of designing a database and the generation of an ERD  As part of the design and.
Chapter 5 Index and Clustering
NORMALIZATION. What is Normalization  The process of effectively organizing data in a database  Two goals  To eliminate redundant data  Ensure data.
Understand Relational Database Management Systems Software Development Fundamentals LESSON 6.1.
Postgresql East Philadelphia, PA Databases – A Historical Perspective.
INFS 6220 Systems Analysis & Design Transactional DBs vs. Data Warehouses.
NORMALIZATION Handout - 4 DBMS. What is Normalization? The process of grouping data elements into tables in a way that simplifies retrieval, reduces data.
SQL Basics Review Reviewing what we’ve learned so far…….
Lecture # 17 Chapter # 10 Normalization Database Systems.
SQL IMPLEMENTATION & ADMINISTRATION Indexing & Views.
Understanding Data Storage
Database Normalization
Basic Concepts in Data Management
Database management concepts
Relational Database Model
Database management concepts
Chapter 17 Designing Databases
Course Instructor: Supriya Gupta Asstt. Prof
BTEC ICT – Unit 18 With Mr Griffiths.
Presentation transcript:

Lecture 2 ISM - © 2010 Houman Younessi Convener: Houman Younessi Information Systems Spring 2011

Lecture 2 ISM - © 2010 Houman Younessi ElementConceptInformation CategoryInformation System RevenueDemandMarket trends and marketing Product quality Pricing Data Acquisition Data Analysis Control Forecasting Optimization Product Orientation

Lecture 2 ISM - © 2010 Houman Younessi Quality - Design - Meeting requirements - Control - Meeting specifications - Delivery - Meeting expectations Example: Hospital

Lecture 2 ISM - © 2010 Houman Younessi The pitfall of Ceteris Paribus The demand side of the market can be represented by the demand curve The shape of the demand curve determines demand points (levels of demand) Demand points in turn determines supply levels needed to maximize revenues However The demand curve (function) changes and shifts with respect to changes in consumer taste, income, population, commodity prices, availability of other products, product quality, access, and price stability

Lecture 2 ISM - © 2010 Houman Younessi Consumer taste, Income, Population, Commodity prices, Availability of other products, Product quality, Access, and Price stability We need to not only acquire data on these but also to analyze and present the information such data might imply. Data Acquisition Data Analysis Control Forecasting, and Optimization applications are to be used.

Lecture 2 ISM - © 2010 Houman Younessi Application: Collection of programs that together achieve a particular objective directly related to a task that the user wishes to perform. Program: Code written - in a human understandable language - that is to be executed in computer memory where it can perform tasks on data. Algorithms + Data Structures

Lecture 2 ISM - © 2010 Houman Younessi Algorithm: A finite set of well-defined instructions for accomplishing a given task which, given an initial state, will terminate in a defined end-state representing a particular goal. e.g. A recipe to cook lasagna e.g. A set of instructions to minimize a path traveled e.g. A set of instructions to sort a set of numbers Recursive, iterative; Deterministic, Non-deterministic; Serial, Parallel

Lecture 2 ISM - © 2010 Houman Younessi Examples of Algorithms: Recursive Iterative function fib(n) if n = 0 return 0 if n = 1 return 1 else return fib(n-1) + fib(n-2) function fib(n) a, c = 0,b = 1 Do (n times) { c = a+b a = b b = c return b}

Lecture 2 ISM - © 2010 Houman Younessi Programming Language: Artificial Language created to produce artifacts called programs that control the behavior of automata, usually a computer. Compilers, Interpreters;

Lecture 2 ISM - © 2010 Houman Younessi Example Programs in Various Languages: int fib(int n) { if (n <= 2) return 1 else return fib(n-1) + fib(n-2) } (+ (fib(- N 1)) (fib(- N 2))))) fib1,fib2 :=1 to n do begin fib1,fib2 :=fib2,fib1; fib1 :=fib1+fib2 end; C family Lisp family Algol family

Lecture 2 ISM - © 2010 Houman Younessi Data Structure: A well-defined form of storing data. Influences the efficiency of algorithm used. Abstract (Data-type), Concrete (Implementation); Simple, Composite; Implemented in Memory

Lecture 2 ISM - © 2010 Houman Younessi Example Data Structure: Stack

Lecture 2 ISM - © 2010 Houman Younessi Database: A system that provides organized collection, retention and presentation of data according to a well-defined model that ensures user selected persistence. Definition and query schemas, Models (Hierarchical, networked, relational, object) Transaction Concurrency

Lecture 2 ISM - © 2010 Houman Younessi Application Types: - Compiler - Operating System - DBMS - Accounting and financial management - Inventory management - CAD

Lecture 2 ISM - © 2010 Houman Younessi Building a Database Step 1: Capturing the Data Model

Lecture 2 ISM - © 2010 Houman Younessi

Lecture 2 ISM - © 2010 Houman Younessi Step 2 NORMALIZATION

Lecture 2 ISM - © 2010 Houman Younessi What is Normalization? Normalization is the process of efficiently organizing data in a database. There are two goals of the normalization process: eliminating redundant data (for example, storing the same data in more than one table) and ensuring data dependencies make sense (only storing related data in a table). Both of these are worthy goals as they reduce the amount of space a database consumes and ensure that data is logically stored. There are five normal forms (1 st to 5 th ). These are cumulative in that to be in 2 nd normal form the data has to be in 1 st normal form first. The first to third normal forms are almost always obeyed. The fourth normal form occasionally, and the fifth normal form almost never. We will cover the first three normal forms here only.

Lecture 2 ISM - © 2010 Houman Younessi First Normal Form (1NF) * Eliminate duplicative columns from the same table. * Create separate tables for each group of related data and identify each row with a unique column or set of columns (the primary key). Second Normal Form (2NF) * Meet all the requirements of the first normal form. * Remove subsets of data that apply to multiple rows of a table and place them in separate tables. * Create relationships between these new tables and their predecessors through the use of foreign keys. Third Normal Form (3NF) * Meet all the requirements of the second normal form. * Remove columns that are not dependent upon the primary key.

Lecture 2 ISM - © 2010 Houman Younessi First Normal Form: Eliminate duplicative columns from the same table. Create separate tables for each group of related data and identify each row with a unique column (the primary key). ManagerSubordinate 1 Subordinate 2Subordinate 3 Subordinate 4 We can now eliminate the repeating groups by forming a table such as SubordinateManager We can now ensure that each entry is identified by a single identifier: Subordinate IDManager IDSubordinateManager

Lecture 2 ISM - © 2010 Houman Younessi Second Normal Form Remove subsets of data that apply to multiple rows of a table and place them in separate tables. Create relationships between these new tables and their predecessors through the use of foreign keys. reduce the amount of redundant data in a table by extracting it, placing it in new table(s) and creating relationships between those tables. CUS_IDFIRSTLASTSTREETCITYSTATEZIP CUS_IDFIRSTLASTSTREETZIP CITYSTATE to

Lecture 2 ISM - © 2010 Houman Younessi Third Normal Form Remove columns that are not fully dependent upon the primary key. CUS_IDPROD_IDUNIT_PRQTTYTOTAL To: CUS_IDPROD_IDUNIT_PRQTTY “TOTAL” is derivable as TOTAL=UNIT_PR*QTTY

Lecture 2 ISM - © 2010 Houman Younessi Next Step