PHP Online Doctor Search

November 4, 2017 | Author: Sumit | Category: Feasibility Study, Php, Databases, Conceptual Model, Software
Share Embed Donate


Short Description

PHP Online Doctor Search...

Description

1.Introduction _____________________________________________________________________ The purpose of this project is to develop an On-line Doctor Finder System that provides customers/Patent with the facility to search doctor and get appointment on-line. The system will provide all the facilities to its customers when their authentications [user id and password] match, including viewing account information, performing transfers, giving the customer an option of changing address, password retrieval, performing transactions, viewing appointments. The system should also support an online enrolment facility for new customers. The administrator should have the ability to perform various operations like inserting all details regards Hospital for the customer and performing functions like providing facility to user to search easily, when the customers want take appointment they have to register first and then admin verify their status after cheeking all details . The administrator also has the privilege to close the customer’s account on the request of the customer. The customer should be able to access his/her account from anywhere just by inputting the correct user-id and password.

Chapter 2 System Analysis _____________________________________________________________________

Identification on need Need to locate a provider quickly? Our online Doctor Finder (provider search) gives you flexibility in a simple format. Be sure to check your criteria for the provider search webpage most appropriate for your plan. This online Doctor Finder helps you find a perfect match for your medical needs Doctor Finder provides you with basic professional information on virtually every licensed physician. While it is our goal to provide the most up to date information, our provider network is constantly developing. Always verify that the provider you choose is participating in our network before you receive services Schedule appointments 24 hours a day, 7 days a week Whether it’s 2:00 AM and your office is closed or it’s 2:00 PM and your phones are busy—be there for your patients and fill your schedules, too.

Turn your website traffic into real appointments Potential patients are visiting your site right now—and leaving. In a matter of minutes Doctor Finder can allow these visitors to book appointments with you instantly.

You receive the appointment details! Patients provide their reason for visit and insurance information, so your practice always runs smoothly. We send several appointment reminders to make sure your patients show up on time. Patients can even book appointments directly from your personal website

Search Hint: The optimal way to search for a physician by name is to search by Last Name only and the State. You may also want to perform a "sounds-like" search if you are unsure of the exact spelling of a name or city, or if your search did not return the desired results. This option is available beneath the name and address fields on the "Search by Physician Name" page. The optimal way to search for a physician by specialty is to select a Specialty and State. If your search result is larger than the predetermined limit, you will be asked to modify the search by adding City and/or Zip Code. Occasionally, a physician is difficult to locate because: 

The physician has moved to a different state and the AMA has not yet received the new address;



A small number of physicians have requested a "no contact" designation on their AMA records (no contact records are managed like an unlisted phone number and are not released); Physicians without active licenses do not appear in DoctorFinder; The physician's name may have a space in it, like "Mc Donald" (use of the space is required); DoctorFinder uses the primary medical specialty designated by the physician (your physician may practice more than one medical specialty).

  

2.2

Preliminary Investigation:

In this process, the development team visits the customer and studies their system. They investigate the need for possible software automation in the given system. By the end of Preliminary Investigation, the team furnishes a document that holds the different specific recommendations for the candidate system. It also includes the personnel assignments, costs, project schedule, and target dates. Main Tasks of the preliminary investigation phase are:



Investigate the present system and identify the functions to be performed



Identify the objectives of the new system. In general, an information system benefits a business by increasing efficiency, improving effectiveness, or providing a competitive advantage Identify problems and suggest a few solutions Identify constraints, i.e. the limitations placed on the project, usually relating to time, money and resources Evaluate feasibility - whether the proposed system promises sufficient benefit to invest the additional resources necessary to establish the user requirements in greater detail

  

To conclude the preliminary examination, the systems analyst writes a brief report to management in which the following are listed: 

The problem that triggered the initial investigation



The time taken by the investigation and the persons consulted The true nature and scope of the problem The recommended solutions for the problem and a cost estimate for each solution

 

The analyst should then arrange a meeting with management to discuss about the report and other matters if need be. The end result, or deliverable, from the Preliminary Investigation phase is either a willingness to proceed further, or the decision to abandon the project.

