MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

D.Y. PATIL POLYTECHNIC

MICRO PROJECT
Academic year: 2024-25

Solution for saving Student Records

Subject : Database Management System Subject code : 313302

Course : Computer Engineering Course Code : CO-3-k

 MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION

Certificate
This is to certify that Mr. Vaibhav Vijay Modhave. Roll No: 77 of Third
Semester diploma in Computer Engineering of Institute, D.Y. Patil Polytechnic
(Instt.Code: 0996) has completed the Micro-Project in course Database
Management System (313302) for the academic year 2024- 2025 as
prescribed in the curriculum.

Place: Ambi Enrollment No: 23212350283

Date: ……………………… Exam Seat No: ………

Subject Teacher Head of the Department Principal

 MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION

Certificate
This is to certify that Mr. Pratik More Roll No: 79 of Third
Semester diploma in Computer Engineering of Institute, D.Y. Patil Polytechnic
(Instt.Code: 0996) has completed the Micro-Project in course Database
Management System (313302) for the academic year 2024- 2025 as
prescribed in the curriculum.

Place: Ambi Enrollment No: 23212350360

Date: ……………………… Exam Seat No: ……….

Subject Teacher Head of the Department Principal

 MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION

Certificate
This is to certify that Ms. Apurva More Roll No: 78 of Third
Semester diploma in Computer Engineering of Institute, D.Y. Patil Polytechnic
(Instt.Code: 0996) has completed the Micro-Project in course Database
Management System (313302) for the academic year 2023- 2025 as
prescribed in the curriculum.

Place: Ambi Enrollment No: 23212350

Date: ……………………… Exam Seat No:………….

Subject Teacher Head of the Department Principal

 MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION

Certificate
This is to certify that Mr. Soham Navnath Borhade Roll No: 22 of Third
Semester diploma in Computer Engineering of Institute, D.Y. Patil Polytechnic
(Instt.Code: 0996) has completed the Micro-Project in course Database
Management System (313302) for the academic year 2024- 2025 as
prescribed in the curriculum.

Place: Ambi Enrollment No: 23212350300

Date: ……………………… Exam Seat No:……….

Subject Teacher Head of the Department Principal

 WEEKLY PROGRESS REPORT MICRO PROJECT

Sr.No. Week Activity Performed Sign of Guide Date

1 1st Discussion and finalization of

topic

2 2nd Preparation and submission

of Abstract
3 3rd Literature Review

4 4th Collection of Data

5 5th Collection of Data

6 6th Discussion and outline of

Content

7 7th Formulation of Content

8 8th Editing and proof Reading of

Content
9 9th Compilation of Report And
Presentation
10 10th Seminar

11 11th Viva voce

12 12th Final submission of Micro

Project
Sign of the student Sign of the faculty
pArt A - miCro proJeCt proposAl

Aim/Benefits of micro-project: -
To understand the basics of convert
galvanometer into ammeter of desired range

Proposed Methodology: -
1. Third of all, we have to select a topic and then
take a reference of subject teacher. The teacher
will assign one set of micro projects and said to
the student to create a report on introduction to
basic electricity.
2. We collected information about the topic using
sources such as the internet. Basic Physics
book and then we asked subject teacher about
topic on which we have a micro project and
then we type the required part-A and done
proper page. Set up and submitted to subject
teacher after the setup of part-A. we prepare a
report of our topic. After finishing all the data
in proper arrangement. We selected proper
margin font. Lay out
4A size etc. At least we get the printouts of the
microproject and submitted to teacher.
ACtion plAn: -
Sr. No. Detail of Date Signature Name of
Activity Of Teacher Members

1 Group All team

formation members
and
allocation
of micro
project
tittle
2 Information All team
search and members
required
analysis
3 Actual All team
/assembly members
project
4 Testing of All team
project members
5 Acquire the All team
printout members
and submit
it
6 submission All team
members
resourCes reQuireD: -

