DBS Development Lifecycle

&
DB Analysis
 Problems associated with Software development that led
to the software crisis.

There are several major reasons for the failure of

software projects, including:
 lack of a complete requirements specification;
 lack of an appropriate development methodology;
 poor decomposition of design into manageable
components.
As a solution to these problems, a structured approach to the
development of software was proposed and is commonly known as the
Information Systems (IS) lifecycle or the Software Development Lifecycle
(SDLC).

DBS Development Lifecycle 2

 The information systems lifecycle

Information system
The resources that enable the collection, management,
control, and dissemination of data/information throughout
an organization.
An information system not only collects, manages, and
controls data used and generated by an organization but
enables the transformation of the data into information.
The essential component at the heart of an information
system is the database that supports it.

DBS Development Lifecycle 3

 The information systems lifecycle

Typically, the stages of the information systems lifecycle include:

i. Planning
ii. Requirements collection and analysis
iii. Design (including database design)
iv. Prototyping
v. Implementation
vi. Testing
vii. Conversion
viii. Operational maintenance

DBS Development Lifecycle 4

 The information systems lifecycle

As a database is a fundamental component of the

larger organization-wide information system, the
database system development lifecycle is inherently
linked with the information systems lifecycle.

DBS Development Lifecycle 5

 The database system development
lifecycle
In this part, we describe the database system
development lifecycle for relational DBMSs.
An overview of the stages of the database system
development lifecycle (DSDLC) shown in the coming
figure.
It’s important to note that the stages of the database system
development lifecycle are not strictly sequential, but involve some
amount of repetition of previous stages through feedback loops.
For example, problems encountered during database design may
necessitate additional requirements collection and analysis.

DBS Development Lifecycle 6

 Stages of DBS
Development lifecycle
DBS Development Lifecycle 8
DBS Development Lifecycle 9
 Database Planning

 Database planning
Is the management activities that allow the stages of the database
system development lifecycle to be realized as efficiently and
effectively as possible.
 Identifying how the stages can be completed in the most effective &
efficient way.

 During planning phase, four major activities are performed:

 Review and approve the database project request.
 Prioritize the database project request.
 Allocate resources such as money, people and tools.
 Arrange a development team to develop the database project.
DBS Development Lifecycle 10
 Database Planning

 Database planning should also include the development of

standards that govern how data will be collected, how the format
should be specified, what necessary documentation will be
needed.

 Two steps:

1. Mission Statement : Major aims for the Database Project.

2. Mission Objectives : Tasks that DB should support, Driven

through Fact Finding techniques: interviews, questionnaire.

DBS Development Lifecycle 11

 Database Planning
Mission Statement

 Interviewing the business director:

 What is the purpose of your company?

 Why do you need the DB?

 How can the DB solve your problem?

DBS Development Lifecycle 12

 Database Planning
Mission Statement

 Interviewing Burger King Director:

 What is the purpose of your company?
To prepare and sell quick service food to fulfill our guest's needs in a
cleaner environment than our competitors.
 Why do you need the DB?
We have many branches over the world , that offers different cosines,
which drive a data management problem, sharing of information between
branches ( for examples : favorite meals, number of employees) which
help in business decision making.
 How can the DB solve your problem?
No more paperwork, automating daily tasks, corporation between
branches.

DBS Development Lifecycle 13

 Database Planning
Mission Statement

Burger King DB project mission statement

The purpose of BK DB project is to maintain the data that is

used & generated to support the fast food business for our client
and to support sharing information between branches and
in decision making.

Clearer view of the project

DBS Development Lifecycle 14

 Database Planning
Mission Objectives

 Interviewing different staff:

 Job description.

 Daily tasks.

 Data that they deal with.

 Daily reports.

 Type of things they keep track on.

 Customer services.

DBS Development Lifecycle 15

 Database Planning
Mission Objectives

1. To manage (add, delete, update) data on branches.

2. To manage (add, delete, update) data on staff.

3. To manage (add, delete, update) on meals.

4. To manage (add, delete, update) on clients.

5. To perform searches on branches.

6. To perform searches on staff.

7. To perform searches on meals.

8. To perform searches on clients

DBS Development Lifecycle 16

DBS Development Lifecycle 17
 System Definition

 Identify System boundaries at a very high level, e.g.:

 Current users.
 Current application areas.

Example: DreamHome Database System

