Srs Efficient Doctor Patient Portal

326
srs
srs (software requirments specifications)

SRS Efficient Doctor Patient Portal

Efficient doctor patient portal is online management system, which provides convenience to
doctors and patients. It is use to book appointments between doctors and patients. The goal of this portal is to provide medical progress. Doctors can manage their schedule and appointments with help of this system. All the empty slots will be visibly available to the patients, which can be booked by the name and id card No. of any particular patient. The system makes it easy for doctors to manage their availability on various dates and timings. Admin maintains the medical history of the patient into the database so that every time any particular patient logs into the system, he/she can easily access their complete medical history whenever needed. In addition, it helps the doctor to refer their patient’s medical history for any further prescriptions. This allows for an automated patient doctor handling system through an online interface. This system will also provide ratings of the doctors. The user can pay online for their appointments.


 

Scope of Project Efficient Doctor Patient Portal:

Project scope is the part of project planning that involves determining and documenting a list of specific project  goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target

Functional and Non Functional Requirements of Efficient Doctor Patient Portal:

Functional Requirements :

A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs

Functional Requirements of Efficient Doctor Patient Portal:

Admin:
1. Admin can login into system.
2. Admin can add/edit/delete services into system.
3. Admin can add/edit/delete information doctors and patients.
4. Admin can view list of patients and doctors registered into the system.
Patient:
1. Patient can register into system
2. Patient can login into system.
3. Patient can check appointment availability.
4. Patient can book appointments online.
5. Patients can search doctors by name and location.
6. Patient can search doctors based on his requirements (like search doctor according to specialty or area wise)
7. Patients can check their medical history.
8. Patient can rate doctors.
Doctor:
1. Doctor can register into system
2. Doctor can login into system.
3. Doctor can view appointments of patients.
4. Doctors can manage their availability by date and time.
5. Doctors can manage their schedule.
6. Doctor can view patient’s medical history.
7. Doctor can view patients ratings.

NON-FUNCTIONAL REQUIREMENTS Efficient Doctor Patient Portal:

  • Application is user friendly.
  • Application Perform fast manipulation and calculations.
  • Application is adaptable.
  • Application will be able to work on all types of operating systems.
  • Application will be capable to handle multi user activities simultaneously.
  • There will be back up system to face any problem in system
  • All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
  • Response Time is very awesome.
Some others are:
  • Accessibility
  • Maintainability
  •  Fault Tolerance.
  • Security
  • Robustnes



 

Use Case Diagram of Diagnosis of Efficient Doctor Patient Portal

a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve



 

 

Usage Scenarios Diagnosis of Efficient Doctor Patient Portal:

A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.

 

ADOPTED METHODOLOGY for Efficient Doctor Patient Portal:

The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.



 

Work Plan of Diagnosis of Efficient Doctor Patient Portal:

Work plan



for complete srs contact us

watsapp: 03469806607