Anisha Final Report

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 41

A Web Based

“School Information System”


FOR
Deep English Secondary school Dhankuta 6, Bichbazzar.

BY
Priyash shrestha
Exam Roll No:12793/20
T.U. Registration No: 7-2-0623-0056-2020
Sunsari Technical College

A Summer Project Report Submitted to


Faculty of Management, Tribhuvan University
in partial fulfillment of the requirements for the degree of
Bachelor of Information Management

Dharan, Sunsari
February, 2024
ACKNOWLEDGEMENT

This report has been prepared for partial fulfillment of the requirements for the degree of Bachelor
of Information Management, prescribed by Faculty of Management, Tribhuvan University. This is
an individual project assigned to us during our academic study in BIM Sixth semester, I should
remain thankful to many people for the successful completion of this summer project.

I would like to express sincere gratitude to my supervisor, Mr. Mahesh shah, for providing
necessary guidelines for completion of this report. I am thankful to him for his continuous
reinforcement and motivation for completing the project successfully. I thank him for his regular
feedback and suggestions to improve the report further.

We are very thankful to the respected Associate Lecturer, Mr. Amar Rai, for helping and
encouraging us in every aspect of my academic study. Also, I would like to thank all the
respondents who filled in the questionnaire and helped me with the continuation of the project.

Finally. I would like to thank my friends for uplifting my spirit to complete the report in time.

i
PREFACE

In today's rapidly evolving technological landscape, educational institutions are increasingly


relying on digital platforms to streamline communication, and foster a collaborative learning
environment. school website plays a vital role in connecting students, parents, and faculty.

As my project is about the school information system. Its a simple school website prepared for the
friendly and helpful guide for everyone connected to the school. It's like the online home for the
school, where students, teachers, parents, and even visitors can easily find important information
and stay updated.

ii
ABSTRACT

A school information website is a digital platform designed to provide comprehensive information about
a specific educational institution or school. These websites serve as a virtual hub where students, parents,
teachers, and other stakeholders can access relevant details and resources related to the school's academic
programs, policies, events, and other important information. The primary goal of a school information
website is to enhance communication and transparency between the school and its community members.

Key features of a school information website may include:

1. About Us Section: Provides an overview of the school's history, mission, vision, and values.
2. Admission Information: Details about the admission process, application forms, eligibility
criteria, and any other relevant information for prospective students.
3. Academic Programs: Information about the curriculum, courses offered, and any specialized
programs or extracurricular activities available.
4. Calendar of Events: A schedule of upcoming events, including academic dates, sports events,
cultural programs, and parent-teacher meetings.
5. Faculty and Staff Directory: Profiles of teachers and staff members, including their
qualifications and contact information.
6. Student Resources: Resources for students, such as class schedules, exam timetables, study
materials, and links to online learning platforms.
7. Parental Resources: Information and resources for parents, including newsletters,
communication channels with teachers, and guidelines for involvement in their child's education.
8. School Policies: Details about school policies, rules, and regulations governing student conduct,
attendance, and other important aspects.
9. Contact Information: Clear contact details, including phone numbers, email addresses, and
physical addresses for various school departments and administrative offices.
10. News and Announcements: Regular updates on school news, achievements, and important
announcements.
11. Gallery: A section featuring photos and videos showcasing school events, activities, and
achievements.

iii
STUDENT DECLARATION

This is to certify that I have completed the Summer Project entitled” School Information System”
under the guidance of “(Mr. Amar Rai)” in partial fulfillment of the requirements for the degree of
Bachelor of Information Management (BIM) at Faculty of Management, Tribhuvan University.
This is my original work and I have not submitted it earlier elsewhere.

Date:

Signature Name: Priyash Shrestha

iv
CERTIFICATE FROM THE SUPERVISOR

This is to certify that the summer project entitled “School Information System” is an academic
work done by “Mr. Priyash Shrestha” submitted in the partial fulfillment of the requirements for
the degree of Bachelor of Information Management at Faculty of Management, Tribhuvan
University under my guidance and supervision. To the best of my knowledge, the information
presented by him/her in the summer project report has not been submitted earlier.

Project Supervisor External Supervisor

