PROJECT REPORT ABOUT DIFFERENT PROJECTS, Summaries of Project Management

Download PROJECT REPORT ABOUT DIFFERENT PROJECTS and more Summaries Project Management in PDF only on Docsity!

Software Requirements

Specification

Project Name:

Doctor Finder

Developed By:

Shubham Savaliya

Abstract: This Software Requirements Specification (SRS) describes the system requirements, and system actions. The Software Requirements Specification includes; ● Introduction, ● Use Cases, ● Functional, Non-functional and Environmental Requirements, For the software; Keywords: Doctor Finder system, uml, use case diagram, use case, software requirements specification, system requirements specification, MySQL, Java, Windows, JSP, doctor, user, administrator.

● To assist users in finding the nearest medical practitioner (or dentist). ● To reduce costs associated with appointment management. ● To build a community of healthcare providers and their users. ● To document the doctor-user relationship in detail by maintaining records of all appointments. ● To generate reports for physicians and system administrators. ● To handle physician billing. ● To enable doctors to upload their profiles and promote their practices.

1.3 Overview

Project Review Deliverables Deadline Review-1 Presentation February 11, 2023 Review-2 Content,Implementat ion,SRS Report, Results and result analysis March 25, 2023 Review-3 Content, Results and result analysis,Future scope, Limitation, Conclusion April 29, 2023 Report Prepare Draft and submit to guide May 24, 2023

2.0 Use Cases UC101 User comes to register on the system website Actors User, system. Goal(s)

1. To be registered with the system. Step(s)
2. The user goes to the website and registers with the system. Result 1) User has now been satisfactorily registered with the system
3. Users can now make doctors’ appointment system with no hassle. UC102 User searches for doctors by area and speciality (or even by name) Actors User, system. Goal(s)
4. To choose a doctor based on their proximity, ratings.
5. To book a doctor’s appointment. Step(s)
6. The user searches for a doctor, selecting the area and speciality, or their specific doctor’s name.
7. The user reads the search returned doctors’ profiles and subsequently chooses the doctor whom they prefer to the rest.
8. The user reads other users’ ratings and recommendations about that specific doctor.
9. The user can return to their search result to see other doctors’ profiles.
10. Finally, the user decides to make an appointment with one of the doctors.
11. The user visually views the doctor’s entire appointment schedule.
12. The user selects a time slot and makes an appointment with that doctor. Result 1) The user gets a system appointment confirmation mail to confirm their placed appointment (this should not be confused with the actual doctor’s confirmation). UC103 Doctor logs in. Actors Doctor, system. Goal(s)
13. To be logged in.
14. To check his/her user appointments. Step(s)
15. Doctor enters his/her username.
16. Doctor enters his/her password.
17. System validates the doctor.

2.1 Use Case Diagrams:

3.0 Functional Requirements User To-Do list management ● User registers with the system. ● User logs into the system. ● User searches for the nearest doctor. ● User places a doctor’s appointment ● User rates system doctors ● User logs out from the system Doctor To-Do List ● Doctor logs with the system. ● Doctor checks his/her appointment schedule. ● Doctor logs out from the system Admin To-Do List ● Admin does the general upkeep of the system. ● Admini draws reports from the system. ● Admin manages doctor’s billing accounts. ● Admin add or delete doctor’s or user’s accounts. 4.0 Non-Functional Requirements

4.1 Usability Requirements

This system provides medical practitioners to have appointments well scheduled. The only requirement is to have computers with Internet connection. The program provides doctors to see their weekly appointments while they are not at their offices. Accessibility of the information and usability of the program is easy. With few clicks the user can reach the destination information.

4.2 Reliability and up-time Requirements

The system should be able to perform consistently and reliably under different conditions and scenarios. The system should be able to recover from failures and errors gracefully.

issues and errors. The system is a web based system and can be run on every computer with Internet access. The system can be installed for any operating system.

4.7 Business Life-Cycle Requirements

While the system is specifically designed to coordinate appointments between doctors and patients in Community Health Centers (CHCs), it can also be customized to suit the needs of other businesses that require appointment management. As a result, this system is practical for a diverse group of industries and can benefit a large number of people. The system may also undergo innovative improvements that can have a broader impact on various businesses. 5.0 Environmental Requirements

5.1 System Hardware Requirements

● PC 2.4 GHz or higher. ● 2 GB RAM or higher. ● 100 GB Disc Space or higher. ● Video-Graphic Card (800 x 600) 128 Mb or more. ● Internet Access.

5.2 System Software Requirements

Software requirement to run the system: ● Microsoft Windows 10. ● Any version of Chrome, Mozilla Firefox, Opera etc. ● Eclipse ● XAMPP ● Java, MySQL

5.3 Application program interfaces (APIs)

There will be no API for this application because there will be no additional software planned to be added to the program.

5.4 Data Import and Export Requirements

Application is a web based one and users can reach their data from any computer with the Internet. ● Import will not be performed. ● Export will not be performed.