hello

1. Physiotherapy Clinical System
A PROJECT REPORT
Submitted by
Gelani Vishal R. (080330131009)
Gondaliya Sagar P. (080330131011)
Kachhadiya Rahul B. (080330131015)
In fulfillment for the award of the degree
Of
BECHLOR OF ENGINEERING
in
Computer Science& Engineering Department
Mahatma Gandhi Institute of Technical Education and Research Center
Navsari
Gujarat Technological University, Ahmedabad
December, 2011

2. CHAPTER-1
INTRODUCTION
“Introduction, a short demo produced for promotion or to meetCompetition
requirements.”

3. 1.1 PROJECT PROFILE
Project Title: Physiotherapy Clinical System
Project objective: Physiotherapy Clinical System is a manage
patient data and Complete Reference for doctor
exclusively designed for legal aspects of a clinic.
It also manages medical, administrative, financial
data. It manages allaspects of billing system
operations quickly and accurately. Thebelow is
the partial listing of the features available for
doctor.
Organization: Sakariya physiotherapy clinic.
4th floor, Doctor house, Hirabag, Varachha
Road, Surat
Email: dr.sakariya@yahoo.co.in
Platform(OS): Windows XP Service Pack 2 & onwards
Back-end: SQL Server
Front-end: VB.NET
Project Guidance(External): Dr. Bhupat Sakariya
Submitted By : Mr. Rahul Kachhadiya
Mr. Vishal Gelani
Mr. Sagar Gondaliya
Submitted To : Computer Science Engineering Department,
MGITER,Navsari

4. Duration : 1 Year
1.2 PURPOSE
Primary purpose of the system is to simplify the task of the system users. There is lots of
deficiency involved in current manual system. This software makes it possible to overcome
most of the deficiency by replacing most of the manual task by atomizing the system.
My main objective is to develop this software to replace some manual working functionality
of current system by atomized and computerized system.
This clinical system is designed to overcome the drawback of exiting manual system. This
system is designed to maintain patient data, scheduling of patient appointment, provide
complete reference to the doctor, manage charges of patient and staff details.
The system uses Vb.NET as a front-end and SQL Server for in back-end.
This system maintains patient appointment, patient data and staff details in the clinic. As well
as maintains all records for doctors. You have to give the username and password to enter in
the system for security purpose. Once you entered in the system, you are allowed edit the
patient entries in the application, add a new entries of the patient, generate the report of
patient recovery in particulardisease, and so on. This system contains all the information of
the clinic, like information of patient, disease, equipment, appointment etc.
To guide system design I will go with sectional approach. There can be many sections in
which I can reach the target to be achieved.
 Data master section
 Report section
 Alert section
To fulfill the objectives and requirement of the clinic this section can be modify.
In data master section one can handled the data of the patients, appointment of patients,
information about equipment in the clinic, information about disease, data of staff and many
various things can be in this section.
In report section one can get the patient disease recovery reports, treatment reports, analysis
of patient disease reports.

5. In the alert section we can get the alerts of the remaining appointment today and doctor have
time to observe the patient etc.
Security point of view the passwords are given to the users of the system. The system
contains different passwords for different users. I will fix it for only for one or more
computer in clinic with the synchronization, and no one else can access outside that clinic
network. And it is beneficial to physiotherapy clinic also.
1.3 TECHNOLOGY AND LITERATURE REVIEW
Currently all the system is working manually. They maintain the record of the patients data of
the clinic, disease information, appointment scheduling, staff details, equipment information
etc. in many different departments. All this things are done manually by man power and
intelligence in the clinic.
The current system is fully managed by manual working. There are many major departments
are involved which are taken in to consideration in the clinic.
The manual work contains many problems, which makes the user frustrated. Here if the
doctors ask for remaining patient appointment in week or month then all the patient
appointment data which is managed by manually are tracked by the receptionist etc. the
biggest problem of manually system is modification. There are many such entries, which the
users have to re-write and carry out the required calculations.
This is very cumbersome job to calculate and again there are chances of incorrect results.
This is how manual system works here currently. They think that because of these tedious
processes they are unable to spend enough time with their works.
1.1 STUDY OF THE CURRENT SYSTEM
Currently most of the physiotherapy clinic works manually. So it consume more time and
manpower to perform or complete a task of job. In existing system all the records of the all
the departments are manually entered in the book of account or the book.
In existing system at the end of the day all the records are entered into the books of account
and during the day they note the records in the register. There are many problems in the
manual system so to remove the problem and to speed up the operation of the system the
clinic’s needs the computerized system.