Name: Mr. Amar Rai Date:

Date:

v
EXECUTIVE SUMMERY

This Summer Projects reports focuses on the development of a “Doctor Appointment


System” for Manjushree Polyclinic & Diagnostic Center Pvt. Ltd, Dharan-9, Sunsari. The
objective of this project is to provide easy access to doctors in the area, to provide easy access
to doctors in the area, to allow better time management for doctors. The report provides an
overview of the organization, its vision, and objectives. It also describes the methodology used
to develop the doctor appointment system, including the projects framework, data and
information sources, and tools and technologies utilized. Overall, the projects have been
successful in achieving their objectives, providing an innovative solution to the clinic doctors
and patients.

The project report outlines the tasks and activities carried out by the team to achieve the
primary objective of gathering information about the use of technology in a particular
organization. organization. The team conducted extensive research to understand and analyze
its technology infrastructure, reviewed internal documentation, and compared the
organization's technology practices to industry best practices and benchmarks. The report also
identifies the organization's challenges, such as the absence of a digital system for doctor
appointment system, which negatively impacts patients’ experience and results not getting
appointment of doctors. To solve this problem, the team proposes the implementation of a web-
based doctor appointment system, and a requirement analysis is carried out to identify the
functional and non-functional requirements of the system. system. The chapter also covers
system design, which involves defining the architecture, components, modules, interfaces, and
data for the system to satisfy specified requirements. Use case, sequence, and activity diagrams
are used to visualize the interactions and workflow of the system.

vi
TABLE OF CONTENTS

ACKNOWLEDGEMENT.................................................................................................................i

PREFACE..........................................................................................................................................ii

ABSTRACT.......................................................................................................................................iii

STUDENT DECLARATION...........................................................................................................iv

EXECUTIVE SUMMERY...............................................................................................................vi

CHAPTER ONE................................................................................................................................1

INTRODUCTION.............................................................................................................................1

1.1 Background............................................................................................................................1

1.2 Introduction of the organization................................................................................................1

1.2.2 Mission.................................................................................................................................1
1.4 Methodology.................................................................................................................................2

1.4.1 Project Framework...............................................................................................................2


1.4.2 Data and Information collection...........................................................................................2
1.4.3 Technique of Project Report Analysis...................................................................................3
TASK AND ACTIVITIES PERFORMED.....................................................................................4

2.1 Analysis of Task and Activities..................................................................................................4

2.2 Analysis of Problem.....................................................................................................................4

2.2.1 Analysis of Possible Solutions...............................................................................................4


2.3 Feasibility Analysis......................................................................................................................5

2.4 Requirement Analysis.................................................................................................................5

2.4.1 Functional Requirement.......................................................................................................5


2.4.1.4 Use case Diagram..........................................................................................................6
2.4.2 Non-Functional Requirements..............................................................................................6
2.5 System Design..............................................................................................................................7

2.5.1 Sequence Diagram................................................................................................................7


2.5.2 E-R Diagram..........................................................................................................................8
2.5.3 Activity Diagram...................................................................................................................9

vii
2.5.4 Class Diagram.....................................................................................................................10
2.6 System Implementation.............................................................................................................11

2.6.1 Module Description............................................................................................................11


2.6.2 System Features.................................................................................................................15
2.6.4 System Testing....................................................................................................................16
2.6.5 Validation Testing...............................................................................................................19
2.6.6 Findings..............................................................................................................................19
CHAPTER- THREE.......................................................................................................................20

DISCUSSION AND CONCLUSION.............................................................................................20

2.8 Discussion...................................................................................................................................20

2.9 Conclusion..................................................................................................................................20

3.0 Recommendations......................................................................................................................20

REFERENCES................................................................................................................................22

APPENDICES..................................................................................................................................23

viii
TABLE OF FIGURES

Figure 1: Use case Diagram................................................................................................................6


Figure 2: Sequence Diagram...............................................................................................................7
Figure 3: E-R Diagram........................................................................................................................8
Figure 4:Activity Diagram..................................................................................................................9
Figure 5: Class Diagram....................................................................................................................10

ix
LIST OF TABLES
Table 1: Test case..............................................................................................................................18

