TABLE OF CONTENT

CHAPTER-1
INTRODUCTION

CHAPTER-2
COMPANY AND INDUSTRY PROFILE

CHAPTER-3
SYSTEM STUDY

CHAPTER-4
SYSTEM DESIGN

CHAPTER-5
SYSTEM DEVELOPMENT & TESTING

CHAPTER-6
CONCLUSION
 CHAPTER-1
INTRODUCTION
 INTRODUCTION

ThemainobjectiveistodevelopaPHPbasedwebapplicationnamed“ClinicAppointment Sys-
tem” that covers all the aspects of making appointment of doctors. It enables healthcare provid-
ers to improve operational effectiveness, reduce costs, reduce medical errors, reduce time con-
sumption and enhance delivery of quality of care.

This system help reduce the problems occur when using the manual system and helps pa-
tientstoskipendlessqueues.Theimportantthingisitwillbecomeeasierforthedatarecordand retrieval.
This software also stores all the patient details, patients profile, prescriptions etc. This sys-
temenablesdoctorsandclinicassistanttomanagepatientrecordsandappointments.Usercan enter their
details, update their profile and they can select doctors to make appointments. Other than that,
the system is user friendlyand it can help the clinic to manage their appointments. The system-
helpstoavoidmakingduplicate appointments. Userscanview availabledoctorsandtheir timings and
can make appointments according to it. Users also get an option to cancel their appointments.
Users can view their upcoming appointments and past appointments are deleted automatically.

The system also allows doctors to log in. Doctors can edit their profile and view their up-
coming appointments, patients etc. They can even send prescriptions to their patients by select-
ing their patients from the dropdown list.

The system also has an administrator section, where only a single person can manage the
whole system. Administrator can add/remove patients, doctors and departments and search for
appointments.

The system features a very intuitive and responsive design that fits devices of all screen
size (Smartphones, PCs, Tablets, and Notebooks etc.). The application automatically adapts its
layout to match user’s screen size.
 CHAPTER-2
INDUSTRY AND COMPANY PROFILE
 INDUSTRY PROFILE

The Software industry includes business for development, maintenance and publication of software that are
using different business models, mainly either “license/ maintenance basd” or “ Cloud Based” (such as
SaaS, PaaS, IaaS, MBaaS, MSaaS, DCaaS, etc.) The industry also include software services such as train-
ing, documentation, consulting and date recovery. The software and computer services industry spends
mote than 11% of its net sales for Research & Development which is in comparison with other industries
the second highest share after pharmaceuticals & biotechnology.

The first company founded to provide software products and services was Computer Usage Company in
1955.[2] Before that time, computers were programmed either by customers, or the few commercial com-
puter vendors of the time, such as Sperry Rand and IBM.

The software industry expanded in the early 1960s, almost immediately after computers were first sold in
mass-produced quantities. Universities, government, and business customers created a demand for soft-
ware. Many of these programs were written in-house by full-time staff programmers. Some were distribut-
ed freely between users of a particular machine for no charge. Others were done on a commercial basis,
and other firms such as Computer Sciences Corporation (founded in 1959) started to grow. Other influen-
tial or typical software companies begun in the early 1960s included Advanced Computer tech-
niques, Automatic Data Processing, Applied Data Research, and Informatics General.[3][4] The comput-
er/hardware makers started bundling operating systems, systems software and programming environments
with their machines.

When Digital Equipment Corporation (DEC) brought a relatively low-priced microcomputer to market, it
brought computing within the reach of many more companies and universities worldwide, and it spawned
great innovation in terms of new, powerful programming languages and methodologies. New software was
built for microcomputers, so other manufacturers including IBM, followed DEC's example quickly, result-
ing in the IBM AS/400 amongst others.

The industry expanded greatly with the rise of the personal computer ("PC") in the mid-1970s, which
brought desktop computing to the office worker for the first time. In the following years, it also created a
growing market for games, applications, and utilities. DOS, Microsoft's first operating system product, was
the dominant operating system at the time.

In the early years of the 21st century, another successful business model has arisen for hosted software,
called software-as-a-service, or SaaS; this was at least the third time[citation needed] this model had been
attempted. From the point of view of producers of some proprietary software, SaaS reduces the concerns
about unauthorized copying, since it can only be accessed through the Web, and by definition no client
software is loaded onto the end user's PC.

Size Of Industry

The global software products market amounts to US$968.25 billion in 2021 and had a compound annual
growth rate (CAGR) of 4%. Major companies include Microsoft, HP, Oracle, Dell and IBM.
Business models within the software industry

Business models of software companies have been widely discussed. Network effects in software ecosys-
tems, networks of companies, and their customers are an important element in the strategy of software
companies.
 COMPANY PROFILE

Company Name: SINFO TECH PRIATE LIMITED

Industry: Software Services & IT Industry
Founder& Chairman: SIIVA RAM KRESHNA. VASANTHA
Founded: 07th May 2020
Head Quarters: Vijayawada
Country: India
Area Served: India

About Sinfo Tech Private Limited

SINFO TECH is a leader in IT services, digital and business solutions. We partner with our clients to sim-
plify, strengthen and transform their businesses to help them reach success. We ensure the highest levels of
certainty and satisfaction through our deep-rooted commitments.
With our comprehensive industry expertise, network of innovation and delivery centers, we make sure that
all our clients get exactly what they want.
Established in 2020, SINFO TECH has grown to significant heights. Through our outstanding service rec-
ord, collaborative partnerships, innovation and corporate responsibility, we have become a significant
player in IT services.
Vision
Our vision is to contribute to the success of our clients. We contribute to our client’s success in whatever
enormity by ensuring that we understand the complete picture.
Our vision is to deliver so much value to our customers that they know that we are their strategic partners
for success.
Our vision is to ensure that we grow because our clients grow.

SINFO TECH prides itself on the long-term relationships

SINFO TECH has worked extensively on multiple technologies spanning various domains addressing is-
sues in various industries. The Company has evolved over time and has built in-house proficiencies and
expertise in various areas from:
• Mobile App development
• Web development
• Backend process automation
• Parallel Processing systems
• Systems with large transactional volumes requiring distributed processing
• Systems with inbuilt redundancy both within a facility and across multiple facilities

