VISVESVARAYA TECHNOLOGICAL UNIVERSITY

“Jnana Sangama ”,Belgaum-590014, Karnataka.

A
Mini Project Report
On
“MUSIC CONCERT TICKET BOOKING SYSTEM”
Submitted in the partial fulfillment of the requirements for the award of the Degree of

BACHELOR OF ENGINEERING
IN
INFORMATION SCIENCE AND ENGINEERING

Submitted by

GOUTHAM P 1EW20IS 032

MANIKANDAN RE 1EW20IS 046
Under the Guidance of

Mrs. VEENA N
Assistant Professor

DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING

EAST WEST INSTITUTE OF TECHNOLOGY

BANGALORE - 560 091
2021-2022
 EASTWESTINSTITUTEOFTECHNOLOGY
Sy. No. 63, Off. Magadi Road, Vishwaneedam Post, Bangalore - 560 091
(Affiliated To Visvesvaraya Technological University, Belgaum)

DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING

CERTIFICATE
This is to certify that the mini project work entitled “MUSIC CONCERT TICKET
BOOKING SYSTEM” presented by GOUTHAM P 1EW20IS032 and MANIKANDAN R
1EW20IS046, bonafied students of EAST WEST INSTITUTE OF TECHNOLOGY,
Bangalore in partial fulfillment for the award of Bachelor of Engineering in Information
Science and Engineering of Visvesvaraya Technological University, Belgaum during the
year 20212022. It is certified that all corrections/suggestions indicated have been in
corporated in the report. The mini project has been approved as it satisfies the academic
requirements in respect of mini project prescribed for the said degree.

------------------------- ------------------------------ -----------------------------

Signature of Guide Signature of HOD Signature of Principal
Mrs. VEENA N Dr. Suresh M B Dr. K Channakeshavalu
Assistant Prof, Dept. of ISE Prof & Head, Dept. of ISE Principal
EWIT, Bangalore EWIT, Bangalore EWIT, Bangalore

External Viva

Name of the Examiners Signature with date

1.

2.
 ABSTRACT
This project is aimed to provide the customers the facility to book tickets for music concerts, through
which they can book tickets anytime and anywhere. “CONCERT TICKET BOOKING SYSTEM’ is
basically made for providing the customer an anytime and anywhere service for booking the ticket for
the concert and to gather information about the concerts. The user can easily know about the concerts
that are released and can make a choice. Admin can use the system by logging into it and can insert
and delete data (for example film description, theatre information). Also, admin can check the statistic
information from the system
Frontend: PHP
Backend: My SQL
 ACKNOWLEDGEMENT
Any achievement, be it scholastic or otherwise does not depend solely on the individual
efforts but on the guidance, encouragement and cooperation of intellectuals, elders and
friends. A number of personalities, in their own capacities have helped me in carrying out
this mini project work. We would like to take this opportunity to thank them all.

First and foremost we would like to thank Dr. K Channakeshavalu, Principal, EWIT,
Bangalore, for his moral support towards completing our mini project work.

We would like to thank, Dr. Suresh M B, Professor and Head of Department of ISE, EWIT,
Bangalore, for his valuable suggestions and expert advice.

We deeply express our sincere gratitude to our guide Mrs.Veena N, Assistant Professor,
Department of ISE, EWIT, Bangalore for her able guidance throughout the mini project work
and guiding me to organize the report in a systematic manner.

We thank my Parents, and all the Faculty members of Department of Information science &
Engineering for their constant support and encouragement.

Last, but not the least, we would like to thank our peers and friends who provided us with
valuable suggestions to improve our mini project.

Goutham P 1EW20IS032
Manikandan 1EW20IS046

Ii
CHAPTERNO PAGENO
TABLE OF CONTENT
i
CONTENTS
ii
ABSTRACT
iv
ACKNOWLEDGEMENT
1 1
1.1 LIST OF FIGURES 1
1.2 INTRODUCTION 2
1.3 Objectives 3
1.4 Overview of Database Management System 3

2 Problem Statement 4
2.1 Description of the datasets 4
2.2 SYSTEM ANALYSIS 4
2.3 Existing System 4
Proposed System 5
3
Objectives of Proposed System 5
3.1
3.2 SYSTEM REQUIREMENT SPECIFICATION 5

4 Software Requirements 6
4.1 Hardware Requirements 6
4.1.1 SYSTEM DESIGN 6
4.1.2 Database design 7
4.1.3 Schema Diagram 8

5 E R Diagram 9
6 Data flow diagram 10
6.1.1 MODULE DESCRIPTION 10
6.1.2 TESTING 11

