BCA 4th Semester Project I Proposal Report Sample - TU
Tribhuvan University
Faculty of Humanities and Social Sciences
Doctor Appointment System
A PROJECT PROPOSAL
Submitted to
Department of Computer Application
[College Name]
In partial fulfillment of the requirements for the Bachelors in Computer Application
Submitted by
[Your Name]
[Roll Number]
[Date]
Under the Supervision of
---
Contents
1. Introduction ....................................................................................................................................................1
2. Problem Statement ....................................................................................................................................1
3. Objective .......................................................................................................................................................2
4. Methodology ...............................................................................................................................................2
a) Requirement Identification ....................................................................................................................2
i) Existing System ..........................................................................................................................................2
ii) Hardware Requirement .........................................................................................................................2
iii) Software Requirement .........................................................................................................................2
b) Feasibility Study .....................................................................................................................................3
i) Economic Feasibility ....................................................................................................................................3
ii) Technical Feasibility ....................................................................................................................................3
iii) Operational Feasibility ................................................................................................................................3
5. GANTT Chart ..................................................................................................................................................4
6. DFD Diagram ...............................................................................................................................................5
7. ER Diagram ...................................................................................................................................................6
8. Expected Outcome .......................................................................................................................................6
9. References ....................................................................................................................................................6
---
1. Introduction
Doctor Appointment System is a web application developed for hospitals to manage staff patient’s data and doctor’s appointment effectively. The main aim of developing “DOCTOR APPOINTMENT SYSTEM” is to computerize the Front Office Management of Hospital. The Doctor Appointment System is tailored for use in hospitals that offer a variety of medical specialties, with the aim of addressing a broad spectrum of administrative and managerial tasks associated with hospital operations. (Al-Khawlani, 2009) The project Doctor Appointment System includes registration of patients, storing their details into the system. Healthcare is a field in which accurate record keeping and communication are critical. The software has the facility to give a unique id for every patient and stores the details of every patient and the staff automatically. With the increase of demand in hospitals, we need effective data management system for handling patient’s data and treatment details in an effective way. It deals with the collection of patient’s information, diagnosis details, etc.
2. Problem Statement
In today's healthcare, healthcare professionals typically communicate important information to one another through paper notes or in-person conversations. The patient takes the prescription to the pharmacy, stands in a queue to hand it over to the pharmacist, and then waits for the pharmacist to prepare the medication. Maintaining and sharing information regarding doctor appointments, operation schedules, and medication details among different Medicare Centers is a significant challenge. The ultimate goal of computerizing this system is to achieve quicker, more efficient results and enhance customer satisfaction. In today’s world the main problem of Doctor Appointment System is that patient have to present in the hospital lobby to get doctor appointment so by digitalizing this process by making Doctor Appointment System web based can be a solution.
3. Objective
1) To schedule an online doctor’s appointment.
2) To show services that are being provided in the hospital.
4. Methodology
a) Requirement Identification
i) Existing System
Hospitals currently use a manual system for the management and maintenance of critical information. The current system requires numerous paper forms, with data stores spread throughout the hospital management infrastructure. Often information is incomplete or does not follow management standards. Forms are often lost in transit between departments requiring a comprehensive auditing process to ensure that no vital information is lost. Multiple copies of the same information exist in the hospital and may lead to inconsistencies in data in various data stores.
ii) Hardware Requirement
PROCESSOR: INTEL DUAL CORE, I5
RAM: 1 GB
HARD DISK: 80 GB
iii) Software Requirement
OPERATING SYSTEM: WINDOWS 10
FRONTEND: HTML, CSS, JAVASCRIPT
SERVER SIDE SCRIPT: PHP
DATABASE: MY SQL
b) Feasibility Study
i) Economic Feasibility
This study is carried out to check the economic impact will have on the system will have on the organization. The amount of fund that the company can pour into the research and development of the system is limited. The expenditures must be justified. Thus, the developed system as well within the budget and this was achieved because most of the technologies used are freely available. Only the customized products have to be purchased.
ii) Technical Feasibility
This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands being placed on the client. The developed system must have a modest requirement, as only minimal or null changes for the implementing this system.
iii) Operational Feasibility
The aspect of study is to check the level of acceptance of the system by the user. This includes the 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.
5. GANTT Chart
Figure: Use case Diagram
6. DFD Diagram
7. ER Diagram
8. Expected Outcome
Since we are entering details of the patients electronically in the “Doctor Appointment System”, data will be secured. Using this application, we can retrieve patient’s history with a single click. Thus, processing information will be faster. It guarantees accurate maintenance of Patient details. It easily reduces the bookkeeping task and thus reduces the human effort and increases accuracy speed.
9. References
Al-Khawlani, M. A. (2009). A web-based Integrated Doctor Appointment System. Kuala Lumper.
---
I hope this Proposal Report Sample will help you while preparing the proposal report for your project.
0 Comments