Leadership
Siiva Ram KreshnaVasantha
(Founder & Chairman)
He started SINFO TECH with a vision to create an organization that combined IT with innovative ideas to
build solutions that benefited a wide range of users and industries. Exceptionally Self- Motivated and Di-
rected. He analyses, evaluates and motivates team- oriented collaborative environment. A part from han-
dling the end-to-end chain of work and with 10 years of experience in corporate development emerging
business.
He Post Graduated from the Business Management and Business Administration Program from the Uni-
versity of Andhra. He has a B.S. in Computer Science from the AcharyaNagarjuna University.
Aravind Krishna Kurapati
(Chief Operating Officer)
He holds a Degree in Software Engineering from Madras University. He has been Director - Operations of
SINFO TECH. He is considered a pioneer in the field, highly respected amongst his peers and his views
are sought in the field of software technology.
SrinivasaraoGude
(Director – F&A)
GudeSrinivasa Rao has a proven record of success in financial and operations management and leadership.
He has appeared ICAI and holds a B. Com in Accounting from the AcharyaNagarjuna University. He has
vast experience in Internal Operations.
KogantiSukanyaChowdary
Associate Director - Technical
She holds a Degree in Computer Science Engineering from JNTU. She has been Associate Director -
Technical of SINFO TECH. She has instituted ground breaking software development practices ensuring
optimal utilization of resources, on time delivery and best in class software quality and services all geared
towards ensuring customer satisfaction for SINFO TECH.
Siva Krishna Gorla
Project Manager and Tech Lead
He holds a Master Degree in Computer Science Engineering from JNTU. He has been Project Manager
and Tech Lead of SINFO TECH. And he has over 10+ years of experience In corporate development and
emerging business. He leads the technical team with precision and passion. Siva encourage team work, ap-
proach and innovation.
 CHAPTER-3
SYSTEM STUDY& ANALYSIS
 SYSTEM STUDY

Systemstudyisthefirststageofsystemdevelopmentlifecycle.Thisgivesaclear pic-
tureofwhatactuallythephysicalsystemis.Thesystemisdoneintwophase.Inthefirstphase, the prelimi-
narysurveyof the system is done which helps in identifythe scope of the system. The second
phase of the system study is more detailed and in-depth study in which the identification of us-
er’s requirement and limitations and problem of the present system are studied. After completing
the system study, a proposal is prepared by the user.

EXISTING SYSTEM
Presently people are making appointments manually. This is a time consuming process, patient
has to physically go to the clinic in order to make appointment. Some clinics provide the oppor-
tunity to make appointments by placing a phone call. But in this case, people are often left unat-
tended.

LIMITATIONS OFEXISTINGSYSTEM
Byanalyzingtheexistingsystem, someof its drawbacksarelisted.
1. Time consuming.
2. Lackof efficiency.
3. Needsto bephysicallypresent at the clinic.
4. Can’tmakeappointmentsinadvanceforlongintervals.

FACT FINDING

The major task of system study is fact finding, in this stage data collection is done in various
methods which are,

 Reviewof writtendocument:
All documentation data carriers-forms, records reports, manuals, etc. was re-
viewed,organizedandevaluated.Reviewallthedocumentswhichcontainthelocations,categoriesand
 the others by the help of maps. The methodof recording eachand every detail of location-
swere studied and noted.

 On-site observation:

Here the operation and physical layout of the current system were studied by direct
observation of the operation /physical layout. The method directed toward describing and
understanding events and behavior as they occur.

 Interviews and questionnaires:

People usually provide the best source of information and hence personal interviews
with the patients. Provide questionnaires to selected persons to collect data.

PROPOSED SYSTEM
Proposed system will overcome the drawbacks of existing system. Existing system is
manual and available appointment applications are not user friendly. Proposed system is com-
puterized and user friendly. The proposed system has many advantages.

MERITS OF PROPOSED SYSTEM

Theuseofproposedsystemwillavoidtheproblemsoftheexistingsystemandwealsoget a new
system for managing information under the Clinic Appointment System. The proposed system
offers:

 Manualwork whichis timeconsumingcanbereduced.

 Easyto storedata in thedatabase.
 Administratorcanadd/removenew doctors,patients& departments.
 Increaseprocessingspeed.
 Aneasilyaccessenvironment for users.
 Doctorscanview/cancelappointments.
 Doctorscansendprescription.
 Automatic removal ofpast appointments.
 Easyto usereal timesearch facility.
 Responsivelayoutthatfitsall devices.
 Improvedsecurity.
 SYSTEM ANALYSIS

System analysis is the detailed study of the various operations performed by the system
and relationship within and outsidethesystem. It is themost essential part ofthedevelopment of
the project. During system analysis data are collected on the available file, decisions points and
transactionshandledbythepresencesystem.Systemanalysismustcarryoutacustomaryapproach to the
use of computers for the problem solving. Nowadays systems are so big and complex that teams
of architectures, analyst, programmers, testers and users must work together to create the mil-
lionsoflinesofcustom-returncodethatdriveourenterprise.Assumingthatanewsystemisto bedevel-
oped, thenext phaseis system analysis. Analysis involved adetailedstudyofthe current system,
leading to specification of a new system.

SYSTEM REQUIREMENTS

SOFTWARE AND HARDWARE REQUIREMENT

The software requirement specification (SRS) and hardware specification forms the basis
of software development. A main purpose of software requirement specification is the clear defi-
nitionandspecificationoffunctionalityandofthesoftwareproduct.Itallowsthedeveloperto be carried
out, performance level to be obtained and corresponding interface to be established.

HARDWARE REQUIREMENTS
Processor:IntelPentium
Monitor size: 14 inch

RAM: 256MB

HardDisk:80GB

SOFTWAREREQUIREMENTS
Technology :Web Application.
Front end :PHP, HTML, JQuery, Bootstrap & CSS.
Back end :MySQL.
Web browser: Mozilla Firefox, Google Chrome, Apple Safari or any Gecko/Web Kit based
browser.
 CHAPTER-4
SYSTEM DESIGN
 SYSTEM DESIGN

Designisthefirststepinthe developmentphaseforanyengineeredproductorsystem. It may-

bedefined“Theprocessofapplyingvarioustechniquesprinciplesforthepurposeofdefining a device, a
processor or a system in sufficient to permit its physical realization.
System design is the creation of specification for a new system. It deals with creation of
input, which is usually the acquiring of needed data, creation of needed database, the input pro-
cedures and output to meet system objectives.

INITIALDESIGN
MAINMODULES:-
Main modules of these systems are given below.

1. ADMINMODULE:-
 AddNew User

Administrator can add new user by filling out required fields.

 RemoveExistingUser

