COMPUTER

APPLICATIONS
PRESENTATION

NAME- ANURAG KUMAR

ROLL NO.- 12407
PROGRAM -B.COM HONOURS. (2nd Year)
 WHAT IS DATABASE?

A database is an organized collection of Structured

information, or data typically stored Electronically in a
computer system. A database is usually controlled by a
database Management system (DBMS). Together, the data
and the DBMS, Along with the applications That are
associated with them, are referred to as a database system,
Often shortened to just database.
 DATABASE MANAGEMENT SYSTEM

●A Database Management system is Software

design to store, retrieve, define, and manage
data in a database.
 IMPORTANCE OF DATABASE MANAGEMENT
SYSTEM :-
1. It makes data and management more Efficient and effective.
2. It provides easy access to better management data.
3. By using query languages database allow quick answer to Sudden and
hoc queries.
4. It maintains accuracy and consistency of data among different units of
organization.
5. It provides data security by Preventing unauthoised use of sensitive
data.
6. It reduces data redundancy and improves storage efficiency.
7. By Integrating tables created by several users in a central database, it
makes data sharing throughout the organization.
8. It helps in maintaining centralized control over
data.
9.Database Management System (DBMS) makes
multiple view of the data Possible with the help of
query language.
10. Database Management System (DBMS) is
program independent,Therefore it supports many
programs there is no need to collect Different data
for different program.
DESIGN A DATABASE :-
 DATABASE DESIGN
● Database design Is the design Of the database structure that will be
used to store And manage data rather than the design of the DBMS
Software. Once the database design is completed, DBMS Handles all
the complicated activities Required to design the designer’s View of
the structures of the structures That are usable to the computer.

● A poorly designed database tends to generate Errors that are likely to

Lead to bad decisions. A bad database design eventually can be self
correcting : Organizations using Poorly designed database Often fail
because their managers do not have access to timely (Oreven correct)
information. Thereby dominating a bad database design.
THE DESIGN PROCESS CONSIST OF THE
FOLLOWING STEPS :-

1. Determine the purpose of your database.

2. Find and organize the information required.
3. Devide the information into tables.
4. Turn information items into Columns.
5. Specify primary keys.
6. Set up the table relationships.
7. Refine your design.
8. Apply the normalization rule.
 DATABASE DESIGNING TECHNIQUES :-

1. Normalization :- Tables are organized in such a way that it

decreases the data redundancy and dependency. Larger tables
are divided into smaller tables and are linked together using
relationships.
2. Entity Relationship (ER) Modeling :- It’s a graphical database
design approach that models Entities , their attributes, and
define relationship among these entities to signify real life
objects. An entity is any real world item that’s different or
unique from the surroundings.
3. Relational Data Model :- Once the Blueprints,i.e.,ER-
diagram is ready, it is transformed into inter related tables.
To Create tables, the details are divided into major entities
and then Each entity Becomes a table, relationship between
table are defines to maintain data integrity.
4. Reality :- Process of designing a database starts with a
real world situation known as reality for which the database
is to be desgned. For designing a database all aspects of
the reality must be Clearly understood by the designer.
 RELATIONSHIP BETWEEN TABLES

●Database relationships are associations between tables that are creating using
Join statement to retrieve data. Both tables can have only one record on each
side of the the relationship. Each primary Key value relates to None or only one
record in the related table.
ONE – TO – ONE RELATIONSHIP
TYPES :-

ONE - TO – MANY
RELATIONSHIP

MANY – TO – ONE
RELATIONSHIP
 ONE -TO - ONE RELATIONSHIP :-

● Both tables can have only one record on each side of the relationship.Each
Primary key value Relates to none or only one record in the related table. Most
one – to- one relationships are Forced by Business rules and do not Flow
naturally from the data. Without such a rule, you can typically combine Both
tables without breaking Any normalization rules.
 ONE TO MANY RELATIONSHIP

●The primary key table contains only one record that relates to none,
one, or many records in the related table.
 MANY TO MANY RELATIONSHIP

● Each record in both tables can relate to none, or any number of records in other table. These relationshis
require a third table, called an associate or linking table,because relational system can not directly
acommodate the relationship.