Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
9 views17 pages

G5 Pid18 Dbms.

The document outlines the Pin Info project, a database management system designed to provide comprehensive and interactive information about Indian states, addressing issues of scattered, inconsistent, and static data. It includes an Entity-Relationship Diagram, normalization processes to ensure data integrity, and a structured database schema for efficient data management. The project aims to enhance accessibility and engagement for students, researchers, and the general public while supporting future enhancements like AI integration.

Uploaded by

jaat6475
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views17 pages

G5 Pid18 Dbms.

The document outlines the Pin Info project, a database management system designed to provide comprehensive and interactive information about Indian states, addressing issues of scattered, inconsistent, and static data. It includes an Entity-Relationship Diagram, normalization processes to ensure data integrity, and a structured database schema for efficient data management. The project aims to enhance accessibility and engagement for students, researchers, and the general public while supporting future enhancements like AI integration.

Uploaded by

jaat6475
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Database Management System

Semester-III(Batch-2024)

Pin Point Information


Website

Supervised By: Submitted By:


Dr. Shikha Harshit Gatyan , 2410990332
Himanshu Kumar, 2410990348
Paras Vasudeva, 2410991874
Kunal Mahura , 2410990392

Department of Computer Science and Engineering Chitkara


University Institute of Engineering & Technology,
Chitkara University, Punjab
Table of Contents

 1. Introduction ............................................................ 1
 2. E-R Diagram .......................................................... 4
 3. Normalization Used ................................................ 7
 3.1 Database Schema ................................................. 11
 Conclusion ............................................................... 14
 Reference .................................................................. 15
Introduction
1.1 Background and Problem Statement
Background: In an increasingly interconnected world, access to accurate and comprehensive
information about geographical regions is crucial for education, tourism, and research. India,
with its diverse states, rich cultural heritage, and varied demographics, presents a unique
challenge and opportunity for information dissemination. While general information is
available, a centralized, interactive, and easily accessible platform for state-specific data is
often lacking.
The Problem: People seeking information about Indian states face several challenges:
 Scattered Information: Data on population, culture, traditions, festivals, and other
key aspects is often fragmented across various sources, making it time-consuming and
difficult to compile.
 Lack of Interactive Access: Existing information is typically presented in static
formats (e.g., text, tables), without an engaging, interactive interface like a clickable
map.
 Inconsistent Data: The quality and timeliness of information can vary greatly
between sources, leading to confusion and unreliability.
 Limited Scope: Most resources focus on one or two aspects (e.g., tourism,
demographics) but rarely provide a holistic view covering multiple facets of a state.
1.2 Solution Overview – Pin Info
Pin Info is a comprehensive information management platform designed to revolutionize how
users access data about Indian states. It provides a structured, technology-driven ecosystem
that combines geographical interaction with rich, verified information, all within a user-
friendly solution.
Key Features:
 Interactive Map Interface: A dynamic map of India where users can click on any
state to retrieve detailed information.
 Comprehensive State Data: Provides insights into population, culture, traditions,
festivals, and other important facts for each state.
 User-Friendly Display: Information is presented in a clear, organized, and easily
digestible format.
 Data Management for Administrators: A backend system for authorized
administrators to add, update, and maintain state information.

1
1.3 Target Demographics and Impact
Target Audience: Pin Info primarily targets:
 Students (K-12 & Higher Education): For academic projects, research, and general
knowledge about Indian geography and culture.
 Researchers and Academics: To quickly access aggregated data for studies on
Indian states.
 Tourists and Travelers: For planning trips and gaining insights into local culture,
festivals, and traditions of various states.
 General Public: Anyone with an interest in learning more about India's diverse
regions.
Impact: By integrating an interactive map with diverse state-specific information, Pin Info
makes learning about India accessible and engaging for everyone.
 Encourages Exploration: The interactive map fosters curiosity and facilitates easy
exploration of different states.
 Provides Reliable Information: Centralizes verified data, reducing the need to scour
multiple unreliable sources.
 Supports Education and Research: Offers a valuable resource for academic
purposes.
 Promotes Cultural Awareness: Highlights the unique cultural richness, traditions,
and festivals of each state.
1.4 Project Objectives
The development of the Pin Info database system is guided by the following objectives:
Primary Objectives:
 Design a robust and scalable database to manage diverse state information
(population, culture, traditions, festivals, etc.).
 Provide quick and intuitive access to state data through an interactive map interface,
ensuring a smooth user experience.
 Ensure data security and integrity, protecting the accuracy and reliability of the
information.
 Build a flexible database structure that can easily expand with future data categories
or regions.
Secondary Objectives:
 Offer summary insights and overviews for each state.
 Implement efficient data backup and recovery systems for information safety.

2
 Support cross-platform accessibility, enabling use on both web and potentially mobile
applications.
Long-Term Objectives:
 Enable AI-driven recommendations for places of interest or cultural experiences
based on user preferences.
 Develop community features allowing users to contribute information or share their