x
ABBREVIATIONS

BIM Bachelor of Information Management


DAS Doctor Appointment System
CSS Cascading Style Sheet
ERD Entity Relationship Diagram
HTML Hypertext Markup Language
HTTP Hypertext Transfer Protocol
IT Information Technology
TU Tribhuvan University
UI User Interface
UML Unified Modeling Language
XAMPP Apache Http Server MySQL Database PHP and Perl
MySQL Database PHP and Perl
PHP Hypertext Preprocessor

xi
CHAPTER ONE

INTRODUCTION

1.1 Background
The writing of the summer project Report is essential requirements for graduation from the Faculty
of Management, Tribhuvan University. This assignment is on off the patients booking their
appointment as per their health condition. Tribhuvan University is to prepare IT professionals in
the use of computer technology to develop effective information system to solve real life problem
in the organization area.

This report is based on organization visit made to Manjushree Polyclinic & Diagnostic Center
Pvt. Ltd, Dharan-9, Sunsari. It has been developed based on the observation during the visit in
the organization. The problem which is related to the organization is solved by IT. This project is
implemented by using database and PHP. Its main aim is to provide the booking facility in the
clinic for the patients as per their health conditions through online.

1.2 Introduction of the organization


The organization under study is Manjushree Polyclinic – Dharan-9, Putali line. The mission of the
clinic is to improve the health and lives of the patients by delivering comprehensive and
compassionate medical service. The vision of the clinic is to build a strong doctor-patient
relationship based on trust, open communication, and mutual respect. To achieve its mission and
vision, the clinic has provided a convenient access such as offers flexible appointment scheduling
options, including online booking and minimize waiting time and ensure that the patient visit is as
efficient and comfortable as possible.

1.2.1 Vision

 To create a seamless and efficient platform that simplifies the process of scheduling and
managing appointments between patients and healthcare providers.

1.2.2 Mission

 To enhance patient access.


 To reduce wait times.
 To provide facilitate communication.

1
1.3 Objective of the Projects

The objectives of project are:

 To provide easy access to doctors in the area.


 To provide hassle free appointment management for medical institutes.
 To allow better time management for doctors.

1.4 Methodology
In project management, methodologies are specific and usually contain a series of steps and
activities for each phase of the project life cycle. In this project I have used Waterfall Model as
given below:

1. Requirement Analysis
2. System Design
3. Implementation
4. Testing
5. Development
6. Maintenance

1.4.1 Project Framework

This chapter reveals the proposed method of implementing the project. The important on this is
systematic planning and implementation to complete system on time.

1.4.2 Data and Information collection

Data are collected through interviews, observation, and the internet. It is collected for the purpose
of analysis. Information consists of facts that define the relationship between pieces of data. Data
becomes information after being processed, information gives off facts when data supports it, and
facts are what data reveals.

The data and information are collected from three major sources:

a. Primary Data

In this project, data has been collected directly through interview and observation. A direct
interview was held with the manager of the organization Mr. Bishesh Khadka and direct
observation in the organization.

2
b. Secondary Data

In this project, the data and information are also collected through secondary sources like the
internet, magazines, books, reports, etc.

c. Work Process Observation

The working mechanism of the organization was observed closely. It gives an idea about the
working system of organization.

1.4.3 Technique of Project Report Analysis

A Gantt Chatt, commonly used in project management, is one of the most popular and useful
ways of showing task or events display against time. Each activity is represented by a bar, length
and position that reflect the start date, duration, and end date of the tasks.

Gantt Chart

Week Phases
1st 2nd 3rd 4th 5th 6th Status

Planning and Completed


Analysis

Research and Data Completed


Collection

Design and Completed


Coding

Testing Completed

Maintenance Completed

Report Completed

3
CHAPTER – TWO

TASK AND ACTIVITIES PERFORMED

2.1 Analysis of Task and Activities


Many tasks and activities were performed which had helped to fulfil the main objective of our
project. The major objectives of the project were to get information about the use of technology in
an organization in the country. Some of the tasks that is performed is given below:

i. Organization Selection

