“Introduction to Database and

Transaction”
Database Management 1 (IT 30)
 Two Approaches to Database and IS
Development
 SDLC
 System Development Life Cycle
 Detailed, well-planned development process
 Time-consuming, but comprehensive
 Long development cycle
 Prototyping
 Rapid application development (RAD)
 Cursory attempt at conceptual data modeling
 Define database during development of initial prototype
 Repeat implementation and maintenance activities with
new prototype versions
2
 Systems Development Life Cycle
(see also Figure 1-7)
Planning

Analysis

Logical Design

Physical Design

Implementation

Maintenance

3
 Systems Development Life Cycle
(see also Figure 1-7) (cont.)
Planning
Planning Purpose–preliminary understanding
Deliverable–request for study
Analysis

Logical Design

Physical Design

Database activity– Implementation

enterprise modeling
and early conceptual
Maintenance
data modeling

4
 Systems Development Life Cycle
(see also Figure 1-7) (cont.)
Purpose–thorough requirements analysis
Planning and structuring
Deliverable–functional system specifications
Analysis
Analysis

Logical Design

Physical Design

Database activity–thorough Implementation

and integrated conceptual
data modeling
Maintenance

5
 Systems Development Life Cycle
(see also Figure 1-7) (cont.)
Purpose–information requirements elicitation
Planning and structure
Deliverable–detailed design specifications
Analysis

Logical Design
Logical Design

Physical Design

Database activity– Implementation

logical database design
(transactions, forms,
Maintenance
displays, views, data
integrity and security)

6
 Systems Development Life Cycle
(see also Figure 1-7) (cont.)
Purpose–develop technology and
Planning organizational specifications

Analysis Deliverable–program/data
structures, technology purchases,
organization redesigns
Logical Design

Physical Design
Physical Design

Database activity– Implementation

physical database design
(define database to DBMS,
Maintenance
physical data organization,
database processing programs)

7
 Systems Development Life Cycle
(see also Figure 1-7) (cont.)
Purpose–programming, testing,
Planning training, installation, documenting

Analysis Deliverable–operational programs,

documentation, training materials
Logical Design

Physical Design

Database activity–
database implementation, Implementation
Implementation
including coded programs,
documentation, Maintenance
installation and conversion

8
 Systems Development Life Cycle
(see also Figure 1-7) (cont.)
Planning Purpose–monitor, repair, enhance

Deliverable–periodic audits
Analysis

Logical Design

Physical Design

Database activity–
database maintenance, Implementation
performance analysis
and tuning, error Maintenance
Maintenance
corrections

9
 Prototyping Database Methodology
(Figure 1-8)

Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 10 10

 Prototyping Database Methodology
(Figure 1-8) (cont.)

Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 11 11

 Prototyping Database Methodology
(Figure 1-8) (cont.)

Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 12 12

Prototyping Database Methodology
(Figure 1-8) (cont.)

13
 Prototyping Database Methodology
(Figure 1-8) (cont.)

Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 14 14

 Database Schema
 External Schema
 User Views
 Subsets of Conceptual Schema
 Can be determined from business-function/data entity
matrices
 DBA determines schema for different users
 Conceptual Schema
 E-R models–covered in Chapters 2 and 3
 Internal Schema
 Logical structures–covered in Chapter 4
 Physical structures–covered in Chapter 5

15
 Figure 1-9 Three-schema architecture

Different people
have different
views of the
database…these
are the external
schema

The internal
schema is the
underlying
design and
implementation

Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 16 16

 Managing Projects
 Project–a planned undertaking of related
activities to reach an objective that has a
beginning and an end
 Initiated and planned in planning stage of
SDLC
 Executed during analysis, design, and
implementation
 Closed at the end of implementation

17
 Managing Projects:
People Involved
 Business analysts
 Systems analysts
 Database analysts and data modelers
 Users
 Programmers
 Database architects
 Data administrators
 Project managers
 Other technical experts

18
 Evolution of Database Systems
 Driven by four main objectives:
 Need for program-data independence 
reduced maintenance
 Desire to manage more complex data types
and structures
 Ease of data access for less technical personnel
 Need for more powerful decision support
platforms

19
Figure 1-10a Evolution of database technologies

20
Figure 1-10b Database architectures

21
Figure 1-10b Database architectures (cont.)

22
Figure 1-10b Database architectures (cont.)

23
 The Range of Database Applications
 Personal databases
 Two-tier and N-tier Client/Server databases
 Enterprise applications
 Enterprise resource planning (ERP) systems
 Data warehousing implementations

24
 Figure 1-11 Two-tier database with local
area network

Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 25 25

 Figure 1-12 Three-tiered client/server database
architecture

Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 26 26

 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

27
 FIGURE 1-13 Computer
System for Pine Valley
Furniture Company

Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 28 28

“Giving the best what we have in making what
you are and what you can be”