SoftwareRequirements

Specification

for
Doc Book

Preparedby
Meet Pitroda, Kathan Chauhan, Subhan Theba
SoftwareRequirementsSpecificationfor hospital management Page ii

Contents
CONTENTS................................................................................................................................................ II

REVISIONS................................................................................................................................................ II

1 INTRODUCTION................................................................................................................................. 1
1.1 DOCUMENT PURPOSE............................................................................................................................... 1
1.2 PRODUCT SCOPE...................................................................................................................................... 1
1.3 INTENDEDAUDIENCEANDDOCUMENTOVERVIEW..................................................................................... 1
1.4 DEFINITIONS,ACRONYMSANDABBREVIATIONS......................................................................................... 2
1.5 DOCUMENT CONVENTIONS...................................................................................................................... 2
1.6 REFERENCESANDACKNOWLEDGMENTS.................................................................................................... 2
2 OVERALLDESCRIPTION................................................................................................................... 3
2.1 PRODUCT OVERVIEW................................................................................................................................ 3
2.2 PRODUCT FUNCTIONALITY........................................................................................................................ 3
2.3 DESIGNANDIMPLEMENTATIONCONSTRAINTS........................................................................................... 4
2.4 ASSUMPTIONSANDDEPENDENCIES........................................................................................................... 4
3 SPECIFICREQUIREMENTS............................................................................................................... 6
3.1 EXTERNALINTERFACEREQUIREMENTS...................................................................................................... 6
3.2 FUNCTIONALREQUIREMENTS.................................................................................................................... 7
3.3 USE CASEMODEL..................................................................................................................................... 8
4 OTHERNON-FUNCTIONAL REQUIREMENTS..................................................................................8
4.1 PERFORMANCEREQUIREMENTS.............................................................................................................. 11
4.2 SAFETY AND SECURITY REQUIREMENTS................................................................................... 11
4.3 SOFTWAREQUALITY ATTRIBUTES........................................................................................................... 11

Revisions
Version PrimaryAuthor( DescriptionofVersion DateCompleted
s)
InitialVe Subhan Theba [Link] 30/07/2024
rsion cription of the system and its
basicfunctionalities
SoftwareRequirementsSpecificationfor hospital management Page iii

Block Diagram
SoftwareRequirementsSpecificationfor hospital management Page iv
SoftwareRequirementsSpecificationfor hospital management Page v
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 1

1Introduction

1.1 DocumentPurpose
This document specifies the software requirements for the Doctor Appointment Booking System. The
purpose is to provide a comprehensive description of the system's functionality, performance, and
constraints, serving as a guide for developers, testers, project managers, and other stakeholders.

1.2 ProductScope

The Doctor Appointment Booking System is a mobile application designed to facilitate appointment
scheduling between patients and doctors. The system allows patients to book, reschedule, and
cancel appointments, while doctors can manage their schedules, view appointments, and provide
feedback. The application enhances user experience, optimizes appointment management, and
improves communication between patients and healthcare providers.

1.3 IntendedAudienceandDocumentOverview

Thisdocumentisintendedfor:
 Developers: Tounderstandthefunctionalandnon-functionalrequirementsofQuickExit.
 Project Managers: To oversee the project's progress and ensure adherence to
therequirements.
 Testers:Todesignandexecute testcasesbasedon thespecifiedrequirements.
 ClientsandProfessors:Toreview
[Link] of this SRS document is organized
asfollows:
 Section2:OverallDescription:
 Section3:SpecificRequirements
 Section4:OtherNon-functionalRequirements
 Section5:OtherRequirements
Readersshouldstartwiththeoverviewsections(Sections1and2)andproceedtothedetailedrequirem
ents(Sections 3 to 4) pertinent to theirrole.
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 2

1.4 Definitions,AcronymsandAbbreviations
 SRS:Software Requirements Specification.
 UI:User Interface.
 API:Application Programming Interface
 FIREBASE:Google’s platform for app development and backend services
 UI:User Interface
 FLUTTER:Google’s UI toolkit for building natively compiled applications

