Professional Documents
Culture Documents
Year 2011
1.0 Introduction
1.1 Definition: What is Patient Tracking?
Patient tracking To handle the appointment tasks more easily i.e. online, to provide online medical help or treatment (in case of nominal disease), to manage the bulk of data of doctors, patients, medical store keepers..etc. Moreover it manages the list of doctors that are joined or left the company, the patients history data, reports generation..etc in the system.
1.2 Purpose:
The present system is completely manual in nature. Patient has to contact doctors/medical help by means of telephonic communication.
1.3 Scope:
All the information is shorted in the various files which are being kept in various departments; this requires more paper work, wastage of time, which results in inefficient working.
1.4 Objective:
It is very tedious and time consuming to get the information from such a vast de-centralized structure. It is need of time to make modifications in the manual oriented complex system.
1|Page
Year 2011
PHP:
PHP is a powerful tool for making dynamic and interactive Web pages. PHP is the widely-used, free, and efficient alternative to competitors such as Microsoft's ASP. In our PHP tutorial you will learn about PHP, and how to execute scripts on your server. What is PHP? PHP stands for PHP: Hypertext Preprocessor PHP is a server-side scripting language, like ASP PHP scripts are executed on the server PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Generic ODBC, etc.) PHP is free to download and use
2|Page
Year 2011
Why PHP?
PHP runs on different platforms (Windows, Linux, Unix, etc.) PHP is compatible with almost all servers used today (Apache, IIS, etc.) PHP is FREE to download from the official PHP resource: www.php.net PHP is easy to learn and runs efficiently on the server side
Where to start?
To get access to a web server with PHP support, you can: Install Apache (or IIS) on your own server, install PHP, and MySQL Or find a web hosting plan with PHP and MySQL sup
3|Page
Year 2011
MySQL:
MySQL is a database server MySQL is ideal for both small and large applications MySQL supports standard SQL MySQL compiles on a number of platforms MySQL is free to download and use MySQL is a database. The data in MySQL is stored in database objects called tables. A table is a collection of related data entries and it consists of columns and rows. Databases are useful when storing information categorically. A company may have a database with the following tables: "City_master", "User_detail", "Doctor_master" and "Medical_store".
4|Page
Year 2011
Ajax:
AJAX stands for Asynchronous JavaScript and XML. Give ability to refresh only those contents of web pages that are changed by the user and Stop the complete page reloading for each user event.
AJAX is not a new programming language, but a new way to use existing standards. With AJAX you can create better, faster, and more userfriendly web applications. AJAX is based on JavaScript and HTTP requests. Because the server returns a new page each time the user submits input, traditional web applications can run slowly and tend to be less userfriendly. With AJAX, your JavaScript communicates directly with the server, through the JavaScript XMLHttpRequest object
With an HTTP request, a web page can make a request to, and get a response from a web server - without reloading the page. The user will stay on the same page, and he or she will not notice that scripts request pages, or send data to a server in the background.
5|Page
Year 2011
Project planning is perhaps one of the most important works in developing any project. Before the project can begin estimate regarding work to be done, what resources will e required and how much time will elapse from start to the finish of a project.
Analysis Design Implementation Testing Maintenance Impleme Fig 2.1 Waterfall model ntati
6|Page
Year 2011
In which first we have studied requirement of market then accordingly we have selected project and designed. After completing design we have implemented it and then after verification and then maintenance.
7|Page
Year 2011
2.5. Feasibility Study: The feasibility study is an important and crucial part of the system analysis. The main purpose to carry out the feasibility analysis is to understand how efficient and beneficial would the new system be to the organization with minimal changes and efforts made. There are three aspects in the feasibility study portion of the preliminary investigations.
2.6. Technical Feasibility: The technical feasibility means whether the project can be done with the current equipment, existing software technology and the current knowledge or not. Our system is technically feasible. It is developed using PHP platform with PHP language for coding. PHP is the most used and acknowledged tool for website development and PHP language is an advanced programming language, which all together makes our system technically feasible.
R.C Technical Institute 8|Page
Year 2011
2.7. Economical Feasibility: Economical feasibility generally means that the system development cost should be sufficiently beneficial in creating a system to make the cost acceptable. The system doesnt need much economic investments as it is developed under the resources that are easily available and no external hardware devices are required.
2.8 . Operational Feasibility: Operation feasibility deals with the acceptance of the users and their willingness to use the system. The system should be such that it is acceptable by all its users and no user hesitates to use it. The system is such that it facilitates both power users and guest users, who are the users of this system. All users help each other to increase their knowledge by sharing different Image And Videos and using feedback section system becomes more interactive. The System is user friendly and can be used easily.
2.9 REQUIREMENTS VALIDATION Are requirements stated clearly? ----------------------------------------------Yes Is the source (e.g. a user, a document, a customer) of the requirement identified? ------------------------------------------------------------------------- Yes Is the system specification structured in a way that leads to easy understanding, easy reference and easy translation into more technical work product? --------------------------------------------------------------------Yes Are requirements valid? -------------------------------------------------------- Yes
9|Page
Year 2011
2.9.1. Features of new system: Administrator control Online appointment Online payment Medicine delivery
2.10. Risk Management: A risk is any anticipated unfavourable event or circumstances that can occur why a project is underway.
2.10.1 Risk identification: Risk identification is the first stage of risk management. It is concerned with discovering possible risks to the project. Risk identification may be carried out as a team process using brainstorming approach. 1) 2) 3) 4) Technology risk People risk Organization risk Tools risks
2.10.2 Risk analysis: Personal Shortfalls: They may cause the development delays and would cause a change in the working strategy due to development dependencies of the functional modules.
Unrealistic Schedule: It may cause the developers to give unrealistic commitments to the users and so lose their faith when the deliverables are not produced as per schedule.
R.C Technical Institute 10 | P a g e
Year 2011
Developing wrong software functions: It can be caused due to wrong requirement analysis or wrong programming method used to automate the requirements. It may cause the system to fail and not be implemented at all.
Developing wrong user function: It may be caused due to lack of user acceptance and user involvement during development.
2.10.3 Risk planning: Personal shortfalls:Ensuring the presence of at least one of the project member through the project duration and completing the targeted work for the day according to priority handled it.
Unrealistic schedule:Plan is done to develop the system at least one week before the training period completion in order to handle the schedule delay.
Developing wrong software functions / developing wrong user function:A constant user involvement at all stages of project deliverables was done in order to check for the correct system flow as well as for user acceptance testing.
11 | P a g e
Year 2011
Misuse of the system:Predefined id and password must be there so that none can misuse the system.
System failure:Well established network and required hardware and environment should be considered.
Limitation:
We know that every system has its limitations. As the bulk of data increases, the response time from system also increases. This system perhaps may totally fail in the countries where the use of computer or internet is not cost effective. If the patient has some serious illness then this system cannot help.
12 | P a g e
Year 2011
Software: Description PHP MySQL Dreamweaver Wamp Server Table 3.2 Software Requirement
13 | P a g e
Year 2011
3.2 Constraint: 3.2.1 Technical Constraints: As we have provided above software and hardware requirement there are no technical constraints for our system.
14 | P a g e
Year 2011
3.2.2 Cost management: The cost of setting system is not a major concern. The company do not have to spend more with initial installation just load the system in the server.
3.2.3 User Constraints: User must have internet connection. User who wishes to connect must have his /her user Id and Password correct.
3.2.4 Safety and security consideration: System provides different of information in screen design to use system safely in the system there are login and password facility for security of database. Two types of authority are there like update and read only security of system.
3.3 Specific Requirement: 3.3.1 Functionality: Our website functions properly if it runs on computer with requirements recommended by us.
3.3.2 Usability: The user should have the basic knowledge of internet to traverse through this system. The user needs user name & password to login into the system. Guest users can also access the system but with some limitations. Registered user has access to all the features of our website as they are registered user of our system. System shows different response messages as necessary.
15 | P a g e
Year 2011
3.3.3 Reliability: System is reliable because it is continuously monitored by administrator. We have also used different validations to restrict user from submitting invalid data. 3.3.4 Performance: If system is used with features as we have mentioned it gives best performance. We have used AJAX control which increases the performance of our system by making it possible to execute some part of page updatable without sending and executing it on server side. We have take care that minimum time is taken in loading pages and making our website faster.
16 | P a g e
Year 2011
4.0 Diagram
Data Flow Diagram (DFD): Context/Zero Level:
Admin
Login verification
Login verification
Patient
Appointment
View medicine detail
Payment Give medicine to patient
Doctor
Login verification
View Patient
Login verification
Medical Store
17 | P a g e
Year 2011
First Level:
Admin Doctor Patient Medical Store
Login details Verrification Login details Verrification Login details Verrification Login details Verrification
Login
Doctor details Doctor details Specialist details Specialist details Ward details Ward details
Dieses details Dieses details
Doctor
Admin
Doctor
Medicine,patient details
medicine details
Precription
patient details
Patient
Appointment details
Appointment details
Appointment
Medical Store
Company,Medicine details
18 | P a g e
Year 2011
Patient
Patient details
Doctor details
Medical Store detail
Login details
Login Details Verification Verification Login Details Login Details Verification Login Details Verification
Admin
Login
Login
User name,selected que.& ans. durig reg. User name,selected que.& ans. durig reg.
Registration Login
19 | P a g e
Year 2011
2.1 ADD
Ward details Dieses details Medical Store details Doctor details Doctor details Specialist details Specialist details Ward details Ward details Dieses details Dieses details M.store details M.store details Doctor details Doctor details Specialist details Specialist details Ward details Ward details Dieses details Dieses details M.store details M.store details
2.2 UPDATE
2.3 DELETE.
Patient
Payment details
Payment details
Payment
20 | P a g e
Year 2011
Doctor
5.1 ADD
Company Medicine
5.2 UPDATE
Company Medicine
5.3 DELETE.
Company Medicine
21 | P a g e
Year 2011
E-R Diagram
U_id
U_pass p_id
Admin
m_id 1
Has
d_id
Login
Has M M M Patient M
Modify
Dieses w _id
d_name pay_id
p_name
M Modify c_id M Company 1 c_name M Has Doctor 1 doc_name M Medicine Has M Give Has doc_id Ward 1 w _name
View
1 Precription
pre_id
p_id
med_id
med_name M Specialist
s_id
s_name
22 | P a g e
Year 2011
Foreign key
City_master:
Column Name C_id C_name Data Type Int(4) Varchar(20) Null No No Description City id City name Constrain Primary key Extra Auto increment
Word_master:
Column Name W_id W_name Data Type Int(4) Varchar(20) Null Description No Word id No Word name Constrain Primary key Extra Auto increment
Security_master:
Column Name S_id S_Question Data Type Int(4) Varchar(70) Null No No Description Security id Security que Constrain Primary key Extra Auto increment
23 | P a g e
Year 2011
Company_master:
Column Name Co_id Co_name Address C_id Pincode Phone_no Email Medical_id Data Type Int(4) Varchar(20) Varchar(40) Int(4) Int(6) bigint(10) Varchar(50) Int(4) Null No No No No No No No No Description Company id Company name Company address City id Pincode of city Phone number Email of company Medical id Constrain Primary key Extra Auto increment
Foreign key
Foreign key
Doctor_master:
Column Name D_id UserName DoctorName Gender Address C_id Pincode Phone_no Mobile_no Email Word_id Status Data Type Int(4) Varchar(20) Varchar(20) Varchar(5) Varchar(30) Int(4) Int(6) bigint(10) bigint(10) Varchar(50) Int(4) Varchar(20) Null No No No No No No No No No No No No Description Doctor id User name of doctor Name of doctor Gender Address of doctor City id Pincode of city Phone number Mobile number Email of doctor Word id Status of doctor Constrain Primary key Extra Auto increment
Foreign key
Foreign key
Medicine:
Column Name Med_id Med_name Co_id Data Type Int(4) Varchar(20) Int(4) Null No No No Description Medicine id Medicine name Company id Constrain Primary key Foreign key Extra Auto increment
24 | P a g e
Year 2011
Login:
Column Name L_id UserName Password Type Sec_id Ans Data Type Int(4) Varchar(20) Varchar(20) Varchar(20) Int(4) Varchar(20) Null No No No No No No Description Login id User name Password of user Type of user Security id Answer of se. ques. Constrain Primary key Extra Auto increment
Foreign key
User_detail:
Column Name U_id UserName F_name L_name Gender Bod Address C_id Pincode Phone_no Mobile_no Email Height Weight BloodGroup Data Type Int(4) Varchar(20) Varchar(20) Varchar(20) Varchar(5) Date Varchar(50) Int(4) Int(6) bigint(10) bigint(10) Varchar(50) Varchar(10) Varchar(10) Varchar(10) Null No No No No No No No No No No No No No No No Description User id User name First name Last name Gender of user Date of birth Address of user City id Pincode of city Phone number Mobile number Email of user Height of user Weight of user Blood group Constrain Primary key Extra Auto increment
Foreign key
Prescription:
Column Name Pre_id H_id Mid Data Type Int(4) Int(4) Int(4) Null No No No Description Prescription Id History id Medicine id Constrain Primary key Foreign key Foreign key Extra Auto increment
25 | P a g e
Year 2011
Medical_store:
Column Name M_id UserName MedicalName Address C_id Pincode Phone_no Mobile_no Email Status Data Type Int(4) Varchar(20) Varchar(20) Varchar(50) Int(4) Int(6) bigint(10) bigint(10) Varchar(50) Varchar(20) Null No No No No No No No No No No Description Medical id User name Medical name Address of medical City id Pincode Phone number Mobilr number Email of medical Status of medical Constrain Primary key Extra Auto increment
Foreign key
History:
Column Name H_id P_id D_id Disease Dose Date M_id Status Data Type Int(4) Int(4) Int(4) Varchar(20) Varchar(20) Date Int(4) Varchar(20) Null No No No No No No No No Description History id Patient id Doctor id Disease of patient Dose of medicine Date history Medical id Status of history Constrain Primary key Foreign key Foreign key Extra Auto increment
Foreign key
26 | P a g e
Year 2011
27 | P a g e
Year 2011
SIGN UP:-
28 | P a g e
Year 2011
29 | P a g e
Year 2011
30 | P a g e
Year 2011
31 | P a g e
Year 2011
32 | P a g e
Year 2011
33 | P a g e
Year 2011
34 | P a g e
Year 2011
35 | P a g e
Year 2011
USER APPOINTMENT:-
36 | P a g e
Year 2011
37 | P a g e
Year 2011
38 | P a g e
Year 2011
39 | P a g e
Year 2011
40 | P a g e
Year 2011
41 | P a g e
Year 2011
42 | P a g e
Year 2011
43 | P a g e
Year 2011
44 | P a g e
Year 2011
45 | P a g e
Year 2011
46 | P a g e
Year 2011
47 | P a g e
Year 2011
48 | P a g e
Year 2011
CONTACTS:-
49 | P a g e
Year 2011
FORGOT PASSWORD:-
50 | P a g e
Year 2011
ABOUTUS:-
51 | P a g e
Year 2011
7.0 Testing
7.1 Testing Plan: Software Testing:Testing involves operation of a system or application under controlled conditions and evaluating the results. The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they dont happen when they should. It is oriented to detection.
The need for Testing:No matter how good a programmer is, no application will ever be one hundred percent correct. Testing was important to us in order to ensure that the application works as efficient as possible and conforms to the needs of the system. Testing was carried out throughout the development of the application, not just the application has been developed, as at this stage it took a great deal of effort to fix any bugs or design problems that were occurred.
7.2 TESTING STRATEGY When our application was configured and customized in the system, the test was observed that this configuration or customization does not cause any improper processing or violation.
52 | P a g e
Year 2011
The following care was taken when the application was developed at the local machine. The interface may have something not proper, which can be tested by this checklist: Number of input parameter equal to number of argument? Parameter and argument attributes match? Number of arguments transmitted to called forms equal to number of parameters? Attributes of arguments transmitted to called forms to attributes of parameters? Number attributes and order of arguments to built-in functions correct? The local data structures for a form are common source of errors. The following types of errors should be searched for, Improper or inconsistent typing Erroneous initialization or default values Incorrect (misspelled or truncated) variables names Inconsistent data types Underflow, overflow and addressing exception As far as unit testing is concerned we did it at the time of coding in an informal but extensive way, so as to reduce number of problems arising out of incorrect syntax, incorrect variable, function names etc. Close the database connection when not required. Care was taken to check for any infinite loop that exists in code before executing the code.
53 | P a g e
Year 2011
Statement Coverage Criterion:This is the simplest coverage criterion. We are checking in it that each statement of the program was executed at least once. Branch Coverage Criterion:An improvement over statement is Branch Coverage. In that we are running a series of test to ensure that all branches are tested at least once.
Path Coverage Criterion:There are many errors which were not detected by statement or branch testing. The reason is that some errors are related to some combination of branches and it may be not check in other test. We are checking in this test is all path of programs are executed or not.
54 | P a g e
Year 2011
7.3.2 Black Box Testing:Black-box and white-box are test design methods. Black-box test design treats the system as a "black-box", so it doesn't explicitly use knowledge of the internal structure. Black-box test design is usually described as focusing on testing functional requirements. Also know as behavioral, functional, opaquebox, and closed-box Black Box Testing was helpful us to find error such as: Interface error Incorrect or missing functions. Errors in data structures or external database access. Performance Errors. Initialization and termination errors.
7.3.3 Unit Testing:Unit testing is a method of testing the correctness of a particular module of source code. The idea is to write test cases for every non-trivial function or method in the module so that each test case is separate from the others if possible. The developers mostly do this type of testing. In this method of testing we test all individual components to ensure that they operate correctly. Each component is tested independently without other system components.
55 | P a g e
Year 2011
7.3.4 Integration Testing:It is the phase of software testing in which individual software modules we are combined and tested as a group. It follows unit testing and precedes system testing. The purpose of Integration testing is to verify functional, performance and reliability requirements placed on major design items. It takes as its input modules that have been checked out by unit testing, groups them in larger aggregates, applies tests defined in an Integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.
56 | P a g e
Year 2011
8.0 Reference
Websites:
Books:
The complete reference Beginning php 5.3
57 | P a g e