Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 14

MIS

CASE STUDY - 4
UNRAVELING THE JARGON

Presented By:
Virendra Kadam
Anurag Kale
Mitali Kapadia
Nikhil Kawde
Bhakti Khanna
REVIEW
 Assumption : A company ABC corp. has
encountered a problem with its application portfolios
and has consulted a consultant firm for the same.
 The consultant firm replied:
 “In my investigation of your application portfolios,
approximately 93.286% of data embedded in
application program logic which is largely
responsible for the integrity and synchronization
problem currently being encountered“.
SOLUTION SUGGESTED BY THE CONSULTANT

 Recommendation for the design of a master database


each of which would employ relational technology to
reduce the database to third normal form.
 Elimination of all the possibilities of semantic
disintegrity upon querying the database.
THE HIDDEN JARGON

 The consultant applied the concept of


NORMALIZATION to the logical data structures
SOME INTERESTING TECHNICAL JARGONS:
DATA INTEGRITY
 Data is susceptible to errors
 As systems become more complex when these
vulnerabilities grow.
 Data Integrity is the mechanisms for eliminating data
corruption that can happen in the process of applications
reading and writing data to and from storage devices.
 In business terms, it is the assurance that data is consistent,
certified and can be reconciled.
 In database terms data integrity refers to the process of
ensuring that a database remains an accurate.
DATA SYNCHRONIZATION
 Synchronization is basically used to update your data
timely and keep them identical between multiple devices
like PC to PC, Laptop to PC, iPhone to PC or Laptop
and vice versa.
 It is quite effective in managing your mass files.
 Database synchronization is a service that helps you in
delivering up-to-date information between different
networks; no matters where they are located.
 The data synchronization process transfers the updated
information to different network platforms.
DATABASE & DATA STRUCTURES

 Database: It is a system intended to organize, store, and


retrieve large amounts of data easily
 It consists of an organized collection of data for one or
more uses
 Data Structure: It’s a particular way of storing &
organizing data in a computer so that it can be used
efficiently
 Its almost used in every program or s/w system
THE CONCEPT OF NORMALIZATION
 Normalization is the process of efficiently organizing data
in a database.
 There are two goals of the normalization process:
1. Eliminating redundant data (storing the same data in
more than one table)
2. Ensuring to store only related data.
 Both of these are worthy goals as they reduce the amount
of space a database consumes and ensure that data is
logically stored
 Normalization ensures that you get the benefits relational
databases offer.
THE NORMAL FORM (NF)
 The database community has developed a series of
guidelines for ensuring that databases are normalized.
 They are as follows:
1. First Normal Form (1NF)

2. Second Normal Form (2NF)


3. Third Normal Form (3NF)
4. Fourth Normal Form (4NF)

5. Fifth Normal Form (5NF)


 First normal form (1NF) rules :
1. Eliminate duplicative columns from the same table.

2. Create separate tables for each group of related data and


identify each row with a unique column or set of columns
(the primary key).

 Second normal form (2NF) rules: further addresses the


concept of removing duplicative data
1. Meet all the requirements of the first normal form.

2. Remove subsets of data that apply to multiple rows of a


table and place them in separate tables.
3. Create relationships between these new tables and their
predecessors through the use of foreign keys.
 Third normal form (3NF) rule :
1. Meet all the requirements of the second normal form.

2. Remove columns that are not dependent upon the


primary key.
RUNDOWN
 Simply put, normalization is a formal process for
determining which fields belong in which tables in a
relational database.
 Better understanding of your data.
 More flexible database structure.
 Easier to maintain database structure.
 Avoids redundant fields.
 Ensures that distinct tables exist when necessary.
THANK YOU!

You might also like