6. Currently all works of the physiotherapy clinical system is done manually, so it is difficult to
maintain patient’s information and decision making based on that information. It is time
consuming and difficult, so clinic needs system which can generate reports based on patient’s
disease and can manage patient’s information and keep data in centralize database.
At first, according to its existing system we gather information regarding our project. So for
getting the complete knowledge about the system we made the detailed study of the existing
system to meet their expected requirement.
1.4 PROPOSED NEW SYSTEM
The field of software of software development is a very immature field.Technique of
project management in the field of software development is embryonic at best and the well-
planned of software projects suffer from massive cost and time overruns.
This system is aimed to provide right information at the right time to middle management to
assist them making decision at the right time.
 System is always management oriented and keeps in view every level of management
and gets the desired information.
 Integrated- refers to different component are actually tied up together. Example;
different departments of clinic linked together.
 Useful for planning – as every clinic makes long-term and short-term plans with the
help of information like patient disease, general information about its physical
condition.
 Effective system helps the administration to know derivations of actual performance
from pre-set
 It is important for increasing efficiency.
 System provides update results of various departments to doctor.
 System is highly computerized so it provides accurate results.
 System adds to the intelligence, alertness, awareness of administration by providing
them information in the form of progress and review reports of an outgoing activity.
 Helps administration in decision making.

7. The proposed system overcomes the disadvantages and limitations of the exiting system.
The objectives of proposed system are as follow:-
 Totally menu driven, user friendly and easy to understand.
 Easy report generation according to the requirements of company.
 All the necessary help is provided to user.
 Password is given to system for security point of view.
 Maintain all necessary billing information.
 Reduce the paperwork within aclinic.
 Good interaction between the various departments of the clinic.
