Database Management

System
Session 8

1
(DBLC) Database Life Cycle
The database life cycle (DBLC) defines the stages involved
for implementing a database, starting with requirements
analysis and ending with monitoring and modification.
Furthermore, the DBLC never ends because database
monitoring, modification, and maintenance are part of the
life cycle, and these activities continue long after a
database has been implemented.

2
(DBLC) Database Life Cycle
The DBLC encompasses the lifetime of the database. The
five stages in the database life cycle are:

1.Requirements analysis
2.Logical design
3.Physical design
4.Implementation
5.Monitoring,
modification,
and maintenance

3
The first three stages (1. Requirements analysis 2. Logical
Design 3. Physical Design) are database-design stages

I. Requirements analysis
Requirements Analysis is the first and most important stage
in the Database Life Cycle.
It is the most labor-intensive for the database designer.
This stage involves assessing the informational needs of an
organization so that a database can be designed to meet
those needs.

4
II. Logical design
During the first part of Logical Design, a conceptual
model is created based on the needs assessment
performed in stage one. A conceptual model is typically
an entity-relationship (ER) diagram that shows the tables,
fields, and primary keys of the database, and how tables
are related (linked) to one another.
The tables sketched in the ER diagram are then normalized.
The normalization process resolves any problems
associated with the database design, so that data can be
accessed quickly and efficiently.

5
conceptual model: A description of the structure of a database.
entity-relationship (ER) diagram: A diagram used during the design phase
of database development to illustrate the organization of and
relationships between data during database design.
normalization: The process of applying increasingly stringent rules to a
relational database to correct any problems associated with poor design.

6
III. Physical Design

The Physical Design stage has only one purpose: to

maximize database efficiency.
This means finding ways to speed up the performance of
the RDBMS. Manipulating certain database design elements
can speed up the two slowest operations in an RDBMS:
retrieving data from and writing data to a database.

7
Description of the Stages in the DBLC
The five stages of the Database Life Cycle associated with
each task:
The stages and the principal task associated with each are
listed below.
1.Requirements analysis: identify business objects
2.Logical design: create a conceptual model
3.Physical design: tweak database for performance
4.Implementation: create SQL tables
5.Monitoring, modification, maintenance: update records

8
Modern Database Life Cycle
(DBLC) contains six phases:
1.database initial study,
2.database design,
3.implementation and loading,
4.testing and evaluation,
5.operation, and
6.maintenance and evolution.

9
Database Initial Study

1.In the Database initial study, the designer must examine

the current system's operation within the company and
determine how and why the current system fails. The
overall purpose of the database initial study is to:
Analyze the company situation.
2.Define problems and constraints.
3.Define objectives.
4.Define scope and boundaries.

10
a. 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.

11
b. 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.

12
c. Define Objectives:
1.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 proposed system's initial objective?
2.Will the system interface with other existing or future
systems in the company?
3.Will the system share the data with other systems or
users?

13
d. Define Scope and Boundaries:
The designer must recognize the existence of two sets of limits:
1. scope
2.and 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.

14
Post Design Stages in Database Life Cycle
The "Post Design Stages" of the database life cycle refer to
the stages that occur after the database has been designed
and implemented. These stages are focused on maintaining
and improving the database over time. The post design
stages typically include:
1. Testing and Validation: Once the database has been
designed and implemented, it is important to test and
validate the database to ensure that it functions as intended.
This involves running test cases and validating the data and
functionality of the database.

15
1.Implementation and Deployment: After the database has been
tested and validated, it can be deployed in a production
environment. This involves setting up the necessary
infrastructure, such as servers and networks, and migrating the
data from the old system to the new system.
2.Maintenance: Once the database is deployed, it requires ongoing
maintenance to ensure that it continues to function properly.
This includes performing regular backups, monitoring the system
for errors or performance issues, and applying updates and
patches as needed.
3.Performance Tuning: Over time, the database may experience
performance issues due to increased data volume or changes in
usage patterns. Performance tuning involves identifying and
resolving performance issues to ensure that the database
remains responsive and efficient. (Review list of indexing, add
indexing, archiving, delete unused data)

16
5. Security and Access Control: Security and access control are
important considerations for any database system. Post-design stages
involve implementing and maintaining appropriate security measures,
such as access controls and encryption, to protect the data from
unauthorized access and breaches.
6. Retirement and Archiving: At some point, the database may become
obsolete or no longer needed. Retirement and archiving involve safely
removing the database from production systems and preserving the
data for archival or historical purposes.

17
The post design stages of the database life cycle are critical
for ensuring that the database continues to meet the needs
of the organization over time. By following best practices
for testing, deployment, maintenance, performance tuning,
security, and retirement, organizations can ensure that
their databases remain secure, reliable, and effective.

18
The final two stages in the DBLC
1. Implementation
2. Monitoring, Modification, and Maintenance,

occur after the database design is complete. The following

paragraphs discuss these stages in detail.

19
Fourth Stage - Implementation

During the implementation stage of the DBLC, the tables

developed in the ER diagram (and subsequently
normalized) are converted into SQL statements. These SQL
statements are then executed in the RDBMS to create a
database. By this stage in the database life cycle,
the System Administrator has installed and configured an
RDBMS.

20
 System Administrator:
• In this case the System administrator is the person
responsible for administering a multi-user computer
system. His duties range from setting up and configuring
system components (i.e. an RDBMS) to performing
maintenance procedures (for example, database backups)
on the system.

21
Fifth Stage: Monitoring, Modification, and
Maintenance
A successfully implemented database must be
carefully monitored to ensure that it is functioning properly
and that it is secure from unauthorized access. The RDBMS
usually provides utilities to help monitor database
functionality and security.
Database modification involves adding and deleting
records, importing data from other systems (as needed),
and creating additional tables, user views, and other
objects and tools. As an organization grows,
its information system must grow to remain useful.

22
 Well-designed Database
A well-designed database enhances the organization's ability
to expand its information system and has several key
characteristics that contribute to its effectiveness and
efficiency. These characteristics include:
1. Data Integrity: A well-designed database ensures that the
data stored within it is accurate, consistent, and reliable. This
is achieved through the use of data validation rules,
referential integrity constraints, and other mechanisms to
ensure that data is entered correctly and remains consistent
over time.

23
1.Scalability: A well-designed database is able to handle
increasing amounts of data and users without compromising its
performance or availability. This is achieved through careful
consideration of database architecture and optimization
techniques, such as indexing, partitioning, and clustering.
2.Performance: A well-designed database is optimized for
performance, ensuring that queries and transactions are
executed quickly and efficiently. This is achieved through the
use of proper indexing, normalization, and query optimization
techniques.
3.Security: A well-designed database is secure, protecting data
from unauthorized access, modification, or deletion. This is
achieved through the use of access control mechanisms,
encryption, and other security features.
24
5. Flexibility: A well-designed database is flexible, allowing
for easy modification and adaptation to changing business
requirements. This is achieved through the use of modular
database design, which allows for the addition or removal of
tables, fields, or relationships as needed.
6. Usability: A well-designed database is easy to use, with a
clear and intuitive interface that allows users to quickly and
efficiently access the data they need. This is achieved
through the use of user-friendly interfaces, logical
organization of data, and appropriate use of data
visualization and reporting tools.

25
• A well-designed database is characterized by its ability to
effectively and efficiently store, retrieve, and manipulate
data, while ensuring the integrity, scalability, performance,
security, flexibility, and usability of the system.
•
Ongoing maintenance procedures include periodic
database backups, for example, an important and ongoing
maintenance procedure. Again, the RDBMS provides
utilities to assist in this task.

26