Sr. No. Name of Specification Qty. Remark

resources
1 Software Microsoft _
Word
2 Book Database _
Management
System

Date: - H.O.D
(Mrs. Himanshi D. Shelke)
 pArt – B
Contents

1.Introduction To Database Management System.

2.What is Entity Relationship(ER) Diagram?

3.ER Diagram On Student Database Management.

4.Explanation of an ER Diagram for a Student Database
Management System.
5.Conclusion.

1. Introduction to Database Management

Systems (DBMS)

A Database Management System (DBMS) is software that enables

the creation, manipulation, and management of databases. It
provides an interface for users and applications to interact with
data, ensuring efficient storage, retrieval, and organization of
information. With the increasing volume of data generated today,
DBMS plays a crucial role in managing data effectively and
securely.

*Key Points Explaining DBMS

1. Data Abstraction and Independence:

- DBMS provides a way to separate the data from the application
programs, enabling changes to be made to the database without
affecting the applications that use it. This abstraction helps maintain
data integrity and flexibility.

2. Data Storage, Retrieval, and Management:

- A DBMS allows for efficient storage of large amounts of data
and provides tools for quick retrieval. It uses indexes, caching, and
optimized queries to speed up data access.

3. Data Security:
- Security features in DBMS protect sensitive data from
unauthorized access. This includes user authentication, access control,
and encryption, ensuring that only authorized users can view or
modify the data.
4. Data Integrity:
- DBMS enforces rules to maintain data accuracy and consistency,
such as constraints (e.g., primary keys, foreign keys) and validation
checks. This helps in preventing data anomalies and ensuring reliable
information.

5. Multi-user Environment:
- A DBMS supports multiple users accessing the database
simultaneously without conflict. It handles concurrent access,
ensuring data consistency through mechanisms like locking and
transactions.

6. Data Backup and Recovery:

- DBMS provides tools for data backup and recovery, protecting
against data loss due to system failures or other disasters. Regular
backups and transaction logs help in restoring data to its previous
state.

7. Data Models:
- Different data models (e.g., relational, hierarchical,
objectoriented) are supported by various DBMSs, allowing for
flexibility in how data is structured and related.
8. Query Language:
- Most DBMSs use Structured Query Language (SQL) for
database operations. SQL allows users to create, read, update, and
delete data easily, facilitating interaction with the database.

9. Data Administration:
- DBMS provides tools for data administration, including
performance tuning, resource allocation, and user management.
Database administrators (DBAs) can monitor and optimize database
performance.

10. Scalability and Performance:

- Modern DBMSs are designed to scale with increasing data loads
and user demands. They utilize techniques such as sharding and
replication to maintain performance as the database grows.
 2. Introduction to Entity-Relationship (ER) Diagrams

An Entity-Relationship (ER) Diagram is a visual representation of

the data and its relationships within a database. It serves as a
blueprint for designing and modeling the data structure, allowing
database designers and stakeholders to understand how entities
(objects) interact with one another. ER diagrams are fundamental
in the initial stages of database design, providing a clear overview
of data requirements and relationships.

Key Points Explaining ER Diagrams

1. Entities:
- Entities represent real-world objects or concepts that have attributes.
Examples include "Customer," "Order," or "Product." Each entity is
depicted as a rectangle in the ER diagram.

2. Attributes:
- Attributes are the properties or details of an entity. For instance, a
"Customer" entity may have attributes such as CustomerID, Name,
Email, and PhoneNumber. Attributes are represented as ovals
connected to their respective entities.
3. Relationships:
- Relationships define how entities interact with each other. They can
be one-to-one, one-to-many, or many-to-many. Relationships are
depicted as diamonds connecting the related entities.

4. Cardinality:
- Cardinality specifies the number of instances of one entity that can
or must be associated with instances of another entity. It helps in
understanding the nature of the relationship (e.g., a customer can
have multiple orders, but each order is linked to one customer).