Administrator can remove existing user by selecting user ID from the drop down box.
 Doctor registration

Administrator can add doctors and assign them duty times and schedules.
 RemoveExistingDoctor

Remove existing doctors by selecting them from a drop down menu.

 Add New Department

The administrator can add new department by entering its name.

 RemoveExistingDepartment

Administrator can remove existing departments.

2. USERMODULE: -

 UserRegistration

Registering the user by the details that includes Name, Username, Email Address, Pass-
word, Residential Address, Phone Number, Gender etc.

 Profile
User scaned it and update their profile including their password.

 Doctors List
User scan browse through the entire list of doctors and select one for making ap-
pointment.

 View Prescription
User can view, print or delete prescriptions sent by doctors.

 Upcoming Appointments
Usercanview/deleteupcomingappointments.Pastappointmentsare automatically
removed from the list to show only the relevant contents.

 Make Appointment
User can search desired departments using the intelligent, auto filling search en-
gine.Theformshowssuggestions/getsautomaticallyfilledasuserstartstyping.The search re-
sult shows relevant doctors list with available time, days etc. User can click make ap-
pointment and they get redirected to the date and time selection page. After selecting de-
sired date, the system returns to user with an appointment ID.

 Notifications
Usercanview notificationsifone his/her appointmentrequest hasbeenmarkedas
‘Pending’ by the doctor.
 3. DOCTORMODULE: -

 Doctor Profile

Doctors can edit their profile details such as Name, Qualification etc.
 SendPrescription

Doctor selects their patient name, appointment ID to send prescription.

 Upcoming Appointments

Doctors can view their upcoming appointments here. They can change appoint-
mentstatustoPendingorActive.Theycanevencanceltheappointment.

DATAFLOWDIAGRAM (DFD)

Generally, DFD’s are used as a design not ationto represents architectural design (Exter-
nal design) and top level design (internal design) specifications. DFD’s represent the system in
hierarchical manner with one top level and many lower level diagrams with each representing
separate parts of the system. A DFD shows what kind of information will be input to and output
from the system, where the data will come from and go to, and where the data will be stored. It
does not show information about the timing of processes, or information about whether processes
willoperateinsequenceorinparallelSincediagrammaticrepresentationsareeasiertointerpretas com-
pared to the technical descriptions, the non-technical users can also understand the system details
clearly. DFD consists of four basic notations which help to depict the information in the sys-
tem.These notations are rectangle, circle, open-ended rectangle, and arrows.
Rectangle Represents an external entity that is the source or destination of data
within the system. Each external entity is represented by a meaningful and
unique name.
Representprocessesthatsowtransformationormanipulationofdata within the
system
Representdatastoresthatindicatetheplaceforstoringinformation within the system.

Theyareusedtorepresentdataflowsthatshowthemovementof data from its

source to destination within the system.

Admin

Clinic Appointment Clinic

Doctor System

User
 Level 1.1

Login Admin Login

Admin

Add user User Information

Remove user

User Login
Add Doctor

Doctor
Remove Doctor

Department
Add Department

appointment
Remove Department

Search Appointment

Update Appointment

Cancel Appointment
Doctor Doctor
Login

Prescription
Edit Profile

appointment
Send Prescrip-
tion

View Appoint-
ment

Change Ap-
pointment

Cancel Ap-
pointment
ER DIAGRAM

An entity–relationship model (ER model) is a data model for describing the data or in-
formation aspects of a business do main or its process requirements, in an abstract way that lends
itself to ultimately being implemented in a databasesuch as arelational database. The main com-
ponents of ER models areentities(things) and the relationships that can exist among them, and
databases. An entitymay be defined as a thing capable of an independent existence that can be
uniquely identified. An entity is an abstraction from the complexities of a domain. When we
speak of an entity, we normally speak of some aspect of the real world that can be distinguished
fromotheraspectsoftherealworld.Arelationshipcaptureshowentitiesarerelatedtooneanother. Rela-
tionship scan be thought of as verbs, linking two or more nouns. Examples: an owns relationship
between a company and a computer, a supervises relationship between an employee and a de-
partment, a performs relationship between an art istanda song, aprovedrelationshipbetweena-
mathematicianandatheorem.Entitiesandrelationshipscanboth have attributes. Every entity (unless
it is a weak entity) must have a minimal set of uniquely identifyingattributes, which is called the
entity's primarykey. Entity–relationship diagrams don't showsingleentitiesorsingleinstancesofre-
lations.Rather,theyshowentitysetsandrelationship sets.

ER DiagramNotations

Entity

Weakentity

Relationship

Attribute

Key Attribute

1.1 DATABASE DESIGN

 Database designis the process of producing a detailed data model of a database. This log-
icaldatamodelcontainsalltheneededlogicalandphysicaldesignchoicesandphysicalstorage parame-
tersneededtogeneratea design inadatadefinitionlanguage,whichcanthenbeusedto

 Determinetherelationshipsbetweenthedifferent dataelements.

 Superimposealogicalstructureuponthe dataon thebasis oftheserelationships

TheClinicAppointmentSystemuses‘clinic’asitdatabaseforstoringallthedataintablesfor

dataprocessing.

NORMALIZATION

Normalizationistheprocessofdecomposingasetofrelationswithanomaliestoproduce smalle-
randwell-structuredrelationsthatcontain minimumredundancy. It isaformalprocessof deciding
which attributes should be grouped together in a relation. The proposed system has the following
relations:

(1) LOGIN(USER_ID,USERNAME, PASSWORD)

(2) UER_INFORMATION (CLINETNAME, USERNAME, EMAIL, USERPHONE, CLI-

ENT ADDRESS1, CLIENTADDRESS2, GENDER)
(3) DOTOR (DRID, DRNAME, DRUSERNAME, DRPASSWORD, DRDDEPT,
DRQUALI, DAY, TIME)
(4) ADMIN (ADMINNAME, ADMINPASS)

(5) APPOINTMENT (APPOINTMENT_ID, PATIENTNAME, DRUSERNAME,

DRNAME, DEPT, DAY, TIME, STATUS)
(6) DEPARTMENT(DEPT_ID, DEPT_NAME)

