The document discusses the database environment and provides an overview of database concepts. It defines key terms like database, data, and information. It describes the evolution from file-based systems to centralized databases managed by a database management system (DBMS). The advantages of databases include improved data sharing and consistency. The document outlines different types of database applications and how databases have evolved with technologies like the internet and web-enabled databases.

1. © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 11
Chapter 1:Chapter 1:
The Database EnvironmentThe Database Environment
Modern Database ManagementModern Database Management
99thth
EditionEdition
Jeffrey A. Hoffer, Mary B. Prescott,Jeffrey A. Hoffer, Mary B. Prescott,
Heikki TopiHeikki Topi

2. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 22
ObjectivesObjectives
 Definition of termsDefinition of terms
 Explain growth and importance of databasesExplain growth and importance of databases
 Name limitations of conventional file processingName limitations of conventional file processing
 Identify five categories of databasesIdentify five categories of databases
 Explain advantages of databasesExplain advantages of databases
 Identify costs and risks of databasesIdentify costs and risks of databases
 List components of database environmentList components of database environment
 Describe evolution of database systemsDescribe evolution of database systems

3. 33
DefinitionsDefinitions
 DatabaseDatabase: organized collection of logically: organized collection of logically
related datarelated data
 DataData: stored representations of meaningful: stored representations of meaningful
objects and eventsobjects and events
 StructuredStructured: numbers, text, dates: numbers, text, dates
 UnstructuredUnstructured: images, video, documents: images, video, documents
 InformationInformation: data processed to increase: data processed to increase
knowledge in the person using the dataknowledge in the person using the data
 MetadataMetadata: data that describes the properties: data that describes the properties
and context of user dataand context of user data

4. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 44
Figure 1-1a Data in context
Context helps users understand data

5. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 55
Graphical displays turn data into useful
information that managers can use for
decision making and interpretation
Figure 1-1b Summarized data

6. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 66
Descriptions of the properties or characteristics of the
data, including data types, field sizes, allowable
values, and data context

7. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall
File-Based Systems (FBS)File-Based Systems (FBS)
77
FBS is a collection of application programs that perform
tasks where each program defines and manages its
own data.
Data
Entry
File
handling
File Def
User 1
Application Program 1 File1
Data
Entry
File
handling
File Def
User 2
Application Program 2 File 2

8. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 88
Disadvantages ofDisadvantages of File-Based Systems (FBS)File-Based Systems (FBS)
 Program-Data DependenceProgram-Data Dependence
 All programs maintain metadata for each file they useAll programs maintain metadata for each file they use
 Duplication of DataDuplication of Data
 Different systems/programs have separate copies of the same dataDifferent systems/programs have separate copies of the same data
 Limited Data SharingLimited Data Sharing
 No centralized control of dataNo centralized control of data
 Lengthy Development TimesLengthy Development Times
 Programmers must design their own file formatsProgrammers must design their own file formats
 Excessive Program MaintenanceExcessive Program Maintenance
 80% of information systems budget80% of information systems budget

9. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 99
Problems with Data DependencyProblems with Data Dependency
 Each application programmer must maintainEach application programmer must maintain
his/her own datahis/her own data
 Each application program needs to includeEach application program needs to include
code for the metadata of each filecode for the metadata of each file
 Each application program must have its ownEach application program must have its own
processing routines for reading, inserting,processing routines for reading, inserting,
updating, and deleting dataupdating, and deleting data
 Lack of coordination and central controlLack of coordination and central control
 Non-standard file formatsNon-standard file formats

10. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall
1010
Duplicate Data

11. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1111
Problems with DataProblems with Data
RedundancyRedundancy
 Waste of space to have duplicate dataWaste of space to have duplicate data
 Causes more maintenance headachesCauses more maintenance headaches
 The biggest problem:The biggest problem:
 Data changes in one file couldData changes in one file could
cause inconsistenciescause inconsistencies
 Compromises inCompromises in data integritydata integrity

12. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1212
SOLUTION:SOLUTION:
The DATABASE ApproachThe DATABASE Approach
 Central repository of shared dataCentral repository of shared data
 Data is managed by a controllingData is managed by a controlling
agentagent
 Stored in a standardized, convenientStored in a standardized, convenient
formform
Requires a Database Management System (DBMS)

13. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1313
Database ManagementDatabase Management
SystemSystem
DBMS manages data resources like an operating system manages hardware
resources
 A software system that is used to create, maintain, and provide
controlled access to user databases
Order Filing
System
Invoicing
System
Payroll
System
DBMS
Central database
Contains employee,
order, inventory,
pricing, and
customer data

14. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1414
Advantages of the Database ApproachAdvantages of the Database Approach
 Program-data independenceProgram-data independence
 Planned data redundancyPlanned data redundancy
 Improved data consistencyImproved data consistency
 Improved data sharingImproved data sharing
 Increased application development productivityIncreased application development productivity
 Enforcement of standardsEnforcement of standards
 Improved data qualityImproved data quality
 Improved data accessibility and responsivenessImproved data accessibility and responsiveness
 Reduced program maintenanceReduced program maintenance
 Improved decision supportImproved decision support

15. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1515
Costs and Risks of the DatabaseCosts and Risks of the Database
ApproachApproach
 New, specialized personnelNew, specialized personnel
 Installation and management cost andInstallation and management cost and