Selection of an organization is an important decision for the project, as the type of organization
dictates most of the requirements for a system. After some research and visiting different local
organizations, "Manjushree Polyclinic & Diagnostic Center Pvt. Ltd " was selected for the project.

ii. Getting the Information about the Organization

After the selection of the organization, the other task was to gather relevant information about the
clinic. The main technique that was used for this purpose was direct observation of the procedures
carried out by each of the staff members of the organization. Further information was collected
through the direct interviewing with the management team and staff members of the organization
with relevant questions.

2.2 Analysis of Problem


The organization is facing certain problems. The main problem of this organization is that there is
lack of access to healthcare services, especially in rural or underserved areas. Some patients must
travel long distances or wait for extended periods to receive necessary medical care, leading to
delays in diagnosis and treatment. Limited access to specialists and specialized treatments further
compounds this issue. One significant issue is the rising cost of healthcare. Many patients struggle
with the financial burden of medical expenses, including high insurance premiums, copayments,
and out-of-pocket costs.

2.2.1 Analysis of Possible Solutions

The most important solution for the analyzed problem could be the Doctor Appointment System in
the form of a website. System. As the organization currently lacks a Doctor Appointment System,
developing such a system could help improve minimize long waiting times for patients. This can be
achieved by utilizing technology such as online appointment booking or mobile applications,
allowing patients to conveniently schedule their appointments and reducing the need for lengthy

4
phone calls or in-person visits. By implementing these solutions, healthcare facilities can enhance
accessibility, minimize waiting times, and deliver a better experience for both doctors and patients.

2.3 Feasibility Analysis


Following feasibility are studied before building the system to see if the system could be built with
exact requirements in required time.

2.3.1 Technical Feasibility:

To design this system, it uses off-self and existing technologies, software, and hardware sand no
technical hurdle to build this system.

2.3.2 Economic feasibility:

The system does not require extra software and hardware i.e., it uses open-source technologies
where there is no recurring cost.

2.3.3 Operational feasibility:

This system is easy to use and there is no need to use of skilled manpower to use this system.

2.4 Requirement Analysis


Requirement analysis focuses on the tasks that determine the needs or conditions to meet the new
or altered product or project, taking account of the possibly conflicting requirement of the various
stakeholders, analyzing, documenting, validating, and managing software or system requirements.
The requirements can be classified as functional and non-functional requirements.

2.4.1 Functional Requirement

This system will store all the data in the single centralized database.
1. Doctor details
2. Patient details
3. Patients’ medical history
 This site will allow users (patients, doctors, staff) to create accounts and provide necessary
information for registration.
 This site will enable patients to schedule appointments with their preferred doctors, specifying
the date, time, and reason for the appointment.
 This site patients will be able to view available time slots and book appointments based on
their preferences.

5
2.4.1.4 Use case Diagram

Figure 1 Use case Diagram

2.4.2 Non-Functional Requirements

• The system should provide quick responses to user requests.


• The system should ensure the confidentiality and integrity of patient data, complying with
applicable data protection regulations.
• The system should be capable of handling a growing number of users, appointments, and
concurrent sessions.

6
2.5 System Design
In this project there is one centralized database used for storing the information of patients who
have signup their account in system, and doctor details.

2.5.1 Sequence Diagram

Figure 1 Sequence Diagram

7
2.5.2 E-R Diagram

Figure 2 E-R Diagram

8
2.5.3 Activity Diagram

Figure 3 Activity Diagram

9
2.5.4 Class Diagram

Figure 4 Class Diagram

10
2.6 System Implementation
In this part, it constructs a new system from the scratch with the help of the system design. This
part will look at the implementation of the system including the database and the main application.
It includes coding, testing and integrate system as per the requirements.

2.6.1 Module Description

Module Description shows the different page of the system and are as follow:

Index Page

This is the initial page appear on the screen when any users search for the website.

Patient Registration Page


In this registration screen, patient need to fill all the detail information as per the form to login their
account.

11
Patient Login Page
Patient should register their account into the system before Login into the system.

12
Home Page
It shows all the items menu existing in the system. It includes Patient login, Doctor login, Admin
login, contact form and details about organization.

13
Admin Dashboard
This page is only for admin where he/she, manages all the tasks and activities in the website.