1.5 DocumentConventions

 This document follows the IEEE formatting requirements. The main text is written in
TimesNew Roman font size 11 or 12. Comments and notes are in italics. The text is single-
spacedwith 1” margins. Section and subsection titles adhere to the template's style
[Link] include:
 Bold:Forsectionheadingsandimportantterms.
 Italics: Forcommentsandnotes.
 Monospace:For codesnippets anddatabasetable names..

1.6 ReferencesandAcknowledgments

ThisSRSreferstothefollowingdocumentsandwebresources:
 IEEEStandardforSoftwareRequirementsSpecifications:IEEESRSStandard

Acknowledgments:
Flutter Documentation
Firebase Documentation
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 3
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 4
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 5
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 6
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 7
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 8
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 9
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 10
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 11
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 12
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 13
 SoftwareRequirementsSpecificationfor hospitalmanagement system Page 14

2OverallDescription

2.1 ProductOverview

The Doctor Appointment Booking System will provide a mobile platform for patients and doctors to
manage appointments. Patients can book appointments with doctors, view and manage their
appointments, and receive notifications. Doctors can manage their schedules, view patient appointments,
and update their availability. The system will leverage Firebase for backend services such as
authentication, data storage, and notifications.

2.2 ProductFunctionality

 User Registration and Login: Users (both patients and doctors) will be able to create
accounts, log in, and manage their profiles.

 Appointment Scheduling: Patients can book, reschedule, or cancel appointments. Doctors

can manage their availability and view scheduled appointments.

 Notification System: Users will receive notifications for appointment confirmations,

reminders, and cancellations.

 Profile Management: Users can update their personal information and view their
appointment history.

 Backend Integration: Firebase will handle authentication, data storage, and notifications.

2.3 DesignandImplementationConstraints

 Hardware Limitations: The system must be designed to run on standard desktop,

mobile,andserver hardware, with reasonablememory and storagerequirements.
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 15
 Technologies:ThesystemwillbedevelopedusingFlutterfortheuserinterfaceandFirebas
efordatabasemanagement.
 Development Standards: The system must be designed using industry-standard
softwaredesignmethods and theUML modeling language.
 SecurityConsiderations:
Thesystemmustensuresecurehandlingofusercredentialsandpersonaldata, leveraging
Firebase's security features.
 Design Conventions: The system will follow established design patterns and
codingstandardstoensuremaintainability,particularlyadheringtobestpracticesinFlutterand
Firebasedevelopment.

2.4 AssumptionsandDependencies

 Cloud Firestore: Firebase's Cloud Firestore will be used as the primary database for storing user
data, appointment details, and doctor information.

 Firebase Cloud Messaging (FCM): For sending notifications regarding upcoming

appointments, reminders, and important updates.

 Google Maps API: If location services are integrated, the application will rely on Google Maps
API for accurate location tracking and display.

 Payment Gateway Integration: If the application includes payment functionalities, it will

depend on a third-party payment gateway for processing transactions.

 Third-Party Libraries: The app may rely on various third-party Flutter packages and libraries
for functionalities like calendar integration, UI components, etc.

 App Store and Google Play Compliance: The application will comply with the respective app
store policies for iOS and Android for successful deployment and distribution.

 User Support Infrastructure: Assumes that there is a customer support system in place to assist
users with issues, questions, or feedback.
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 16


SoftwareRequirementsSpecificationfor hospitalmanagement system Page 17
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 18
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 19
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 20
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 21
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 22
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 23

3SpecificRequirements

3.1 ExternalInterfaceRequirements

3.1.1 UserInterfaces

TheGatePassSystem(QuickExit)providesaweband applicationbased userinterface

forstudents,guards, and rectors. The interface is designed to be intuitive and user-friendly,
accessible on anydeviceor platform.
Patient App Interface:
 Home Screen: Displays upcoming appointments and allows searching for doctors.
 appointment Booking: Select doctors, choose date/time, and confirm appointments..
 Profile Management: Update personal info, view medical records, and manage
preferences
 notifications: Reminders for appointments and important alerts