complexitycomplexity
 Conversion costsConversion costs
 Need for explicit backup and recoveryNeed for explicit backup and recovery
 Organizational conflictOrganizational conflict

16. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1616
Elements of the DatabaseElements of the Database
ApproachApproach
 Data modelsData models
 Graphical system capturing nature and relationship of dataGraphical system capturing nature and relationship of data
 Enterprise Data Model–high-level entities and relationships forEnterprise Data Model–high-level entities and relationships for
the organizationthe organization
 Project Data Model–more detailed view, matching data structureProject Data Model–more detailed view, matching data structure
in database or data warehousein database or data warehouse
 Relational DatabasesRelational Databases
 Database technology involving tables (relations) representingDatabase technology involving tables (relations) representing
entities and primary/foreign keys representing relationshipsentities and primary/foreign keys representing relationships
 Use of Internet TechnologyUse of Internet Technology
 Networks and telecommunications, distributed databases, client-Networks and telecommunications, distributed databases, client-
server, and 3-tier architecturesserver, and 3-tier architectures
 Database ApplicationsDatabase Applications
 Application programs used to perform database activitiesApplication programs used to perform database activities
(create, read, update, and delete) for database users(create, read, update, and delete) for database users

17. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1717
Segment of an enterprise data model
Segment of a project-level data model
Figure 1-2 Comparison of enterprise and project level data models

18. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1818
One customer
may place many
orders, but each
order is placed by
a single customer
 One-to-many
relationship

19. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1919
One order has
many order lines;
each order line is
associated with a
single order
 One-to-many
relationship

20. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2020
One product can
be in many
order lines, each
order line refers
to a single
product
 One-to-many
relationship

21. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2121
Therefore, one
order involves
many products
and one product is
involved in many
orders
 Many-to-many
relationship

22. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2222

23. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2323
Figure 1-5 Components of the Database Environment

24. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2424
Components of theComponents of the
Database EnvironmentDatabase Environment
 CASE ToolsCASE Tools––computer-aided software engineeringcomputer-aided software engineering
 RepositoryRepository––centralized storehouse of metadatacentralized storehouse of metadata
 Database Management System (DBMS)Database Management System (DBMS) ––
software for managing the databasesoftware for managing the database
 DatabaseDatabase––storehouse of the datastorehouse of the data
 Application ProgramsApplication Programs ––software using the datasoftware using the data
 User InterfaceUser Interface––text and graphical displays to userstext and graphical displays to users
 Data/Database AdministratorsData/Database Administrators ––personnelpersonnel
responsible for maintaining the databaseresponsible for maintaining the database
 System DevelopersSystem Developers ––personnel responsible forpersonnel responsible for
designing databases and softwaredesigning databases and software
 End UsersEnd Users––people who use the applications andpeople who use the applications and
databasesdatabases

25. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2525
The Range of Database ApplicationsThe Range of Database Applications
 Personal databasesPersonal databases
 Workgroup databasesWorkgroup databases
 Departmental/divisional databasesDepartmental/divisional databases
 Enterprise databaseEnterprise database
 Enterprise resource planning (ERP) systemsEnterprise resource planning (ERP) systems
 Data warehousing implementationsData warehousing implementations

26. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2626
Table 1-6 Summary of Database Applications

27. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2727

28. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2828
Figure 1-7 Workgroup database with wireless
local area network

29. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 2929
Enterprise Database ApplicationsEnterprise Database Applications
 Enterprise Resource Planning (ERP)Enterprise Resource Planning (ERP)
 Integrate all enterprise functionsIntegrate all enterprise functions
(manufacturing, finance, sales, marketing,(manufacturing, finance, sales, marketing,
inventory, accounting, human resources)inventory, accounting, human resources)
 Data WarehouseData Warehouse
 Integrated decision support system derivedIntegrated decision support system derived
from various operational databasesfrom various operational databases

30. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 3030
Figure 1-8 An enterprise data warehouse

31. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 3131
Web-Enabled DatabasesWeb-Enabled Databases
 Web applications requiring databasesWeb applications requiring databases
 Customer relationship management (CRM)Customer relationship management (CRM)
 Business-to-consumer (B2C)Business-to-consumer (B2C)
 Electronic data interchange (EDI)Electronic data interchange (EDI)
 Private intranetsPrivate intranets
 XML-defined Web servicesXML-defined Web services

32. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 3232
Web-Enabled Databases (cont.)Web-Enabled Databases (cont.)
 Issues to considerIssues to consider
 Which technologies to use?Which technologies to use?
 Security/privacy protectionSecurity/privacy protection
 Managing huge volumes of data from InternetManaging huge volumes of data from Internet
transactionstransactions
 Maintaining data qualityMaintaining data quality

33. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 3333
Figure 1-9 Evolution of database technologies

34. Chapter 1 © 2009 Pearson Education, Inc. Publishing as Prentice Hall© 2009 Pearson Education, Inc. Publishing as Prentice Hall 3434
All rights reserved. No part of this publication may be reproduced, stored in a
retrieval system, or transmitted, in any form or by any means, electronic,
mechanical, photocopying, recording, or otherwise, without the prior written
permission of the publisher. Printed in the United States of America.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice HallCopyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall