MAHARASHTRA STATE BOARD TECHNICAL

EDUCATION, MUMBAI.
Designing a Normalized Database for a College
ON
Guided By
PROF: Firoz Pathan Khan

Submitted by
Md Farmaan Ali
Ansari Nauman Anis Ahmed
Wakad Alam
Hammad Yamin Khan

Department of Computer Engineering

JAMIA POLYTECHNIC
AKKALKUWA DIST.NANDURBAR

Akkalkuwa(425415)
 ANNEXURE 2

EVALUATION SHEET FOR THE MICROPROJECT

ACADEMIC YEAR: 2023-24 NAME OF FACULTY: Firoz Pathan Khan

COURSE: DBMS

SEMESTER:3rd DEPARTMENT: COMPUTER ENGG

TITTLE OF PROJECT:

CO’S ADDRESSED BY THE MICROPROJECT:

Roll Student Name Marks Out Marks Out Of Total Out Of

No. Of 6 4 10

(Name & Signature of faculty)

 Jamia Polytechnic Akkalkuwa

CERTIFICATE
This Is To Certify That Mr./Ms. Of
Branch
Enrolment No.
Has Completed His
Micro Project Enitled
Of Subject as per
Requirment Of( Semester)
MSBTE I Scheme Curriculum Under The
Guidence Of Satisfactorily
During Academic Year 202324.

Micro project Guide Head of Dept Principal

Designing a Normalized Database for a College
Table of Contents
1. Introduction
Background
Objectives

2. Database Design for a College

Understanding the College Environment
Information to be Managed
Data Normalization
Entity-Relationship Diagram

3. Database Schema
Entities and Their Attributes
Relationships
Primary and Foreign Keys

4. Data Normalization
First Normal Form (1NF)
Second Normal Form (2NF)
Third Normal Form (3NF)
Boyce-Codd Normal Form (BCNF)
5. Creating Database Tables
SQL Statements
Table Creation and Data Insertion

6. Queries and Reports

Sample SQL Queries
Generating Student Reports
Faculty Schedules

7. Database Security and Integrity

User Access Control
Data Validation and Constraints

8. Optimizing Database Performance

Indexing
Query Optimization
Data Backup and Recovery

9. Integration with College Systems

Connecting with Attendance Systems
Library Management Integration
10. Expanding the Database for Future Needs
Adding New Functionalities
Incorporating Online Learning Systems

11. Conclusion
Summary of Achievements
Benefits of a Normalized College Database
Future Prospects and Continuous Improvement

12. References

13. Appendices
SQL Queries for Database Creation
Sample Student and Faculty Records
ER Diagram and Schema Diagram

1. Introduction
In today's digital age, educational institutions, like colleges, generate
and handle vast amounts of data. This data includes student records,
faculty information, course details, financial transactions, and much
more. To efficiently manage this information, designing a normalized
database is paramount. This micro project focuses on the design and
implementation of a normalized database for a college, covering
database schema, data normalization, SQL queries, and integrating it
with various college systems.
The ever-evolving landscape of higher education, efficient data
management is paramount. Educational institutions, particularly
colleges and universities, handle a vast array of data daily, including
student information, course details, faculty records, and
administrative data. To ensure the smooth operation of various
departments and the delivery of quality education, an organized and
optimized database system is imperative.
Background
Colleges serve as hubs of information, managing extensive databases
that encompass student records, course catalogs, faculty information,
financial records, and more. The significance of an organized, secure,
and efficient database cannot be overstated. This system not only
eases administrative processes but also enhances the overall
educational experience for students.
As higher education institutions expand and evolve, the need for a
comprehensive database becomes increasingly pronounced. Data
must be accurately stored, easily retrievable, and secure against data
breaches. This is where the concept of a normalized database comes
into play. Normalization is a systematic approach to data organization
that minimizes data redundancy and ensures data integrity. It enables
efficient data retrieval, simplifies updates, and provides a robust
foundation for relational databases.

2. Database Design for a College

Understanding the College Environment:
Designing a database for a college requires a profound understanding
of the educational ecosystem. The database should cater to student
enrollment, faculty management, course registration, fee collection,
academic records, and many other aspects.

Information to be Managed:
The information that the database manages encompasses student
details (e.g., name, roll number, contact information), faculty records
(e.g., name, designation), course information (e.g., course code, title,
credits), financial transactions (e.g., fees, scholarships), and
attendance records, among others.

Data Normalization:
A well-designed database should follow the principles of data
normalization to minimize data redundancy and ensure data
integrity. Data normalization involves organizing data into structured
tables with minimal duplication.

Entity-Relationship Diagram:
The Entity-Relationship Diagram (ERD) provides a visual
representation of the database's structure, including entities (e.g.,
students, courses), attributes (e.g., name, roll number), and the
relationships between them (e.g., a student enrolls in courses).

3. Database Schema

Entities and Their Attributes:

The database schema defines the entities (tables) and their attributes
(columns). For example, the "Students" table includes attributes such
as "StudentID," "FirstName," "LastName," and "DateOfBirth."

Relationships:
Relationships between tables are established through keys. For
instance, the "Courses" table might relate to the "Students" table
through a "StudentID" foreign key.

Primary and Foreign Keys:

To maintain data integrity, primary keys uniquely identify each
record, while foreign keys establish relationships with other tables.

4. Data Normalization

Data normalization involves organizing data into different forms, each

with specific rules, to ensure minimal redundancy and efficient data
manipulation.

First Normal Form (1NF):

In 1NF, tables have distinct rows, and each column contains only
atomic values.

Second Normal Form (2NF):

2NF ensures that there is no partial dependency on the primary key.
All non-key attributes should depend on the entire primary key.
Third Normal Form (3NF):
3NF further eliminates transitive dependencies, ensuring that non-
key attributes depend only on the primary key.

Boyce-Codd Normal Form (BCNF):

BCNF is the highest level of normalization, dealing with situations
where there can be multiple candidate keys in a table.

5. Creating Database Tables

Creating a complete program for designing a normalized database for
a college is beyond the scope of a single response. However, I can
provide you with an outline of the steps and an example SQL code
snippet for creating a "Students" table to get you started.
Outline of Steps for Building a College Database:
Define the requirements and objectives of the college database.
Identify the entities, attributes, and relationships.
Design the Entity-Relationship Diagram (ERD).
Normalize the data to 3NF or BCNF.
Create the database schema and tables using SQL.
Implement database constraints, such as primary keys and foreign
keys.
Develop SQL queries for data retrieval and manipulation.
Implement security measures.
Optimize database performance.
Integrate with other college systems.
Here's an example SQL code snippet for creating a "Students" table:
sqlCopy code
CREATE TABLE Students ( StudentID INT PRIMARY KEY, FirstName
VARCHAR(50) NOT NULL, LastName VARCHAR(50) NOT NULL,
DateOfBirth DATE, Email VARCHAR(100), Phone VARCHAR(15),
Address VARCHAR(255) );
In this example, we create a "Students" table with the following
attributes:
StudentID: A unique identifier for each student.
FirstName and LastName: Student's first and last names.
DateOfBirth: Student's date of birth.
Email: Student's email address (optional).
Phone: Student's contact number (optional).
Address: Student's residential address (optional).
You would repeat similar steps to create tables for other entities,
such as "Courses," "Faculty," and "Enrollments," and establish
relationships between them using foreign keys. Additionally, you
would develop SQL queries to insert, update, and retrieve data.
Keep in mind that the actual database design and implementation
can be quite complex, and you may need to use a database
management system like MySQL, PostgreSQL, or Oracle to execute
these SQL commands.
If you have specific questions or need further assistance with a
particular aspect of the database design or SQL queries, please let
me know, and I'd be happy to provide more guidance.
```sql
CREATE TABLE Students (
StudentID INT PRIMARY KEY,
FirstName VARCHAR(50),
LastName VARCHAR(50),
DateOfBirth DATE
);
```
6. Queries and Reports
SQL queries are used to retrieve and manipulate data within the
database. Sample queries include selecting all students or courses.
Reports can be generated for student profiles or faculty schedules.

7. Database Security and Integrity

Security measures, such as user access control, ensure that only

authorized individuals can access and modify the database. Data
validation and constraints maintain data accuracy.

8. Optimizing Database Performance

To enhance performance, indexing is employed, and queries are

optimized. Data backup and recovery mechanisms are put in place to
prevent data loss.
9. Integration with College Systems

The college database can be integrated with attendance systems,

ensuring real-time attendance tracking. It can also be linked with the
library management system to manage book records and checkouts
efficiently.

10. Expanding the Database for Future Needs

The database can be expanded by adding new functionalities, such as

integrating online learning systems, enabling remote learning, and
monitoring student progress.

11. Conclusion

In conclusion, designing a normalized database for a college is crucial

for efficient data management and streamlined processes. It ensures
data accuracy, minimizes redundancy, and provides a robust
foundation for integrating with various college systems. The benefits
include improved record-keeping, enhanced security, and future
scalability. As educational institutions continue to rely on digital
solutions, a well-designed college database is indispensable. Future
prospects involve continuous improvements, expanding
functionalities, and adapting to the evolving educational landscape.