3. 1.INTRODUCTION
1.1 Overview of the Project
1.2 Objectives of the Project
1.3 The need for the Project
1.4 Overview of Existing Systems and Technologies
1.5 Scope of the Project
1.6 Deliverables
2.FEASIBILITY STUDY
2.1 Financial Feasibility
2.2 Technical Feasibility
2.3 Resource
2.4 Time Feasibility
2.5 Economically feasibility
2.6 Behavioral Feasibility
2.7 Operational Feasibility
2.8 Risk Feasibility
2.9 Social/Legal Feasibility
3. Considerations(Also NonFunctionalRequirements)
4. 4.DIAGRAMS:
4.1 Use Case
4.2 ER diagram
4.3 Sequence Diaqram
4.4 Class Diagram
4.5 State Machine Diagram
4.6 Object Diagram
4.7 Activity Diagram
5.TESTING
5. 1.1 Overview of the project:
Online patient treatment system is online management system
that provide a self-diagnosis for user staying far from the
hospital. It’s software which will automate the major hospital
operations. This application is useful to the people who are far
away from the hospital and the patient can get treatment when
the doctor is not available, in hospital .
It refers to a number of efficient automated systems designed for
tracking patient information, diagnoses, prescriptions,
interactions and encounters within healthcare organizations like
medical clinics or hospitals.
The self-diagnosis features help the patient for taking medicine
without consulting the doctor. But it can provide treatment up to
level that means rectifiable diseases without doctor suggestion
with some dosage of tablets.
This system provide a self-test to the patient, if hospital are not
available in near place. The patients can interact with an
appropriate doctor through online chatting or discussion forum.
1.2 Objective of the project:
The objectivesof this project are
Provide an online treatment platform
6. Medicalrecord
Timely patient care
List of specialized doctors
Immediate information storage
Automate the Updating process
Manualcalculation
Preparation of accurate and prompt reports
Makes it easy to check records
Computerized billing
1.2 The Need for the project:
This system helpfulfor the people, who are Busy with their
professional work. They can get doctorsuggestions through
onlineand can share their problems with doctor. The self-
diagnosisfeatures help the patientfor taking medicine without
consulting the doctor. It can provide treatment up to some level
that means rectifiable diseases without doctor suggestion with
some dosage of tablets.
Other then this onlinepatient treatment system is capableof
managing records and other reports. It refers to a number of
efficient automatedsystems designed for tracking patient
information,diagnoses, prescriptions, interactionsand
encounters within healthcareorganizationslike medical clinicsor
hospitals.
7. In the current context, getting statistical information about the -
record of a patient need extra effort and only helps the hospital
management and is not useful to the patientout of the hospital
or remote areas. This system provides a solution to this problem
by providingautomaticallygenerated statistical information in
many aspects and created the computerized hospital
environment .
1.4 Overview of Existing Systems and Technologies
Online patienttreatment system created the computerized
hospital environment by eliminatingthe manualwork by the
staff. This system can be helpfulto the hospital management
system. The existed system only helpsthe hospitalmanagement
and is not useful to the patient out of the hospitalor remote
areas.
Main Technologies associated with OPTS:
OPERATING SYSTEM : Windows 7/ XP/8
FRONT END : Html,css,java
Web programming technologies (JS,JSP,HTML,CSS)
MySQL (Database)
Diagram and design tools(Visio, Nclass, Draw.IO,
Microsoft project )
1.5 Scope of the project:
Main actor of this system:
Patient
8. Doctor
Managingstaff
1.Patient
Login the system
Search doctor `
2.Doctor
Suggest medicine
treatment
3. Administration
Create user account
Schedule of the doctors
Maintainrecord of patient
1.6 Deliverables:
A web based software system. This containa central database
and functionalitiesfor various stakeholders. Since many number
of stakeholders are involved,different GUIs will be providedto
different users.
2.1 Financial Feasibility :
9. The cost of using this software will be minimal as it will be used
by the people staying in remote areas and urban areas. Using this
software will save the doctoral fees and extra charges that are
above the reach of common people.
This system does not consist of any multimedia data transfer,
bandwidth required for the operation of this application is very
low.
BENEFITS:
Across the associated cost, there will be many benefits for the
customers that many people have to wait for long in scheduling
appointment with the doctors, but this problem is also solved by
our software. User donned appointment to meet the doctors,
they can directly discuss their problem with doctor in our online
discussion forum or can send their queries.
2.2 Technical Feasibility:
Project hospital management system is a complete web based
application.
The main technologies and tools that are associated with this
project are
CSS
JV
C++
HTML
10. JSP
NetBeans
Drawing tools
Microsoft Project
Visio
Draw IO
Each of the technologies is freely availableandthe technical skills
required are manageable. Time limitation of the product
development and the ease of implementing using these
technologies are synchronized.
So, it is technically feasible
2.3 Resource Feasibility:
Resources that is required for the hospital management system
includes,
Programming devices (laptop)
Hosting space ( freely available )
Programming tool (free available)
Programming individuals
2.4 Time Feasibility:
This has been discovered that many people have to wait for long
in schedulingappointmentwith the doctors, but this problem is
also solved by our software. User donned appointmentto meet
the doctors; they can directly discuss their problem with doctor
in our onlinediscussion forum or can send their queries.
11. 2.5 Economically feasibility
The system being developedis economic with the hospital point
of view .it is cost effective in the sense that the eliminatedthe
paper work completely. The result obtainedcontainsminimum
errors and are highly accurate as the data is required.
2.6 Behavioral Feasibility
The system working is quite easy to use and learn due to its
simple and attractive interface.
2.7 Operational Feasibility
The aspect of study is to check the level of acceptance of the
system by the user. This includesthe process of training the user
to use the system efficiently. The user must not feel threatened
by the system, instead must accept it as a necessity. The level of
acceptance by the users solely depends on the methods that are
employed to educate the user about the system and to make him
familiar with it. His level of confidence must be raised so that he
is also able to make some constructive criticism, which is
welcomed, as he is the final user of the system.
2.8 Risk feasibility
Risk feasibility can be discussed under several contexts.
Risk associated with size
12. Estimate size of the product in line of codes:
The system doesn’t contain any multimedia aspect, the file size
of this software don’t exceed 300MB. It will contain significant
amount of code lines. Only the administrator will control the
application and user cannot easily understand the line of code if
he/she is not professional.
Estimated size of product in number of programs:
This software is constructed as a single web application witha
simple login page rather than having much number of sites for
different users. Depending on the access rights, the content will
be showed or hidden.
Database size will not exceed the values supported by MySQL
(65526 entries per table). Number of relationsand entities are
minimized by using best practices of normalizationtheories.
User of the product:
Patient
Doctor
Administrator
Number of project changes to the requirements for the product?
Before delivery?
Before delivery the requirements of software is clearly
identifiedbefore the implementationphase.
After delivery?
After delivery the requirements will be changed if new
functionalitiesare needed to be added.
13. Amount of reused software:
This system will use some JSP libraries to incorporate
additional functionalitiessuch as to support file uploads.
Business impact risks
This software can only implement or can be integrated to an
existing system as Hospitalmanagement system. It
automatessome key features associated in hospital, there
user can increase the revenue.
Reasonable of delivery deadlines:
Being a 14 weeks project, the project online patient
treatment will have several deadlinesand deliverablesthat
are scheduled successively, dependingon the coding and
designing cost and effort ,the deadlinesare quiet
reasonable.
Number of customers who will use this product and the
consistency of their needs relative to the product:
As mentioned above, we can categorize stakeholder into 3
main categories. Thissoftware can support many number of
users simultaneouslydue to the low bandwidth
requirements.
Number of other products/systems with which this product
must be interoperable:
This product can be integrated with current hospital
management system with single modifications.
Sophistication of end user:
14. This software is designed while maintainingthe complexity
at a very low level. Usability is highly improved by providing
help documents and making GUIs easy to use.
Amount and quality of product documentation that must be
produced and delivered to the customer:
Customer will be providedwith a complete online user
manual.As the software is implemented as a freeware and
open source system, the code will be available for free.
Cost associated with delivery:
At the initaialstage the associated cost will befor the
hosting cost.
Are tools for analysis and design available?
It will require several designing software
Draw.io(databasedesign)
NCLASS(class diagram)
Visio (Software related diagrams)
Are compilers or code generators available and appreciate for the
product to the built?
JSP is used as the main scripting language.
All the libraries and interpreters will be freely available.
Are testing tools available and appropriate for the product to be
built?
JUNIT is the main testing tool that will be used.JUNIT is
freely availabletool that supports automated testing.
Are software configuration management tools available?
15. Configurationmanagement will be done using Git that is
freely available.
Does the environment make use of a database or repository?
This is a databaseoriented system that will use MYAQL.Are
all the software tools integrated with one another?
Main deliverableswill be packaged under a single project.
All the stakeholders will have a single project. All the
stakeholderswill have a single login page.
Process issue risks:
This software follows the RUP software development
process. This provides flexibilityand it can change according
to needed requirements.
Technical issue risks:
Do you use a specific method for test case design?
JUNIT will be used as the main testing tool
that automatesthe testing process.
Are configuration management software tools used to
control and track change activity throughout the software
process?
GIT will be used throughout the software
implementationprocess.
Technology risks
Is the technology to be built new?
All the technologies are very well established
and old enough (but not obsolete).
Do the system requirements demand the creation of
16. new algorithms, input or output technology?
This software have several algorithmsto keep
manualrecord of patient, records of appointment
of patient, specialized doctors list .
Social/Legal Feasibility
The toolsand specificationsused in OPTS is widely
availableand provide the system as an open source
system. Only the maintenancecost will be charged
from customers.
This product does not break any laws.
JSP Software libraries that are used in this system are
free open source libraries.
Since, it will have a great impact in a hospitalmanagement
system.
Considerations (Also Non Functional
Requirements)
Performance:
ONLINE PATIENT TREATMENTSYSTEM requires a
very low bandwidth,hence the performance will
not degrade with increasing number of potential
users. At the developmentstage, a free hosting
service will be used. But when installingthe system
to a real hospitalenvironment,it will be hosted in a
much more reliableserver to increase the
performance.
MySQL will provide the adequatespeed for
database transactions. Since no big data analysisis
17. done, MYSQL is the idealdatabase for this project.
Response time: less than 2 seconds
Processing time: Less than 2 seconds (no
batch processing involved)Query and
reporting times: yet to be tested
Throughput:yet
to be tested
Storage: yet to be
tested
Security:
Security measures are provided in many aspects in
this system.
User authentication:
Users will have to authenticateusing the
username and passwords. Dependingon the
access level each user will gain functionality
of the system. Passwords can be changed by
the user.
Login details:
Each user’s login time and logout time will be
recorded in the system, to make the tractability
process easy in case of a faulty action.
Usability and ease of use:
Users will be provided with a complete user manual
as a pdf. The interfaces are designed to make it easy
for any potentialuser to get familiarwith the
system within one hour. No additional trainingis
18. required to use the system.
Capacity and scalability:
ONLINT PATIENT TREATMENT system can
accommodate many simultaneoususers. The system
is designed to make it easy to integrate to an existing
system like the Moodlesystem.
Availability:
System will be available throughoutthe 24 hours.
Mean time to failure and mean time to repairwill be
decided to increase the availability.With a paid
hosting space, the availabilitycan be guaranteed to a
great precision.
For online patienttreatment system we have following
references:
www.google.com
www.hospial.com
www.yahoo.com
Online patient treatment system is online
management system that provide a self-
19. diagnosis for user staying far from the hospital.
It’s software which will automate the major
hospital operations.In the system,A patient on
the system log in page appear if he already have
an account then he will login the system
otherwise sign in. A list appears in which the list
of doctors of different department are given with
their PA information. The patient contact the PA
of doctor. The PA gives the appointment with
token number. The patient contact the doctor,
according to his token number.The patient
contact to doctor ,according to his token
number.The doctor treats the patient and
suggests some medicines or ask the patient for
proper treatment.The administrator give bill.The
patient will give online payment and log out he
system.
24. user
_
LIST
+doc names: string
+docpanamel: string
+department: string
Getdocname():string
Getdocpaname():string
Getdepartment():string
PATIENT
- id:int
+ name: string
+diseasename:string
+email: string
+address: string
getid(): string
getname(): string
getdiseasename(): int
getmobile no.(): double
getemail(): string
getw-id(): string
getw-name(): string
DOCTOR PA
+name(): string
+docname: string
-contactno:int
getname (): string
getdocname (): string
getcontactno (): string
DOCTOR
+s-name:string
- id: string
- email: string
+department:string
getsname(): string
getid(): string
getemai(): string
getdepartment():string
ADMINISTRSTOR
+recordofpatient: int
+billingdetail:double
Getrecordofpatient():strin
g
Gerbillingdetail():double
25. Treating patient
Getdata_of_user
login
maintanc
eee
Cont
aaac
t
Wait and try
again
Get info about
patient disease
Getting
access
Take info
Contact
doc
Give appointment
Treat
patient
Log out
Online
payment
Turn on
Suggest medicine
Execute list
Fail to execute
page
accessin
g
getting
If any
problem
treatment
Show bill to patient
Log
off
failure
Check list
29. Build Number P1-100
Tester Name Rabia nasir
Test Type Unit test
Test Case Name Test set sign in
Test Case
Number
TC1000
Test Case
Description
Testing the sign in function
ITEMS TO BE TESTED
1. Check whether the sign in page appear
2. Check whether the patient already have account
SPECIFICATIONS
INPUT: EXPECTED OUTPUT
Sign in Sign in page appear to make patient account
PROCEDURAL STEPS
1.create the bool sign in function
2.check whether theinput is valid or ot
3.makethepatient account
30. Build Number P1-101
Tester Name Alishba Bibi
Test Type Unit test
Test Case Name Test setPassword
Test Case
Number
TC1001
Test Case
Description
Testing the password
ITEMS TO BE TESTED
1. The password can not be more than 6 digits
2. Whether the password is valid or not
SPECIFICATIONS
INPUT: EXPECTED OUTPUT
Password The system will be logged in
PROCEDURAL STEPS
1.Create the char password function
2.Check whether the password isvalid or not
3. The patient will be login
31. Build Number P1-102
Tester Name Rabia nasir
Test Type Unit test
Test Case Name Test set user name
Test Case
Number
TC1002
Test Case
Description
Testing the user name
ITEMS TO BE TESTED
1. Check whether the username is valid or not
2. Check whether the username is correct or not
SPECIFICATIONS
INPUT: EXPECTED OUTPUT
User name Ask for password
PROCEDURAL STEPS
1.Create the char username function
2.Check whether the input is valid or not
3.Check whether the username is crrect or not
32. Build Number P1-103
Tester Name Sadaf khanwal
Test Type Unit test
Test Case Name Test doctor list
Test Case
Number
TC1003
Test Case
Description
Testing whether the list appear or not
ITEMS TO BE TESTED
1. Wheather the input is valid or not
2. Appear doctor list or not
SPECIFICATIONS
INPUT: EXPECTED OUTPUT
List Appear the list of doctors
PROCEDURAL STEPS
1.Create the set_listfunction.
2.Set the names of doctors in this function
3.Check whether the inputis valid or not.
4. Make ist of doctors according to disease
33. Build Number P1-104
Tester Name Rabia nasir
Test Type Unit test
Test Case Name Test set-Docname
Test Case
Number
TC1005
Test Case
Description
Testing whether the doctor is available or nor
ITEMS TO BE TESTED
1. Whether the doctor is available or not
2. Information about doctor appear or not
SPECIFICATIONS
INPUT: EXPECTED OUTPUT
Doc name Appear the information about a doctor
PROCEDURAL STEPS
1. Createtheset-doc function
2. Check whetherthe correct doctorname is enteringor not
3.enter information of doctor in this function
34. Build Number P1-105
Tester Name Rabia nasir
Test Type Unit test
Test Case Name Test set-disease
Test Case
Number
TC1006
Test Case
Description
Testing
ITEMS TO BE TESTED
1. Whetherthe doctors is available or not
SPECIFICATIONS
INPUT: EXPECTED OUTPUT
Disease Appear the doctor llist accordingto input
PROCEDURAL STEPS
1. Createtheset-disease function.
2.Check wheather the doctoravailable or not
3.Enter thediseses name in this fuction
35. Build Number P1-107
Tester Name Rabia nasir
Test Type Unit test
Test Case Name Test set-appointment
Test Case
Number
TC1008
Test Case
Description
ITEMS TO BE TESTED
1. A timing and token no. appear
SPECIFICATIONS
INPUT: EXPECTED OUTPUT
Appintment Tell time and fee of doctor
PROCEDURAL STEPS
1.create a function of set appointment
2.enter the timingthat pa give to patient
3.check it is valid or not
36. Build Number P1-108
Tester Name Rabia nasir
Test Type Unit test
Test Case Name Test set-Log out
Test Case
Number
TC1009
Test Case
Description
Testing that patient has paid and save the information for nextvist.
ITEMS TO BE TESTED
1. Wheather the patient has paid or not
2. Wheather the patient first visit if then sav the information of patient
SPECIFICATIONS
INPUT: EXPECTED OUTPUT
Log out Confirmation page appear
PROCEDURAL STEPS
1Create the logout function
2.check thatpatient has payedor not
3.save the info of patient for next vist
37. Build Number P1-109
Tester Name Rabia
Test Type Unit test
Test Case Name Test set-payment
Test Case
Number
TC1010
Test Case
Description
Testing the online payment
ITEMS TO BE TESTED
1. Check wheather the patient already payed the bill or not
2. The payment is valid or not
SPECIFICATIONS
INPUT: EXPECTED OUTPUT
Username The payment is already given or not
PROCEDURAL STEPS
1.Create the function for online payment
2.Check whether the payment is done or not
3.Enter theuser name