DBS Development Lifecycle 18
 System Definition

 Identify User views; Define what is required of a database

application from the perspective of:
 A particular job role (such as Manager or Supervisor) or
 Enterprise application area (such as marketing or personnel).

Example: User Views

DBS Development Lifecycle 19
DBS Development Lifecycle 20
 Requirements Collection & Analysis

 Collecting and analyzing information about the part of

organization to be supported by the database system, and using
this information to identify users’ requirements of new system.

 Identifying the required functionality for a database system is

crucial, as systems with inadequate functionality will fail.

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

DBS Development Lifecycle 21

 Requirements Collection & Analysis

 An important activity is to decide how to manage the

requirements for a database system with multiple user
views.

 Three main approaches:

 Centralized approach;

 View integration approach; (we use this approach)

 Combination of both approaches.

DBS Development Lifecycle 22

 Centralized approach

Requirements for each user view are merged into a

single list of requirements for the new database system.
A data model representing all user views is created
during the database design stage.
Generally, this approach is preferred when there is a
significant overlap in requirements for each user view
and the database system is not overly complex.
The centralized approach involves collating the
requirements for different user views into a single list of
requirements as shown in the following figure:

DBS Development Lifecycle 23

 Requirements Collection & Analysis
Centralized Approach

DBS Development Lifecycle 24

 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.
• The view integration approach involves leaving the
requirements for each user view as separate lists of
requirements. We create data models representing each user
view. A data model that represents a single user view is called a
local logical data model. We then merge the local data models
to create a global logical data model representing all user
views of the organization.

DBS Development Lifecycle 25

 Requirements Collection & Analysis View
Integration Approach

DBS Development Lifecycle 26

 Requirements Collection & Analysis

 Critical to capture necessary facts to build the required

database application.

 These facts are captured using fact-finding

techniques.

 When Are Fact-Finding Techniques Used?

 Fact-finding used throughout database application lifecycle.

 Crucial to early stages including database planning, system

definition, and requirements collection and analysis stages.
DBS Development Lifecycle 27
 Requirements Collection & Analysis

 Fact-Finding Techniques:

1. Examining documentation,

2. Interviewing (unstructured/structured & open/closed ended questions) ,

3. Observing organization in operation,

4. Research,

5. Questionnaires (free-format and fixed-format).

DBS Development Lifecycle 28

DBS Development Lifecycle 29
 Database Design

 Creating a design for a database that will support the

enterprise’s mission statement and mission objectives
for the required database system.

 Main aims:
 To represent data and relationships required
by users and applications.
 To provide a data model which supports transactions.
 To specify a design that meets performance requirements.

DBS Development Lifecycle 30

 Database Design

 Three main phases of DB design:

 Conceptual Database Design.
• Create a conceptual data model Independent of any implementation details.
 Logical Database Design. (What)
• At this point you know which type of DBMS you will implementing in - e.g.
relational, object-oriented etc (but not the actual DBMS).
• Test the correctness of the data model through normalization.
 Physical Database Design. (How)
• Derive tables & constraints.
• Identify storage structures and access methods.
• Design security features.

DBS Development Lifecycle 31

DBS Development Lifecycle 32
 DBMS Selection

 Selection of an appropriate DBMS to support the

database system.

 Undertaken at any time prior to logical design.

 Main steps for selecting a DBMS:

 Define Terms of Reference of study;
 Shortlist two or three products;
 Evaluate products;
 Recommend selection and produce report.

DBS Development Lifecycle 33

DBS Development Lifecycle 34
 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.

DBS Development Lifecycle 35

DBS Development Lifecycle 36
 Prototyping

 Building working model of a database system to evaluate

how the final system will look and function.

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

DBS Development Lifecycle 37

DBS Development Lifecycle 38
 Implementation

 Physical realization of the database and application

designs.

 Create database schemas and empty database files. (DDL)

 Create the application programs. (DML and JAVA or C++ ...)

DBS Development Lifecycle 39

DBS Development Lifecycle 40
 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.

DBS Development Lifecycle 41

DBS Development Lifecycle 42
 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.

DBS Development Lifecycle 43

DBS Development Lifecycle 44
 Operational Maintenance

 Process of monitoring and maintaining database system

following installation.

 Operational Maintenance Activities:

 Monitoring performance of system.

 Maintaining and upgrading database application.

 Incorporating new requirements into DB application.

DBS Development Lifecycle 45