DataBase Life

Cycle
(DBLC)
 The Database Life Cycle (DBLC)
Intoduction
The Database Life Cycle
(DBLC) contains six phases,
as shown in the following
Figure: database initial
study, database design,
implementation and loading,
testing and evaluation,
operation, and maintenance
and evolution.

 Database Initial Study:

In the Database initial study, the • Analyze the company
designer must examine the situation.
current system's operation •Define problems and
within the company and constraints.
determine how and why the •Define objectives.
current system fails. The overall •Define scope and
purpose of the database initial boundaries.
study is to :

 Database Initial Study:

1. Analyze the Company Situation:

The company situation describes the general conditions in which a

company operates, its organizational structure, and its mission. To
analyze the company situation, the database designer must discover
what the company's operational components are, how they function,
and how they interact.

 Database Initial Study:

2. Define Problems and Constraints:

The designer has both formal and informal sources of information.

The process of defining problems might initially appear to be

unstructured. Company end users are often unable to describe
precisely the larger scope of company operations or to identify
the real problems encountered during company operations.

 Database Initial Study:

c. Define Objectives:
A proposed database system must be designed to help solve at
least the major problems identified during the problem discovery

process. In any case, the database designer must begin to address

the following questions:

What is the Will the system interface with Will the system share
proposed system's other existing or future the data with other
initial objective? systems in the company? systems or users?
 Database Initial Study:
d. Define Scope and Boundaries:
The designer must recognize the existence of two sets of limits:
Scope Boundaries
The system's scope defines the extent of the design according to
operational requirements. Will the database design encompass the
entire organization, one or more departments within the organization,
or one or more functions of a single department?
Knowing the scope helps in defining the required data structures, the
type and number of entities, the physical size of the database, and so
on. The proposed system is also subject to limits known as
boundaries, which are external to the system.
Boundaries are also imposed by existing hardware and software.
 Data base design:

The DB design phase focuses on the design of DB model supporting

companies operations & its objectives. This is a critical & important
DBLC step. Since it should mean final product to meet both user &
system requirements. One has to concentrate on data characteristics
required to built in datamodel. Thus designing data is an integral part
of the DBLC’s second phase.
This phase is divided into 4 stages:
Conceptual design
Entity relationship modeling & normalization
Data model verification
Distributed database design
 Conceptual design
In conceptual design stage, the database designer analyze the company
situation define the actual problems, according to the objectives of the
organization company scope & boundaries of the system.
Entity relationship modeling & normalization
The data modeling is used to detect the problem regiment, data abstraction, data types &
real word objectives. The process of defining the business rules & developing the
conceptual data model by using ER diagram to make a stable data model. The purpose of
ER diagrams is :
a) Identify the main entities (b) Indentify, analyze and pre-define the problems
(c) Define the relationship among the entities
(d) Define the attributes & set primary key, foreign key, constrains for each of the
entities
(e) Apply normalization process for the entities & finally complete the initial ER diagrams
 Data model verification
The verification requires the data model with a series of tasks again:
Each end user data use & transfer
Access part to define the data, store data & reach data for manipulation
Checking constraints for validation of data and security of data
When the data in the database is distributed across the system, the database designer
must plane & develop it as a distributed and hence provide allocation of peripheral resources
& strategies. The verification process is selecting the central entity. The central entity defined
in terms of its participation in most of the data models relationship & the system operations
with in the central entity frame work;
1)Ensure the modules, cohesively 2)Cohesively describes the strength of the relationship
of the relationship among the module entities.
3)Analyse each module relationship with other modules to address module coupling
4)Module coupling describe the extent to which modules are independent of one another
5)Processes – must be according to their frequency – daily, weekly, monthly, yearly,
operational type – insert, update, delete, quarries & reports
 Distributed database design
DBMS software selection:
The selection of DBMS software is an important & critical step to the systems
smooth operation. The database designer must describe.
1)Cost –includes purchase price along with maintenance, operational, license,
installation, training & conversion cost
2)DBMS features & its tools – The DBMS software includes a verify of tools that
facilitates application development task such as QBE, screen designing data dictionary,
report generators, application generators etc.
The database administrator facilitates performance security, concurrency controls,
transaction procession.
a) Portability – DBMS can be portable across various platforms system & languages
b)DBMS hardware requirements – it includes RAM, processes, disk space etc.
 Distributed database design
Local design: DBMS software selection:
It translates the conceptual design in to the internal data model for selector DBMS
such as DBI, SQL server, My SQL, Oracle & MS-office. The logical design is software
dependent. The logical design for RDBMS includes specification of tables, index, views,
transaction, access authority etc.
Physical design:
It is the process of selecting data storage and data characteristics of the
data base. The storage characteristics are a function of the types of devices,
hardware data access methods supported by a system. Therefore, it is a technical
jobs & effects not only location of data in the storage devices but also the
performances of the system.The physical design is more complex when data are
distributed at different locations because the performances is effected by their
communication media through put.
 Implementation and Loading
The output of the database design phase is a series of instructions detailing the
creation of tables, attributes, domains, views, indexes, security constraints, and
storage and performance guidelines. In this phase, you actually implement all
these design specifications.

a. Install the DBMS:

This step is required only when a new dedicated instance of the DBMS is
necessary for the system. The DBMS may be installed on a new server or it may
be installed on existing servers. One current trend is called virtualization.
Virtualization is a technique that creates logical representations of computing
resources that are independent of the underlying physical computing resources.
 Implementation and Loading
b. Create the Database(s):
In most modern relational DBMSs a new database implementation requires the
creation of special storage-related constructs to house the end-user tables. The
constructs usually include the storage group (or file groups), the table spaces, and
the tables.

c. Load or Convert the Data:

After the database has been created, the data must be loaded into the
database tables. Typically, the data will have to be migrated from the prior
version of the system. Often, data to be included in the system must be
aggregated from multiple sources. Data may have to be imported from other
relational databases, non relational databases, flat files, legacy systems, or even
manual paper-and-pencil systems