(Spring 2015) Instructor: Craig Duckett Lecture 03: Tuesday, April 14, 2015 Data vs. Information 1.

Slides:



Advertisements
Similar presentations
Data vs. Information Data raw facts no context just numbers and text Information data with context processed data value-added to data –summarized –organized.
Advertisements

Introduction to Databases
Management Information Systems, Sixth Edition
Data - Information - Knowledge
Design Objectives Chapter 2. Design Objectives Why should you be concerned with database design? The importance of theory The advantages of learning good.
File Systems and Databases
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Databases and Processing Modes. Fundamental Data Storage Concepts and Definitions What is an entity? An entity is something about which information is.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Chapter 4: Database Management. Databases Before the Use of Computers Data kept in books, ledgers, card files, folders, and file cabinets Long response.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Lufthansa Case pp 23 Questions: What type of Information System is described? (TSP, PCS, ECS, MIS, DSS, EIS?) What are the components: People, Hardware,
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
Data at the Core of the Enterprise. Objectives  Define of database systems  Introduce data modeling and SQL  Discuss emerging requirements of database.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Database Systems: Design, Implementation, and Management Ninth Edition
Data at the Core of the Enterprise. Objectives  Define of database systems.  Introduce data modeling and SQL.  Discuss emerging requirements of database.
© Paradigm Publishing, Inc. 5-1 Chapter 5 Application Software Chapter 5 Application Software.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
XP Class Objectives – 9/10 and 9/12 Learn how to design a small database Understand the goals of a database Understand the terminology of database design.
© Paradigm Publishing Inc. 9-1 Chapter 9 Database and Information Management.
ITEC224 Database Programming
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 6: Foundations of Business Intelligence - Databases and Information Management Dr. Andrew P. Ciganek, Ph.D.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Management Information Systems By Effy Oz & Andy Jones
Concepts and Terminology Introduction to Database.
© Paradigm Publishing Inc. 9-1 Chapter 9 Database and Information Management.
What is a Database? A Database is…  an organized set of stored information usually on one topic  a collection of records  a way to organize information.
Discovering Computers Fundamentals Fifth Edition Chapter 9 Database Management.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
(Spring 2015) Instructor: Craig Duckett Lecture 10: Tuesday, May 12, 2015 Mere Mortals Chap. 7 Summary, Team Work Time 1.
Instructor: Craig Duckett Lecture 03: Tuesday, October 6 th, 2015 SQL Sorting, Aggregates and Joining Tables 1 BIT275: Database Design (Fall 2015)
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Database Design Overview and Principles. Why Design? A well designed relational database maintains data integrity and allows you to access any data and.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS Instructor Ms. Arwa Binsaleh.
(Spring 2015) Instructor: Craig Duckett Lecture 08: Tuesday, May 5, 2015 Mere Mortals Chap. 6 Summary, Team Work Time 1.
Introduction to Databases. What is a database?  A database program is nothing more than an electronic version of a 3x5 card file  A database is defined.
IS 320 Notes for April 15, Learning Objectives Understand database concepts. Use normalization to efficiently store data in a database. Use.
(Winter 2016) Instructor: Craig Duckett Lecture 15: Thursday, February 25 th Visual Studio Walk-Through 1.
Foundations of Information Systems in Business. System ® System  A system is an interrelated set of business procedures used within one business unit.
Computer Applications Chapter 16. Management Information Systems Management Information Systems (MIS)- an organized system of processing and reporting.
(Winter 2016) Instructor: Craig Duckett Lecture 13: Thursday, February 18 th Mere Mortals: Chap. 9 Summary, Team Work 1.
(Spring 2015) Instructor: Craig Duckett Lecture 07: Tuesday, April 28, 2015 PHASE 1: Discovery DUE TONIGHT 1.
(Winter 2016) Instructor: Craig Duckett Lecture 03: Tuesday, January 12 th Data vs. Information Conducting Interviews 42 Questions 1.
PREPARED BY: PN. SITI HADIJAH BINTI NORSANI. LEARNING OUTCOMES: Upon completion of this course, students should be able to: 1. Understand the structure.
Data -Data is the raw materials from which information is generated. -Data are raw facts or observations typically about physical phenomena or business.
(Spring 2015) Instructor: Craig Duckett Lecture 14: Thursday, May 12 th, 2016 Visual Studio Community Edition 1.
1 Management Information Systems M Agung Ali Fikri, SE. MM.
Introduction: Databases and Database Systems Lecture # 1 June 19,2012 National University of Computer and Emerging Sciences.
Management Information Systems by Prof. Park Kyung-Hye Chapter 7 (8th Week) Databases and Data Warehouses 07.
(Winter 2017) Instructor: Craig Duckett
Introduction To DBMS.
(Winter 2017) Instructor: Craig Duckett
(Winter 2017) Instructor: Craig Duckett
(Winter 2017) Instructor: Craig Duckett
(Winter 2017) Instructor: Craig Duckett
Chapter 1 Database Systems
(Winter 2017) Instructor: Craig Duckett
Chapter 9 Database and Information Management.
Instructor: Craig Duckett
PREP Instructor: Craig Duckett Lecture 07: Tuesday, April 19th , 2016
Chapter 1 Database Systems
The ultimate in data organization
Chapter 17 Designing Databases
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management
Presentation transcript:

(Spring 2015) Instructor: Craig Duckett Lecture 03: Tuesday, April 14, 2015 Data vs. Information 1

2 PHASE 1: DISCOVERY DUE: Tuesday, April 28 th, uploaded to Team Web Site and ZIPPED and uploaded to StudentRacker by Phase 1 Project Manager Phase 2: Design due Tuesday, May 19 th