14
2.6.2 System Features

Account Features:
Creating Patient Account-Patient
Patients should register there details as per the requirement to create their login account to book an
appointment.
Logging In-Patient
The system will allow patient to login with username and password if they already possess Valid
account on the system. The system will protect the patient information and ensure all the data will
not be viewable by others.
Adding Doctors-Admin
Administrator can add the doctor as per their Specialties, Name, Email and Contact No.
Logging In-Doctors
This system allows doctors login if they are registered by the administration and provide
them username and password to login their account to view the patient booking and to give
medical history to the patient.
Deleting Doctors-Admin
Administration can remove doctors from the system.
Cancelling booking-Doctor-Admin
Doctors and Admin can cancel patient booking if the patient doesn’t come for checkup from the
system.
Appointment History-Admin
Administration can view the appointment booked by the patient as per the health condition and
even cancel the appointment from the system.

2.6.3 Tools Used


 HTML: It is basically used to format text as titles and headings to arrange graphics on this
system and used to link different pages within the system.
 CSS: In this system CSS is used for developing sites structure by creating design or
online the html elements including colors, layout, and fonts.
 Bootstrap: In this project bootstraps used for designing and making the website
screen responsive.
 PHP: PHP code embedded into HTML for making website dynamic and used for
connecting website into database.
 MySQL: In this project, MySQL is used for the database management of the system.
 XAMPP: It is used for creating and configuring with database which is written in
MySQL without internet.
 JavaScript: In this project JavaScript is used for creating some animation in the
page content.

15
2.6.4 System Testing

System testing is an essential phase in software which is usually done for executing a program. Its
primary purpose is to verify whether the system adheres to the specified requirements. In the
development process of this project, a flexible methodology was employed, allowing testing to
commence during the development phase itself. Bugs and issues were identified and promptly
addressed as they were discovered.

Unit Testing
Unit testing, which focuses on testing individual units or components of the software, was
performed during the implementation phase. Each time code was written, it was immediately
executed and closely monitored for any bugs. Any bugs identified were then rectified by
introducing new code or modifying the existing one. Detailed analysis of error messages played a
significant role in identifying and correcting issues by making appropriate code changes.

The goal is to identify and fix defects early in the development cycle, promoting code reliability
and maintainability. Unit tests also serve as documentation for future reference and provide a safety
net for developers when making changes to the codebase. By thoroughly testing individual units,
the doctor appointment system's overall integrity and robustness are strengthened, laying a solid
foundation for subsequent integration and system testing phases.

Test Case
Title: Doctor Appointment System

Description: Test case refers to a specific set of conditions, actions, and expected outcomes that
are designed to validate the functionality or behavior of a system, feature, or component. It is a
documented procedure that helps in the execution and evaluation of the system under test.
The system should be able to register patient and book an appointment and save on database with
the input patients' data.

Test Case Format:

 Test Case ID
 Test Scenario
 Test Steps
 Test Data
16
 Expected/Intended Results
 Test Status – Pass/Fail

Preconditions:
 The user is logged into the appointment system.
 The user has appropriate access rights and permissions to create appointments.

Assumptions:
 Users have reliable internet access.
 Patients and healthcare providers register and create profiles.
 Patients can cancel or reschedule appointments.
 Data privacy and security measures are implemented.

Test Steps:

1. Enter the necessary details to create a new appointment:


 Select the desired doctor from the available options.
 Enter the patient's name.
 Select the appointment date and time.
 Provide any additional required information, such as reason for the appointment or special
requests.
2. Click on the "Create Appointment" button.

Expected Results:
1. The appointment is successfully created and saved in the system.
2. The user is redirected to the appointment confirmation page or shown a success message.
3. The appointment details match the information entered during step 1.
4. The appointment receives a unique identifier or reference number.

Table 1: Test case

