Tuesday, February 1, 20001 Management of Information Systems: 45-870 Mini-3 Spring 2000.

Slides:



Advertisements
Similar presentations
Information Systems Today: Managing in the Digital World
Advertisements

Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Relational Databases Chapter 4.
M.S. Access Module CAS 133 Russ Erdman. M.S. Access Module Assignment Overview Two options for the unit: All students complete Units A, B and C In class.
ACCESS PART 2. Objectives Database Tables Table Parts Key Field Query and Reports Import from Excel Link to Excel.
Data Modeling with ERD ISYS 363. Entity-Relationship Diagram An entity is a “thing” in the real world, such as a person, place, event for which we intend.
The Relational Database Model:
3-1 Chapter 3 Data and Knowledge Management
Designing a Database Unleashing the Power of Relational Database Design.
Introduction to Database. File Formats Comma delimited file –"s1","peter",3 –"s2","paul",2.5 –"s3","mary",3.5 –Demo: Excel – Data/Import Extended Markup.
Databases Week 7 LBSC 690 Information Technology.
1004INT Information Systems Week 10 Databases as Business Tools.
Thursday, January 27, Management of Information Systems: Mini-3 Spring 2000.
Information Technology in Organizations
Fall Information Systems for Management Introduction to Course Section L01 Marcel V. Joaquin, CMA Information Systems for Management.
Attribute databases. GIS Definition Diagram Output Query Results.
Chapter 6 Data Flow Diagramming Copyright © 2010 by The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/Irwin.
Copyright © 2016 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Databases & Data Warehouses Chapter 3 Database Processing.
File and Database Design SYS364. Today’s Agenda WHTSA DBMS, RDBMS, SQL A place for everything and everything in its place. Entity Relationship Diagrams.
Database Design Concepts
Introduction –All information systems create, read, update and delete data. This data is stored in files and databases. Files are collections of similar.
Access 2007 Database Application Managing Business Information Effectively BCIS 1 and 2.
2005 SPRING CSMUIntroduction to Information Management1 Organizing Data John Sum Institute of Technology Management National Chung Hsing University.
Relational databases and third normal form As always click on speaker notes under view when executing to get more information!
CHAPTER 8: MANAGING DATA RESOURCES. File Organization Terms Field: group of characters that represent something Record: group of related fields File:
DATABASE DESIGN USING MICROSOFT ACCESS. What is a Database?  DMS Database management system  Database Collection of data organized in a manner that.
CTFS Workshop Shameema Esufali Suzanne Lao Data coordinators and technical resources for the network
Database Management Systems
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.
Copyright Ó Oracle Corporation, All rights reserved. Normalization Use the student note section below for further explanation of the slide content.Use.
Information Systems Today (©2006 Prentice Hall) 3-1 CS3754 Class Note 12 Summery of Relational Database.
Concepts of Database Management Seventh Edition
Organizing Data Revision: pages 8-10, 31 Chapter 3.
What we’ve learnt Doc 5.69 Doc 5.70 Section 1-3. A simple database Related objects Tables hold the data Forms, reports, queries to access the data.
Designing Databases Systems Analysis and Design, 7e Kendall & Kendall 13 © 2008 Pearson Prentice Hall.
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.
Constraints - primary and foreign keys in Oracle Please use speaker notes for additional information!
6.1 © 2010 by Prentice Hall 6 Chapter Foundations of Business Intelligence: Databases and Information Management.
MS Access. Access is a DBMS/RDMS DBMS = Database Management System RDMS = Relational Database Management System.
Advanced Accounting Information Systems Day 7 Database Modeling.
Databases,Tables and Forms Access Text by Grauer Chapters 1 & 2.
Access Review. Access Access is a database application A database is a collection of records and files organized for a particular purpose Access supports.
+ Information Systems and Databases 2.2 Organisation.
Chapter 13 Designing Databases Systems Analysis and Design Kendall & Kendall Sixth Edition.
ENTITY RELATIONSHIP DIAGRAM ENTITY RELATIONSHIP DIAGRAM IS A SPECIALIZED GRAPHIC THAT ILLUSTRATES THE INTERRELATIONSHIPS BETWEEN ENTITIES IN A DATABASE.
Database Design Normalisation. Last Session Looked at: –What databases were –Where they are used –How they are used.
Database Management Supplement 1. 2 I. The Hierarchy of Data Database File (Entity, Table) Record (info for a specific entity, Row) Field (Attribute,
5-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
U:/msu/course/cse/103 Day 18, Slide 1 CSE 103 Day 18 If you are not enrolled in CSE 103, please save and log out by 10:10.
Lesson 2: Designing a Database and Creating Tables.
Information Systems Today: Managing in the Digital World TB3-1 3 Technology Briefing Database Management “Modern organizations are said to be drowning.
Planning & Creating a Database By Ms. Naira Microsoft Access.
1 2 Concepts of Database Management, 4 th Edition, Pratt & Adamski Chapter 2 The Relational Model 1: Introduction, QBE, and Relational Algebra.
* Database is a group of related objects * Objects can be Tables, Forms, Queries or Reports * All data reside in Tables * A Row in a Table is a record.
6.1 © 2007 by Prentice Hall Chapter 6 (Laudon & Laudon) Foundations of Business Intelligence: Databases and Information Management.
Howard Paul. Sequential Access Index Files and Data File Random Access.
EXAM-2 OVERVIEW Aliya Farheen
Hoi Le. Why database? Spreadsheet is not good to: Store very large information Efficiently update data Use in multi-user mode Hoi Le2.
What Is Normalization  In relational database design, the process of organizing data to minimize redundancy  Usually involves dividing a database into.
MS Access. Most A2 projects use MS Access Has sufficient depth to support a significant project. Relational Databases. Fairly easy to develop a good user.
Starter Draw a mind map for topic 6 Databases. Objectives Revise topic CG3.6 Databases using various activities and ensure that topics covered are understood.
Flat file and relational databases Flat file database In a flat file database information is held in a single table. Student IDStudent name GenderDOBCourse.
Information Systems Today: Managing in the Digital World
Chapter 6 Data flow diagramming ACCOUNTING INFORMATION SYSTEMS
CSCI-100 Introduction to Computing
Databases and Information Management
Databases and Information Management
Presentation transcript:

Tuesday, February 1, Management of Information Systems: Mini-3 Spring 2000

Tuesday, February 1, Agenda Announcements Technology Byte Presentations Designing and Creating Databases (Cont’d) Brief Review of Database Design Principles Using MS Access 2000 to Create Relational Databases Writing Queries for Relational Databases Using MS Access 2000 to Write Queries for Relational Databases

Tuesday, February 1, Announcements Technology Byte Presentations Today (2/1): Section A: DeathSpiral.Com, E-Sixpack Section B: Jeree’s Kids, Hot TaMaLes Thursday (2/3): Section A: Digital Agents, Hyperlinks Section B: Alwin & the Chipmunks, Cash Money Brothers IT Exercise I Graded/Returned Comments

Tuesday, February 1, Announcements Schedule modifications There will be NO handout on Internet, Intranets, Extranets Today we will continue with Database topics We will discuss Chapter 6 on Thursday (2/3) IT Exercise II due no later than midnight this Friday, 2/4/00 Submit one set of answers for your team You can to me as an MS Word attachment or submit as hard copy

Tuesday, February 1, Announcements Technology Byte Report Due on no later than midnight this Friday, 2/4/00 Submit as a web page linked to your team’s home page that you had created in the first IT exercise

Tuesday, February 1, Technology Byte Presentations Section A: DeathSpiral.Com E-Sixpack Section B: Jeree’s Kids Hot TaMaLes

Tuesday, February 1, Creating Relational Databases: Brief Review What is a relational database Going from a “flat” file to a relational database…..

Tuesday, February 1, A Traditional “Flat” File

Tuesday, February 1, Relational DataBase Faculty Table Dept Table Course Table

Tuesday, February 1, How to get from a flat file to a relational database? Identify Entities (Tables) Identify Attributes (Fields) Normalize Entities Identify Relationships between Normalized Entities Identify Primary and Foreign Keys

Tuesday, February 1, EXAMPLE #1: Department DB Data include: n Department Name n Department Chair n Department Address n Department Phone n Faculty ID # n Faculty Name n Faculty Rank n Course Name n Course # n Course Credits n Course Enrollment Capacity

Tuesday, February 1, Step#1: Pull out repeating groups (First Normal Form) Step#1: Pull out repeating groups (First Normal Form) FROM: Department (Dept-Name, Dept-Chair, Dept-Addr, Dept-Phone, Fac-ID, Fac-Name, Fac-Rank, Course-Name, Course#, Course-Cred, Course-Cap) TO: Department (Dept-Name, Dept-Chair, Dept-Addr, Dept-Phone) Faculty-Course (Fac-ID, Fac-Name, Fac-Rank, Course-Name, Course#, Course-Cred, Course-Cap)

Tuesday, February 1, Step#2: Pull out facts about a portion of the key (Second Normal Form) Step#2: Pull out facts about a portion of the key (Second Normal Form) Doesn’t apply here?

Tuesday, February 1, Step#3: Pull out facts about a non-key attribute (Third Normal Form) Step#3: Pull out facts about a non-key attribute (Third Normal Form) FROM: Faculty-Course (Fac-ID, Fac-Name, Fac-Rank, Course-Name, Course#, Course-Cred, Course-Cap) TO: Faculty (Fac-ID, Fac-Name, Fac-Rank) Course (Course-Name, Course#, Course-Cred, Course-Cap)

Tuesday, February 1, Normalized Relations for this Data Department (Dept-Name, Dept-Chair, Dept-Addr, Dept- Phone) Faculty (Fac-ID, Fac-Name, Fac-Rank, Fac-Dept) Course (Course-Name, Course#, Course-Cred, Course-Cap, Course-Fac)

Tuesday, February 1, From Normalized Relations to an Entity Relationship Diagram each normalized relation becomes an entity identifier of each normalized relation becomes the primary key secondary identifier of each normalized relation becomes a foreign key Characteristics of each normalized relation determine relationship between entities

Tuesday, February 1, Entity Relationship Diagram Example #1 Department Course Faculty (Fac-ID, Fac-Name, Fac-Rank, Fac-Dept) (Dept-Name, Dept-Chair, Dept-Addr, Dept-Phone) (Course#, Course-Name, Course-Cred, Course-Cap, Course-Fac)

Tuesday, February 1, From an ERD to a Database in MS Access 2000 Adding Tables, Relationships and Data By hand Importing from spreadsheet Important! Must use normalized tables, relationships and data when creating the database in MS Access Illustration for Example 1 See Data for IT Exercise II and MS Access Tips 1

Tuesday, February 1, Retrieving Data from Databases Selecting Relations Joining Relations Projecting columns (fields) from the joined relation Selecting rows (records) from the joined relation

Tuesday, February 1, Retrieving Data from Databases (Cont’d) Deriving new attributes Indexing/sorting rows (records) Calculating totals Presenting data

Tuesday, February 1, Writing Queries in MS Access 2000 See MS Access Tips 2 Simple queries Grouping, summing & sorting fields Selecting data Calculated fields Displaying/not displaying fields Make vs. Select Table queries Illustrative Examples

Tuesday, February 1, Designing Databases: Another Example Normalizing and creating an ERD for the Sales Report Data

Tuesday, February 1, EXAMPLE #2: Sales Report Data Data includes: n Sales Person # n Sales Person Name n Sales Area n Customer Name n Customer Number n Warehouse Number n Warehouse Location n Sales Amount

Tuesday, February 1, Step#1: Pull out repeating groups (First Normal Form) Step#1: Pull out repeating groups (First Normal Form) FROM: SalesReport (SalesPerson#, SalesPerson-Name, Sales-Area, Customer#, Customer-Name, Warehouse#, Warehouse-Location, Sales-Amount) TO: SalesPerson (SalesPerson#, SalesPerson-Name, Sales-Area) SalesPerson-Customer (SalesPerson#, Customer#, Customer-Name, Warehouse#, Warehouse-Location, Sales-Amount)

Tuesday, February 1, Step#2: Pull out facts about a portion of the key (Second Normal Form) Step#2: Pull out facts about a portion of the key (Second Normal Form) FROM: SalesPerson-Customer (SalesPerson#, Customer#, Customer-Name, Warehouse#, Warehouse-Location, Sales-Amount) TO: Sales (SalesPerson#, Customer#, Sales-Amount) Customer-Warehouse (Customer#, Customer-Name, Warehouse#, Warehouse-Location)

Tuesday, February 1, Step#3: Pull out facts about a non-key attribute (Third Normal Form) Step#3: Pull out facts about a non-key attribute (Third Normal Form) FROM: Customer-Warehouse (Customer#, Customer-Name, Warehouse#, Warehouse-Location) TO: Customer (Customer#, Customer-Name) Warehouse (Warehouse#, Warehouse-Location)

Tuesday, February 1, Normalized Relations for this Data Sales (SalesPerson#, Customer#, Sales-Amount) SalesPerson (SalesPerson#, SalesPerson-Name, Sales-Area) Customer (Customer#, Customer-Name, Warehouse#) Warehouse (Warehouse#, Warehouse-Location)

Tuesday, February 1, Entity Relationship Diagram Example SalesPerson Customer Warehouse Sales (SalesPerson#, Customer#, Sales-Amount) (SalesPerson#, SalesPerson-Name, Sales-Area) (Customer#, Customer-Name, Warehouse#) (Warehouse#, Warehouse-Location)