7 Unit Testing 13
System Testing

SCREENSHOTS
CONCLUSION
REFERENCES

iii
FIGURE NO PAGE NO
4.1 6
4.2 7
4.3 8
6.1 10
6.2 11
LIST OF FIGURES
6.3 12
FIGURE NAME
6.4 12
Schema Diagram
6.5 12
E R Diagram
7.1 13
Data flow diagram
7.2 13
Admin login test case
7.3 14
Admin login test case
7.4 14
Admin entering the doctor details test case
7.5 15
Admin entering the patient details test case
7.6 15
Admin entering the room details test case
7.7 16
Admin login page
7.8 16
Admin panel
7.9 17
Patients List
7.10 17
Doctors List
7.11 18
Room Type List
7.12 18
Room List
7.13 19
User List
7.14 19
7.15 System Info 20
7.16 Update Patient Details 20
Update Doctor Details
Update Room Type Details
Update Room Details
Edit User Details
View Doctor Details
View Patient History
View Room Details
iv
 Hospital Patient Records Management System

CHAPTER 1
INTRODUCTION
Hospital Patient Records Management Systems (HPRMS) are comprehensive, integrated
management systems designed to manage the information of patients of a hospital and
manage the service processes. Hospitals are becoming more reliant on the capability of
patient management information system to assist in the diagnosis process and
management, for better and improved services and practices. The main goal of hprms is to
streamline the flow of information across the hospital towards effective decision making
for patient care, in an optimized and efficient manner. Recording of patient information,
be it medical, personal, financial or legal, or recording of medical personnel information
on paper is at risk of thievery, fire outbreaks, misplacement by employees and even petty
things such as handwriting legibility. An automated HPRMS will be necessary because
there are a lot of difficulties in maintaining a large amount of information on paper,
especially as there is usually no back-up for the information, access to information can
prove difficult and time-consuming if it has to be searched for, and accuracy is needed in
the recording of vital information, and chief medical personnel cannot oversee all that is
written on the vast amount of paper to be used. It is, therefore, vital for a healthcare
organization such as a hospital to have an automated patient management record system.
There are a number of hospital management applications, open source and non-open
source, but they are usually difficult to customize or proprietary and expensive, and their
designs are not readily available for appreciation and improvements. The aim of this
research is, therefore, to design a and create a Hospital patient record management system
that would enhance information integrity, reduce transcription errors by minimizing the
chances of wrong documentation, reduce duplication of information entries, optimize
report turnaround time, reduce the chances of pilferage as related data would be readily
available electronically, and maintain records of indoor and outdoor patients.

1.1 Objectives
Specific Objectives are:
• Improving patient administration procedures resulting in shorter waiting times and
better services to patients.
• To form an integral part of larger quality improvement program in the department
• To improvement the management efficiency of hospitals
• Improved patient care
Dept. of ISE, EWIT 2021-22 Page 1
 Hospital Patient Records Management System

• Maintaining record of each patient history  Login and Account generation

1.2 Overview of Database Management Systems

A Database is a collection of related data organized in a way that data can be easily
accessed, managed and updated. Any piece of information can be a data. Database is
actually a place where related piece of information is stored and various operations can be
performed on it. A database management system is software that allows creation,
definition and manipulation of database. DBMS is actually a tool used to perform any
kind of operation on data in database. DBMS also provides protection and security to
database. It maintains data consistency in case of multiple users. Here are some examples
of popular DBMS: MySQL, Oracle, Microsoft Access and IBM2 etc.

A DBMS makes it possible for end users to create, read, update and delete data in a
database. The DBMS essentially serves as an interface between the database and the end
users or application programs, ensuring the data is completely organized and remains
easily accessible. Ex: A real estate database stores information of different types of
properties and the preferences of the owner regarding the tenant.

The information stored in the database can be accessed by registered or valid users upon
login. The users can also update, retrieve or insert data into the database. Hospital patient
records management system refers to a system of procedures and protocols responsible
for governing patient information throughout the entirety of the data lifecycle. From the
moment a patient record is created, it must be appropriately stored, secured, and
maintained. After it has been retained for the necessary amount of time (its retention
period), the record must be properly destroyed. There is a complex set of rules and
regulations regarding medical records management, and for good reason. When health
records are mismanaged, patients are put at risk. That patient safety improves when
hospitals adopt electronic health records, poor management can lead to medication errors,
missed diagnoses, treatment lapses and other potentially life threatening events.

