ISYS6307

Data & Information Management

Week 1
Database Development Lifecycle
 Learning Outcome
At the end of this course, the student should
be able to:
• Sketch Database Development Life Cycle on
Development Application
 Sub Topics
• Introduction
• Database Development LifeCycle
• Database Planning
• Database Design
• DbMS Selection
• Application Design
• Prototyping
• Implementation
INTRODUCTION
 Introduction
On the other hand, the development of many
applications is hampered by the slow
migration process to the new system, high
operational and maintenance costs, and poor
system performance. As a solution, a Software
Development Life Cycle (SDLC) is proposed and
on the database side a Database Development
Life Cycle (DSDLC) is proposed.
DATABASE DEVELOPMENT LIFECYCLE
 Database Development
Lifecycle

Database Development Lifecycle process

Source : Connoly & Begg (2015)

Stage
Database planning
System definition
Requirements collection and
analysis
Database design
DBMS selection
Application design
Prototyping (optional)
Implementation
Data conversion and loading
Testing
Operational maintenance
Summary Of Database
Development Lifecycle
Main Activities
Planning how the stages of the lifecycle can be realized most efficiently and effectively.
Specifying the scope and boundaries of the database system, including the major user
views, its users, and application areas.
Collection and analysis of the requirements for the new database system.
Conceptual, logical, and physical design of the database.
Selecting a suitable DBMS for the database system.
Designing the user interface and the application programs that use and process the
database.
Building a working model of the database system, which allows the designers or users to
visualize and evaluate how the final system will look and function.
Creating the physical database definitions and the application programs..
Loading data from the old system to the new system and, where possible, converting any
existing applications to run on the new database.
Database system is tested for errors and validated against the requirements specified by the
users.
Database system is fully implemented. The system is continuously monitored and
maintained. When necessary, new requirements are incorporated into the database
system through the preceding stages of the lifecycle.
DATABASE PLANNING
 Introduction of Database
Planning

Database planning • Identification of enterprise plans

must be integrated and goals with subsequent
with the overall IS determination of information
systems needs;
strategy of the • Evaluation of current information
organization. There systems to determine existing
are three main strengths and weaknesses;
issues involved in • Appraisal of IT opportunities that
formulating an IS might yield competitive
strategy, which are: advantage.
SYSTEM DEFINITION
 Identifying User

Identifying user views is an important

aspect of developing a database
system because it helps to ensure
that no major users of the database
are forgotten when developing the
requirements for the new database
system, also in the development of a
relatively complex database system by
allowing the requirements to be
broken down into manageable pieces.
 System Definition

Boundary or access privilege for user

Source : Connoly & Begg (2015)
 Analysis of information
Information
is gathered A description of the data
for each used or generated;
major user
view (that
is, job role The details of how data is to
or be used or generated;
enterprise
application
area), Any additional requirements
including:
for the new database system
 Three Main Approaches

The following of the

requirements on a
database system with
multiple user views:

The view A combination

The centralized
integration of both
approach
approach approaches
 Global Data

In the database design stage, a

global data model is created, which
represents all user views. The
global data model is composed of
diagrams and documentation that
formally describe the data
requirements of the users.
 The centralized approach
to managing multiple
user views

Data processing from different user to database (root mode)

Source : Connoly & Begg (2015)
 Local Data Model and
Global Data Model
Local data model : Each model is composed of
diagrams and documentation that formally
describes the requirements of one or more but
not all user views of the database.
The local data models are then merged at a
later stage of database design to produce a
global data model, which represents all user
requirements for the database.
 The view integration
approach to managing
multiple user views

Data processing from different previllage

user to database
Source : Connoly & Begg (2015)
DATABASE DESIGN
 Comparison Between
Bottom-up and Top-down
Database Design
Bottom-up

The bottom-up approach begins at the fundamental level of

attributes (that is, properties of entities and relationships), which
through analysis of the associations between attributes are
grouped into relations that represent types of entities and
relationships between entities.

Top-down

The Top-down approach starts with the development of data

models that contain a few high-level entities and relationships and
then applies successive top-down refinements to identify lower-
level entities, relationships, and the associated attributes.
 Data Model

• Each user’s
Data model makes it perspective of the
easier to understand data
• The nature of the
the meaning of the
data itself,
data, and thus we independent of its
model data to physical
ensure that we representations
understand: • The use of data
across user views
DBMS SELECTION
 DBMS Selection
If no DBMS exists, an appropriate part of the
lifecycle in which to make a selection is between the
conceptual and logical database design phases.

However, selection can be done at any time prior to

logical design provided sufficient information is
available regarding system requirements such as
performance, ease of restructuring, security, and
integrity constraints.
 Source Of Information
For DBMS Selection

The World Wide Web is an excellent source of

information and can be used to identify potential
candidate DBMSs. For example, InfoWorld’s online
technology test center provides a comprehensive
review of DBMS products.
 Evaluate a DBMS Product
For the purposes of the evaluation, these
features can be assessed as groups (for
example, data definition) or individually (for
example, data types available).
DbMS Selection

Assesment for choosing database

Source : Connoly & Begg (2015)
 DBMS Selection

Assesment calculation
Source : Connoly & Begg (2015)
APPLICATION DESIGN
 Application Design In
General

In addition to designing how

the required functionality is to
be achieved, we have to
design an appropriate user
interface to the database
system. This interface should
present the required
information in a user-friendly
way.
PROTOTYPING
 Definition of Prototyping

A prototype is a
working model that
does not normally have
all the required
features or provide all
the functionality of the
final system.
 Comparison Between
Two Prototyping

Requirements prototyping

uses a prototype to determine the requirements of a

proposed database system, and once the requirements
are complete, the prototype is discarded.

Evolutionary prototyping

Although evolutionary prototyping is used for the same

purposes, the important difference is that the prototype
is not discarded, but with further development
becomes the working database system
IMPLEMENTATION
 Database
Implementation

The database implementation is achieved using the

DDL of the selected DBMS or a GUI, which provides the
same functionality while hiding the low-level DDL
statements.

The DDL statements are used to create the database

structures and empty database files. Any specified user
views are also implemented at this stage. Security and
integrity controls for the system are also implemented
 References
Connolly, T., & Begg, C. (2015). Database
System A Practical Approach to Design,
Implemetation, and Management 6th Edition.
Pearson
Thank You