A PROJECT REPORT

ON

(Vaccine Management System)

Submitted in partial fulfillment of the requirement

For the award of the degree of

BACHELOR OF COMPUTER APPLICATIONS

SESSION (2020-2021)

Under the guidance of: Submitted by:

External guide: Mr. Surender Dabur Abdul Kalam (0103601)
Internal guide: Ms. Jyotsana Pandey Abhay Pratap Singh (0103602)

Aman Verma (0103612)

Batch: BCA (2018-2021)

DAYANAND ACADEMY OF MANAGEMENT STUDIES,

KANPUR
AFFILIATED TO

C.S.J.M. UNIVERSITY, KANPUR

 A PROJECT REPORT
ON

(Vaccine Management System)

Submitted in partial fulfillment of the requirement
For the award of degree of

BACHELOR OF COMPUTER APPLICATIONS

Of

C.S.J.M University, Kanpur

Session-(2020 – 21)

Under the guidance of: Submitted by:

External guide: Mr. Surender Dabur Abdul Kalam (0103601)
Internal guide: Ms. Jyotsana Pandey Abhay Pratap Singh (0103602)

Aman Verma (0103612)

Batch (2018 – 2021)

DAYANAND ACADEMY OF MANAGEMENT STUDIES,

KANPUR
 ACKNOWLEDGEMENT

I would like to express my sincere gratitude and regards to my external guide

Mr. Surender Dabur for his inspiration, supervision and invaluable guidance

during the training. I would also like to thank Mr. Pradeep Kumar Tiwari of

Dayanand Academy Of Management Studies for giving me such an opportunity

to continue my training in the Dayanand Academy Of Management Studies and

providing the facility.

At last I would also like to extend my sincere gratitude to all my faculty

members and specially Ms. Jyotsana Pandey for giving their valuable suggestions.

With regards

Signature of Student:

(Sign of HOD) (Sign of internal guide)

 Table of Contents

S. No. Topic Page No.

1. Acknowledgement

2. Title of the project

3. Introduction

3.1 Basic introduction of Project

3.2 Objective and Scope of project

3.3 Project Category

3.4 Tools and Technologies used

4. System analysis

4.1 Preliminary analysis & Information gathering

4.2 Input/outputs

4.3 Feasibility Study

4.4 System Requirements Specification

4.5 Software Engineering Model Used

4.6 Cost Estimation

4.7 Project Scheduling

5. System Design

5.1 Project Planning

5.2 Modules

5.3 Data Flow Diagram

5.4 E-R Diagram

5.5 Data Base Design

5.6 Screen Shots

6. Testing

7. Implementation & Maintenance

8. References / Bibliography
TITTLE OF THE PROJECT

Vaccine
Management
System
 3. INTRODUCTION

3.1 BASIC INTRODUCTION OF THE PROJECT

The VACCINE MANAGEMENT SYSTEM has been developed to override the problem
prevailing in practicing manual system. This software is supported to eliminate and in some
case reduce the hardship faced by thus existing system. Moreover this system is designed for
the particular need of the vaccination centre to carry out their operation in a smooth and
effective manner.
The application is reduced as much possible to avoid errors while entering the data. It also
provides error message while entering invalid data and no formal knowledge is needed of the
user to use this system. Thus by this all it provides a very user-friendly VACCINE
MANAGEMENT SYSTEM as described above, can lead to error free source, reliable and
fast management system. The user can also concentrate on other activities rather than
concentrating on record keeping. Thus the resources of the organization can be used
effectively. There is database which is maintained in which all the names of patients and their
complete information is stored. Reports can be published faster anytime.
Every health care organization whether big or small, public or private has challenges to
overcome and managing the information of patients, doctors, treatments, appointments and
vaccine. Every VACCINE MANAGEMENT APPLICATION has different organizational
needs, therefore we have designed exclusive employee management system that are adapted
to your managerial requirements. This application will ensure that your organization is
equipped with the right level of information and details for your future goals. Our system will
also have remote access features which will allow you to manage your workforce anytime at
all times. This system will ultimately allow you to manage resources better. 
 3.2 OBJECTIVE OF THE PROJECT

The main Objectives of creating this VACCINE MANAGEMENT SYSTEM are as follows:

 To reduce the hardships faced by thus existing system.

 To provide secure vaccination system and maintains all the requirement of the
vaccination process such as authentication, confidentiality and integrity.
 To reduce manual work load, and to process work fast and effective.
 To ensure vaccine quality and to increase supply chain efficiency for proper
distribution.
 To ensure the satisfaction of all the users and to keep the records safe of the vaccine
receivers.
 Besides security and simplicity, other issues that need to be considered are reliability,
convenience, flexibility, mobility and cost.

How vaccination management system works:

 Patients will be required to register themselves for the vaccination process.
 Patients will be given unique LOGIN ID and PASSWORD.
 In the DATABASE the information of every registering patient, availability of
vaccine and doses would be stored.
 Time and date allotted for vaccination process will be displayed on the home page
of the system once registration is successfully done and all the requirements are
met.
 Once vaccination process is completed it will be displayed.
 Patients can enter their review about the process , health state and
 Vaccination centers.
 3.2 SCOPE OF THE PROJECT

 It is an Advanced Technology used nowadays. It increases the E- Knowledge of the

user which is very important for the current generation of growing world. This
Vaccine Management System also helps in enhancing the knowledge of internet to
the users.
 This Vaccine Management System is an online facility and hence very useful for the
users. Patients can book an appointment for vaccination at any time of the day and
from any place of the country as per their choice. This can help in reducing the rush at
the Vaccination Centers.
 Login Credentials for the Users can be sent directly to the registered E- Mail address
which will help in maintaining the privacy of the user .Users can also get information
and updates related to their vaccination programs as per the schedule.
 Sometimes the Hospitals or the Vaccination Centers want to send message to the
registered mobile number regards the updates of the availability of the vaccines and
doctors, they can use this facility of the Vaccine Management System. The
information can be sent to multiple users in no time.
 In future, Vaccine Management System can be made more secure by using the
technology such as finger print recognition or Face Detection Techniques. This will
ensure the users safe and error free vaccination.
 3.3 PROJECT CATEGORY

Relational Database Management System (RDBMS): This is an RDBMS based

project which is currently using MYSQL for all the transaction statements.
MYSQL is an open source RDBMS system.

Brief Introduction about RDBMS:

A relational database management system (RDBMS) is a database management system

(DBMS) that is based on the relational model as invented by E.F.CODD, of IBM’s San Jose
Research Laboratory. Many popular databases currently in use are based on the relational
database model. RDBMSs have become a predominant choice for the storage of information
in new databases used for financial records, manufacturing and logistical information,
personnel data, and much more since the 1980s. Relational databases have often replaced
legacy hierarchical databases and network databases because they are easier to understand
and use. However, relational databases have been challenged by object databases, which were

introduced in an attempt to address the object-relational impedance mismatch in relational

database, and XML databases.
INTRODUCTION OF RDBMS:

Implementation Methodology
Model view controller or MVC as it is popularly called, is a software design
pattern for developing web applications. A model view controller pattern is made up
of the following three parts:

 Model: The lowest level of the pattern which is responsible for maintaining
data.
 View: This is responsible for displaying all or a portion of the data to the
user.
 Controller: Software code that controls the interactions between the
Model and view.

MVC is popular as it isolates the application logic from the user interface layer and
supports separation. Here the controller receives all requests for the application and
then works with the model to prepare any data needed by the view. The view then
uses the data prepared by the controller to generate a final presentable response.
The MVC abstraction can be graphically represented as follows.
IMPLIMANTATION METHODOLOGY:
NAME OF COMPONENT SPECIFICATION
Operating System Windows 9,8, Windows XP, Windows 7,
Windows 10 Linux
Language PHP
Framework My SQL
Database My SQL
Web Server Any of Mozilla, Opera, Chrome etc.

Hardware Requirements:
NAME OF COMPONENT SPECIFICATION
Processor INTEL CORE
RAM 4GB
Hard Disk 128 GB
Monitor 15” color monitor
Keyboard 122 keys
 3.4 TOOLS AND TECHNOLOGIES USED

TECHNOLOGIES USED:

• Django: project has been developed over the Django Framework.

TOOLS USED:
 WINDOWS: When referring to an operating system, WINDOWS or WIN
is an operating environment created by MICROSOFT that provides an
interface, known as a Graphical User Interface (GUI) for computers.
Windows eliminates the need to memorize commands for the command line
by using a mouse to navigate through menus, dialog box, buttons, tabs and
icons. If you are using a PC (IBM) computer you are most likely using a
version of Windows. If you are on an Apple computer you are using MAC OS.
Microsoft Windows was first introduced with version 1.0 on
November 10.1983. Since its release, there have been over a dozen versions of
Windows.

Windows XP

Windows XP was made available in two versions, windows XP HOME and

windows XP Professional. The company focused on mobility, such as technology
allowed for in 2001 and included plug and play features for connecting to
wireless networks. The operating system utilizes the 802.11x wireless security
standard.

The initial Windows XP release was followed by the release of Windows XP 64

Bit Edition (v2002), Windows XP Media center edition and Windows XP edition
(v2003).
Microsoft to end Official Windows XP support in April 2014.
On April 8, 2014 Microsoft will cease official XP support. After this date users
of the XP operating system will no longer receive patches or system updates to
protect against viruses and malware. Because the operating system has been so
popular and is still in use 11 years after release, the biggest problem facing users
is choosing to continue to run an outdated operating system or upgrade to a new
OS, which could mean a steep learning curve and increased costs. In addition
to paying for a new operating system, some users looking to upgrade will find
they need to upgrade system hardware to run a newer version of the windows
operating system.
The Impact on Businesses
As of 2013 it is believed that more than 400 million computers still run the
Windows XP operating system, representing a 37 percent market share,
according to Small Business Computing. "Windows XP may seem like a relic of
the past. For businesses, however, XP has proven to be a sturdy, stable and largely
reliable OS — provided that you kept it updated and secure, of course. These
traits help explain the 11 year-old operating system's enduring popularity." The
end of support for Windows XP translates into a huge number of desktops and
laptops that may become targets for hackers and owners will be left to wrestle
with software compatibility issues. Even Microsoft's own Internet Explorer 9
browser won't run on Windows XP, but not all software will end compatibility
right away. For example, Google announced that the Chrome browser will
support Windows XP users until at least 2015. The exceptions will be few and far
between, however. Software manufacturers will optimize for more recent versions
of Windows so expect to find more applications and devices that are not Windows
XP-compatible as official support for the operating system ends
Government Computers Especially Vulnerable

According to recent news reports, the expiration of official Windows XP

support will impact government computers. "Federal officials have known for
more than six years that Microsoft will withdraw its free support for Windows
XP on April 8, 2014. Despite a recent rush to complete upgrades, an
estimated 10 percent of government computers — out of several million —
will still be running the operating system on that date, company officials
said." cites the Washington Post. The article also claims that federal officials
asked Microsoft to extend its deadline for ending support for Windows XP, but
the request was denied.
Anti-Malware Signatures for One Year

To help ease the transition from the outdated operating system, Microsoft
has said it will continue to issue anti-malware updates for Windows XP for
more than a year after the April deadline passes to help organizations
complete their migrations. Week notes that for enterprise customers, this
applies to System Center Endpoint Protection, Forefront Client Security,
Forefront Endpoint Protection and Windows In tune running on Windows XP.

To Upgrade or Not?

As noted in this datamation article, there are effectively two sides to the
"upgrade or not" discussion. First, one is the updating of current, existing
software. The assumption being that the current state of things is "working" with
the accepted possibility that "working" might include a security exposure that
has been discovered and requires updating in order to close. The other scenario
is a new deployment where there is nothing currently and we are starting from
scratch.

Why Microsoft Windows is called Windows?

Before the release of Microsoft Windows, Microsoft users were used to the
single-task command line operating system MS-DOS. Because Microsoft names
most of its products with one word, it needed a word that best described its new
GUI operating system. Microsoft chose “Windows” because of the multiple
windows that allow different tasks and programs to be run at the same time.
Because you cannot trademark a common name like “Windows” it is officially
knows as “Microsoft Windows”. The first version of Microsoft Windows was
version 1.0 released in 1985.
 Django
Django is a high-level PHP web framework that enables rapid development of secure
and maintainable websites. Built by experienced developers, Django takes care of
much of the hassle of web development, so you can focus on writing your app without
needing to reinvent the wheel. It is free and open source, has a thriving and
active community, great documentation, and many options for free and paid-for
support.

Django helps you write software that is:

 Complete: Django follows the "Batteries included" philosophy and provides
almost everything developers might want to do "out of the box". Because
everything you need is part of the one "product", it all works seamlessly
together, follows consistent design principles, and has extensive and up-to-date
documentation.
 Versatile: Django can be (and has been) used to build almost any type of
website from content management systems and wikis, through to social
networks and news sites. It can work with any client-side framework, and can
deliver content in almost any format (including HTML, RSS feeds,
JSON, XML, etc). Internally, while it provides choices for almost any
Functionality you might want (e.g. several popular Databases, Templating
engines, etc.), it can also be extended to use other components if needed.

 Secure: Django helps developers avoid many common security mistakes

by providing a framework that has been engineered to "do the right
things" to protect the website automatically. For example, Django
provides a secure way to manage user accounts and passwords, avoiding
common mistakes like putting session information in cookies where it is
vulnerable (instead cookies just contain a key, and the actual data is
stored in the database) or directly storing passwords rather than
a password hash. Django enables protection against much
vulnerability by default, including SQL injection, cross-site scripting,
 cross-site request forgery and click jacking (see Website security for
more details of such attacks).
 Scalable: Django uses a component-based “shared-nothing” architecture
(each part of the architecture is independent of the others, and can hence
be replaced or changed if needed). Having a clear separation between
the different parts means that it can scale for increased having a clear
separation between the different parts means that it can scale for
increased traffic by adding hardware at any level: Caching server,
Database server and application server. Some of the busiest sites have
successfully scaled Django to meet their demands (e.g. Instagram and
Disqus, to name just two).
 Maintainable: Django code is written using design principles and
patterns that encourage the creation of maintainable and reusable code.
In particular, it makes use of the Don't Repeat Yourself (DRY) principle
so there is no unnecessary duplication, reducing the amount of code.
Django also promotes the grouping of related functionality into reusable
"applications" and, at a lower level, groups related code into modules
(along the lines of the Model View Controller (MVC) pattern).
 Portable: Django is written in PHP, which runs on many platforms. That
means that you are not tied to any particular server platform, and can
run your applications on many flavors of Linux, Windows, and Mac
OS X. Furthermore, Django is well-supported by many web hosting
providers, who often provide specific infrastructure and documentation
for hosting Django sites.
Where did it come from?

Django was initially developed between 2003 and 2005 by a web team who
were responsible for creating and maintaining newspaper websites. After
creating a number of sites, the team began to factor out and reuse lots of
common code and design patterns. This common code evolved into a generic
web development framework, which was open-sourced as the "Django"
project in July 2005. Django has continued to grow and improve, from its
first milestone release (1.0) in September 2008 through to the recently-released
version 2.0 (2017). Each release has added new functionality and bug fixes,
ranging from support for new types of databases, template engines, and caching,
through to the addition of "generic" view functions and classes (which reduce
the amount of code that developers have to write for a number of programming
tasks). Django is now a thriving, collaborative open source project, with many
thousands of users and contributors. While it does still have some features
that reflect its origin, Django has evolved into a versatile framework that is
capable of developing any type of website.
What does Django look like?
In a traditional data-driven website, a web application waits for HTTP requests
from the web browser (or other client). When a request is received the
application works out what is needed based on the URL and possibly
information in POST data or GET data. Depending on what is required it may
then read or write information from a database or perform other tasks required to
satisfy the request. The application will then return a response to the web
browser, often dynamically creating an HTML page for the browser to display
by inserting the retrieved data into placeholders in an HTML template.
Django web applications typically group the code that handles each of these steps
into separate files:
 URLs: While it is possible to process requests from every single URL via
a single function, it is much more maintainable to write a separate view
function to handle each resource. A URL mapper is used to redirect
 HTTP requests to the appropriate view based on the request URL. The
URL mapper can also match particular patterns of strings or digits that
appear in a URL and pass these to a view function as data.
 View: A view is a request handler function, which receives HTTP
requests and returns HTTP responses. Views access the data needed to
satisfy requests via models, and delegate the formatting of the response
to templates.
 Models: Models are PHP objects that define the structure of an
application's data, and provide mechanisms to manage (add, modify,
delete) and query records in the database.

WORKING OF Django

 Templates: A template is a text file defining the structure or layout of

a file (such as an HTML page), with placeholders used to represent
actual content. A view can dynamically create an HTML page using an
HTML template, populating it with data from a model. A template can
 be used to define the structure of any type of file; it doesn't have to be
HTML!

Installation of Django:
 Firstly we will install virtual environment wrapper
pip install virtualenvwrapper-win
 Firstly we will create a virtual environment for Django
mkvirtualenv Axpino
 Now we will install Django into our Environment
pip install Django
 Now we will create a folder to store our projects and navigate to it
mkdir projects cd projects
 Now we will create our first project

django-admin startproject projectname

 Navigate to project folder and start server

cd projectname PHP manage.py runserver
 FRAMEWORK OF Django
Creating views:

 Firstly we will create a app inside our project

 Select the Environment using command >>workon env_name
 Navigate to projects folder >>cd projects
 Navigate to your project >>cd project_name
 Create a app using command >>PHP manage.py startapp app_name
 Let us add a path in urls file in our app

from django.urls import path

from . import views
urlpatterns = [
path('',views.home,name="home")
]

 Let create a view function

from django.shortcuts import render
from django.http import HttpResponse
# Create your views here.
def home(request):
return HttpResponse("This is my webpage")
 Let add path in main project url