experiences (with moderation).
 Support integration with external data sources for real-time updates (e.g., weather,
news related to states).
 Scale to manage data for a broader geographical scope (e.g., entire countries,
continents).
1.5 Database Design Significance
The database design is crucial for Pin Info, as it must handle:
 State Profiles: Detailed information for each Indian state.
 Categorized Data: Separated information on population, culture, traditions, and
festivals.
 Administrative Management: Records for authorized users who can update data.
It ensures:
 Data Accuracy: Prevents duplication and maintains consistent information across all
categories for each state.
 Fast Retrieval: Allows for quick loading and display of information when a user
clicks on a state.
 Scalability: Supports a growing volume of detailed information for numerous states.
 Integration Capability: Facilitates future expansion and connection with other
systems.

3
Entity Relationship (ER) Diagram

2.1 About ER Diagram


The Entity-Relationship (ER) Diagram for the Pin Info Platform visually represents the
logical structure of the database. It identifies the main entities (data objects), their attributes
(properties), and the relationships between them. This diagram forms the backbone of the
platform’s data management system, ensuring data integrity and efficient storage.
2.2 Entities and Attributes
 State:
o Attributes: StateID (PK), Name, Population, Capital, Area, Language,
GeographicalDescription, TouristAttractions.
o Represents: Each individual state of India.
 Culture:
o Attributes: CultureID (PK), StateID (FK), Overview, ArtForms, Cuisine,
Clothing.
o Represents: Cultural aspects associated with each state.
 Tradition:
o Attributes: TraditionID (PK), StateID (FK), Name, Description,
HistoricalSignificance.
o Represents: Specific traditions and customs practiced in each state.
 Festival:
o Attributes: FestivalID (PK), StateID (FK), Name, Description, Month,
Significance.
o Represents: Major festivals celebrated in each state.
 Administrator:
o Attributes: AdminID (PK), Username, Password, Email, LastLogin.
o Represents: Authorized users responsible for data management.
2.3 Relationships
1. State has Culture (1:M): One State can have multiple Culture entries (e.g., various art
forms, cuisines).
2. State has Tradition (1:M): One State can have many Tradition entries.
3. State has Festival (1:M): One State can have multiple Festival entries.
4. Administrator manages State Info (1:M): One Administrator can manage information

4
for multiple State entities (through updating Culture, Tradition, and Festival entries
linked to states).
2.4 ER Diagram
This ER model integrates all geographical and cultural entities and their relationships:
 Core Entity: State, which connects to Culture, Tradition, and Festival.
 Information Entities: Culture, Tradition, Festival provide detailed aspects for each
state.
 Management Entity: Administrator handles updates to the state-related information.
The structure ensures flexibility in managing and presenting diverse information about Indian
states while maintaining data integrity and scalability.

5
6
Normalization
Normalization is the process of organizing data in a database to reduce redundancy and improve
data integrity. For the Pin Info platform, normalization ensures that state, cultural, traditional,
and festival information is stored efficiently, without duplication, and with clear relationships.
We will normalize the schema into Third Normal Form (3NF) through the following steps:

3.1 Unnormalized Form (UNF)


Initially, data might be stored in a single, unstructured way with repeating or multivalued
attributes.
Example (UNF):

StateNa Populat Culture_ArtF Culture_Cu- Festiv Festival AdminUser AdminPass


me ion orms isine als Mo nths name word

Makki di
Punjab 30M Bhangra Roti Lohri Jan admin1 pass123

Sarson da Baisakh
Punjab 30M Giddha Saag Apr admin1 pass123

Rajasth Dal Bati Diwali


an 68M Ghoomar Churma Oct/Nov admin2 pass456

3.2 First Normal Form (1NF)


We separate repeating attributes (like multiple art forms, cuisines, festivals) into new tables
and ensure each field holds only atomic values.

State (1NF):
StateID Name Population Capital Area Language GeographicalDescription

101 Punjab 30M Chandigarh ... Punjabi ...

102 Rajasthan 68M Jaipur ... Hindi ...

7
Culture (1NF):
CultureID StateID Type Description

1 101 ArtForm Bhangra

2 101 Cuisine Makki di Roti

3 101 ArtForm Giddha

4 101 Cuisine Sarson da Saag

5 102 ArtForm Ghoomar

6 102 Cuisine Dal Bati

Festival (1NF):
FestivalID StateID Name Month

1 101 Lohri January

2 101 Baisakhi April

3 102 Diwali Oct/Nov

Administrator (1NF):
AdminID Username Password

1 admin1 pass123

2 admin2 pass456

3.3 Second Normal Form (2NF)


To remove partial dependencies, we ensure all non-key attributes are fully dependent on the
primary key. In our 1NF example, most tables already meet 2NF as they have simple primary
keys or compound keys where non-key attributes depend on the full key. If Culture had
StateName as an attribute and CultureID was its primary key, we'd move StateName to the
State table.
For example, ensuring Overview, ArtForms, Cuisine, Clothing in Culture table directly relate
to CultureID (which itself links to StateID).

