01database_env

01database_env - Introduction to the Database Environment...

Info iconThis preview shows pages 1–12. Sign up to view the full content.

View Full Document Right Arrow Icon
Introduction to the Database Environment Douglas Shook 01/13/05
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Part One Introduction to Data
Background image of page 2
Database, Shook – Spring 2005 Data Management Intentionally do not store "information“ atomize information to create data Databases are the foundation of most organizational information systems Demands of: Knowledge Management Fast Response Dot Com ERP
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Database, Shook – Spring 2005 User View of “Data” (info)
Background image of page 4
Database, Shook – Spring 2005 Entity Relationship Diagram (ERD)
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Database, Shook – Spring 2005 Why Data Management? Organizations cannot exist without their data View data independent from the people and programs that use it Manage data as other resources ‑‑‑> DATA ---> INFORMATION ‑‑> DECISIONS Databases are the foundation of most organizational information systems
Background image of page 6
Database, Shook – Spring 2005 Pine Valley Furniture A pedagogical model for data management Typical small, growing business Started with manual systems Growth requires a movement toward using conceptual resources to manage physical resources
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Database, Shook – Spring 2005 Pine Valley Data Processing
Background image of page 8
Database, Shook – Spring 2005 In The Beginning: Manual Systems Advantages + simple/cheap to implement + conceptually clear + minimal special skills and equipment Disadvantages - constant flows of paperwork required to sync - complex questions difficult/time consuming - summary info not readily available - duplicate/inconsistent data abounds - access depends on physical location - exceptions create problems
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Database, Shook – Spring 2005 Then there was Cobol "Application‑Centric Approach" File Processing Systems ‑ separate files for departments/functions Advantages + automate the manual systems + physical location not important + conceptually clear Disadvantages - inconsistent data - uncontrolled redundancy - inflexibility - limited data sharing - enforcement standards - programmer productivity - program maintenance
Background image of page 10
Database, Shook – Spring 2005 File Processing Chimneys "Islands of Data"
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 12
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 37

01database_env - Introduction to the Database Environment...

This preview shows document pages 1 - 12. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online