(7) PRESCRIPTION TION (PRESC_ID, APPOINTMENT_ID, PATIENTUSERNAME,

DOCTORUSERNAME, CONTENT)
(8) TIMING(COUNT,DOCTOR_ID,DATE)
First Normal Form
First Normal form (1NF)is now considered to be part of the formal definition of relational
model.1NF is designed to disallow multi valued attribute, composite attributes, and their combi-
nations. It states that the domain of an attribute must include only atomic values. Ado main
isatomic, if elements of the domain are considered to be in divisible units. We say that are na-
tional schema R is in 1NF if the domain of all attributes of ‘R’ is atomic. The tables included in
developingthe‘clinic’containatomicvaluesandhenceitisin1NF.The‘user_information’table con-
tains an address field of the user, this fields are divided into fields such aa clientaddress1, clien-
tadress2 for making it indivisible and atomic.

SecondNormalForm

Second Normal form (2NF) is based on the concept of functional dependency. A relation
R is in 2NF if it is in 1NF and every non key attribute A of R is fully dependent on the primary
key. That is, relationissaidtobein2NFifeachattributeAinRmeetsoneofthefollowingcriteria:

(a) Itappearsin theprimarykey.

(b) It isfullyfunctionallydependentontheprimary key.

The tables designed in the proposed system, contain a primary key for uniquely identifying each
user. For e.g.: table login has user_idas a primary key for unique identification of the user. The
table prescription has preside as the primary key and department has dept_id as primary key. All
non-key attributes of the table department sis fully dependent on the primary key dept_id.

Third Normal Form

Third Normal form (3NF) is based on the concept of transitive dependency. A relation is
saidtobein3NFifitisin2NFandhasnotransitivedependencies.Thatisallthenonkeyattribute should be
functionally determined by the primary key. In the proposed system all attributes of tables are
fully depends on the primary key only that is all non-key attributes are mutually independent.
TABLE DESIGN
Table: Login

FIELDNAME DATATYPE SIZE CONSTRAINTS DESCRIPTION

user_id varchar 11 - StoresuserIDofthe
user Auto Incre-
mentedValue
User name varchar 30 Primary Key Stores username.

password varchar 30 - Stores password.

Table: user _information

FIELDNAME DATATYPE SIZE CONSTRAINTS DESCRIPTION
Client name varchar 100 - StoresUserFull
Name.
username varchar 30 Foreign Key Storesusername.

password varchar 30 - Stores password.

email varchar 30 - Storesuser email

address.
User phone bigint 10 - Storesphone number
of user
clientadress1 text - - Storesuser address
line1.
clientaddress2 text - - Storesuser address
line2.
gender varchar 1 - Storesgenderofuser.

Table:doctor
FIELDNAME DATATYPE SIZE CONSTRAINTS DESCRIPTION
Dr id int 11 - StoresdoctorID.Auto
Incremented value.
Dr user name varchar 30 Foreign Key Storesdoctor
Username.
Dr name varchar 60 - Storesdoctorname.

Dr password varchar 60 - Storesdoctor

Password.
 Dr dept varchar 100 - Storesdoctor
Department.
Dr quali varchar 100 - Storesdoctor
Qualification.
day varchar 60 - Storesdayin which
The doctor is availa-
ble.
time varchar 60 - Stores time interval of
the doctor

Table: admin
FIELDNAME DATATYPE SIZE CONSTRAINTS DESCRIPTION
adminname varchar 30 Primary Key Stores Admin
username.
adminpass varchar 60 - Stores admin
password.

Table: appointment

FIELDNAME DATATYPE SIZE CONSTRAINTS DESCRIPTION

appointment_id int 11 Primary Key Storesappointmentid.
Autoincrement num-
ber.
Patient varchar 30 - Storespatient
username username.
Dr user name varchar 30 - Storesdoctor
username.
Dr name varchar 60 - Storesdoctorfull
name.
dept varchar 30 - Storesnameof
departmentwhere
doctorbelongsto.
day varchar 15 - Stores appointment
date.
time varchar 15 - Stores appointment
time.
status varchar 10 - Stores status of the
appointment.Active/
Pending.

Table: Department

FIELDNAME DATATYPE SIZE CONSTRAINTS DESCRIP-

TION
FIELDNAME DATATYPE SIZE CONSTRAINTS DESCRIPTION
presc_id int 11 Primary Key Storesprescriptionid.
Autoincrement num-
ber.
appointment_id int 11 - Storesappointmentid.

Patient varchar 30 - Storespatient

username username.
Doctor varchar 30 - Storesdoctor
username username.
content text - - Storescontentofthe
prescription.
dept_id int 11 Primary Key Storesdepartmen-
tid.
Autoincrement
number.
dept_name varchar 60 - Stores department
Name.

Table: Timing

FIELDNAME DATATYPE SIZE CONSTRAINTS DESCRIPTION

count Int 11 - Storesthenumberof
appointments of a
specificdoctorfora day.

doctor_id varchar 30 - Storesdoctoruser

name.
date varchar 30 - Stores appointment
date

INPUTDESIGN

Input design is the process of converting a user – oriented description of the inputs to a
computerbasedbusinesssystemintoaprogrammer–orientedspecification.Thegoalofdesigning input
datais to makedataentryas easy, logical and freefromerrors as possible. Input design is a
partoftheoverallsystemdesign,whichrequirescarefulattention.Ifthedatagoingintothesystem is in-
correct, then the processing and output will magnify these errors. The proposed system satisfies
the following input design objectives:
 1. Acosteffectivemethodof input.

2. Thehighest possiblelevel of accuracy.

3. Theinput is acceptable to andunderstood bytheuser staff.

Input Objectives are:

i. Controlling the amount of input: Wherever user input is required, the number of
key strokes is reduced by giving possible input values as default in that area. The
viewer canselecttheanswerinsingleclick.Theamountofinformationenteredbytheviewer
using the keyboard is reduced to the maximum and the software is made very user
friendly.
ii. Avoiding Delay: A processing delay resulting from data preparation or data entry
operations is called a bottleneck. Such bottlenecks are avoided to the maximum. Pro-
gressbarorprogressmetersaredisplayedtokeeptheuserwaitingandalsotoshow the speed
and amount of download.

iii. Avoiding Errors in Data: The rate at which errors occur depends on the quantity of
data. Here the quantity of data is reduced to the lowest, and a text file is easily man-
ageable.

iv. Avoiding Extra Steps: The viewer can quit at any point of time. Even at the time of
upload or download the viewer can quit. The viewer need not wait for any specific
event to happen for quitting the process.

v. KeepingtheprocessSimple:Thisimpliesthatthesystemhasallthemeasuretokeep the er-

rors out even if the user is giving wrong data. It handles the situation with grace and
doesn’t create much hype about the situation to the user.