Doctor App Interface:
 Schedule Management: View and manage daily/weekly schedules.
 Appointment View: Access patient details and manage consultations.
 Notifications: Alerts for appointments and important updates.

RectorInterface:
 ManageLeaveRequests:Allows rectorstoapproveordenyovernight leaverequests.
 RequestHistory:Shows ahistoryofallleaveapplicationsanddecisions.

3.1.2 HardwareInterfaces
 SoftwareRequirementsSpecificationfor hospitalmanagement system Page 24

 The application must be compatible with Android and iOS smartphones and tablets.
.

3.1.3 SoftwareInterfaces

 Firebase Authentication: For user login and registration.

 Firebase Firestore: For storing appointment data, user profiles, and notification logs.
 Firebase Cloud Messaging: For sending real-time notifications to users.

3.2 FunctionalRequirements

Thissectiondetailsthefunctionalrequirements oftheHosptitalmasagementSystem,
buildingonthegeneralfunctionalitiesoutlined

 User Registration and Login:

o Users must be able to register using their email address and password.
o Users must be able to log in using their registered credentials.
o The system should support password recovery and account management.

 Appointment Scheduling:

o Patients should be able to select a doctor, choose a time slot, and book an appointment.
o Patients should be able to reschedule or cancel appointments.
o Doctors should be able to view and manage their appointment schedule.
o Doctors should be able to set their availability for appointments.

 Notification System:

o The system should send notifications for appointment confirmations, reminders, and
cancellations.
o Notifications should be sent via Firebase Cloud Messaging.

 Profile Management:
o Users should be able to view and update their personal information, including contact
details and medical history.
o Users should be able to view their appointment history.
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 25

3.3 UseCaseModel

3.3.1 UseCase#1:Patient Use Cases:

 Register Account: Patients can create a new account by providing their email and password.

 Purpose: Allows patients to create a new account on the app.

 Process:
o Users enter their email address and choose a secure password.
o The system verifies if the email is already registered.
o Upon successful verification, the user account is created, and a confirmation email is
sent.

 Log In: Patients can log in to their account using their registered credentials.

 Purpose: Enables patients to access their account using their credentials.

 Process:
o Users enter their registered email and password on the login screen.
o The system authenticates the credentials against the Firebase database.
o If credentials are correct, users are granted access to their account.

 Book Appointment: Patients can select a doctor, choose a time slot, and confirm the
appointment.

 Purpose: Allows patients to schedule an appointment with a doctor.

 Process:
o Patients can search for doctors by specialty, name, or location.
o Once a doctor is selected, available time slots are displayed.
o Patients choose a convenient date and time and confirm the appointment.
o The system updates the doctor's schedule and sends a confirmation notification to the
patient.

 Reschedule Appointment: Patients can change the time or date of an existing appointment.

 Cancel Appointment: Patients can cancel a scheduled appointment.

 View Appointment History: Patients can view a list of past and upcoming appointments.

 Receive Notifications: Patients receive notifications about appointment status and reminders.
 SoftwareRequirementsSpecificationfor hospitalmanagement system Page 26

3.3.2 UseCase#2:Doctor

1. Register Account

 Purpose: Allows doctors to create a new account on the app.

 Process:
o Doctors enter their email address and choose a secure password.
o The system checks if the email is already registered.
o Doctors may be required to provide additional information such as medical license details
for verification.
o Upon successful verification, the doctor’s account is created, and a confirmation email is
sent.

2. Log In

 Purpose: Enables doctors to access their account using their credentials.

 Process:
o Doctors enter their registered email and password on the login screen.
o The system authenticates the credentials against the Firebase database.
o If credentials are correct, doctors are granted access to their account, where they can
manage their schedule and appointments.

3. Manage Schedule

 Purpose: Allows doctors to update their availability and manage their appointment schedule.

 Process:
o Doctors access the scheduling section within the app.
o They can set their available hours, block out times, or mark specific days as unavailable.
o The system updates the availability in real-time, reflecting changes in the patients’
booking interface.
o Doctors can also view and manage booked appointments, adjusting their availability
based on their schedule.