8
State Table (2NF): This table holds core state information, with no partial dependencies.
StateID (PK) Name Population Capital Area Language GeographicalDescription

101 Punjab 30M Chandigarh ... Punjabi ...

102 Rajasthan 68M Jaipur ... Hindi ...

Culture Table (2NF): This table is also in 2NF, as each attribute depends on the full primary
key (CultureID).
CultureID StateID
(PK) (FK) Overview ArtForms Cuisine Clothing

A vibrant culture Bhangra, Traditional


1 101 with... Giddha Makki di Roti attire...

Dal Bati Colorful


2 102 A rich history... Ghoomar Churma dresses...

Festival Table (2NF): The attributes in this table are fully dependent on the FestivalID.
FestivalID (PK) StateID (FK) Name Description Month Significance

1 101 Lohri Celebrated in winter... January Harvest festival

2 102 Diwali A major festival of lights... Oct/Nov Victory of light...

3.4 Third Normal Form (3NF)


To achieve 3NF, we remove transitive dependencies, meaning no non-key attribute is
dependent on another non-key attribute. In the case of "Pin Info," the 2NF tables already satisfy
the conditions for 3NF because there are no transitive dependencies to be removed.
However, to demonstrate the principle using a similar example from the provided document, if
we had a table that contained both state information and the administrator who manages it, we
would separate the administrator's details into a separate table.

9
Administrator Table (3NF): This table contains details for the administrator who manages
the data for various states

AdminID (PK) Username Password

1 admin1 pass123

2 admin2 pass456

3.5 Final Normalized Schema (3NF)


After normalization, the Pin Info platform includes:
 State(StateID, Name, Population, Capital, Area, Language, GeographicalDescription,
TouristAttractions)
 Culture(CultureID, StateID (FK), Overview, ArtForms, Cuisine, Clothing)
 Tradition(TraditionID, StateID (FK), Name, Description, HistoricalSignificance)
 Festival(FestivalID, StateID (FK), Name, Description, Month, Significance)
 Administrator(AdminID, Username, Password, Email, LastLogin)

Benefits of Normalization for Pin Info:


 Eliminates Redundancy: Avoids storing the same information multiple times (e.g., state
name not repeated in culture records).
 Ensures Atomic and Consistent Data: Each piece of information is stored in its smallest
meaningful unit and remains consistent across the database.
 Strengthens Data Integrity: Prevents anomalies during data insertion, update, or
deletion.
 Improves Storage Efficiency: Reduces the overall size of the database.
 Enables Clear Relationships: Defines unambiguous connections between states, their
cultural aspects, traditions, and festivals

10
Database Schema (SQL DDL)
The database schema has been designed to represent the logical structure of data as derived
from the ER model and refined through normalization. It defines the entities, their attributes,
primary and foreign keys, and the relationships among them using SQL Data Definition
Language (DDL).

4.1 States Table

4.2 Cultures Table

4.3 Traditions Table

11
4.4 Festivals Table

4.5 Administrators Table

4.6 Relationships in Schema


 States – Cultures: A State can have multiple Cultures entries (one-to-many
relationship).
 States – Traditions: A State can have multiple Traditions entries (one-to-many
relationship).

12
 States – Festivals: A State can have multiple Festivals entries (one-to-many
relationship).
 Administrators – States (Indirect): Administrators manage the data (Culture,
Tradition, Festival) associated with States. This is a conceptual link for system
administration rather than a direct foreign key relationship within the main data
tables.
This schema is normalized up to Third Normal Form (3NF), ensuring minimal redundancy
and strong referential integrity across the Pin Info database.

13
Conclusion
In conclusion, the Pin Info project is designed to solve the problem of fragmented and
difficult-to-access information about Indian states by providing a centralized, interactive
platform. The comprehensive report outlines a robust solution, from the initial problem
statement and Software Requirements Specification (SRS) to the detailed database design. By
leveraging a normalized schema, as demonstrated through the 3NF tables, the system ensures
data accuracy, integrity, and scalability. The logical diagrams, including the Context
Diagram, DFDs, and ER Diagram, provide a clear blueprint for development, ensuring a
user-friendly and reliable application. Ultimately, this project aims to make learning about
India's diverse states more accessible and engaging for students, researchers, and the general
public, with a foundation built for future enhancements like AI integration and community
features.

14
References

1. W3Schools. (n.d.). SQL Tutorial. Retrieved from https://www.w3schools.com/sql/


2. GeeksforGeeks. (n.d.). Database Management System (DBMS). Retrieved from
https://www.geeksforgeeks.org/dbms/
3. dbdiagram.io. (n.d.). Database Relationship Diagrams. Retrieved from
https://dbdiagram.io/
4. TablePlus. (n.d.). Modern, Native Database Client. Retrieved from
https://tableplus.com/

15

You might also like