Software Requirements Specification (1)
Software Requirements Specification (1)
Specification (SRS)
Doctor-Patient Appointment System
Submitted By:
Submitted To:
Sir Umar Hyat
Abdul Wali Khan University, Mardan
Table of Contents
Introduction
1.1 Purpose of the Project
1.2 Scope of the Project
1.3 Objectives
1.4 Target Audience
Target Audience
3.1 Patients
3.2 Doctors
3.3 Administrators
3.4 Stakeholders
Non-Functional Requirements
7.1 Performance
7.2 Security
7.3 Usability
7.4 Maintainability
1. Introduction
1.1 Purpose of the Project
Creating an intuitive web application where patients can browse doctors, schedule
appointments, and organize their schedules seamlessly.
Equipping doctors with tools to manage their schedules, view appointments, and
update their profiles efficiently.
Developing an admin panel to monitor the system, assign user roles, and generate
insightful reports.
Ensuring robust data security to safeguard user privacy and maintain trust.
Optimizing the platform for accessibility across desktops, tablets, and mobile
devices via web browsers.
1.3 Objectives
Doctors: Healthcare providers who need an organized way to manage their schedules,
access patient information, and handle appointment requests.
1.
2. Scope and Objectives
Scope
For Patients:
For Doctors:
Access patient medical histories (if integrated with a medical records system).
Out of Scope:
2.2 Objectives
3. Target Audience
3.1 Patients: Individuals who use the system to book appointments with healthcare
providers. These users span various age groups and may have differing levels of
technical expertise.
3.2 Doctors: Healthcare professionals who utilize the system to organize their
schedules and appointments. This group includes general practitioners, specialists,
and other medical experts.
3.4 Stakeholders:
User Registration and Login: Patients can securely create accounts using their email
or phone number.
Search for Doctors: Search functionality allows patients to find doctors based on
specialty, location, or availability.
Appointment Reminders: Automated reminders are sent via email or SMS to reduce
missed appointments.
Medical History Access (Optional): Patients can view their medical records if the
system integrates with an electronic medical records (EMR) platform.
Schedule Management: Doctors can define their availability and manage their
working hours.
Patient Management: View patient details, appointment history, and other relevant
information.
User Management: Administrators have tools to manage both patient and doctor
accounts.
5.1 Patient:
5.2 Doctor:
5.3 Admin:
Oversee and manage user accounts for both patients and doctors.
6.3 Search and Filtering Module: Allows patients to search for doctors based on
specialty, location, or availability with ease.
6.5 Admin Dashboard: Equips administrators with tools to manage user accounts,
oversee appointments, and configure system settings.
7. Non-Functional Requirements
7.1 Performance
Response Time: Pages should load within 2 seconds under normal load
conditions.
Scalability: The system should handle up to 10,000 concurrent users.
Availability: The system should have an uptime of 99.9%.
7.2 Security
Authentication: Secure login mechanisms (e.g., email/password or OTP).
Data Encryption: Sensitive data must be encrypted during transmission
and at rest.
Audit and Logging: Critical actions should be logged for auditing
purposes.
7.3 Usability
Intuitive Interface: Key features should be accessible within 3 clicks.
Accessibility: The system should comply with WCAG 2.1 standards.
Responsive Design: The system should work seamlessly on desktops,
tablets, and mobile devices.
7.4 Maintainability
Modularity: The system should be built using a modular architecture.
Documentation: Comprehensive technical and user documentation
should be provided.
Backup and Recovery: Regular backups should be performed, with a
recovery plan in place.
o Manage Users: Admins can add, edit, or delete patient and doctor
accounts.
o Generate Reports: Admins can generate reports on system
usage, appointments, and other metrics.