Several activities done in the input stages are:

a. Datarecording→collection ofdataatits source.

b. Datatranscription→ transcriptionof datato aninput form.

 c. Dataconversion →conversion ofthe input datato acomputer acceptablemedium.

d. Dataverification→checkingtheconversion.

e. Datacontrol→checkingtheaccuracyandcontrollingtheflowofthedatatothecomputer.

f. Datatransmission→transmittingor transporting, thedatatothecomputer.

g. Datavalidation&correction→checking&correctingtheerrorstheinputdatabyprogram

When it enters the computer system.

OUTPUT DESIGN

Theoutputfromaninformationsystemshouldaccomplishoneormoreofthe following ob-

jectives:
a. Conveyinformationaboutpastactivities,currentstatusorprojectionsin future.

b. Signalimportantevents,opportunities,problemsorwarnings.

c. Triggeranaction.

d. Confirmtheaction.

a. External Outputs

Manufacturers create and design external outputs for printers. External outputs ena-
ble the system to leave the trigger actions on the part of their recipients or confirm actions to
their recipients.
Someoftheexternaloutputsaredesignedasturnaroundoutputs,whichare implemented as
a form and re-enter the system as an input.

b. Internaloutputs
Internaloutputs arepresent insidethesystem,andused byend-usersand managers.

Theysupport themanagement in decision makingandreporting

 CHAPTER-5
SYSTEM DEVELOPMENT
 SYSTEM DEVELOPMENT

FEATURES OF FRONT END AND BACK END

PHP

PHP (recursive acronym for PHP: Hypertext Pre-processor) is a widely-used open source
general-purpose scripting language that is especially suited for web development and can be
embedded into HTML. It is a server-side scripting language designed primarily for web de-
velopmentbutalsousedasa general-purposeprogramminglanguage.PHPstartedoutasa smallo-
pensourceprojectthatevolvedasmoreandmorepeoplefoundouthowusefulitwas. RasmusLerdorf
unleashed the first version of PHP way back in 1994.

 PHPisaserversidescriptinglanguagethatisembeddedinHTML.Itisusedtomanage dynamic
content, databases, session tracking, even build entire e-commerce sites.
 Itisintegratedwithanumberofpopulardatabases,includingMySQL,PostgreSQL, Ora-
cle, Sybase, Informix, and Microsoft SQL Server.
 PHPispleasinglyzippyinitsexecution,especiallywhencompiledasanApachemodule on the
Unix side. The MySQL server, once started, executes even very complex queries with
huge result sets in record-setting time.
 PHPsupportsalargenumberofmajorprotocolssuchasPOP3,IMAP,andLDAP.PHP4 added
support for Java and distributed object architectures (COM and CORBA), making n-tier
development a possibility for the first time.
 PHPisforgiving:PHPlanguagetriestobe asforgivingaspossible.

 PHPSyntax is C-Like.

Commonuses of PHP include:

 PHPperformssystemfunctions,i.e.fromfilesonasystemitcancreate,open,read, write,
and close them.

 PHPcanhandleforms,i.e.gatherdatafromfiles,savedatatoafile,throughemailyou can send

data, return data to the user.
  Youadd,delete,modifyelementswithinyourdatabasethroughPHP.

 Accesscookiesvariablesandsetcookies.

 UsingPHP,you canrestrictuserstoaccesssome pagesofyour website.

 Itcanencryptdata.

HTML

HTMLstandsforHyperTextMark-upLanguage,whichisthemostwidelyusedlanguageon Web to
develop web pages.

 HypertextreferstothewayinwhichWebpages(HTMLdocuments)arelinkedtogether. Thus
the link available on a webpage are called Hypertext.
 As its name suggests, HTML is a Markup Language which means you use HTML to
simply"mark-up"atextdocumentwithtagsthattellaWebbrowserhowtostructureitto display.

Originally, HTML was developed with the intent of defining the structure of documents like
headings,paragraphs,lists,andsoforthtofacilitatethesharingofscientificinformationbetween re-
searchers.

Now,HTMLisbeingwidelyusedtoformatwebpageswiththehelpofdifferenttagsavailable in HTML
language.

Java Script
JavaScriptisalightweight,interpretedprogramminglanguage.Itisdesignedforcreatingnetwork-
centric applications. It is complimentary to and integrated with Java. JavaScript is very easy to
implementbecauseitisintegratedwithHTML.Itisopenandcross-platform.Itisadynamiccomputer
programming language. It is lightweight and most commonly used as a part of web pag-
es,whoseimplementationsallowclient-sidescripttointeractwiththeuserandmakedynamic pages. It is
an interpreted programming language with object-oriented capabilities.
Characteristics of Java Script are:

 JavaScriptisalightweight,interpretedprogramminglanguage.

 Designedforcreatingnetwork-centricapplications.

 ComplementarytoandintegratedwithJava.

 ComplementarytoandintegratedwithHTML.

 Open and cross-platform.

Advantages of Java Script are:

 Less server interaction−You can valid at user input before sending the page off to the

server. This saves server traffic, which means less load on your server.

 Immediate feedback to the visitors−They don't have to wait for a page reload to see if

They have forgotten to enter something.

 Increased inter activity−You can create interfaces that react when the user hovers over

Them with a mouse or activates them via the keyboard.

 Richerinterfaces−YoucanuseJavaScripttoincludesuchitemsasdrag-and-drop components
and sliders to give a Rich Interface to your site visitors.

MySQL

MySQListhemostpopularOpenSourceRelationalSQLdatabasemanagementsystem.MySQL iso-
neofthebestRDBMSbeingusedfordevelopingweb-basedsoftwareapplications.MySQLis a fast,
easy-to-use RDBMS being used formanysmall and bigbusinesses. MySQLis developed, market-
ed, and supported by MySQL AB, which is a Swedish company. MySQL is becoming so popular
because of many good reasons:

 MySQLis released underan open-sourcelicense.Soyou havenothingtopayto useit.

  MySQLisaverypowerfulprograminitsownright.Ithandlesalargesubsetofthe functionality of
the most expensive and powerful database packages.
 MySQLuses astandardform ofthe well-known SQLdatalanguage.

 MySQLworksonmanyoperatingsystemsandwithmanylanguagesincludingPHP, PERL, C,
C++, JAVA, etc.
 MySQLworks veryquicklyand works well evenwith largedata sets.

 MySQLis veryfriendlyto PHP, themost appreciated languagefor web development.

 MySQLsupportslargedatabases,upto50millionrowsormoreinatable.Thedefaultfile sizelim-