.

2.3 Feasibility Study

It is a test of system proposal, according to its workability, impact on application area, ability to meet user need, and effective use of resources. It focuses on four major questions:

1. What are the user’s demonstrable needs and how does a candidate system meet them? 2. What resources are available for given candidate system? Is the problem worth solving? 3. What are the likely impacts of the candidate system on application area? 4. How well does it fit within the application area?

These questions revolve around investigation and evaluation of the problem, identification and description of candidate system, specification of performance and the cost of each system, and final selection of the best system. Objective of feasibility study is not to solve the problem but to acquire a sense of its scope. During the analysis, the problem definition is crystallized and aspects of the problem to be included in the system are determined. Feasibility analysis is to serve as decision phase to have an analysis of questions that, is there a new and better way to do the job that will benefit the user, what are the cost and savings of the alternatives. Three key considerations are involved in feasibility analysis: economic, technical, and behavioural.

2.3.1 Economic Feasibility Economic analysis is the most frequently used method for evaluating the effectiveness of a candidate system. More commonly known as cost benefit 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 implement the system. The benefits and savings that are expected from a candidate system are mainly in terms of time. When a user is

directly able to handle a project through interfaces provided by OBS without the burden of coding for every kind of modification a lot of time and human effort is saved. There was a need of estimating the bearing cost on the resources needed (manpower and computing systems) for the development of the system. Full Cost estimation of the resources was done prior to the project kick off. There was procurement costs, consultations cost, purchase of equipments, installations cost and management cost involved with the development of the new proposed system. In addition, there are start up costs, and no new costs for operating system software, communications equipment installations, recruitment of new personnel, cost of disruption to the rest of the system required. There is further no need to purchase special applications software, do software modifications, training and data collection, and just a meager documentation preparation cost involved. Lastly, there is a system maintenance, depreciation or rental cost involved with the new system.

2.3.2 Technical Feasibility

Technical feasibility centers on the existing computer system (hardware, software, etc.) and to what extent it can support the proposed addition. This phase involves financial considerations to accommodate technical enhancements. If the budget is a serious constraint, then the project is judged not feasible. System Technical feasibility is one of the most difficult areas to assess at this time of systems engineering. If right assumptions are made anything might seem possible. The considerations that are normally associated with technical feasibility include:

1) Development Risk: Can the system element be designed so that necessary function and performance are achieved within the constraints uncovered during the analysis of the present system?

The new system proposes to bring significant changes to the present system to make it more efficient. The new system proposed meets all the constraints requirements and performance requirements identified for the system to become successful.

2) Resource availability: Are skilled staffs available for the development of the new proposed system? Are any other necessary resources available to build the system? The Participants working with the proposal are seniors who have sufficient knowledge and learning skills required to know about the development of the new system. There is also no need of any other special need of resources with the development of the proposed system and it can be very well developed using the computing and non-computing resources available within the present system.

3) Technology: Has the relevant technology progressed to a state that will support the system? Technology in the form of different works done in the related field is already available with the commercial world and has been already successively used in many areas. Therefore, there is no need of any special technology to be developed. The new system is fully capable of meeting the performance, reliability, maintainability and predictability requirements. The social and legal feasibility encompasses a broad range of concerns that include contracts, liability, infringement etc. Since the system is being developed by the students of the institute themselves there are no such concerns involved with the development of the proposed system. The degree to which alternatives are considered is often limited by cost and time constraints. However variations should be considered which could

provide alternative solutions to the defined problem. Alternative systems that could provide all the functionality of the desired system are not available and hence the present solution is itself the most complete solution of the defined problem. FBTS has a feasibility of around 95% to be implemented. The candidate system fully supports the existing computer system (hardware, software, etc).

2.3.3 Behavioural Feasibility People are inherently resistant to change, and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user is likely to have towards the development of a system. The introduction of candidate system Work Planner will not require special effort to educate, sell and train the user on new ways of conducting the system. As far as performance of the system is concerned the candidate system will help attain accuracy with least response time and minimum of programmer’s efforts through the user-friendly interface.