Patient privacy is also at risk. Medical records contain highly sensitive personal
information, and when oversights occur, privacy is compromised. With healthcare data
breaches increasing, patients are losing confidence. According to a recent consumer
survey, 87% of patients are unwilling to share their full medical histories, citing concerns
about privacy protections. Poor records management also leaves hospitals, medical
practices and other providers vulnerable to costly fines and lawsuits, as well as criminal

Dept. of ISE, EWIT 2021-22 Page 2

 Hospital Patient Records Management System

charges. Hospital patient records management system brings together all the information
and processes of a hospital and patient in a single platform.

1.3 Problem Statement

Before innovative and smart Hospital Patient Management System came into practice, it
was quite difficult to maintain proper records of the daily activities of hospitals, patient
information, the maintenance schedule & inventory of medical equipments in the hospital,
and how funds are being allocated and used. This resulted in the waste of money, time
and manpower.

1.4 Description of the Datasets

• An Entity called User is created with the Id as Primary Key, Username, and
Password for storing user password, avatar, last login, date added, date updated.
• An Entity called Doctor list is created with the Id as Primary Key, which should
be unique. This Attribute is also followed by name, specialization, email, contact,
date created, date added.
• An Entity called Patient list is created with the attributes Id as a Primary Key,
which should be unique. This entity also includes attributes like patient name,
patient code, status, date created, date updated.
• An Entity called Patient history is created with the attribute Id as a Primary Key.
This entity also includes attributes like diagnosis, treatment, illness, remarks, date
created, date updated.
• An Entity called Room list is created with the attribute Id as Primary Key. This
entity includes Name, capacity, room type id, description, date created, date
updated.
• An Entity called Room type list is created with the attribute Id as a Primary Key,
which includes room, description, date created, date updated.
• An Entity called Admission history is created with the attribute Id as a Primary
Key, which includes patient id, room id, date admitted, date discharge, status, date
created, date updated.
• An Entity called System info created with the attribute id as Primary key, which
includes meta field, meta value.

CHAPTER 2

Dept. of ISE, EWIT 2021-22 Page 3

 Hospital Patient Records Management System

SYSTEM ANALYSIS
2.1 Existing System
In this system hospitals currently use a manual system for the management and
maintenance of critical information. The current system requires numerous paper forms,
with data stores spread throughout the hospital management infrastructure. Often
information (on forms) is incomplete, or does not follow management standards. Forms
are often lost in transit between departments requiring a comprehensive auditing process
to ensure that no vital information is lost. Multiple copies of the same information exist in
the hospital and may lead to inconsistencies in data in various data stores.

2.2 Proposed System

In this Hospital Patient Records Management System (hprms) is designed for any
hospital to replace their existing manual, paper-based system. The new system is to
control the following information; patient information, room availability, staff and
operating room schedules. These services are to be provided in an efficient, cost-effective
manner, with the goal of reducing the time and resources currently required for such tasks.

2.3 Objectives of Proposed System

• The main objective of Hospital Patient Record Management System is to manage
the details of doctors, patients, rooms availability, user details.
• The information must be managed in an efficient and cost wise fashion so that the
resources will be effectively utilized.
• The project is totally built at administrative level and thus only the admin is
guaranteed the access.
• The HPRMS will automate the management of the hospital making it more
efficient and error free.
• It aims at standardizing data, consolidating data, ensuring data integrity and
reducing inconsistencies.

CHAPTER 3

Dept. of ISE, EWIT 2021-22 Page 4

 Hospital Patient Records Management System

SYSTEM REQUIREMENTS
3.1 Software Requirements
The Software Requirements deal with defining software resources requirements and
prerequisites that needs to be installed on a computer to provide optimal functioning of an
application.

3.1.1 Front End

• User interface: HTML

• Operating System: Microsoft Windows 10
• Web Browser: Chrome, Opera

3.1.2 Back End

• Script language: PHP

• Database: My SQL
• Application Server: XAMPP server (v3.3.0) for Apache server (localhost)

3.2 Hardware Requirements

The software should run on any sort of desktop or laptop environment, regardless of the
operating system. Essential input/output devices are keyboard, mouse, and printers;
nothing else is required but can be recommended if desired

• Processor: 11th Gen Intel(R) Core (TM) i3-1115G4

• Hard Disk: 64-bit Operating System
• RAM: 8GB
• Display: 15” Monitor
• Hard Disk: 1Tb
• Other standard physical devices like keyboard, mouse etc.
CHAPTER 4
SYSTEM DESIGN
System design the process of defining the architecture, modules, interfaces and data for a
system to satisfy specific requirements. System design could be seen as the application of
system theory to product development. There is some overlap with the disciplines of
systems analysis, system architecture and systems engineering.

Dept. of ISE, EWIT 2021-22 Page 5

 Hospital Patient Records Management System

4.1 Database design

4.1.1 Schema Diagram
A Database schema is the skeleton structure that represents the logical view of the entire
database. If formulates all the constraints that are to be applied on the data. A database
schema defines its entities and the relationship among them. It contains a descriptive
detail of the database, whicSh can be depicted by means of schema diagram.

Figure 4.1 Schema Diagram

4.1.2 E R Diagram
An Entity Relationship model, also called as Entity Relationship (ER) Diagram, is a
graphical representation of entities and their relationships to each other, typically used in
computing in regards to the organization of data within database or information system.

Dept. of ISE, EWIT 2021-22 Page 6

 Hospital Patient Records Management System

Figure 4.2 E R Diagram

4.1.3 Data flow diagram

Data flow diagram is a way of representing a flow of data through a process or a system.
The data flow diagram also provides information about the outputs and inputs of each

entity and process itself.

Figure 4.3 Data flow Diagram

Data flow diagram of Hospital Patient Records Management System has external entities
like manage users, manage doctor list, manage patient list, manage patient history,
manage room list, manage room type list, mange admission history, manage system info
these entities are involved in our system. In between process and external entities, there
are data flow that show a brief description of the type of information exchange between
the entities and the system.

Chapter 5
Dept. of ISE, EWIT 2021-22 Page 7
 Hospital Patient Records Management System

Modules Description
Module is a collection of source files and build settings that allow you to divide your
project into discrete units of functionality. The project can have one or many modules,
and one module may use another module as a dependency. We can independently build,
test, and debug each module.

User:
This module allows the details regarding the username, password, and login, date added,
date updated, status.
Doctor list:
This module shall have the details regarding the doctor-name, specialization, email,
contact number, date created, date added.
Patient list:
This module contains the details regarding the patient id, name, code, status, date updated,
date created. Patient history:
This module contains the reports of the patient and their history, it allows getting the
detail information of patient health condition.
Room list:
This module contains the details regarding the room id, room type id, name, description,
capacity of the room, date created, date updated Room type list:
This module holds the room description and the number of patients it can accommodate,
price etc.
Admission history:
This module handles the entire admission process, it helps the organization to manage
admission form, admission enquiry like patient id, room id, date admitted, date
discharged, status, date created, date updated.
System info:
This module shall have the details regarding the information of the system which has the
system id, meta field, meta value.

CHAPTER 6
TESTING
System testing, the system is used experimentally to ensure that software does not fail. In
other words, we can say that it will run according to its specifications and in the way

Dept. of ISE, EWIT 2021-22 Page 8

 Hospital Patient Records Management System

users expect. Special test data are input for processing, and the results examined. The
importance of system testing is that the system is expected to run according to member’s
requirement before delivering it to the user. The system is tested on basis of
specifications so that it does not fail on user site.

6.1.1 Unit testing:

The steps involved during unit testing are:
• Preparation of test cases.
• Preparation of the possible test data with all the validation checks.
• Complete code review of the module.
• Actual testing done manually.
• Modifications done for errors found during testing.
• Prepared the test result scripts.
After completing the Unit testing of all modules, the whole system is integrated with all
its dependencies in that module. While system integrated, we integrated the modules one
by one and testing the system at each step. This helped in reduction of errors at the time
of system testing.
A test case in software engineering is set of conditions or variables under which a
tester will determine whether an application or software system is working correctly or
not. Thus, to check the encoding and decoding of this particular application, test case is
written for each unit and then test cases for whole system.

Table 6.1: Admin login test case

Test Case No. 1

Name of Test Admin Login

Test Case Description When admin login successful it should enter to the home page
Sample Input Admin should enter the username and password
Expected Output It should enter to the home page
Actual Output Login successful and it is directed to the home page
Remarks Pass
Table 6.2: Admin login test case

Test Case No. 2

Name of Test Admin Login

Dept. of ISE, EWIT 2021-22 Page 9

 Hospital Patient Records Management System

Test Case Description When admin login successful it should enter to the home page
Sample Input Admin should enter the username and password
Expected Output It should enter to the home page
Actual Output Login unsuccessful and it is not directed to the home page
Remarks Fail
6.1.2 System Testing
Steps involved in system testing are: 
Integration of all modules in the system
 Preparation of the test cases.
• Preparation of the possible test data with all the validation checks.
• Actual testing done manually.
• Recording of all the reproduced errors.
• Modifications done for the errors found during testing.
• Prepared the test result scripts after rectification of the errors. After the completion of
system testing, the next following phase was the Acceptance Testing.

A test case in software engineering is set of conditions or variables under which a

tester will determine whether an application or software system is working correctly or
not. Thus, to check the encoding and decoding of this particular application, test case is
written for whole system.
Table 6.3: Admin entering the doctor details test case

Test Case No. 3

Name of Test Entering doctor data

Test Case Description Admin entering doctor details like id, name, email, contact,
specialization, date created, date updated.

Sample Input Entering doctor details

Expected Output Data should be stored in database
Actual Output After entered by the admin it should stored in database
Remarks Pass
Table 6.4: Admin entering the patient details test case

Test Case No. 4

Dept. of ISE, EWIT 2021-22 Page 10

 Hospital Patient Records Management System

Name of Test Entering patient data

Test Case Description Admin enters patient details like patient name, cod, id, status,
date created, date updated.

Sample Input Entering data

Expected Output Entered data should be stored in the data base
Actual Output It is stored in the database
Remarks Pass
Table 6.5: Admin entering the room details test case

Test Case No. 5

Name of Test Entering room details

Test Case Description Admin entering room details like name, capacity, room type id,
date created.

Sample Input Entering data

Expected Output Entered data should be stored in the database
Actual Output It is stored in the database
Remarks Pass

CHAPTER 7
SCREENSHOTS
7.1 Admin Login Page
Admin can login using username and password.

Figure 7.1: Admin login page

Dept. of ISE, EWIT 2021-22 Page 11

 Hospital Patient Records Management System

7.2 Admin Panel

Admin Panel contains number of Room types, Total room, Doctors and Patients.

Figure 7.2: Admin panel

7.3 Patients List

Admin can view the list of patients.

Figure 7.3: Patients list page

7.4 Doctors list

The admin can view the list of doctors.

Dept. of ISE, EWIT 2021-22 Page 12

 Hospital Patient Records Management System

Figure 7.4: Doctors list page

7.5 Room Type List

The admin can view the list of room types.

Figure 7.5: List of room types page

7.6 Room List

The admin can view the list of rooms.

Dept. of ISE, EWIT 2021-22 Page 13

 Hospital Patient Records Management System

Figure 7.6: List of room page

7.7 User List

Admin can view the list of users.

Figure 7.7: List of system user

7.8 System Info

System information of the Hospital Patient Records Management System.

Dept. of ISE, EWIT 2021-22 Page 14

 Hospital Patient Records Management System

Figure 7.8: System Information Page

7.9 Update Patient Details

Admin can update the patient information

Figure 7.9: Update patient details page

7.10 Update Doctor Details

The admin can update the doctor details.

Dept. of ISE, EWIT 2021-22 Page 15

 Hospital Patient Records Management System

Figure 7.10: Doctor details update page

7.11 Update Room Type Details

The admin can update the details of room types.

Figure 7.11: Update room type details page

7.12 Update Room details

The admin can update the details of room.

Dept. of ISE, EWIT 2021-22 Page 16

 Hospital Patient Records Management System

Figure 6.12: Room details update page

7.13 Edit user details

Admin can edit the user details.

Figure 7.13: User details edit page

7.14 View Doctors Details

Admin can view the details of doctors

Dept. of ISE, EWIT 2021-22 Page 17

 Hospital Patient Records Management System

Figure 7.14: Doctor details

7.15 View Patient History

Admin can view the details of the patients

Figure 7.15: Patient history details

7.16 View Room Details

Admin can view the details of the room.

Dept. of ISE, EWIT 2021-22 Page 18

 Hospital Patient Records Management System

Figure 7.16: Room details

Dept. of ISE, EWIT 2021-22 Page 19

 CONCLUSION
Taking into account all the mentioned details, we can make the conclusion that the
hospital patient records management system is the inevitable part of the lifecycle of the
modern medical institution. It automates numerous daily operations and enables smooth
interactions of the users. Developing the hospital system software is a great opportunity
to create the distinct, efficient and fast delivering healthcare model. Implementation of
hospital patient records management system project helps to store all the kinds of record
like doctor’s details, patient list, room types, room list, user information, system
information. This beneficial decision covers the needs of the patients, staff and hospital
authorities and simplifies their interactions. It has become the usual approach to manage
the hospital. Many clinics have already experienced its advantages and continue
developing new hospital patient record management system project modules.
 REFERENCES
[1] Silberschatz Korth and Sudharshan, Database System Concepts, 6 th Edition,
McGrawHill, 2013.
[2] Coronel, Morris,and Rob, Database Principles Fundamentals
of Design, Implementation and Management, Cengage Learning
2012.
[3] www.campcodes.com