Chapter 10

Database System
Development Lifecycle

Pearson Education © 2014

Database System Development
Lifecycle
Database planning

System definition

Requirements collection and analysis

Database design

DBMS selection

2
Pearson Education © 2014
Database System Development
Lifecycle
Application design
Prototyping (optional)
Implementation
Data conversion and loading
Testing
Operational maintenance

3
Pearson Education © 2014
Stages of
the
Database
System
Developme
nt Lifecycle

Pearson Education © 2014

Database Planning
Management activities that allow stages
of database system development lifecycle
to be realized as efficiently and
effectively as possible.
 Defining Mission Statement
 Identifying Mission Objectives
 Developing Standards

5
Pearson Education © 2014
Database Planning – Mission
Statement
Mission statement for the database project
defines major aims of database application.
 Defined by owner/director

6
Pearson Education © 2014
Database Planning – Mission
Objectives
Each objective should identify a particular
task that the database must support.
The assumption is that if the database system
supports the mission objectives, then the
mission statement should be met.

7
Pearson Education © 2014
Mission Objectives for DreamHome Database System

8
Pearson Education © 2014
Database Planning
Database planning should also include
development of standards that govern:
how data will be collected,
how the format should be specified,
what necessary documentation will be needed,
how design and implementation should proceed.

9
Pearson Education © 2014
System Definition

Describes scope and boundaries of

database system and the major user
views.

User view defines what is required of a

database system from perspective of:
a particular job role (such as Manager or
Supervisor) or
enterprise application area (such as
marketing, payroll, etc.).
10
Pearson Education © 2014
System Boundary for DreamHome Database System

11
Pearson Education © 2014
Major User Views for DreamHome Database System

12
Pearson Education © 2014
Requirements Collection and
Analysis
This stage involves the collection and
analysis of information about the part of the
enterprise to be served by the database.
Many techniques for gathering information.
 Fact finding technique (Chapter 11)

13
Pearson Education © 2014
Requirements Collection and
Analysis
Information is gathered for each major
user view including:
a description of data used or generated;
details of how data is to be used/generated;
any additional requirements for new database
system.

Information is analyzed to identify

requirements (features) to be included in
new database system.
14
Pearson Education © 2014
Database Design

Data modeling:
Building data model requires answering
questions about entities, relationships, and
attributes.

15
Pearson Education © 2014
DBMS Selection
Selection of an appropriate DBMS to
support the database system.
The aim is to select a system that—
Meets the current and future requirements
of the enterprise
Balanced against costs that include—
purchase of the DBMS product,
any additional software or hardware required
to support the database system, and
the cost associated with changeover and staff
training.
There are various features that can be
used to evaluate a DBMS product 16
Pearson Education © 2014
DBMS Evaluation Features

17
Pearson Education © 2014
DBMS Evaluation Features

18
Pearson Education © 2014
Application Design
Design of user interface and application
programs that use and process the
database.

Database design and application design

are parallel activities.

Includes two important activities:

transaction design;
user interface design.
19
Pearson Education © 2014
Application Design - Transactions
An action, or series of actions, carried
out by a single user or application
program, which accesses or changes
content of the database.
A transaction represent real world
events such as the registering of a
property for rent, the addition of new
member of staff, etc.
A transaction may be composed of
several operations, such as the transfer
of money from one account to another.
20
Pearson Education © 2014
Prototyping (optional)
Building working model of a database
system.

Purpose
to identify features of a system that work well,
or are inadequate;
to suggest improvements or even new features;
to clarify the users’ requirements;
to evaluate feasibility of a particular system
design.
21
Pearson Education © 2014
Implementation
Physical realization of the database and
application designs.
Use DDL to create database schemas and empty
database files.
Use DDL to create any specified user views.
Create the application programs.
Use DML.

22
Pearson Education © 2014
Data Conversion and Loading
Transferring any existing data into new
database and converting any existing
applications to run on new database.

Only required when new database system is

replacing an old system.
DBMS normally has utility that loads existing
files into new database.

23
Pearson Education © 2014
Testing
Process of running the database system with intent of
finding errors.

Use carefully planned test strategies and realistic data.

Demonstrates that database and application programs
appear to be working according to requirements.
Test:
Learnability—How long does it take a new user to become
productive with the system
Robustness– How tolerant is the system of user error

24
Pearson Education © 2014
Operational Maintenance
Process of monitoring and maintaining
database system following installation.
Monitoring performance of system.
if performance falls, may require tuning or
reorganization of the database.
Maintaining and upgrading database
application (when required).
Incorporating new requirements into
database application.
25
Pearson Education © 2014