Professional Documents
Culture Documents
Micro Project Report: (Your Guide Name)
Micro Project Report: (Your Guide Name)
A STUDY ON
1
MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION, MUMBAI
Certificate
This is to certify that Mr. / Ms.
the Micro Project satisfactorily in Subject Data Base Management System (22319) in
the academic year 2018-2019 as per the MSBTE prescribed curriculum of I Scheme.
Seal of
Institute
2
Index…
1 Introduction 4
2 Types OF Normalization 6
3 Need of Normalization 6
4 Anomalies 7-8
8 Conclusion 15
9 References 16
3
“INTRODUCTION
TO
NORMALIZATION”
“It is a database design technique which is used to organize the tables in such
a manner that it should reduce redundancy and dependence of data.
It divides large tables in small tables.
And links the smaller tables using their relationship.
Normalization is a process in which data attributes within a data model are
organized to increase the cohesion of entity types. In other words, the goal of
data normalization is to reduce and even eliminate data redundancy, an
important consideration for application developers because it is incredibly
difficult to stores objects in a relational database that maintains the same
information in several places.”
4
“TYPES OF NORMALIZATION”
5
NEED OF NORMALIZATION
➢ Data Redundancy:-
Data should not be redundant, which means that the duplication of data should be kept to a
minimum for several reasons. For example, it is unnecessary to store an employee's home
address in more than one table. With duplicate data, unnecessary space is used. Confusion is
always a threat when, for instance, an address for an employee in one table does not match the
address of the same employee in another table. Which table is correct? Do you have
documentation to verify the employee's current address? As if data management were not
difficult enough, redundancy of data could prove to be a disaster.
➢ There are two primary needs of having a highly normalized data schema:-
• Increased consistency:- Information is stored in one place and one place only,
reducing the possibility of inconsistent data.
• Easier object-to-data mapping.:- Highly-normalized data schemas in general are
closer conceptually to object-oriented schemas because the object-oriented goals of
promoting high cohesion and loose coupling between classes results in similar solutions
6
Anomalies in DBMS
There are three types of anomalies that occur when the database is not normalized. These are –
Insertion, update and deletion anomaly. Let’s take an example to understand this.
Update anomaly: In the above table we have two rows for employee Rick as he belongs to two
departments of the company. If we want to update the address of Rick then we have to update the
same in two rows or the data will become inconsistent. If somehow, the correct address gets updated
in one department but not in other then as per the database, Rick would be having two different
addresses, which is not correct and would lead to inconsistent data.
Insert anomaly: Suppose a new employee joins the company, who is under training and currently
not assigned to any department then we would not be able to insert the data into the table if emp_dept
field doesn’t allow nulls.
Delete anomaly: Suppose, if at a point of time the company closes the department D890 then
deleting the rows that are having emp_dept as D890 would also delete the information of employee
Maggie since she is assigned only to this department.
To overcome these anomalies we need to normalize the data. In the next section we will discuss
about normalization.
7
1ST NORMALIZARTION FORM
If a relation contain composite or multi-valued attribute, it violates first normal form or a relation is in first
normal form if it does not contain any composite or multi-valued attribute. A relation is in first normal
form if every attribute in that relation is singled valued attribute.
8
2ND NORMALIZED FORM
A database is in second normal form if it satisfies the following conditions:
9
3RD NORMALIZED FORM
Third normal form (3NF) is a normal form that is used in normalizing a database design to reduce the duplication
of data and ensure referential integrity by ensuring that:-
(1) the entity is in second normal form
(2) all the attributes in a table are determined only by the candidate keys of that relation and not by any non-prime
attributes.
3NF was designed to improve database processing while minimizing storage costs. 3NF data modeling was ideal
for online transaction processing (OLTP) applications with heavy order entry type of needs.[1]
10
Boyce-Cod Normal Form (BCNF)
Boyce-Codd Normal Form (BCNF) is one of the forms of database normalization. A database
table is in BCNF if and only if there are no non-trivial functional dependencies of attributes
on anything other than a superset of a candidate key.
BCNF is also sometimes referred to as 3.5NF, or 3.5 Normal Form.
BCNF was developed by Raymond Boyce and E.F. Codd; the latter is widely considered the
father of relational database design.
BCNF is really an extension of 3rd Normal Form (3NF). For this reason it is frequently
termed 3.5NF. 3NF states that all data in a table must depend only on that table’s primary key,
and not on any other field in the table. At first glance it would seem that BCNF and 3NF are
the same thing. However, in some rare cases it does happen that a 3NF table is not BCNF-
compliant. This may happen in tables with two or more overlapping composite candidate
keys.
11
Conclusion
With the help of data normalization the data can be modified in the database like for
inserting,updating, deleting the data. Vince’s ware house has large no.of items that needs to be
entered intothe database. The data present in warehouse has huge amount of denormalized
data and this data.
12
References
• https://www.google.co.in/search?biw=1366&bih=608&ei=-
y3EW9XwK4z5vAThoaj4AQ&q=conclusion+for+normalization&oq=conclusion+
for+normaliza&gs_l=psy-
ab.3.0.0i22i30k1l4.2095.6646.0.8454.24.24.0.0.0.0.259.2371.6j14j1.21.0....0...1.1.64.p
sy-ab..3.21.2369...0j0i67k1j0i131k1.0.rvmkULPDM4Q
• https://www.coursehero.com/file/p4bakqm/Conclusion-With-the-help-of-data-
normalization-the-data-can-be-modified-in-the/
• https://www.google.co.in/search?biw=1366&bih=608&ei=Dy3EW9D7OcSR9QOW
j7zAAg&q=3NF+DATABASE+&oq=3NF+DATABASE+&gs_l=psy-
ab.3..0l4j0i22i30k1l6.14954.14954.0.15297.1.1.0.0.0.0.98.98.1.1.0....0...1.1.64.psy-
ab..0.1.97....0.e0h2xRZnve8
13
Weekly Work / Progress Report
14
Evaluation Sheet for the Micro Project
Academic Year: 2018-19 Program: Computer Engg. Name of Faculty: Ms. T.Memane
Course: DMS Course Code: 22319 Semester: III
Title of The Project: A DETAILED STUDY OF GUIDELINES REQUIRED FOR PRESENTATION SKILLS IN THE
FORM OF CHART
COs Addressed by the Micro Project:
A. Communicate effectively by avoiding barriers in various formal and informal situations.
B. Communicate skillfully using non-verbal methods of communication.
C. Give presentations by using audio-visual aids.
Major Learning Outcomes achieved by students by doing the project:
(a) Practical Outcomes: 1) Write the importance and guidelines of presentation skills.
(b) Unit Outcomes in Cognitive Domain:
1) Prepare and make seminar presentation.
2) Prepare and Participate in debate speaking ‘for’ or ‘against’ the given topic.
3) Prepare the points for computer presentation for the given topic.
4) Make effective computer presentations.
(c) Outcomes in Affective Domain:
a) Follow safety practices
b) Maitain cleanliness.
c) Demonstrate working as a leader /a team member.
d) Follow ethics.
Comments/Suggestions about team work/leadership/inter-personal communication (if any)
……………………………………………………………………………………………
Marks out of 6 for Marks out of 4for
Roll performance in performance in Total out of
Student Name
No. group activity (D5 oral/presentation 10
Col.8) (D5 Col.9)
7
8
9
15
WEEKLY REPORT
WEEK NO. Work or
activity TEACHER’S SIGN
Performed
INTRODUCTION
1 OF
NORMALIZATION
2 TYPES OF
NORMALIZATION
3 NEED OF
NORMALIZATION
4 ANOMALIES:
5 INSERT
ANOMALIE
DELETE
7 ANOMALIE
8 UPDATE
ANOMALIE
9 ABOUT NF
10 HOSPITAL 1 NF
11 COLLEGE 2 NF
12 MEDICAL 3 NF
16