itforatableis4GB,butyoucanincreasethis(ifyouroperatingsystemcanhandle it) to a theoreti-
cal limit of 8 million terabytes (TB).
 MySQLiscustomizable.Theopen-sourceGPLlicenseallowsprogrammerstomodifythe
MySQL software to fit their own specific environments.

PROJECT PLAN

Properprojectmanagementisessentialforthesuccessfulcompletionofasoftwareproject.
Software project management (responsible for project planning) specifies activities necessary to
complete the project. After this, a project schedule is prepared to accomplish the specified tasks.
The purpose of planning and scheduling is to develop the software according to the user re-
quirementswithintheallocatedtimeandbudget.Projectplanningispartofprojectmanagement,
whichrelatestotheuseofschedulessuchasGanttchartstoplanandsubsequentlyreportprogress within
the project environment.

Initially, theproject scopeis defined and the appropriate methods for completing the pro-
ject are determined. Following this step, the durationsfor the various tasksnecessary to complete
thework are listed and grouped into a work breakdown structure. Project planning is often used
to organize different areas of a project, including project plans,workloads and the management of
teams and individuals.The logicaldependenciesbetween tasks are defined using anactivity net-
work diagram that enables identification of the critical path. Project planning is inherentlyuncer-
tainasitmustbedonebeforetheprojectisactuallystarted.Therefore,thedurationof the tasks is often es-
timated through a weighted average of optimistic, normal, and pessimistic cases. The critical
chain method adds "buffers" in the planning to anticipate potential delays in projectexecu-
tion.Floatorslacktimeintheschedulecanbecalculatedusingprojectmanagement soft-
ware.Thenthenecessaryresourcescanbeestimatedandcostsforeachactivitycanbe allocatedtoeachre-
source,givingthetotalprojectcost.Atthisstage,the projectschedulemaybe optimized to achieve the
appropriate balance between resource usageand project duration to comply with the project ob-
jectives. Once established and agreed, the project schedule becomes what is known as the base-
line schedule. Progress will be measured against the baseline schedule through-
outthelifeoftheproject.Analysingprogresscomparedtothebaselinescheduleisknown
asearnedvaluemanagement.Theinputsoftheprojectplanningphaseincludethe project charterand the
concept proposal. The outputs of the project planning phase include the project require-
ments,theprojectschedule,andtheprojectmanagementplan.TheProjectPlanningcanbe donemanual-
ly.However,whenmanagingseveralprojects,itisusuallyeasierandfasterto useproject management
software. The objective of a project plan is to define the approach to be used by the Project team
to deliver the intended project management scope of the project.

 Introduction

Describes the objectives of the project and provides information about the constraints
thataffectthesoftware.Theblooddonationmobileapplication,ClinicAppointmentSystem is-
usedtomakemedicalappointmentsquicklyandeffectivelybytheuser.ClinicAppointment Sys-
temhelpspeopletogetrightinformationaboutdoctors,specializationandavailabilityand let them
to make appointments easily through an intuitive user interface.

 ProjectOrganization

Describes the responsibilities assigned to the project management team members for
completing the project. The system was developed by a single a user, and each task was
completed in fixed time and schedule.

 Risk Analyses

k. Describes the risks that can possibly arise during software development as well as explains
how to assess and reduce the effect of risks. The major risks involved in the software devel-
opment process was to locate blood banks in different places, provide adequateknowl-
edgeamongbloodbanksandpeopleaboutblooddonation.Ifnobloodbank is registered in the sys-
tem registered users are not able to use the app properly. To reduce ther is ksin software the
system should be available in all blood banks and among common people.
 Resourcerequirements

Specifies the hardware and software required to carry out the software project. Cost estima-
 tionisdoneaccordingtotheseresourcerequirements.Thecostincludes,costoflearning materi-
alsbrought,costincurredintravelingtobloodbanks,costassessedforbuyingsoftware and hardware
etc…
 Workbreakdown

Describes the activities in to which the project is divided. It also describes the Mile-
stones and deliverables of the project activities. The first activity of the system develop-
mentincludeddesigningofthesystem,database,inputandoutputs.Thentheservices and the web
portion were developed based on the design. It was made working considered as a delivera-
ble to check whether the services are running properly.
 ProjectSchedule

Specifies the dependencies of activities one achother. Based on this, the time re-
quired by the project management team members to complete the project activities is esti-
mated. Only if the web services are developed mobile application will be able to run. The da-
ta base including tables are to be created in the beginning itself for the proper functioning of
the system. If the designing phase is completed in a small amount of time, then the total work
time can be estimated.

There are several plans that may be a part of or linked to a project plan. These plans in-
clude quality assurance plan, verification plan and validation plan, configuration management
plan maintenance plan and staffing. The WBS is the hierarchicallist of the project's phases, tasks,
andmilestones.It'sthecoreoftheprojectschedule.TheWBSiscriticalbecauseitdrives thescopeof the
project. The scope translates into the timeline and budget. The time that you estimateit-
willtaketocompletethetasksbyenteringeitherworkorduration.Workistheamount ofeffortorperson-
hoursneededtocompleteatask.Durationistheamountofactualtimethatwill pass before the task is
completed. Thus, if a task takes 16 hours of work and one person does the work, its duration is
two days (assuming an 8-hour work day). If two people do the work, its duration is one day.

PROJECTSCHEDULING

Projectschedulingprovidesdetailssuchasstartandenddateoftheproject,milestonesand tasks
for the project. In addition, it specifies the resources (such as people, equipment, and facilities)
required to complete the project and the dependencies of tasks of the project on each oth-
er.Beforeaprojectschedulecanbecreated,theschedulemakershouldhaveaworkbreakdown structure
(WBS), an effort estimate for each task, and a resource list with availability for each resource.
An appropriate project schedule prepared according to project plan not only aims to completethe
project on timebut also helps to avoid theadditional cost incurred when the project is delayed. In
order for a project schedule to be healthy, the following criteria must be met:

 Theschedule mustbeconstantly(weeklyworks best)updated.

 TheEAC (Estimationat Completion) value mustbeequalto thebaselinevalue.

 Theremainingeffortmustbeappropriatelydistributedamongteammembers(takingvacations into
consideration).