5. Primary Keys:
- A primary key is a unique identifier for each entity instance,
ensuring that no two instances are identical. It is typically underlined
in the ER diagram to denote its significance.

6. Foreign Keys:
- Foreign keys are attributes that create a link between two entities,
allowing for data integrity and relationship enforcement. They
represent a reference to the primary key of another entity.
7. Weak Entities:
- Weak entities are those that do not have a primary key of their own
and depend on a "strong" entity for identification. They are
represented by a double rectangle and have a partial key.

8. Generalization and Specialization:

- Generalization is the process of extracting shared characteristics
from multiple entities to form a generalized entity. Specialization,
conversely, involves creating sub-entities from a general entity
based on distinct attributes.

9. Normalization:
- ER diagrams aid in the normalization process, which organizes the
database to reduce redundancy and improve data integrity. By
analyzing relationships, designers can ensure that the database
structure is efficient.

10. Visual Communication:

- ER diagrams serve as an effective communication tool between
technical teams and stakeholders. They provide a clear, visual
representation of the data model, facilitating discussions and
clarifying requirements.
3.ER Diagram On Student Database Managemnet.
3. Explanation of an ER Diagram for a Student Database
Management System

An Entity-Relationship (ER) Diagram for a Student Database

Management System serves as a visual representation of the
various entities involved in managing student data and their
relationships. This diagram helps in understanding the structure
of the database, making it easier to implement and manage
student-related information effectively.

*Key Entities and Their Relationships

1. Entities:
- Student: Represents individual students. Attributes might include
StudentID (Primary Key), Name, Email, DateOfBirth, and
PhoneNumber.
- Course: Represents courses offered by the institution. Attributes
could include CourseID (Primary Key), CourseName, Credits, and
Department.
- Grades: Represents Grades. Attributes might include enrolment
number(Primary Key), grade id, grades.
- Enrollment: Represents the relationship between students and
courses. This is often a weak entity because it depends on both the
Student and Course entities. Attributes may include EnrollmentID
(Primary Key), date and student id(Foreign Key).

2. Relationships:
- Enrolls: This relationship connects the Student and Enrollment
entities. It indicates that a student can enroll in multiple courses, and
each enrollment record is linked to one student. This is a one-to-
many relationship.
- select:- This relationship connects the student and courses entities.
An student can select multiple courses.This is also a one-to-is
associated with a specific course. Again, this is a many-to-on
e relationship.

Diagram Structure

- Student Entity: A rectangle labeled "Student" with attributes

(StudentID, Name, Email, DateOfBirth, PhoneNumber) represented
as ovals connected to the rectangle.
- Course Entity: A rectangle labeled "Course" with attributes
(CourseID, CourseName, Credits, Department) shown similarly.

- Enrollment Entity:
- Relationships:
- The "Enrolls" relationship is represented as a diamond connecting
Student and Enrollment, with cardinality indicators showing that
one student can have multiple enrollments.

- The "Select" relationship connects Student and Course, indicating

one Student can take many courses.
- The "Get" relationship connects Student to Grades, showing that
each Grades is linked to a specific Student.

Example Cardinalities

- Student to Enrollment: One-to-Many (1:N) — A single student can

enroll in multiple courses.
- Student to Grades: One-to-Many (1:N) — A course can have
multiple students enrolled.
- Student to Course: One-to-Many (1:N) — An instructor can teach
multiple courses, but a course is taught by one instructor.
 5.Conclusion

In conclusion, the Student Database Management

Microproject has demonstrated the importance of
efficient data handling in educational settings. Through
the design and implementation of a robust database
system, we have successfully streamlined student
information management, enhancing accessibility and
reliability. This project not only showcased our
technical skills in database design and programming
but also highlighted the value of effective data
organization in facilitating academic administration.
As we move forward, the insights gained from this
microproject will serve as a foundation for future
developments in database management and can be
applied to real-world scenarios within educational
institutions.