.
The overall purpose of system is to provide profitability and related to the administration and
Staffs understand the basic idea of plan in future direction.
1.5 SCOPE
The main scope behind this project is to provide the administration of clinic to store an
interactive application, which would increase their efficiency to work at the optimization
level and decrease in human effort needed behind the work they want do.
The main objective of This “ Physiotherapy Clinical System ” is system is to give an all data
related clinical system that`s keeps all the record of the patient information about all types of
pain like lag bones, hand bones, solder point and so on.
This application greatly speeds up and simplifies the task of the administration who
isinvolved. Whenever the problem will accord at that time this system software are maintain
the improve the resistance as well as the all clinical management system are working
independently.

8. CHAPTER – 2
PROJECT MANAGEMENT
“Project management is the discipline of planning, organizing, and managing
resources to bring about the successful completion of the specific project……..”

9. 2.1 Project Development Approach
A project needs to be developed with the help of some software model which makes the
project good, reliable, reduces the cost of the project, make it user friendly. In my project I
will use the iterative model which combines the benefits of the protyping and the waterfall
model.
Introduction:
Iterative and incremental development is at the heart of cyclic software development process
developed in response to the weaknesses of the waterfall model. It starts with an initial
planning and ends with development the cyclic interactions between.
Steps of Model:

10. A common mistake is to consider “iterative” and “incremental” as synonyms, which they are
not. In software/systems development, however, they typically go hand in hand.
The basic idea is to developed a system through repeated cycles (iterative) and in smaller
portions at a time (incremental), allowing the developed to take advantage of what was
learned during the development of earlier portions or versions of the system. Learning comes
from both the development and use of the system, where possible key steps in the process
start with simple implementation of subset of the software requirements and iteratively
enhance the evolving versions until the full system is implemented. At each iteration, design
modification is made and new function capabilities are added.
The procedure itself consists of the initialization step, the iteration step, and the project
control list. The initialization step creates a base version of the system. The goal for this
initial implementation is to create a product to which the user can react. It should offer a
sampling of the key aspects of the problem and provide a solution that is sample enough to
understand and implement easily. To guide the iteration process, a project control list is
created that contain a record of all tasks that need to be performed. It includes such items as
new features to be implemented and areas of redesign of the existing solution. The control list
is constantly being revised as a result of the analysis phase.
The iteration involves the redesign and implementation of a task from project control list, and
the analysis of the current version of the system. The goal for the design and implementation
of any iteration is to be simple, straightforward, and modular, supporting redesign at that
stage or a task added to the project control list. The level of design detail is not dictated by
the interactive approach. In light-weight iterative project the code may represent the major
sources of documentation of the system; however, in mission-critical iterative project formal
software Design Document may be used. The analysis of iteration is based upon user
feedback, and the program analysis facilities available. It involves analysis of the structure,
modularity, usability, reliability, efficiency, & achievement of goals. The project control list
is modified in light of the analysis results.

11. How it works?
Incremental development slices the system functionality into incremental (portion). In each
incremental, a slice of functionality is delivered through cross-discipline work, form the
requirements to the development. The unified process groups increments/iterations into
phases: inception, elaboration, construction, and transition.
 Inception identifies project scope, risks, and requirements (functional and non-
functional) at a high level but in enough detail that work can be estimated.
 Elaboration delivers a working architecture th-incomlete
Implementation and Developing In my project
In my project, I have followed this model strategy which helps us to prepare a better final
product. As mentioned in the above discussion, I kept the project control task which was
prepared on the base of requirement and derived design of the system.
One effective use of this type of model is for product development, in which the developers
(I) themselves provide the specifications and therefore have a lot of control on what
specifications go in the system and what say out. In fact, most products undergo this type of
development process.
 Firstly I have to plan my project on the basis of this model.

12.  Then I have to collect the information about what the user want. What are the
requirements that I have to achieve?
 Then I have to analyses the requirements and make a typical design of the project.
 Then I have to implement my project.
 If the task is completes then we have to deploy it and if not we should test and
evaluate it and then again analyze and implements.
 After Successful completion of the design task I started coding for this project.
 During the coding phase I had worked on module bases.
Advantage of this approach:
 An advantage of this approach is that it can result in better testing because testing
each increment is likely to be easier then testing entire system as in waterfall model.
Furthermore, as in prototyping, the increments provide feedback to the client that is
useful for determining the final requirement of the system.

13. 2.2 FEASIBILTY STUDY
A feasibility study is an evaluation of a proposal designed to determine the difficulty in
carrying out a designated task. Generally, a feasibility study precedes technical development
and project implementation. In other words, a feasibility study is an evaluation or analysis of
the potential impact of the potential impact of a proposed project.
2.2.1Technology and system feasibility
The assessment is based on an outline design of system requirements in term of input,
process, output, fields, programs, and procedures. This can be quantified in terms of volumes
of data, trends, frequency of updating, etc. in order to estimate whether the new system will
perform ad equality or not. Technological feasibility is carried out to determine whether the
company has the capability has the capability, in term of software, hardware, personal and
expertise, to handle the completion of the project.
The proposed system will be developed using the JAVA and this is technical feasibility
Technical Requirement How Accomplished
Front End VB.NET
Back End SQL Server
Local Host Required
Documentation Tools Microsoft Office 2010
Table:2.1 Technical Feasibility
2.2.2 Economic feasibility

14. Economic analysis is the most frequently used method for evaluating the effectiveness of a
new system. More commonly known as cost/benefits analysis, the procedure is to determine
the benefits and savings that are expected from a candidate system and compare them with
costs. If benefits outweigh costs, then the decision is made to design and implementation the
system. An entrepreneur must accurately weight the cost versus benefits before taking an
action.
Cost-based study: it is important to identify cost and benefits factors, which can be
categorized as follows: (1) Development costs; and (2) operating cost. This is an analysis of
the cost to be incurred in the system and the benefits derivable out of the system.
Time-based study:This is an analysis of the time required to achieve a return on
investments. The future value of a project is also a factor.
2.2.3 Legal feasibility
Determines whether the proposed system conflicts with legal requirements, e.g. a data
processing system must comply with the local Data protection Acts.
2.2.4 Operational feasibility
Operational feasibility is a measure of how well a proposed system solves the problems, and
takes advantage of the opportunities identified during scope definition and how it satisfies the
requirements identified in the requirements analysis phase of system development.
2.2.5 Schedule feasibility
A project will fail if takes too long to be completed before it is useful. Typically this means
estimating how long the system will take to developed, and if it can be completed in a given
time period using some methods like payback period. Schedule feasibility is a measure of
how reasonable the project timetable is given our technical expertise, are the project
deadlines reasonable? Some projects are initiated with specific deadlines. You need to
determine whether the deadline is mandatory or desirable.

15. 2.2.6 Other feasibility factors
2.2.6.1 Market and real estate feasibility
Market Feasibility study typically involves testing geographic location for a real estate
development project, and usually involves parcels of real estate land. Developer often
conducts market studies to determine the best location within a jurisdiction, and to test
alternative land uses for given parcels. Jurisdiction often require developers to complete
feasibility studies before they will approve a permit application for retail, commercial,
industrial, manufacturing, housing, office or mixed-use project. Market feasibility takes into
account the importance of the business in selected area.
2.2.6.2 Resource feasibility
This involves question such as how much time is available to build the new system, when it
can be built, whether it interfaces with normal business operations, type and amount of
resources required, dependencies.
2.2.6.3 Cultural feasibility
In this stage, the project alternativesare evaluated for their impact on the local and general
culture. For example, environmental factors need to be considered and these factors are to be
well known. Further an clinical system own culture can clash with result of the project.

16. 2.3 Project Planning
This selection contains the software requirement to a level of detail
sufficient to designers to design the system, and testers to test that system.
In our project there is team of three members.
 Gelani Vishal R.
 Gondaliya Sagar P.
 Kachhadiya Rahul B.
Our team is guided by Prof.Diya N. Vadhwani
2.3.1 Roles and Responsibility
Work Task Module Performed By
Analysis Master Module, Transaction Gelani Vishal,
Modules, Report Module Gondaliya Sagar,
Kachhadiya Rahul.
Design Master Module, Transaction Gelani Vishal,
Modules, Report Module Gondaliya Sagar,
Kachhadiya Rahul.
Coding
Testing
Documentation Master Module, Transaction Gelani Vishal,
Modules, Report Module Gondaliya Sagar,
Kachhadiya Rahul.
Table 2.2 Roles and responsibility

17. 2.3.2 Schedule Representation
 Table-1 Detail project Table for Requirement Specification
PLANNED PLANNED ACTUAL ACTUAL
SR.NO. TASK. START END START END
DATE. DATE. DATE. DATE.
1 Problem
Reorganization
2 Self-Review
3 Specification
4 Review
Table:2.3 Requirement Specification
 Table-2 Detail Project Table for Design
PLANNED PLANNED ACTUAL ACTUAL
SR.NO. TASK. START END START END
DATE. DATE. DATE. DATE.
1 Data Dictionary
2 Dataflow
Diagram
Table:2.4 Design

18.  Table-3 Detail Project Table for Documentation
PLANNED PLANNED ACTUAL ACTUAL
SR.NO. TASK. START END START END
DATE. DATE. DATE. DATE.
1 Documentation

19. CHAPTER-3
SOFTWARE REQUIREMENT
SPECIFICATION
“This specification is to assist the management in evolving right strategic in
implementation of a proper system for an activity. A through study and gap
analysis with best of practice ensures the right design of system.”

20. 3.1 INTRODUCTION
3.1.1 PURPOSE
Currently most of the clinic works manually. So it consume more time and labor to perform
or complete a task of system. In existing system all the records are manually entered by
administration.
So the main purpose of the system is to eliminate the tedious and lengthy work, and make it
more accurate and easy for the user’s.
3.1.2 Scope
This software has a wider scope in the physiotherapy clinic. As there are no of Hospital’s
And in which physiotherapy department requires a system to maintain all the information
of the patient and efficient to store that data.
This application greatly speeds up and simplifies the task of the administration who is
involved. Whenever the problem will accord at that time this system software are maintain
the improve the resistance as well as the all clinical management system are working
independently.
.

21. 3.2 OVERALL DESCRIPTION
3.2.1 PRODUCT PERSPECTIVE
This software is specially developed for the physiotherapy clinic like record of patient,
patient scheduling, patient assessment, patient information, and exercise schedule, staff
detail.
So we can say that this system is a part of the whole inventory management system. It is very
helpful to clinic to reduce their work and make the work accurate and effective.
3.2.2 PRODUCT FUNCTION
This physiotherapy clinical system is designed to overcome drawback of exiting manual
system. This system is designed to maintain record of patient, patient scheduling, patient
assessment, and patient information, and exercise schedule, staff detail so on.
You have to give the User Id and Password to enter in the system for security purpose. Once
you entered in the system. You are allowed to be for retrieving patient information and billing
(charges information) from the database. This system contain all necessary information of
physiotherapist.
3.2.3 USER CHARACTERISTICS
There are a number of users with different permission and authority. Each and every users of
this system before using it must know what he is allow to do, What are the task they can
perform in the system, what are the restriction for them etc.

22. Each user have the basic knowledge of Application system and also basic things about
computing. For the special user like Doctor’s, they should have knowledge of the system’s
tools for monitoring the store’s progress and other user’s activities.
3.3 SPECIFIC REQUIREMENTS
3.3.1 EXTERNAL REQUIREMENTS
3.3.1.1 USER INTERFACE REQUIREMENTS
For user interface system requires a display device like, CRT monitor, LCD monitor, LED
monitor, etc. the screen format of the system may be any resolution between 800*600 and
1200*800.
For report layout the system requires a printing device like,. ink jet printer, laser jet printer,
etc. it also requires different formats of pages for different reporting, like purchase it may be
of size A4, for planning it may be of size A2, etc.
3.3.1.2 SOFTWARE INTERFACE REQUIREMENT
This system can be run on the operating System of windows. So there must be a operating
system like Windows XP, Windows XP, Windows Vista, Windows 7, etc.
The system requires different front end tool as VB.NET and Back end tool as SQL sever
database. It requires the Microsoft office 2010 as documentation tool.
3.3.1.3 HARDWARE INTERFACE REQUIREMENTS.
Screen resolution of at least 800*600 required for complete viewing of screen. Higher
resolution will not be a problem.

23. Any pointing device.(mouse)
Memory constraints-256MB RAM>
Hard Disk 40GB.
3.5. DATA DICTIONARY
Table Name: User_login
Column Name Data Type Constraint
user_name varchar(50) Primary key
Pass varchar(50)
Table-3.1 user_login
Table Name: Patient_detail
Column Name Data Type Constraint
p_id numeric(15) primary key
p_name varchar(50)
p_age numeric(5)
p_sex char(10)
p_address varchar(50)
Table Name: Patient_Record
Column Name Data Type Constraint
p-id numeric(15)
p-name varchar(50)

24. CHAPTER-4
SYSTEM ANALYSIS MODELING
“The purpose of the systems analysis and design stage is to architect and design a technical
solution which is able to meet all the requirements of the customer, as defined in the business
requirement document…”