To carry out project scheduling appropriately, some principles are followed. These prin-
ciples help the project management team to prepare the project schedule. Several techniques
areused forkeepingtrack oftheproject schedule. Thesetechniquesareapplied afterinformation is
collected from the project planning activities. This information includes estimation of effort, se-
lection of suitable process model, and decomposition of tasksintomultiple subtasks and so on.
Clinic Appointment System was scheduled to complete in 4 months’ duration. The system de-
velopment was completed in the scheduled time period. The cost estimated in development of
the system was accurate and was exact to the estimation after the completion of the project.

SYSTEM TESTING

TYPES OF TESTING

Software testing determines the correctness, completeness, and quality of software being
developed. Validation refers to the process of checking that the developed software meets the re-
quirements specified by the user. The activities involved in the testing phase basically evaluate
the capability of that system meets its requirements. The main objective of software testing is to
detect errors in the software. Errors occur if some part of the developed system is found to be in-
correct, incomplete or inconsistent. Test techniques include, but are not limited to, the process of
executing a program or application with the intent of findingsoftware bugs(errors or other de-
fects). It involves the execution of a software component or system to evaluate one or more
properties of interest. In general, these properties indicate the extent to which the component or
system under test:

 Meetstherequirementsthatguideditsdesignanddevelopment,

 Respondscorrectlyto allkinds of inputs,

 Performsitsfunctionswithinanacceptable time,

 Is sufficientlyusable,

 Canbeinstalledandruninitsintended environments,and

 Achievesthegeneralresultitsstakeholdersdesire.

Asthenumberofpossibletestsforevensimplesoftwarecomponentsispracticallyinfinite, all
software testing uses some strategy to select tests that are feasible for the available time and re-
sources. As a result, software testing typically (but not exclusively) attempts to execute a pro-
gramorapplicationwiththeintentoffindingsoftwarebugs(errorsorotherdefects).Software testing-
canprovideobjective,independentinformationaboutthequalityofsoftwareandriskofits failuretouser-
sand/orsponsors.Softwaretestingcanbeconductedassoonasexecutablesoftware (evenifpartially-
complete)exists.Theoverallapproachtosoftwaredevelopmentoftendetermines when and how test-
ing is conducted. For example, in a phased process, most testing occurs after system require-
ments have been defined and then implemented in testable programs. In contrast, under an Agile
approach, requirements, programming, and testing are often done concurrently.

White box Testing

Tests are performed to ensure that all internal operations of the software are per-
formedaccording to the specifications of the client. This is called White box testing.

White-box testing(also known asclear box testing,glass box testing,transparent box test-
ing, andstructural testing) is a method of testingsoftwarethat tests internal structures or workings
of an application, as opposed to its functionality (i.e. black-box testing).

In white-box testing an internal perspective of the system, as well as programming skills,

are used to design testcaes. White box testing can be applied at the unit, integrationandsystem-
levelsofthesoftwaretestingprocess.Althoughtraditionaltesters tended to think of white-box testing
as being done at the unit level, it is used for integration and system testing more frequently to-
day. It can test paths within a unit, paths between units during integra-
tion,andbetweensubsystemsduringasystem–leveltest.Thoughthismethodoftestdesign can uncover
many errors or problems, it has the potential to miss unimplemented parts of the specification or
missing requirements. The details entered by the administrator are saved and stored in the data-
base, and testing is done to verify whether the control of each form or action is working in the
exact way.

Black box Testing

Testsareperformedtoensurethateachfunctionisworkingproperly.Thisisreferredtoas Black
box testing. Black-box testingis a method of software testingthat examines the functionality of an
application (e.g. what the software does) without peering into its internal structures or workings.
This method of test can be applied to virtually every level of software test-
ing:unit,integration,systemandacceptance.Ittypicallycomprisesmostifnotallhigherlevel testing, but
can also dominateunit testingas well. Test cases are built around specifications and requirements,
i.e., what the application is supposed to do. Test cases are generally derived from external de-
scriptions of the software, including specifications, requirements and design parameters. Alt-
hough the tests used are primarilyfunctionalin nature,non-functionaltests may also be used.The
test designer selects both valid and invalid inputs and determines the correct output with-
outanyknowledgeofthetestobject'sinternalstructure.Testingisconductedinthesystemso thatthefunc-
tionsnamelyLogin,Making,searchingthenearestdonor,gettingroutestothenearest blood banks etc.
are done properly.

TESTING STRATEGY
Condition Testing

Test cases are derived to determine whether the logic conditions and decision statements
are free from errors. Condition testing strategy is used to check if the operators used are correct
and to verifyconditions such as ifan errormessageis displayed ifanon-registered useris signed in
to the application, or a user is registered without providing his email, address or full name.
Loop Testing

This testingis used to check thevarietyofloops present in programming. Theworkingof the

loops such as while, for and do while are checked for its proper execution. The statements inside
the loop body are executed line by line for every condition that satisfies the loop.

Unit Testing

This testing is performed to test the individual units in the system. Each module in the
systemistestedindividuallyandexecutedlinebylineforaccuratefunctioningofthesystem.The ap-
pointment part of the user module has been tested for its proper functioning, since it’s the core
part of the application.

IntegrationTesting

Theobjectiveofintegrationtestingistotakealltestedindividualmodules,integratethem, test
them again and develop the system. The user module, the appointment module as well as the
doctor & admin should be integrated together for the proper functioning of the whole system.
Testingisconductedatthisstagetocheckwhethertherequestedactionhascompletedsuccessfully and
changes are affected properly at both the doctor and admin modules.

AcceptanceTesting

This testing is performed to ensure that the functional, behavioural, and performance re-
quirements of the system is met. It may involvephysical tests orperformance tests. The ac-
ceptance test suite is run against the supplied input data or using an acceptance test script to di-
rect the testers. Then the results obtained are compared with the expected results. If there is a
correctmatchforeverycase,thetestsuiteissaidtopass.Ifnot,thesystemmayeitherberejected or accept-
ed on conditions previously agreed between the sponsor and the manufacturer. The objective is
to provide confidence that the delivered system meets the business requirements of both sponsors
and users. The acceptance phase may also act as the final quality gateway, where any quality de-
fects not previously detected may be uncovered. The system is implemented after all these
checks and validations.
 SYSTEM IMPLEMENTATION
