Chapter 10

Database System
Development Lifecycle

Pearson Education © 2014

Information System
Resources that enable collection,
management, control, and dissemination of
information throughout an organization.

Database is fundamental component of

IS, and its development/usage should be
viewed from perspective of the wider
requirements of the organization.

2
Pearson Education © 2014
Database System Development
Lifecycle
Database planning

System definition

Requirements collection and analysis

Database design

DBMS selection (optional)

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

4
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, personnel, or stock control).
5
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 to be included in new
database system. Described in the
requirements specification.
6
Pearson Education © 2014
Requirements Collection and
Analysis
Another important activity is deciding
how to manage the requirements for a
database system with multiple user
views.
Three main approaches:
centralized approach;
view integration approach;
combination of both approaches.

7
Pearson Education © 2014
Requirements Collection and
Analysis
Centralized approach
Requirements for each user view are
merged into a single set of requirements.
A data model is created representing all
user views during the database design
stage.

8
Pearson Education © 2014
Centralized Approach to
Managing Multiple User Views

9
Pearson Education © 2014
Requirements Collection and
Analysis
View integration approach
Requirements for each user view remain as
separate lists.
Data models representing each user view
are created and then merged later during
the database design stage.

10
Pearson Education © 2014
Requirements Collection and
Analysis
Data model representing single user view
(or a subset of all user views) is called a
local data model.

Each model includes diagrams and

documentation describing requirements
for one or more but not all user views of
database.

11
Pearson Education © 2014
Requirements Collection and
Analysis
Local data models are then merged at a
later stage during database design to
produce a global data model, which
represents all user views for the database.

12
Pearson Education © 2014
View Integration Approach to
Managing Multiple User Views

13
Pearson Education © 2014
Database Design
Process of creating a design for a
database that will support the
enterprise’s mission statement and
mission objectives for the required
database system.

14
Pearson Education © 2014
Database Design
Main approaches include:
Top-down
Bottom-up
Inside-out
Mixed

15
Pearson Education © 2014
Database Design
Main purposes of data modeling include:
to assist in understanding the meaning
(semantics) of the data;
to facilitate communication about the
information requirements.

Building data model requires answering

questions about entities, relationships,
and attributes.

16
Pearson Education © 2014
Database Design
A data model ensures we understand:
- each user’s perspective of the data;
- nature of the data itself, independent of its
physical representations;
- use of data across user views.

17
Pearson Education © 2014
Database Design

Three phases of database design:

Conceptual database design
Logical database design
Physical database design.

18
Pearson Education © 2014
Conceptual Database Design

Process of constructing a model of the

data used in an enterprise, independent
of all physical considerations.

Data model is built using the information

in users’ requirements specification.

Conceptual data model is source of

information for logical design phase.

19
Pearson Education © 2014
Logical Database Design
Process of constructing a model of the
data used in an enterprise based on a
specific data model (e.g. relational), but
independent of a particular DBMS and
other physical considerations.

Conceptual data model is refined and

mapped on to a logical data model.

20
Pearson Education © 2014
Physical Database Design

Process of producing a description of the

database implementation on secondary
storage.

Describes base relations, file organizations,

and indexes used to achieve efficient access
to data. Also describes any associated
integrity constraints and security measures.

Tailored to a specific DBMS system.

21
Pearson Education © 2014
Three-Level ANSI-SPARC
Architecture and Phases of
Database Design

22
Pearson Education © 2014
CASE Tools

Support provided by CASE tools

include:
- data dictionary to store information about
database system’s data;
- design tools to support data analysis;
- tools to permit development of corporate
data model, and conceptual and logical
data models;
- tools to enable prototyping of applications.

23
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.
24
Pearson Education © 2014
Prototyping
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.
25
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.

26
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.

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

Use carefully planned test strategies and

realistic data.
Testing cannot show absence of faults; it can
show only that software faults are present.
Demonstrates that database and application
programs appear to be working according to
requirements.
28
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.
29
Pearson Education © 2014
Data Administration and
Database Administration
The Data Administrator (DA) and
Database Administrator (DBA) are
responsible for managing and controlling
the corporate data and corporate
database, respectively.

DA is more concerned with early stages

of database system development lifecycle
and DBA is more concerned with later
stages.
30
Pearson Education © 2014