from django.contrib import admin
from django.urls import path,
urlpatterns = [
path('',include('calc.urls’)),
path('admin/', admin.site.urls
]
Advantages of Django:
 Written in PHP:
Django is one of the web frameworks which are written in PHP
programming language. Hence, it becomes easier for programmers to
build web applications with clean, readable, and maintainable code by
taking advantage of syntax rules of PHP. Also, the developers can easily
curtail the development time by building custom web applications
without writing additional code.
 Accelerates custom web application development:
Django is one of the most mature web frameworks for PHP. Its design
rules focus extensively on reducing web application development time.
The features provided by Django enable developers to build custom
web applications rapidly according to varying business requirements.
A large percentage of PHP programmers even opt for Django when
they have to meet both goals and deadlines.
 Designed as a batteries-included web framework:
Django is one of the web frameworks that adopt the batteries-
included approach. While developing a custom web application,
Django provides the resources required by developers out of the box. It
provides code for common operations like database manipulation,
HTML templating, URL routing, session management, and security.
The batteries included approach help developers to curtail web
application development time significantly.
 Supports MVC programming paradigm:
Django, like other modern web frameworks, supports model-view-
controller (MVC) design rule. The MVC programming paradigm
allows programmers to keep a web application’s user interface (UI)
and business logic layers separated. The approach further helps
 programmers to simplify and speed up development of large web
applications by separating their user interface and business logic
layers. Django further allows programmers to reuse the same business
logic across multiple projects.

 Compatible with major operating systems and databases:

Nowadays, users access web applications on various devices and
platforms. Django enhances the accessibility of web applications by
supporting major operating systems like Windows, Linux and Mac OS.
At the same time, the ORM system provided by Django makes it easier
for programmers to work with several widely used databases. They can
even use the ORM system to perform common database operations
and migrate from one database to another without writing additional
code.
 Provides robust security features:
The built-in security features provided by Django help developers to
protect the web applications from a variety of targeted security attacks
- cross-site scripting, SQL injection and cross-site request forgery.
At the same time, the web framework enhances the security of web
applications by preventing common security mistakes related to PHP
coding.
 Easy to extend and scale:
Django has been evolving consistently to enable programmers to
build better and modern web applications. At the same time, the
Django developers can easily customize, scale, and extend the web
framework by making changes to its decoupled components. They even
have option to unplug or replace these decoupled components according
to precise requirements of individual projects. Likewise, they can
accelerate development of large and complex web applications by
wiring up a wide range of components.
 Supported by a large and active community:
As an open source web framework for PHP, Django helps developers
to reduce web application development cost significantly. But it is
 supported by a large and active community of developers. The
members of the Django community update new plug-ins and code
snippets regularly to simplify web application development. The
developers can easily speed up custom web application
development by taking advantage of these resources uploaded by
members of the Django community. The members of the community
even help developers to resolve common web application development
issues and problems.

Disadvantages of Django:

 Impacts performance of small web applications:

The robust features provided by Django make it easier for programmers
to build large and complex web applications. But the developers do
not need some of these advanced features while developing small
and simple web applications. The additional features even impact the
performance of small web applications adversely. Hence, PHP
programmers have to explore ways to improve the performance of
small web application while using Django.
 A process lacks the capability to handle multiple requests simultaneously:
Most web frameworks improve the performance of web applications by
making each process handle multiple requests at a time. But Django,
unlike other modern web framework, does not enable individual
processes to handle multiple requests simultaneously. Hence,
programmers have to explore ways to make individual processes
handle multiple requests efficiently and quickly at a time.
 Makes web application components tightly-coupled:
Most PHP programmers nowadays opt for component-based
development approach to accelerate web application development and
maintenance. Unlike other modern web frameworks, PHP does not keep
the components of a web application loosely-coupled. It even requires
programmers to deploy all components of the web application at a time.
 Relies heavily on the ORM system:
 The ORM system provided by Django makes it easier for developers to
work with multiple databases and perform common database
operations. But the ORM system used by the web framework lacks
some of the robust features provided by other widely used ORM
systems. Also, it does not enable developers to take advantage of the
robust the PHP SQL toolkit – SQL Alchemy - fully.

TCP:
Transmission Control Protocol is a connection-based protocol that provides a reliable flow
of data between two computers.

UDP:
The UDP protocol provides for communication that is not guaranteed between two
applications on the network. UDP is not connection-based like TCP. Rather, it sends
independent packets of data, called datagram, from one application to another. Sending
datagram is much like sending a letter through the postal service.

FTP Protocol:
File Transfer Protocol (FTP) is a standard network protocol used to exchange and manipulate
files over an Internet Protocol computer network, such as the Internet.

FTP Protocol:
File Transfer Protocol (FTP) is a standard network protocol used to exchange and manipulate
files over an Internet Protocol computer network, such as the Internet. FTP is built on client-
server architecture and utilizes separate control and data connections between the client and

server applications.

UNDERSTANDING PORTS:
Generally speaking, a computer has a single physical connection to the network. All data
destined for a particular computer arrives through that connection. However, the data may
be intended for different applications running on the computer.
 4. SYSTEM ANALYSIS

4.1 PRELIMINARY ANALYSIS & INFORMATION

GATHERING:
System analysis is not only time consuming but also a rigorous task. But it is a
crucial and most important phase of Software development process.

Preliminary Investigation is the process of gathering data for requirement

analysis. It is more helpful for problem definition and requirement specification.

In the first phase, the system is investigated. The objective of this phase is to
conduct an initial analysis and findings of the system as follows:

• Need Analysis:

This phase is used to identify the need for a new system. It is very
important step. Everything performed in future depends on this phase.
• System scope:
The scope of the system is defined at this stage. The scope of a system
can be reduced due to financial and political problems etc.
• Alternate solution:
A system may be developed by many ways. This step identifies all possible
ways to develop a system. It is used to select the best solution that fulfills the
requirements.
In this phase, the current business system is studied in detail to find out how it
works and how to improve it. The analyst conducts the following activities:

• Need Analysis:
Need analysis is also called requirements analysis. It consists of all
requirements of the system from users and managers. The developed
system must fulfill all these requirements determined in this step.

• Data Gathering Techniques:

Data gathering techniques are used to collect detailed information about
system. These techniques are written documents, interviewing, questionnaires,
observation and sampling.

• Data Analysis:
Data analysis is a process of analyzing the data to obtain accurate information.
Many tools are used for this purpose such as data flow diagram and flowcharts
etc.
• Analysis Report:
Analysis report is produced at the end of system analysis. It is submitted to the
top management for review. The report should consist of the following parts:
• It must explain the current system.
• It should explain the problems in the current system.
• It should describe the requirements and recommendations for new system.
DESIGN OF SYSTEM:
System design phase is used to design the logical and physical model of new
system. The system design states how the new system will meet the
requirement identified in system analysis phase.

1. Logical Design:
Logical design describes the general functional capabilities of new system. It
reviews the system requirements and considers major system components.
CASE tools and project management software are used in this step. Different
tools are used to prepare logical design such as MS Project and Gantt chart etc.
2. Physical Design:
Physical design describes how the proposed system will deliver the capabilities
specified in the logical design. It specifies the following:
• Output requirements
• Input requirements
• Storage requirements
• Processing requirements
• System control
• Backup and Recovery Procedures
3. Report:
A detailed report is prepared at the end of design phase. It is also submitted to
the higher management for approval.

4.2 INPUT OF THE PROJECT

Input is a term that refers specifically to any particular items, product or

mechanism that refers to an internal or external device that can be used for the
purpose of triggering the progression of a particular process.

 For registration of Vaccination, system will ask for

Name of the patient,
E-Mail Id of patient,
Address of patient,
Age of patient,
Gender of patient,
Aadhar Number of patient,
Date of Birth of patient,
Phone Number of patient,
Password for Login in future,
Test Reports required,
Vaccine required.
 For Login for Admin
Name of the admin,
Password for login.
 4.2 OUTPUT OF THE PROJECT

Output is a term that refers specifically to any particular item, product or

mechanism that refers to an internal or external that can be used to generate
result of a particular process.

 Notification of “REGISTERED FOR VACCINATION”.

 DATE and TIME of vaccination.
 Notification of “VACCINATED SUCCESSFULLY” after vaccination.
 Option for review.
 4.3 FEASIBILITY STUDY

Feasibility is to determine of whether or not is project is worth doing. The process

followed in making this determination is called a feasibility study. A feasibility
analysis usually involves a thorough assessment of the operational (need) financial
and technical aspects of a proposal feasibility study in the test of the system proposal
made to identify whether the user needs may be satisfied using the correct software
and hardware technologies, whether the system will be cost effective from a business
point of view and whether it can be developed with the given budgetary constraints.

Different Type of Feasibility Study:

In the conduct of the feasibility study, the analyst will usually consider seven distinct, but
inter - related type of feasibility management feasibility time feasibility.

 Technical Feasibility: Technical Feasibility deals with the hardware as well as

software requirements. Technology is not a constraint to type system
development. We have to find out whether the necessary technology the proposed
equipment have the capacity to hold the data which is used in the project , should
be checked to carry out this technical feasibility. The Technical Feasibility issues
usually raised during the feasibility stage of the investigation includes these.
 Response time under certain conditions.
 Ability to process a certain volume of transaction at particular speed.
 Facility to communication data to distant location.
 Operational Feasibility: This analysis involves how it will work when it is
installed and the assessment of political and managerial environment in which it is
implemented. People are inherently resistant to change and computers have been
known to facilitate change. The new proposed system is very much useful to the
users and there for it will be accept broad audience from around the world. It is
mainly related to human organization and political aspects. The point to be
considered are:
 What changes will be brought will the system?
 What organizational structures are distributed?
 What new skill will be required? Do the existing staff members have
these skills?

If not, can they be trained in due course of time Generally project

will not be rejected simply because of operational simply because of
operational infallibility but such considerations are likely to critically
affect then nature and scope of the eventual recommendations.

 Economical Feasibility: Economic analysis is the frequency used

technical for evaluating the effectiveness of a proposed system. More
frequently known as cost /benefits analysis: the procedure is to
determine the benefits and saving that are expected from a proposed
system and compare them with costs. If benefits out -weigh costs, a
decision is taken to design and implement the system. Otherwise,
further justification or alternative in the proposed. System will have to
be made if it is to have a change of being approved. This is an ongoing
effort that improves in accuracy at each phase of the system life cycle.
Thus feasibility study should center along the following points.
 Improvement resulting over the existing method in terms of
accuracy and timelines.
 Cost comparison.
 Estimate on the life expectancy of the hardware.
  Social Feasibility: Social feasibility is a determination of whether a proposed
project will be acceptable to the people or not. This determination typically
examines. Accepted by the group directly affected by the proposed system change.

 Management Feasibility: It is a determination of whether a proposed project will be

acceptable to management. If does not accept a project or gives a negligible
support to it; the analyst will tend to view the project as a non-feasible one.

 Time Feasibility: Time feasibility is a determination of whether a proposed project

can be implemented fully with in a stipulated time frame. It a project takes too
much time it is likely to be rejected.

4.4 SOFTWARE REQUIREMENTS SPECIFICATION

 Introduction
The VACCINE MANAGEMENT SYSTEM has been developed
to override the problem prevailing in practicing manual system. This
software is supported to eliminate and in some case reduce the hardship
faced by thus existing system. Moreover this system is designed for the
particular need of the vaccination centre to carry out their operation in a
smooth and effective manner.
 Purpose
This software will be used by several patient to vaccinated them self.

 Scope
The best thing about this software is to provide easy way of
vaccination.
 It is an Advanced Technology used nowadays. It increases the E- Knowledge of the
user which is very important for the current generation of growing world. This
Vaccine Management System also helps in enhancing the knowledge of internet to
the users.
 This Vaccine Management System is an online facility and hence very useful for the
users. Patients can book an appointment for vaccination at any time of the day and
 from any place of the country as per their choice. This can help in reducing the rush at
the Vaccination Centers.
 Login Credentials for the Users can be sent directly to the registered E- Mail address
which will help in maintaining the privacy of the user .Users can also get information
and updates related to their vaccination programs as per the schedule.
 Sometimes the Hospitals or the Vaccination Centers want to send message to the
registered mobile number regards the updates of the availability of the vaccines and
doctors, they can use this facility of the Vaccine Management System. The
information can be sent to multiple users in no time.
 In future, Vaccine Management System can be made more secure by using the
technology such as finger print recognition or Face Detection Techniques. This will
ensure the users safe and error free vaccination.

4.5 SOFTWARE ENGINEERING MODEL USED

Software Prototyping Model:

Prototype methodology is defined as a Software Development model in which a prototype is
built, tests, and then reworked when needed until an acceptable prototype is achieved. It also
creates a base to produce the final system.

Software prototyping model works best in scenarios where the project's requirements
are not known. It is an iterative, trial, and error method which take place between the
developer and the client.
Prototyping Model Phase:
Prototyping Model has following six SDLC phases as follow:
Step 1: Requirements gathering and analysis

A prototyping model starts with requirement analysis. In this phase, the

requirements of the system are defined in detail. During the process, the users
of the system are interviewed to know what their expectation from the system
is.

Step 2: Design

The second phase is a preliminary design or a quick design. In this stage, a

simple design of the system is created. However, it is not a complete design. It
gives a brief idea of the system to the user. The quick design helps in
developing the prototype.

Step 3: Build a Prototype

In this phase, an actual prototype is designed based on the information

gathered from quick design. It is a small working model of the required system.

Step 4: Customer evaluation

In this stage, the proposed system is presented to the client for an initial
evaluation. It helps to find out the strength and weakness of the working
model. Comment and suggestion are collected from the customer and
provided to the developer.

Step 5: Refining prototype

If the user is not happy with the current prototype, you need to refine the
prototype according to the user's feedback and suggestions.

This phase will not over until all the requirements specified by the user are
met. Once the user is satisfied with the developed prototype, a final system
is developed based on the approved final prototype.

Step 6: Implement Product and Maintain

Once the final system is developed based on the final prototype, it is

thoroughly tested and deployed to production. The system undergoes routine
maintenance for minimizing downtime and prevents large-scale failures.

4.6 COST ESTIMATION

Studies within the last few years have shown that a great deal more money is
often spent on projects than is initially anticipated. IBM's Consulting Group
did a survey of 24 leading companies in 1994 and found that 55% of the
software developed cost more than the initial cost estimates (Hussein,
2002a). The Standish Group also did a study in 1994 of 8,380 projects in the
United States and found that 53% of the software projects that were completed
cost 189% of the original estimates (Hussein, 2002a). Although these numbers
are from a few years ago, they likely have not changed much recently
(Hussein, 2002b). The problem of making accurate cost estimates can be
attributed to a number of reasons: the wrong cost estimation processes may
be used, no processes may be used, or the nature of the problem may not allow
for accurate cost estimation. Cost estimation is an often overlooked project
management practice. Defining Cost Estimation: Cost estimation can be
defined as the
approximate judgment of the costs for a project. Cost estimation will never
be an exact science because there are too many variables involved in the
calculation for a cost estimate, such as human, technical, environmental, and
political. Furthermore, any process that involves a significant human factor
can never be exact because humans are far too complex to be entirely
predictable. Furthermore, software development for any fair-sized project will
inevitably include a number of tasks that have complexities that are difficult to
judge because of the complexity of software systems. Cost estimation is usually
measured in terms of effort. The most common metric used is person months
or years (or man months or years). The effort is the amount of time for one
person to work for a certain period of time.

Cost Estimation and Project Planning

Cost estimation is an important tool that can affect the planning and budgeting
of a project. Because there are a finite number of resources for a project,
all of the features of a requirements document can often not all be included
in the final product. A cost estimate done at the beginning of a project will
help determine which features can be included within the resource constraints
of the project (e.g., time). Requirements can be prioritized to ensure that the
most important features are included in the product. The risk of a project is
reduced when the most important features are included at the beginning
because the complexity of a project increases with its size, which means
there is more opportunity for mistakes as development progresses. Thus,
cost estimation can have a big impact on the life cycle and schedule for a
project.

Cost Estimation during the Software Life Cycle

Cost estimation should be done throughout the entire life cycle. The first time
cost estimation can be done is at the beginning of the project after the
requirements have been outlined. Cost estimation may even be done more than
once at the beginning of the project. For example, several companies may bid
on a contract based on some preliminary or initial requirements, and then once
a company wins the bid, a second round of estimation could be done with more
refined and detailed requirements. Doing cost estimation during the entire life
cycle allows
for the refinement of the estimate because there is more data available.

4.7 PROJECT SCHEDULING

The project scheduling is the tool that communicates what works needs to be
performed, which resources of the organization will perform the work and the
timeframes in which that work need to be performed. The project schedule
should reflect all of the work associated with delivering the project of time.
Without a full and complete schedule, the project manager will be unable to
communicate the complete effort, in terms of cost and resources, necessary to
deliver the project. The online project management software allows project
managers to track project schedules, resources, budgets and project related
assets in real time. The project schedule can be viewed and updated by team
members associated with project, keeping everyone well informed on the
overall projects. Project scheduling is simple when managed online,
thankfully, especially since the software does all the hard part for you! Before
going deeper into project scheduling, let‘s review the fundamentals to project
scheduling. Project scheduling occurs during the planning phase of the project.
You have to ask yourself three questions to start:

1. What needs to be done?

2. When will it be done?

3. Who will do it? Once you‘ve got answers to these questions, then you can
begin to plan dates, link activities, set the duration, milestones and resources.

The following are the steps needed to schedule a project:

Define Activities:

What are the activities that you have to do in the project? By using a Work
Breakdown Structure (WBS) and a deliverables diagram, you can begin to
take these activities and organize them by mapping out the tasks necessary to
complete them in an order than makes sense.

Do Estimates:

Now that you have the activities defined and broken down into tasks, you
next have to determine the time and effort it will take to complete them. This
is an essential piece of the equation in order to calculate the correct schedule.

Determine Dependencies:
Tasks are not an island, and often one cannot be started until the other is
completed. That‘s called a task dependency, and your schedule is going to
have to reflect these linked tasks. One way to do this is by putting a bit of slack
in your schedule to accommodate these related tasks.

Assign Resources:

The last step to finalizing your planned schedule is to decide on what resources
you are going to need to get those tasks done on time. You‘re going to have to
assemble a team, and their time will need to be scheduled just like the tasks.

How to Maintain/ Schedule Once the Project Is Initiated:

Once we‘ve got all the pieces of your schedule together, the last thing you
want to do is manually punch it into a static document like an Excel
spreadsheet. Project management software can automate much of the process
for you. But not all project management software is the same. There are
programs on the market that are great for simple scheduling duties, but when
leading a project, big or small, we need a tool that can adapt to the
variety of scheduling issues you‘re going to need to track. Like noted above,
there are three tiers of scheduling: tasks, people and projects.

Project management:

The three main focus areas of the project management are reporting,
monitoring and risk management. These are covered during the whole lifecycle
of the project through three main processes:

 Analysis of project capability

 Project planning
 Project monitoring and control
5. SYSTEM DESIGN
In this phase, a logical system is built which fulfils the given requirements.
Design phase of software development deals with transforming the client’s
requirements into a logically working system. Normally, design is performed
in the following two steps:
  Primary Design Phase:
In this phase, the system is designed at block level. The blocks are
created on the basis of analysis done in the problem identification phase.
Different blocks are created for different functions emphasis is put on
minimizing the information flow between blocks. Thus, all activities
which require more interaction are kept in one block.
 Secondary Design Phase:
In this phase, the detailed design of every block is performed.

The general tasks involved in the design are the following:

• Design various blocks for overall system processes.

• Design smaller, compact and workable module in each block.
• Design various database structures.
• Specify details of programs to achieve desired functionality.
• Design the form of inputs and output of the system.
• Perform documentation of the design.
• System reviews

5.1 PROJECT PLANNING

Project planning is part of project management, which relates to the use of

schedules such as Gantt chart to plan and subsequently report progress within
the project environment. Initially, the project scope is defined and the
appropriate methods for completing the project and determined. Following
this step, the duration for the various tasks necessary to complete the work and
listed and grouped into a work breakdown structure. Project planning is often
used to organize different areas of project, including project plans, work load
and the management of teams and individuals. The logic dependencies of the
critical path. Project planning is inherently uncertain as it must be done before
the project is actually started.

Here’s the planning of the project:

 For registration of Vaccination, system will ask for:-

I. Name of the patient,
I. First name,
II. Middle name,
III. Last name
II. E-Mail Id of patient,
III. Address of patient,
IV. Age of patient,
V. Gender of patient,
VI. Aadhar Number of patient,
VII. Date Of Birth of patient,
VIII. Phone Number of patient
IX. Password for Login in future,
X. Test Reports required,
XI. Vaccine required.
 For Login for Admin:
 Name of the admin
 Password for login
 For information about Vaccine:-
 Vaccine name
 Vaccine Company
 Availability of doses
 Durability
 Expiry of Vaccine
 Vaccine cost

5.2 MODULES

We know that it‘s quite difficult to do anything of its whole part at a time. So,
It‘s the task of the programmer to split the whole set of task into various
small module so that one can handle them effectively. But it depends upon the
software system that in which Extent it will be broken so that there is no inter
dependency among them.

This project developed for” VACCINE MANAGEMENT SYSTEM” is broken into

following module:

 Patient Module
In this module, the patient will be asked to enter his login id and password as per the
choice and then the user will be given access to use the vaccine management system
and will be allowed to have access to other modules of the software.

 Booking Module:
In this module, the patients will be allowed to book the vaccines as per their
requirement and the status of availability of vaccine and the booking status will be
visible to the user.
 Appointment Module:
In this module, the status of the appointment of the patient with the doctor and their
date, day and time of receiving the vaccine will be visible to the user. Also with this
the admin can see the appointments for the day. This module will also send
notification for the reminder.
 Vaccine Management:
In this module, the vaccine available in the Vaccination Center and the amount of
doses that can be given to the patient will be kept in track.
 Test Management:
In this module, the tests that the patients has uploaded or the tests that the patients
wishes to be conducted at the time of his appointment will be displayed here. Both the
user and the admin will be able to have access to this module. Patients can upload
new reports here too.

 Vaccination Center Management:

In this module, the users will get the information about the opening and closing time
of the center and the information about the doctor, health workers etc.
5.3 DATA FLOW DIAGRAM
A Data Flow Diagram (DFD) is a diagram that describes the flow of data and
the processes that change data throughout a system. It is a structured analysis
and design tool that can be used for flowcharting in place of or in association
with information. Oriented and process oriented system flowcharts. When
analysts prepare the Data Flow Diagram, they specify the user needs at a level
of detail that virtually determines the information flow into and out of
the system and the required data resources. This network is constructed by
using a set of symbols that do not imply physical implementations. The Data
Flow Diagram reviews the current physical system, prepares input and output
specifications, specifies the implementation plan etc. Four basic symbols are
used to construct data flow diagrams. They are symbols that represent data
source, data flows, and data transformation and data storage. The points at
which data are transformed are represented by enclosed figures, usually circles,
which are called nodes.

DATA FLOW DIAGRAM SYMBOLS

ZERO LEVEL DED:
 Vaccination
Center
Management

Vaccine
Vaccine Management Test
Management Management
System

Patient
Management

FIRST LEVEL DED:

5.4 E-R DIAGRAM
The entity relationship data model is based on apperception of a real world that consists of
a collection of basic objects called entities and relationship among these objects. The ER
data model is used in available DBMS to model application database. Earlier commercial
systems were based on the hierarchical and network approach. The entity relationship
model is generalization of these models. It allows this representation of explicit constraints
as well as relationships. An entity is a thing or object in the real world that is distinguishable
from other objects. Entities are described in a database by a set of attributes. Even though
the ER model has some means of describing the physical database model it is basically
useful in the design and communication of the logical database.

E-R DIGARAM SYMBOLS:

ENTITY RELATIONSHIP DIAGRAM:

 5.5 DATABASE DESIGN

I. PATIENT TABLE:

ATTRIBUTES DATA TYPE SIZE

patient_id varchar 50

aadhar_id varchar 50

login_id varchar 50

Passwd varchar 50

Fname varchar 50

Mname varchar 50

Lname varchar 50

Address varchar 50

Age integer -----

Gender varchar 50

DOB varchar 50

phone_no integer -----

email_id varchar 50

test_report file MAX

vac_name varchar 50

II. ADMIN TABLE:

 ATTRIBUTE DATA TYPE SIZE

admin_id varchar 50

admin_pass varchar 50

III. VACCINE TABLE:

ATTRIBUTE DATA TYPE SIZE

vac_name varchar 50

vac_comp varchar 50

vac_doses varchar 50

vac_dura varchar 50

vac_exp varchar 50

vac_cost varchar 50
IV. APPOINTMENT TABLE:

ATTRIBUTES DATA TYPE SIZE

p_name varchar 50

time varchar 50

date varchar 50

phone no. integer -----

vac_name varchar 50

V. BOOKING TABLE:

ATTRIBUTES DATA TYPE SIZE

book_id varchar 50

book_time varchar 50

book_date varchar 50

book_transaction integer -----

VI. TEST TABLE:

ATTRIBUTES DATA TYPE SIZE

 blood_test file MAX

diabetes file MAX

Covid_19 file MAX

blood_sugar_level file MAX

other file MAX

5.6 SCREENSHOTS

FIRST PAGE:
Home screen will appear first, when the user start page shown and Login screen will appear
after successful user registration. Enter username, password and capture code.

MENU PAGE:
After login user, it will enter in MENU page.
1 for add data to Book appointment, 2 for view vaccine data, 3 for search, 4 for exit.

BOOK APPOINTMENT:
After enter the all details the appointment will conform.
VACCINATED STATUS:
It is show the vaccinated people detail.
VACCINE STATISTICS:

It is to show the number of available vaccine.

 6. TESTING
 Objective:
 The objective our test plan is to find and report as many bugs as possible
to improve the integrity of our program. Although exhaustive testing is
not possible, we will exercise a broad range of tests to achieve our goal.
We will also test the user friendliness of our app .The application will
24 be used as an important tool, but we would like to ensure that it
could be run on a variety of platforms with little impact on
performance or usability.

 Process Overview:
The following represents the overall flow of the testing process:
• Identify the requirements to be tested. All test cases shall be derived using the
current Program Specification.
• Identify which particular test(s) will be used to test each module.
• Review the test data and test cases to ensure that the unit has been thoroughly
verified and that the test data and test cases are adequate to verify proper
operation of the unit.
• Identify the expected results for each test.
• Document the test case configuration, test data, and expected results.
• Perform the test(s).
• Document the test data, test cases, and test configuration used during the
testing 25 process. This information shall be submitted via the Unit/System
Test Report (STR).
• Successful unit testing is required before the unit is eligible for
component integration/system testing.
• Unsuccessful testing requires a Bug Report Form to be generated. This
document shall describe the test case, the problem encountered, it’s
possible cause, and the sequence of events that led to the problem. It
shall be used as a basis for later technical analysis.
• Test documents and reports shall be submitted. Any specifications to be
reviewed, revised, or updated shall be handled immediately.

Testing Process:
The diagram above outlines the Test Process approach that will be followed.

• Organize Project: Involves creating a System Test Plan, Schedule & Test
Approach, and assigning responsibilities.
• Design/Build System Test: Involves identifying Test Cycles, Test Cases,
Entrance & Exit Criteria, Expected Results, etc. In general, test
conditions/expected results will be identified by the Test Team in conjunction
with the Development Team. The Test Team will then identify Test Cases
and the Data required. The Test conditions are derived from the Program
Specifications Document.
• Design/Build Test Procedures: Includes setting up procedures such as
Error Management systems and Status reporting.
• Build Test Environment: Includes requesting/building hardware, software
and data setups.
• Execute System Tests: Identified in the Design/Build Test Procedures
will be executed. All results will be documented and Bug Report Forms filled
out and given to the Development Team as necessary.
• Signoff happens when all pre-defined exit criteria have been achieved.

Testing Strategy:
The following outlines the types of testing that will be done for unit, integration, and
system testing. While it includes what will be tested, the specific use cases that
determine how the testing is done will be detailed in the Test Design Document. The test
cases that will be used for designing use cases are shown below.

Test Cases:

Tested By Abhay, Aman

Test Type Unit Testing
Test Case Number 1
Test Case Name Login
Test Case Description The user should give any username and
password.

Item(s) to be tested
1 Verification of login
Specifications
Input Expected output/Result
Type the username and password Successful welcome
Logout Page exits

TABLE 2:
Tested By Abhay, Aman
Test Type Unit Testing
Test Case Number 2
Test Case Name Checking 1
Test Case Description The user should add user details.

Item(s) to be tested
1 Verification of user will complete.

Specifications
Input Expected output / Result
Check the score and popup message Message will be show vaccinated.

Logout Page exits

7. IMPLEMENTATION & MAINTANCE

INTRODUCTION:
Maintenance of the project is very easy due to its modular design and
concept any modification can be done very easily. All the data are stored in
the software as per user need & if user wants to change he has to change that
particular data, as it will be reflected in the software everywhere. Some of the
maintenance applied is:

BREAKDOWN MAINTENANCE:

The maintenance is applied when an error occurs & system halts and further
processing cannot be done .At this time user can view documentation or consult
us for rectification & we will analyze and change the code if needed. Example:
- If user gets a error ―report width is larger than paper size‖ while printing
report & reports cannot be generated then by viewing the help documentation
& changing the paper size to A4‘ size of default printer will rectify the
problem.”

PREVENTATIVE MAINTENANCE:

User does this maintenance at regular intervals for smooth functioning

(Operation) of software as per procedure and steps mentioned in the manual.
Some reasons for maintenance are:-

• Error Correction: Errors, which were not caught during testing, after the
system has, been implemented. Rectification of such errors is called corrective
maintenance.

• New or changed requirements: When Organization requirements changes

due to changing opportunities.
• Improved performance or maintenance requirements: Changes that is made
to improve system performance or to make it easier to maintain in the future
are called preventive maintenance. Advances in technology (Adaptive
maintenance): - Adaptive maintenance includes all the changes made to a
system in order to introduce a new technology.

SECURITY MEASURES:
The security measures imposed in the software are: -
 A login password is provided in the software. User must login to activate the
application.
 User cannot change the password. To change password he must contact the
administrator.
 The user/password is given through Django server. If it is installed on
Windows, then run in degraded mode.
 Data security, correctness integrity is checked up before saving, update
or delete if errors found the procedure is aborted.
 A primary key & foreign key concept is implemented for avoiding
incorrect data entry or intentional or accidental delete or modification of
data.
 When user tries to delete the data then this first check for its reference
used by other data, if found the deletion aborted. I am also providing
various securities at user level or at forms.
 8. FUTURE SCOPE OF THE PROJECT

Advanced Technology:

It is an Advanced Technology used nowadays. It increases the E- Knowledge of the user

which is very important for the current generation of growing world. This Vaccine
Management System also helps in enhancing the knowledge of internet to the users.

Internet:

This Vaccine Management System is an online facility and hence very useful for the users.
Patients can book an appointment for vaccination at any time of the day and from any place
of the country as per their choice. This can help in reducing the rush at the Vaccination
Centers.

E-Mails:

Login Credentials for the Users can be sent directly to the registered E- Mail address which
will help in maintaining the privacy of the user .Users can also get information and updates
related to their vaccination programs as per the schedule.

E- SMS:

Sometimes the Hospitals or the Vaccination Centers want to send message to the registered
mobile number regards the updates of the availability of the vaccines and doctors, they can
use this facility of the Vaccine Management System. The information can be sent to
multiple users in no time.

Finger Print and Face Detection:

In future, Vaccine Management System can be made more secure by using the technology
such as finger print recognition or Face Detection Techniques. This will ensure the users safe
and error free vaccination.
 9. LIMITATIONS OF THE PROJECT

Although we have put our best effects to make the software flexible, easy to operate but
limitation cannot be ruled out even by us. Though the software present a broad range of
options to its users some intricate option could not be covered into it.

A number of new vaccine have been rolled out across the developing world, cold chain
system are struggling to efficiently support national immunization programs in ensuring the
availability of safe and potent vaccine.

Considerable effects have made the software east to operate even for the people not related to
the field of Computers but it is acknowledged that a layman may find it a bit problematic at
the first instance .The user is provided help at each step for his convenience in working with
the software.

Some other limitations:

 The system may indicate some errors if the database is not updated as per the
availability of vaccines.
 Patients may not get required date and time as per the schedule.
 There may be some problems in generation of LOGIN ID and PASSWORD as if the
information provided does not meet the requirements.
 REFERENCES
Websites:-
 https://www.cronj.com
 https://www.javatpoint.com/phthon-tutorial
 https://www.w3schools.com/python
 https://www.quora.com/
 https://www.w3schools.com/css/

Books:-
 HTML & CSS – Jon Duckett
PYTHON For BEGINNERS—Denny Novikov
 PYTHON PROGRAMMING –Ryan Turner