3 The Team Project Five Phase Due Dates Phase 1: Discovery (200 Points) DUE TUESDAY, APRIL 28 Phase 2: Design (200 Points) DUE TUESDAY, MAY 19 Phase 3: Develop (200 Points) DUE THURSDAY, MAY 28 Phase 4: Distribute (200 Points) DUE TUESDAY, JUNE 9 Phase 5: Documentation (200 Points) DUE THURSDAY, JUNE 18

4 A Side Trip How Data is Stored in the Computer Representation of Bitmapped Graphics Slide In an SQL database, we can store large files as BLOB s (Binary Large OBjects)

5 Database Design for Mere Mortals: Chapter 2 Summary Chapter 2: Design Objectives A logical design of the database is highly important. Wizards that help you create tables are of no real use if the database itself is designed improperly. Accuracy, integrity and consistency of data will be dependent upon a good design. Many problems can arise if there are design flaws, such as inaccurate retrieval of information. Objectives of Good Design: Supports required and ad hoc information retrieval Contains efficiently constructed tables Imposes data integrity at the field, table and relationship level Data must provide accurate and valid information that is meaningful to the organization The database structure should be easily modified for possible future growth Advantages of Good Design: Easy to modify and maintain the structure Easy to modify data Easy retrieval of information Easy to develop and build user applications

6 Database Design for Mere Mortals: Chapter 2 Summary There are three traditional design methods: A requirements analysis phase involves examining the business being modeled, interviewing users and management to assess the current system and to analyze future needs and determining information requirements for the businessas a whole A data modeling phase involves modeling the database structure itself by using a method such as entity relationship diagramming (ER diagramming). This provides a means of visually representing various aspects of the database structure, such as the tables, table relationships and relationship characteristics. The Normalization phase is the process of decomposing large tables into smaller tables in order to eliminate redundant data, duplicate data and avoid problems with inserting, modifying or deleting data. Table structures are tested against normal forms, which are a specific set of rules that can be used to test a table structure to be sure it is sound and free of problems. These normal forms are: First through Fifth Normal Forms, Boyce-Codd Normal Form and Domain/Key Normal Form.

Data vs. Information Data raw facts no context just numbers and text Information data with context processed data value-added to data summarized organized analyzed

Data vs. Information Data: Information: 5/12/15 - The date of your mid-term exam. $51,215 - The average starting salary of a computer science major Zip code of Snake's Navel, Arkansas

Data vs. Information Data Information

Data  Information  Knowledge Data Information Summarizing the data Averaging the data Selecting part of the data Graphing the data Adding context Adding value

Data  Information  Knowledge Information Knowledge How is the info tied to outcomes? Are there any patterns in the info? What info is relevant to the problem? How does this info effect the system? What is the best way to use the info? How can we add more value to the info?

Information Systems Generic Goal: Transform Data  into  Information At the Core of an Information System is a Database (raw data).

Information Systems (TSP and PCS) Data doesn’t just "appear" Capturing Data is really the first step These systems help capture data but they also have other purposes (goals): 1. Transaction Processing Systems (TPS) 2. Process Control Systems (PCS) Discrete, Batch, Continuous

Capturing Data What kind of data is being captured? How is this data transformed into Information? How Is that information transformed into knowledge? How does that knowledge aid in decision-making?

Data Processing Recall that a basic system is composed of 5 components 1.Input 2.Output 3.Processing 4.Feedback 5.Control Typically processing helps transform data into information. InputOutput Processing Raw Data Information

Processing Summarizing Computing Averages Graphing Creating Charts Visualizing Data

A Scenario… Imagine it's 8:00 o'clock in the morning, and you're walking through a factory, that factory is in production, and you notice a pressure gauge on a pipe that shows 2200 psi. That is a piece of data. You go into the control room and there is a computer screen, and that screen is a graph of pressure, and you can see in fact that the pressure in that pipe is rising for rapidly. This is information provided to you as a time-series of data, data that is presented in such a way that makes sense, that tells you something. What is the knowledge you need right now? Presented with this information, what do you need to know right now? The key knowledge you need is what should I do? How should I respond? How should I react to this particular set of circumstances? Should I open a valve? Which valve should I open? Should I close a valve? Should I press the fire alarm and evacuate the factory because it's about to explore, or should I go and tell the director that we are at last on production and we can go and celebrate? If you know how to react, then you can make the correct decision. If you don't have that knowledge, then you're powerless. That's the difference between the data, the information, and the knowledge. The knowledge is the piece that allows you to make a decision. Now, where would you get that knowledge? Knowledge is the factor that allows you to take effective action, to make the correct decision with capability and know-how. Data Information Knowledge

18 Projects and the Team Formations Bothell Youth Court Wants a small database to hold names/cases/dates that can push a reminder when a particular case is scheduled to come up. Two people will be using it, both with administer access School of STEM (UW Bothell) Current using an Excel spreadsheet to enter and track information and would love to have a database to do this instead Project 3 Anybody have need of a database? Club? Recipes? Movies? Music? If so, list it on the index card (see next slide) Project 4 Anybody have need of a database? Club? Recipes? Movies? Music? If so, list it on the index card (see next slide)

19 Projects and Team Preferences Front of Index Card Your Name Project Preferences 1. Most Favorite Least Favorite Team Member Preferences Would LIKE to team with Would NOT want to team with Back of Index Card Skills Assessment Team Management Skills (0 – 5) Database Skills (0 – 5) SQL Skills (0 – 5) Design Skills (0 – 5) Project Idea Example: Club, recipes, films, music collection, etc

20 TEAMS Online Team Collaboration Programs (Free)

21 A Look at Phase 1: Discovery DUE Tuesday, May 5 th, 2015 A Quick Look