System implementation is the final stage of software development life cycle. For the suc-
cessful implementation and cooperation of new systems users must be selected, educated and
trained. Unless the users are not trained, the system will become complex and it will feel as a
burden for them. Aproduct software implementation methodis a systematically structured ap-
proach to effectively integrate software based service or component into the workflow of an or-
ganizational structure or an individual end-user. A product software implementation method is
ablueprinttogetusersand/ororganizationsrunningwithaspecificsoftwareproduct.Themethod is a set
of rules and views to cope with the most common issues that occur when implementing a soft-
ware product: business alignment from the organizational view and acceptance from human
view. It is stated that the implementation of (product) software consumes up to 1/3 of the budget
ofasoftwarepurchase.Thecomplexityofimplementingproduct softwarediffersonseveral issues. Ex-
amples are: the number of end users that will use the product software, the effects that the im-
plementation has on changes of tasks and responsibilities for the end user, the culture and the in-
tegrity of the organization where the software is going to be used and the budget available for
acquiring product software.

The implementation stage of the system begins by preparing a plan for implementation of
the system. According to this plan, activities are to be carried out, discussions are made regard-
ing the equipment to be required and resources and additional facilities required to implement the
system.Themostcriticalstageinachievingasuccessfulsystemisbygivingusersconfidencethat the sys-
tem will work based on their requirements and be effective. This method also offers the greatest
securities since the old system can take over if the errors are found or inabilityto handle certain
type of transactions while using the new system.

The implementation involves the following formalities:

 Careful planning.

 Investigation of the systems and constraints.

 Design the methods to achieve the changes.

 Training the staffs in the changed phase.

 Evaluation of the change over method.

 SYSTEM MAINTANANCE AND SECURITY

SYSTEM MAINTANANCE

A process of modifying a software system or component after delivery to correct faults,

to improve performance is known as software maintenance. A common perception of mainte-
nance is that it merely involves fixing effects. However, one study indicated that the majority,
over80%, of the maintenance effort is used for non-corrective actions. Software maintenance is a
very broad activity that includes error correction, enhancements of capabilities, deletion of obso-
lete capabilities, and optimization. Because change is inevitable, mechanisms must be developed
for evaluation, controllingand makingmodifications. So anywork doneto changethesoftwareafter
it is in operation is considered to be maintenance work. The purpose is to preserve the value of
software over the time. The value can be enhanced by expanding the customer base, meeting ad-
ditionalrequirements,becomingeasiertouse,moreefficientandemployingnewertechnology. Mainte-
nance may span for 20 years, whereas development may be 1-2 years.

Corrective maintenance is done to repair the faults ordefects found in day–to–day system
functions, that is software design, logic and coding errors. Adaptive maintenance is the imple-
mentation of changes in a part of the system which has been affected by changes that occurred in
someotherpartofthesystem. Theobjectiveofperspectivemaintenanceshould beto prevent failures
and optimizethesoftware. Minor adaptive changes should behandledbynormal maintenance pro-
cess. Major adaptive changes should be carried out as a separate development project.

SYSTEM SECURITY

System security is a branch of technology known as information security as applied to

computersandnetworks. Theobjectiveofsystem securityincludesprotectionofinformationand prop-
ertyfromtheft,corruption,ornaturaldisaster,whileallowingtheinformationandpropertyto remain ac-
cessible and productive to its intended users. The terms system security, means the collectivepro-
cessesandmechanismsbywhichsensitiveandvaluableinformationandservicesare protected from
publication, tampering or collapse by unauthorized activities or untrustworthy individuals and
unplanned events respectively. The technologies of system security are based on logic. As securi-
ty is not necessarily the primary goal of most computer applications, designing a program with
securityin mind often imposes restrictions on that program's behaviour. Internet is a part of eve-
ryday life; web applications are an essential component of every business activity. Customers
and trading partners expect fast, accurate and secure applications with robust functionality.
Companies want sites that are easy to maintain and update, yet cost effective. Auditorsandsecuri-
tyofficerswanttoensurethatthewebapplicationsarecontrolledandthatthere is strong data integrity.
All of these requirements need to be blended to ensure that each web application meets the com-
pany’s goals, satisfies the customers

Any system developed should be secured and protected against possible hazards. Security
measures are provided to prevent unauthorized access of various levels. An uninterrupted supply
should be provided, so that the power failure or voltage fluctuations will not erase the data in the
files or database. Data security is the practice of keeping data protected from corruption and un-
authorizedaccess.Thefocusbehinddatasecurityistoensureprivacywhileprotectingpersonal orcorpo-
ratedata.Dataistherawformofinformationstoredascolumnsandrowsinourdatabase, networkserver-
sandpersonalcomputers.Authorizationensuresthatthelogged-inuserisallowed to use a page or per-
form an operation. Authorization is typically based on one or more roles (sometimes called
groups) to which the user belongs. Password protection and simple procedure tohidetheirperson-
aldataareprovidedtotheusersasapartofthesecurityobjectives.Thesystem allows the users to use the
app onlyafter signing in using their username and password provided during registration.

The admin is well protected by a password and username since all services are controlled
bythe admin, anyintrusion in to the admin can cause damage or a failurein the system. Theuser
can only access the service but can’t modify any. Each user is treated individually and can’t in-
terrupt to the details of another user account and make changes or modifications hence the activi-
ty of each single user is well protected and secured.
CHAPTER-6
CONCLUSION
 CONCLUSION

Making clinic appointments shouldn’t be hard, but often due to the manual way of making ap-
pointments, patients findit’shardtomakeappointmentswiththeirdesireddoctor.Oftenpatients have
to wait in long queues and yet sometimes they won’t be able to book their appointments. Clinic
Appointment System is an easy solution for such patients. They don’t have to wait in endless
queues or ask someone to do them a favor, because Clinic Appointment system has everything
they need to make an appointment with their desired doctor. Clinic Appointment System comes
with a clean and responsive interface, so that user can make appointments from every device, all
they need is an internet connection.

From the hospital/clinic point of view, they often fail to satisfy the needs of their pa-
tients/customers. Sometimes, a staff may need to take a leave and it may cause the whole ap-
pointmentproceduretogodown.WiththenewClinicAppointmentSystem,alltheyneedtodo is de-
ploythe application to their web server and theyare done. Once the administrator has added all
the departments and doctors list, patient can book their appointments by visiting the system. No
need of a third person to process the request.

Clinic Appointment System also provides doctors an account to in teract with their pa-
tients. Now doctors can easily send prescriptions online, or see their patient details in advance or
even better, they can cancel/ put the appointment to the pending list. Patient on the other side,
don’t have to worry about losing his/her prescription since it’s stored in the hospital’s servers.