4. View Appointments

 Purpose: Enables doctors to view their scheduled appointments and patient details.

 Process:
o Doctors access the appointments section, where a list of all upcoming and past
appointments is displayed.
o Each appointment entry provides details such as the patient’s name, appointment date and
time, and reason for the visit.
o Doctors can click on an appointment to view more detailed information, including patient
history and notes.
 SoftwareRequirementsSpecificationfor hospitalmanagement system Page 27

o The system allows doctors to prepare in advance for each appointment and make any
necessary arrangements.

5. Receive Notifications

 Purpose: Keeps doctors informed about appointment confirmations, changes, and reminders.

 Process:
o Notifications are sent to doctors regarding new appointment bookings, cancellations,
rescheduling, and reminders for upcoming appointments.
o Notifications can be delivered via in-app alerts, push notifications, or email, depending
on the doctor's preferences.
o Doctors are alerted promptly about any changes to their schedule, allowing them to
manage their time effectively.
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 28
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 29

4Non-functionalRequirements

4.1 PerformanceRequirements

 Simultaneous User Handling:

o The system must be designed to support up to 10,000 concurrent users without

significant degradation in performance.

o This involves optimizing server resources, efficient database queries, and scalable
backend architecture using Firebase's real-time database and cloud functions.

 Response Time:

o All user interactions, including booking appointments, logging in, and updating
schedules, should be processed within 2 seconds.

o This requirement is critical for ensuring a smooth user experience and includes
actions like loading screens, database queries, and API calls.

o To achieve this, the app should implement asynchronous operations and minimize
data transfer by using lightweight data formats such as JSON.

4.2 Safety and Security Requirements

 Data Encryption:

o All sensitive user data, including personal information and appointment details, must
be encrypted both in transit and at rest.

o Encryption standards such as TLS (Transport Layer Security) for data in transit and
AES (Advanced Encryption Standard) for data at rest should be employed.

o Firebase’s built-in security features, such as Firestore security rules and Firebase
Authentication, should be utilized to enforce encryption.

 Compliance with Data Protection Regulations:

o The application must comply with relevant data protection regulations, such as the
General Data Protection Regulation (GDPR) in the EU or HIPAA in the US,
depending on the region of deployment.

o This includes obtaining explicit consent from users for data collection, providing
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 30
them with the ability to access and delete their data, and ensuring data is stored and
processed in compliance with these regulations.

 Secure Authentication:

o Passwords must be securely handled by hashing and salting using algorithms like
bcrypt.

o The application should provide secure account recovery options, such as multi-factor
authentication (MFA) and email-based password reset.

o Firebase Authentication services can be used to manage user authentication securely,

supporting features like MFA and secure password storage.

4.2 Software Quality Attributes

 Usability:

o The application should be designed with a user-friendly interface that is intuitive and
easy to navigate.

o The UI/UX design should be consistent, with clear labeling, minimalistic design, and
responsive elements that work well on various screen sizes.

o Regular user testing and feedback sessions should be conducted to ensure that the
application meets the needs of its users, focusing on accessibility and user
experience.

 Reliability:

o The system should maintain a minimum uptime of 99.9%, ensuring that users have
consistent access to the application with minimal downtime.
o This requires robust infrastructure, including reliable cloud services provided by
Firebase, redundancy in database and server setup, and continuous monitoring for
potential issues.
o Regular backups and disaster recovery plans should be in place to quickly restore
service in case of failures.

 Maintainability:

o The codebase should be modular, following best practices like separation of

concerns and using design patterns where applicable.

o Code should be well-documented with clear comments, and comprehensive

documentation should be maintained for all aspects of the system, including setup,
deployment, and troubleshooting.

o The system should be designed to allow for easy updates and feature enhancements,
using version control (e.g., Git) and continuous integration/continuous deployment
(CI/CD) pipelines to streamline development and deployment processes.
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 31
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 32
SoftwareRequirementsSpecificationfor hospitalmanagement system Page 33