Mini_Project
Mini_Project
ON
OF
BACHELOR OF ENGINEERING IN
INFORMATION TECHNOLOGY
BY
Dr. H. J. Joshi
AY 2023 - 24
SCTR’s PUNE INSTITUTEOF COMPUTER TECHNOLOGY
DEPARTMENT OF INFORMATION TECHNOLOGY
CERTIFICATE
Submitted by
Is a bonafide work carried out by them under the supervision of Dr. H.J Joshi and it is
approved for the partial fulfilment of the requirement of Project Based Learning for the
award of the Degree of Bachelor of Engineering (Information Technology)
Date:
Place: PUNE
Acknowledgement
The development of this School Management System project would not have been
possible without the support of several individuals and resources. I want to express
my sincere gratitude to Dr. H.J Joshi of the IT Department. His guidance,
support, and encouragement throughout the project were invaluable. I am grateful
for his insights and feedback, which helped me navigate the challenges and ensure
the project's successful completion.
3
ABSTRACT
4
TABLE OF CONTENT
1. Introduction 4
2 Description 5
3 System Requirements 7
4 System Design 13
5 Conclusion 16
5
Chapter - 1
Introduction
One of the key features of the School Management System is its ability to centralize
data related to student information, academic records, attendance, grades, and
financial transactions. By maintaining a unified database, the SMS eliminates
redundancy , reduces errors, and ensures data accuracy and security. This
centralized approach not only simplifies record -keeping but also provides
administrators, teachers, and parents with real-time access to critical information,
enhancing decision-making and operational efficiency.
Academic planning and scheduling are streamlined with the SMS's advanced tools
and features. Administrators can create and manage timetables, allocate resources,
and track course progress seamlessly. This ensures optimal utilization of resources,
minimizes scheduling conflicts, and enables schools to adapt to changing
educational requirements effectively. Teachers benefit from organized schedules,
enabling them to focus more on teaching and student engagement.
6
Chapter - 2
Description
Students:
Registration and Profile Management: Students can register online, providing basic
information for creating their academic profile. They can also update their profiles,
upload documents, and view their academic progress.
Course Enrollment: The SMS allows students to enroll in courses, view course
schedules, and track their academic performance.
Attendance Tracking: Students can view their attendance records, request leave if
necessary, and receive notifications for attendance-related updates.
Teachers:
Grade Recording: The SMS enables teachers to record and update grades, generate
grade reports, and share progress reports with students and parents.
Administrators:
User Account Management: Administrators have the authority to create, edit, and
delete user accounts within the SMS, ensuring proper access control and user
security.
The following sections will provide a detailed explanation of the system design,
including the database structure, user interface design considerations, and the
implemented functionalities. Additionally, the report will explore the testing
procedures conducted to ensure the HMS functions as intended.
Chapter - 3
Specific Requirements
System Requirements:
• Hardware:
o The hardware requirements will depend on the size and anticipated user base of
the healthcare facility. However, a typical system might require a server with a
reliable processor (e.g., Intel Core i5 or equivalent), sufficient RAM (e.g., 16GB or
more), and adequate storage capacity (depending on data volume).
• Software:
o Operating System: A stable and secure operating system like a recent version of
Linux (e.g., Ubuntu Server) or Windows Server is recommended.
o Web Server: An Apache web server or similar software is required to host the
HMS application and deliver web pages to users.
o PHP: The server-side scripting language PHP will be used to develop the HMS
functionalities.
Different user roles should have specific access levels and permissions based on
their responsibilities.
Student Management:
Administrative Tools:
User account management for administrators to create, edit, and delete user
accounts.
Attendance Tracking:
Grade Management:
Recording and updating grades by teachers for assignments, quizzes, exams, etc.
Generation of grade reports and progress reports for students, parents, and
administrators.
Non-Functional Requirements:
• Security:
• Performance:
o The SMS should be responsive and provide a smooth user experience. o The
system should be able to handle multiple concurrent users without significant
performance degradation.
10
Chapter – 4
System Design
1. Presentation Layer:
o This layer comprises the user interface (UI) elements that users interact
with.
o It will be developed using HTML, CSS, and potentially JavaScript for
dynamic elements.
o The UI will cater to different user roles (patient, doctor, administrator)
and provide functionalities specific to each role.
2. Business Logic Layer:
o This layer, also known as the application layer, is responsible for
processing user requests and interactions.
o It will be implemented using PHP for server-side scripting.
o PHP scripts will handle tasks like:
▪ User authentication and authorization
▪ Interacting with the database (MySQL) through queries
▪ Processing data and applying business logic rules
▪ Generating dynamic web pages based on user actions
3. Data Layer:
o This layer stores all the essential data for the HMS application.
o MySQL will be used as the relational database management system.
o The database will be designed with a schema that efficiently stores and
organizes data relevant to patients, doctors, appointments, and
potentially medical history (depending on design).
Data Model:
The HMS will utilize a relational database model stored in MySQL. The database
will consist of several interconnected tables, each containing specific data points.
Here's an example of some core tables:
• Students: This table will store student information such as student ID, name,
demographics (date of birth, address , contact details ), and potentially a
reference field for school history (if implemented).
• Teachers: This table will store teacher information such as teacher ID, name,
specialization, and potentially a schedule reference field.
11
• Courses: This table will store course information such as appointment ID,
date, time, course ID, teacher ID, and potentially additional details like room
no.
User Interface (UI) Design:
The UI will be designed for user-friendliness and cater to the specific needs of each
user role:
• Students: Students will have a login portal to access their profiles. The UI will
allow them to manage their profiles, check attendance , and potentially view
their marks (depending on design).
• Teachers : Teachers will have a login portal to access their schedules , view
student information, and potentially record marks directly within the system.
• Administrators : Administrators will have a comprehensive dashboard for
managing user accounts , generating reports on various aspects (students,
teachers, etc.), and overseeing the overall system operations.
Security Considerations:
Security is paramount for an HMS as it deals with sensitive patient data. The system
will implement robust security measures including:
The following section will delve into the implementation details, including the chosen
technologies and the development process.
12
ER Model
The Entity-Relationship (ER) model visually represents the entities (data objects)
within the HMS and the relationships between them. Here's a breakdown of the
entities and their relationships:
• Entities:
o Parent
o Student
o Admin
o Teachers
13
13
Screenshots:
14
Chapter 6
Conclusion
By centralizing data and offering financial management tools , the SMS fosters
transparency and accountability , building trust among stakeholders . The system's
reporting and analytics features enable informed decision-making, while integration
with external systems enhances functionality and adaptability.
15