0% found this document useful (0 votes)
27 views30 pages

Asdf Wefef

asdfk asldfkjas lasdkfj alsdkfjhr alskfj

Uploaded by

battal2023513
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
27 views30 pages

Asdf Wefef

asdfk asldfkjas lasdkfj alsdkfjhr alskfj

Uploaded by

battal2023513
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 30

CHAPTER 1:

THE DATABASE
ENVIRONMENT

Modern Database Management 1


OBJECTIVES
 Definition of terms
 Explain growth and importance of databases
 Name limitations of conventional file processing
 Identify five categories of databases
 Explain advantages of databases
 Identify costs and risks of databases
 List components of database environment
 Describe evolution of database systems

2
DEFINITIONS
 Database: organized collection of logically related data
 Data: stored representations of meaningful objects and events
 Structured: numbers, text, dates
 Unstructured: images, video, documents

 Metadata: data that describes the properties and context of user data

3
Descriptions of the properties or characteristics of the
data, including data types, field sizes, allowable
values, and data context

4
DISADVANTAGES OF FILE
PROCESSING
 Program-Data Dependence
 All programs maintain metadata for each file they use
 Duplication of Data
 Different systems/programs have separate copies of the same data
 Limited Data Sharing
 No centralized control of data
 Lengthy Development Times
 Programmers must design their own file formats
 Excessive Program Maintenance
 80% of information systems budget

5
PROBLEMS WITH DATA

DEPENDENCY
Each application programmer must maintain his/her own data
 Each application program needs to include code for the metadata of
each file
 Each application program must have its own processing routines for
reading, inserting, updating, and deleting data
 Lack of coordination and central control
 Non-standard file formats

6
PROBLEMS WITH DATA
REDUNDANCY
Waste of space to have duplicate data
Causes more maintenance headaches
The biggest problem:
 Data changes in one file could cause
inconsistencies
 Compromises in data integrity

7
Duplicate Data

8
SOLUTION:
THE DATABASE APPROACH
Central repository of shared data
Data is managed by a controlling agent
Stored in a standardized, convenient form

Requires a Database Management System (DBMS)


9
DATABASE
MANAGEMENT
 A software system that is used to create, maintain, and provide
controlled access to user databases

SYSTEM
Order Filing
System

Invoicing Central database


DBMS
System
Contains employee,
order, inventory,
pricing, and
Payroll
customer data
System

DBMS manages data resources like an operating system manages hardware resources

10
ADVANTAGES OF THE DATABASE
APPROACH
 Program-data independence
 Planned data redundancy
 Improved data consistency
 Improved data sharing
 Increased application development productivity
 Enforcement of standards
 Improved data quality
 Improved data accessibility
 Reduced program maintenance

11
COSTS AND RISKS OF THE
DATABASE APPROACH
 Installation and management cost and complexity
 Conversion costs
 Need for explicit backup and recovery
 Organizational conflict

12
Data models
Graphical system capturing nature and relationship of data
E-R model is design or blueprint of database that can later
be implemented as database/
Database
Database Design
Design
Relational Databases
Database technology involving tables (relations)
representing entities and primary/foreign keys representing
relationships
The Process of Database Design

ANALYSIS
Problem
Data Modeling
Domain
(eg. Using E-R Model

DESIGN
IMPLEMENTATION Relational Logical
Relational Model
DBMS
Figure 1-2 Comparison of enterprise and project level data models
Segment of an enterprise data model

Segment of a project-level data model

14
One customer
may place many
orders, but each
order is placed by
a single customer
 One-to-many
relationship

15
One order has
many order lines;
each order line is
associated with a
single order
 One-to-many
relationship

16
One product can
be in many
order lines, each
order line refers
to a single
product
 One-to-many
relationship

17
Therefore, one
order involves
many products
and one product is
involved in many
orders

 Many-to-many
relationship

18
19
Figure 1-5 Components of the Database Environment

20
COMPONENTS OF THE
DATABASE ENVIRONMENT
 CASE Tools–computer-aided software engineering
 Repository–centralized storehouse of metadata
 Database Management System (DBMS) –software for
managing the database
 Database–storehouse of the data
 Application Programs–software using the data
 User Interface–text and graphical displays to users
 Data/Database Administrators–personnel responsible for
maintaining the database
 System Developers–personnel responsible for designing
databases and software
 End Users–people who use the applications and databases
21
THE RANGE OF DATABASE
APPLICATIONS
 Personal databases
 Workgroup databases
 Departmental/divisional databases
 Enterprise database
 Enterprise resource planning (ERP) systems
 Data warehousing implementations

22
ENTERPRISE DATABASE
APPLICATIONS
 Enterprise Resource Planning (ERP)
 Integrate all enterprise functions (manufacturing, finance, sales, marketing,
inventory, accounting, human resources)
 Data Warehouse
 Integrated decision support system derived from various operational databases

23
WEB-ENABLED
DATABASES
 Web applications requiring databases
 Customer relationship management (CRM)
 Business-to-consumer (B2C)
 Electronic data interchange (EDI)
 Private intranets
 XML-defined Web services

24
Table 1-6 Summary of Database Applications

25
26
Figure 1-7 Workgroup database with wireless
local area network

27
Figure 1-8 An enterprise data warehouse

28
Figure 1-9 Evolution of database technologies

29
Copyright © Pearson Education, Inc. Publishing as Prentice Hall

30

You might also like