2.4

Project Planning

Planning begins with process decomposition. The project schedule provides a road map for a software project manager. Using a schedule as a guide, the project manager can track and control each step in the software engineering process.

2.4.1

Project Tracking

S. N.

Work Task

Description

Timeline

1.

Requirements Specification

Complete specification of the system including the framing of policy etc.

1-2

2.

Database creation

List of tables and attributes of each of them.

2-4

High Level Design :

3.

High-level Design

and



E-R Diagram



DFD



Use case Diagram



Class Diagram & etc.

Detailed

4-7

Detailed Design : 

Pseudo code or algorithm for each activity

Implementation of

4.

Implementation of the frontend of the system



Login Screen



Screen that giving various options for each login



Screens for each of the options

Screens connected to data base and updating front-end data base as required.

7-10

5.

Integrating the with the database

6.

Integration Testing

The system should be thoroughly tested by running all the test cases written for the system.

11-12

Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.

12-14

7.

2.5 Project Scheduling

10-11

11-14 Weeks TESTING & 10-11 Weeks

P R O C E S S

7-10 Weeks

4-7 Weeks DETAILED 2-4 Weeks DATABASE 1-2 Weeks REQUIREME NT ANALYSIS

CREATION

DESIGN

IMPLEME NTATION

INTEGRATIO N

FINAL REVIEW

2.6. Software Requirement Specification PHP started out as a small open source project that evolved as more and more people found out how useful it was. Rasmus Lerdorf unleashed the first version of PHP way back in 1994. PHP is a recursive acronym for "PHP: Hypertext Preprocessor". PHP is a server side scripting language that is embedded in HTML. It is used to manage dynamic content, databases, session tracking, even build entire e-commerce sites. It is integrated with a number of popular databases, including MySQL, PostgreSQL, Oracle, Sybase, Informix, and Microsoft SQL Server. PHP is pleasingly zippy in its execution, especially when compiled as an Apache module on the Unix side. The MySQL server, once started, executes even very complex queries with huge result sets in record-setting time. PHP supports a large number of major protocols such as POP3, IMAP, and LDAP. PHP4 added support for Java and distributed object architectures (COM and CORBA), making n-tier development a possibility for the first time. PHP is forgiving: PHP language tries to be as forgiving as possible. PHP Syntax is C-Like.

Common uses of PHP: PHP performs system functions, i.e. from files on a system it can create, open, read, write, and close them. PHP can handle forms, i.e. gather data from files, save data to a file, thru email you can send data, return data to the user. You add, delete, modify elements within your database thru PHP. Access cookies variables and set cookies. Using PHP, you can restrict users to access some pages of your website. It can encrypt data.

Characteristics of PHP: Five important characteristics make PHP's practical nature possible:  

Simplicity Efficiency



Security



Flexibility



Familiarity

Minimum system requirements are listed below: Hardware and Software Requirements Processor

Intel Core i3

RAM:

256 MB or more

Operating System:

Windows 2000 Server, Windows XP, 2007.

Database

SQL Server 2005

Hard Disk space:

50 GB

Web

Internet Explorer 5.0 or higher, Google Chrome

Software

Dream viewer

2.7. Software Engineering Paradigm applied. Conceptual Model The first consideration in any project development is to define the projects life – cycle model. The software life – cycle encompasses all the activities required to define, develop, test, deliver, operate and maintain a software product. Different models emphasize different aspects of the life cycle, and no single model is appropriate for all types of software’s. It is important to define a life – cycle model for each product because the model provides a basis for categorizing and controlling the various activities required to develop and maintain a software product. A life–cycle model enhances project manageability, resource allocation, cost control, and product quality. There are many life–cycle models, as:

i.

The Waterfall Model

ii.

The Prototyping Model

iii.

Spiral Model

The Waterfall Model:

The model used in the development of this project is Waterfall model. This is due to some of the reasons like 

The model is more controlled and systematic



All the requirements are identified at the time of initiating the project.

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF