AD3391

DATABASE DESIGN AND

MANAGEMENT
 Unit -1

CONCEPTUAL DATA MODELING

Database environment – Database system

development lifecycle –Requirements collection –

Database design - Entity-Relationship model

–Enhanced-ER model – UML class diagrams.

Database Design :
• Database design is the process of creating a
structured plan for a database that outlines how data will be
stored, organized, and accessed.
• It involves designing the database schema, which defines the
structure and relationships between data elements and
determines the most appropriate data types and storage
mechanisms for the data.
• Designed database are easy to maintain, improves data
consistency and are cost effective in terms of disk storage
space.
• The database designer decides how the data elements correlate
and what data must be stored.
The main objectives of database design in DBMS are,

1.To produce logical and

2.physical designs models of the proposed database system.

• The logical model concentrates on the data requirements and

the data to be stored independent of physical considerations.

• The physical data design model involves translating the logical

DB design of the database onto physical media using hardware
resources and software systems such as database management
systems (DBMS).
• Database development life cycle
Requirements analysis :

• 1.Planning – This stages of database design concepts are

concerned with planning of entire Database Development.

• Life Cycle. It takes into consideration the Information Systems

strategy of the organization.

• 2.System definition – This stage defines the scope and

boundaries of the proposed database system.
• There are several key considerations in database design,
including:

1. Data requirements: Identify the types of data that need to be

stored and the relationships between different data elements.

2. Data normalization: Divide the data into smaller, related

tables to eliminate redundancy and improve data integrity.

3. Indexes: Determine which data elements need to be indexed

to improve query performance.

4. Data types: Choose appropriate data types for each data

element to ensure efficient storage and retrieval of data.
Process of Databases Design:
1. Identify the data requirements:
• Determine the types of data that need to be stored and the
relationships between different data elements.
• This might involve gathering requirements from users and
stakeholders and analyzing the data to understand its structure
and relationships.
2.Normalize the data:
• Divide the data into smaller, related tables to eliminate
redundancy and improve data integrity.
This process, known as normalization
• It involves breaking down data into smaller, more atomic units
and establishing relationships between those units.
3.Design the database schema:
• Define the structure and relationships between data elements
using a database schema.

• A database schema is a visual representation of the database

that shows the tables, columns, and relationships between
different data elements.
4.Choose data types and storage mechanisms:
• Determine the most appropriate data types and storage
mechanisms for the data.

• This might involve choosing data types that are efficient for
storing and retrieving data and selecting storage mechanisms
that are optimized for the specific needs of the database.
5.Create indexes:
• Determine which data elements need to be indexed to improve
query performance.

• An index is a data structure that helps the database system

locate data more quickly.
6. Test and refine the design:

• Test the database design to ensure that it meets the needs of

the organization and makes efficient use of resources.

• This might involve running performance tests and making

adjustments to the design as needed.

What is Data Normalization?
• Data normalization is the process of organizing a database in
a way that reduces redundancy and dependency and improves
the integrity and efficiency of the data.
• There are several levels of data normalization, each with its
own set of rules. The most common levels of normalization
are:
• First normal form (1NF)
• Second normal form (2NF)
• Third normal form (3NF)
• First normal form (1NF): In 1NF, data is divided into tables
with unique primary keys, and there are no repeating groups of
data within a table.
• Second normal form (2NF): In 2NF, data is further
normalized by removing partial dependencies on the primary
key.
• This means that non-key attributes are dependent on the entire
primary key, rather than just a part of it.
• Third normal form (3NF): In 3NF, data is further normalized
by removing transitive dependencies.
• This means that non-key attributes are dependent only on the
primary key, and not on other non-key attributes.
Data normalization is a process that helps
to eliminate redundancy and improve the integrity and efficiency
of a database.
• By normalizing the data, organizations can design
more effective and efficient databases that are easier to update
and maintain.
• Types of Database Schemas:
• 1.Conceptual schema: A conceptual schema is a high-level
view of the data that is independent of the physical
implementation of the database.
• It provides an abstract representation of the data that is used to
define the overall structure and relationships between data
elements.
2.Logical schema: A logical schema is a more detailed view of

the data that represents the structure and relationships of the data

as it is actually stored in the database.

• It defines the tables, columns, and relationships between data

elements, and specifies the data types and constraints for each

element.
• 3.Physical schema: A physical schema is a low-level view of

the data that represents how the data is actually stored and

accessed in the database.

• It includes details about the specific storage mechanisms and

file structures that are used to store the data, as well as the

physical layout and organization of the data.

4.User schema: A user schema is a view of the data that is

specific to a particular user or group of users.

• It represents the data that is relevant to the user and the way

that the user wants to access and view the data.

Why Database Design is Important?
• Database design is important because it determines the
efficiency and effectiveness of a database in storing and
retrieving data.
A few specific reasons why database design is important:
• 1. Data integrity: A well-designed database can help ensure
the integrity of the data, which means that the data is accurate,
consistent, and free from errors.
• 2.Query performance:A well-designed database can improve
query performance by making it easier and faster to retrieve data.
• 3. Scalability: A well-designed database can be more scalable,
which means that it can handle increasing amounts of data and
queries without degrading performance.
• 4. Cost savings:A well-designed database can be more cost-
effective, as it can reduce the need for additional hardware and
software resources to support the database.
• Database Maintenance
• 1. Data accuracy : To ensure that the data in the database is
accurate and up to date.
• 2. Data integrity: To maintain the integrity of the data, which
means that the data is consistent and follows the rules
• 3. Performance: To optimize the performance of the
database.
• 4. Data security: To protect the data from unauthorized
access and manipulation.
• There are several key activities that are involved in good
database maintenance:
• 1. Backups: Regular backups of the database are essential to
ensure that the data can be restored in case of a disaster or
other data loss event.
• 2. Indexing: Indexing helps to improve the performance of the
database by creating structures that allow the database to
locate data more quickly.
• 3. Data cleansing: Data cleansing involves identifying and
correcting errors or inconsistencies in the data.
• 4. Optimization: Optimization involves identifying and

addressing performance issues in the database.

• 5. Security: Good database maintenance includes measures to

protect the data from unauthorized access and manipulation.