17
Step Test Module Input Test case Expected Test
Result Result
1. Patient Entering fields Not entering few Should display Passed
Registration required details required fields
message
2. Patient Entering all Entering all required Should display Passed
Registration required fields details successfully
registered
message
3. Patient Login Enter username Enter wrong Should display Passed
and password username and error message
password
4. Patient Login Enter username Enter correct Should Passed
and password username and successfully
password display login
message
5. Doctor Login Enter username Enter wrong Should display Passed
and password username and error message
password
6. Doctor Login Enter username Enter correct Should Passed
and password username and successfully
password display login
message
7. Enroll Book Selecting Doctor Should display Passed
appointment name, specialist, required fields
time, Date message
incorrectly
8. Enroll Book Selecting Doctor Should display Passed
appointment name, specialist, appointment
time, Date correctly booked
9. Admin login Enter username Enter wrong Should display Passed
and password username and error message
password

18
10. Admin login Enter username Enter correct Should display Passed
and password username and successfully
password login message

2.6.5 Validation Testing

Validation testing involves a comprehensive assessment of its functionality and adherence to


requirements. The process begins by reviewing the system's requirements to understand its
expected behavior, user roles, appointment scheduling rules, and notifications. A test plan is then
created, outlining the testing approach, objectives, and test cases. Test data is prepared to cover
various scenarios, such as different appointment types, doctors, and patients.

2.6.6 Findings

During the testing of the doctor appointment system, several findings were identified. Firstly, there
were instances of incorrect appointment scheduling, including overlapping appointments and
double bookings, which may lead to confusion and inconvenience for both doctors and patients.
Additionally, notification failures were observed, with appointment confirmations, reminders, and
cancellations not being sent or delivered reliably, potentially resulting in missed appointments or
miscommunication.

19
CHAPTER- THREE

DISCUSSION AND CONCLUSION

2.8 Discussion
The main objective of this project is to design web-based system of Doctor Appointment System
for to Manjushree Polyclinic & Diagnostic Center Pvt. Ltd. Being through the different difficulties
an overcoming those difficulties with the help from different sources the project has been
completed successfully.

2.9 Conclusion
In conclusion, the implementation of a doctor appointment system offers numerous benefits to both
patients and healthcare facilities. This system improves accessibility by allowing patients to easily
book appointments online, regardless of their location or mobility. It enhances time and resource
management by automating the scheduling process, minimizing conflicts, and optimizing the
utilization of healthcare providers' time. Moreover, the system enhances the overall patient
experience by reducing waiting times, minimizing the likelihood of missed appointments, and
providing convenient appointment reminders. By streamlining the appointment process, the doctor
appointment system ultimately contributes to a more efficient and effective healthcare service
delivery.

3.0 Recommendations
It's difficult to design a perfect system in 6 weeks, thus there are many things that can be enhanced
afterwards.

Functional: Due to a lack of time and technical expertise, several functionalities can be added and
improved including User Interface and User Experience.

 Use the exact and fuzzy search functions to find doctors by name, and sort doctors by their
availability date and time.
 Use of an online chat channel or a feedback form.
 Create a smartphone app for a hands-on experience.
 Improved accounting services through accounting management.
 Multiple authorized users with varying levels of access to administer different sections.

Non-functional: Some non-functional features are also important to gain a better experience.

 Well optimized web application Web application.


 Google Page Speed Insights is passed.

20
 Google Optimize is a must-pass.
 Improve performance by optimizing database indexing.
 Improve the mobile platform's UI and UX.

21
REFERENCES

ANDREI, CASU-POP, GHEORGHE, & BOIANGIU. (2019). A STUDY ON USING WATERFALL


AND AGILE METHODS IN. JOURNAL OF INFORMATION SYSTEMS & OPERATIONS
MANAGEMENT.

Davis, A., Bersoff, E., & Comer, E. (1988). A strategy for comparing alternative software development life
cycle models. IEEE Transactions on Software Engineering, 1453-1461.

D'Souza, C. (2004). Ecolabel programmes: a stakeholder (consumer) perspective. Corporate


Communications: An International Journal, 179-188.

Gupta, D., & Denton, B. (2008). Appointment scheduling in health care: Challenges and
opportunities. IIE Transactions, 800-819.

Kumar, S., & Kiran, J. (2019). Effective Online Medical Appointment System. International Journal of
Scientific & Technology Research.

22
APPENDICES

23
24
25
26
27
28
29

You might also like