Software Requirements Specifications

<Doctor Appointment App>

Project Code:

Internal Advisor:
Sir Israr Ahmed

External Advisor:

Project Manager:
Dr. Muhammad Ilyas

Project Team:
Ali Zahid (16-uglc-418)
Talha Shoukat (16-uglc-410)
Atta Ullah (16-uglc-418)

Submission Date:
02-Dec-2019

__________________ _________________
Project Supervisor’ Signature Project Manager’s Signature
<Project code> Software Requirements Specifications <Version1.0>

Document Information
Category Information

Customer UOS
Project <Doctor Appointment App>
Document Requirement Specifications
Document Version 1.0
Identifier PGBH01-2003-RS
Status Draft
Author(s) <Ali Zahid, Talha Shoukat, Attaullah>
Approver(s) PM
Issue Date Nov.18, 2019
Document Location
1. Advisor
Distribution 2. PM
3. Project Office

Definition of Terms, Acronyms and Abbreviations

This section should provide the definitions of all terms, acronyms, and abbreviations required to interpret
the terms used in the document properly.

Term Description
ASP Active Server Pages
RS Requirements Specifications

IOS iPhone Operating System

UI User Interface

FAQs Frequently Asked Questions

MacOS Macintosh Operating System

Dec 02, 2019 Page 2 of 13

<Project code> Software Requirements Specifications <Version1.0>

Dec 02, 2019 Page 3 of 13

<Project code> Software Requirements Specifications <Version1.0>

Dec 02, 2019 Page 4 of 13

<Project code> Software Requirements Specifications

Table of Contents

1. INTRODUCTION.................................................................................................................5
1.1 PURPOSE OF DOCUMENT........................................................................................................5
1.2 PROJECT OVERVIEW...............................................................................................................5
1.3 SCOPE.....................................................................................................................................5

2. OVERALL SYSTEM DESCRIPTION................................................................................5

2.1 USER CHARACTERISTICS........................................................................................................5
2.2 OPERATING ENVIRONMENT.....................................................................................................6
2.3 SYSTEM CONSTRAINTS...........................................................................................................6

3. EXTERNAL INTERFACE REQUIREMENTS.................................................................6

3.1 HARDWARE INTERFACES........................................................................................................6
3.2 SOFTWARE INTERFACES..........................................................................................................6
3.3 COMMUNICATIONS INTERFACES.............................................................................................6

4. FUNCTIONAL REQUIREMENTS.........................................................................................7
4.1 FUNCTIONAL REQUIREMENTS FOR THE PATIENT:...................................................................7
4.2 FUNCTIONAL REQUIREMENTS FOR THE DOCTOR:..................................................................7
4.3 FUNCTIONAL REQUIREMENTS FOR THE ADMIN:.....................................................................7

5 NON-FUNCTIONAL REQUIREMENTS...........................................................................8
5.1 USABILITY..............................................................................................................................8
5.2 RELIABILITY...........................................................................................................................8
5.3 PERFORMANCE REQUIREMENTS.............................................................................................8
5.4 SAFETY REQUIREMENTS.........................................................................................................8
5.5 SECURITY REQUIREMENTS.....................................................................................................8
5.6 USER DOCUMENTATION..........................................................................................................9

6 BUSINESS RULES................................................................................................................9

7. ASSUMPTIONS AND DEPENDENCIES...............................................................................9

7.1 ASSUMPTIONS:........................................................................................................................9
7.2 DEPENDENCIES:......................................................................................................................9
Dec 02, 2019 Page 5 of 13
<Project code> Software Requirements Specifications

8. REFERENCES....................................................................................................................10

9. Appendices............................................................................................................................10

Dec 02, 2019 Page 6 of 13

<Project code> Software Requirements Specifications

1. Introduction

1.1 Purpose of Document

The main purpose of this document is to provide the whole description about the project so who
will read this document can understand the overall system of the project where the purpose of
this is to encapsulate the working and functionality of this project.

1.2 Project Overview

This project is used for managing information in the health care such as patient record, patient
appointment system, patients scheduling appointment and doctor schedule is not only a simpler
way to save time and reduce cost, but also a way to support and improve the health care
information to be more accessible and flexible (modifying, saving, deleting, updating) for
system users and storing data efficiently. In addition, it improves the quality of data control. The
main objective of this project is to make an official android app for patients so that they can
appoint a doctor from the comfort of their home or anywhere at any time through app.

1.3 Scope
To be Provided:
 Online Account Registration
 Online Doctor Details
 Patient Records
 Scheduling
 Notifications

Not to be Provided:
 No medical prescriptions online
 No transaction online

2. Overall System Description

This project is developed for a medical purpose. It will be an android base application. Users of
this system will Patients, Doctors and Admin. Moto of this system is to digitalize medical
environment for people.
Both doctor and patient must register their account on this app. It will allow doctors set their
fees and all other details such as qualifications, area of specialization etc. On the other hand,
patients can appoint a doctor if they are satisfied by his profile. Patient will be able to choose a
doctor according to their choice. Doctor can approve or discard an appointment; doctor can also
cancel an appointment due to emergency or non-availability. Patient can communicate with
Dec 02, 2019 Page 7 of 13
<Project code> Software Requirements Specifications

doctors, but communication only possible if doctor is willing to communicate with patient.
Doctor have the authority of communication module.

2.1 User characteristics

The users of this system are:
 Doctor
 Patient
 Admin

2.2 Operating environment

Initially this is an Android base environment which will be used to run in the medical field. It
can be run on any android device. It will obviously require an internet connection to connect
with main server.

Platforms:
Android Operating System

2.3 System Constraints

Constraints may include the following:
 It cannot run on IOS, Linux, MacOS etc.
 Minimum 512Mb’s of RAM, 1.3 GHz of processor, 128Mb.
 A person who has no knowledge of computers will find it difficult to understand the
system. Main Language will be English.
 As it is purely related to medical field and interaction between doctor and patient so
there will be no illegal aspects in it.
 No Environmental constraints.
 This system is designed for adult persons which is a simple UI based system and it can
be used by any person who have little knowledge of technology and English language.

3. External Interface Requirements

System requirements are what is necessary for users to install the android application in their
systems and be used hopefully without any difficulties. The aim of this to help the users make
sure they have all required tools and equipment. With analysis there are some objectives for
hardware, software and communication.

3.1 Hardware Interfaces

An android cellphone or tablet that can run the app online having specification at least 1 Gb
ram, good internet speed for smooth running of application.

3.2 Software Interfaces

 Android Operating System (6.0 Marshmallow installed packages)
Dec 02, 2019 Page 8 of 13
<Project code> Software Requirements Specifications

 SQLite Database Server

 Android Studio Tool

3.3 Communications Interfaces

The communication mechanism used here will be mostly dependent on e-mails. The patient and
doctor will be notified through e-mails. The In-App notifications and chat box will also be
available. The network standard will be Internet and electronic device is android mobile phone.

4. Functional Requirements
4.1 Functional requirements for the patient:
 The patient must be able to create an online account
 The patient must be able to log in to his/her account
 The patient shall be able to search for the doctors by specialty, name, working time and/or
gender.
 The patient must be able to see the appointment information online
 The patient must be able to make an appointment
 The patient must be able to cancel an appointment
 The patient must be able to reschedule an appointment
 The patient must be able to confirm an appointment online
 The patient must be able to add the doctor of his/her choice to appointment
 The patient must be able to update his/her personal data
 The patient must be able to register for a new account
 The patient must be able to log out from the account
 The patient must be able to delete his account
 The patient must be able to change the password of the account
 The patient must be able to pay for the doctor visits
 The patient must be able to create a new entry in the personal data
 The patient must be able to delete his/her entry of the personal data

4.2 Functional requirements for the Doctor:

 The doctor can be able register an account online
 The doctor can be able log in to his/her account
 Doctors can manage all appointments made with him on his account.
 Doctors can also approve the appointments
 Doctors can cancel appointments.
 Doctor must be able to create the prescription for a patient.
 Doctor must be able to add medical data to the patient’s entry.
 Doctor must be able to see the medical data of the patient. The medical data includes
previous examinations and prescriptions.

4.3 Functional requirements for the Admin:

 Admin can log in to his/her account
 Admin can update, delete, retrieve data
 Admin staff can keep records of all activities on the system
Dec 02, 2019 Page 9 of 13
<Project code> Software Requirements Specifications

 If a technical problem occurs, someone has to report them to the vendor so that the problem
is fixed and that is the work of an admin.

5 Non-functional Requirements
5.1 Usability
 The system must be easy to use by both patients and doctors such that they do not need to
read an extensive number of manuals.
 The menus of the system must be easily navigable by the users with buttons that are easy to
understand.
 The system must be intuitive and simple in the way it displays all relevant data and
relationships.

5.2 Reliability
 The system must provide a password enabled login to the user to avoid any foreign entity
changing the data in the system.
 The system should provide the user updates on completion of requested processes and if the
requested processes fail, it should provide the user the reason for the failure.
 The system should not update the data in any database for any failed processes.

5.3 Performance Requirements

 The system must not lag, because the users using it don’t have down-time to wait for it to
complete an action.
 System will be developed in such a way that can run on any system with a minimal
specification. Its working greatly depends online. As there will be limited number of users
so less load is expected on server.
 All the functions of the system must be available to the user every time the system is turned
on.

5.4 Safety Requirements

The system we are developing is an online system working on android based app, so it will be
made sure that it is safe from hacking devices.

5.5 Security Requirements

The security of the system is based on login/logout which will ensure the right user is
authenticated by the system. Integrity, in the context of computer systems, refers to methods of
ensuring that data is real, accurate and safeguarded from unauthorized user modification.
As our app is an android app which will be uploaded on google play store platform so the
privacy policies will be well ensured by google.

Dec 02, 2019 Page 10 of 13

<Project code> Software Requirements Specifications

5.6 User Documentation

User Manual Includes:
 Software Usage Guide
 Software Features
 Tips and tricks
 Resolving common problems of software
 FAQs
 Embedded assistance (for example, tool tips and dynamic page content)
 Support Portals

6 Business Rules
Roles:
Doctor’s Role:
 Doctors will be able to register online.
 Doctors can upload his details and qualification etc.
 Doctor can approve the patients request.

Patient’s Role:
 Patients can register their account.
 Patients can browse the app and check the doctor availability.
 Patients can send request to the doctor for appointment.
 Patients can send multiple request to doctors simultaneously.

Admin’s Role:
 Admins can install, update, tune, diagnose, and babysit both internal and third-party
applications.
 Admin staff can keep records of all activities on the system.
 Admin staff can change status of both.
 If a technical problem occurs, someone has to report them to the vendor so that the problem
is fixed and that is the work of admin.

7. Assumptions and Dependencies

7.1 Assumptions:
First assumption is that the user must be using an android device to ensure the app
compatibility.
Second assumption is that the user must have an internet connection to use the app and interact
with the app.
These factors are not system constraints, but areas where future changes might drive changes in
the requirements. The project could be affected if these assumptions are incorrect, are not
shared, or changed.

Dec 02, 2019 Page 11 of 13

<Project code> Software Requirements Specifications

7.2 Dependencies:
The main and most important dependency is the internet connectivity. If there is no internet, our
system will have no meaning or no functionality of usage.

8. References
Ref. No. Document Title Date of Release/ Publication Document Source
PGBH01- Project Proposal Oct 14, 2019 https://drive.google.com/
2003- drive/folders/1zRiQqtLQcf
Proposal uEB6EQZUItqAuynHAeLG
CW
The Importance of Dec 03, 2015 https://www.business2co
Information Technology mmunity.com/tech-
1 in Business Today gadgets/importance-
information-technology-
business-today-01393380
Journal of Medical Apr 26, 2017 https://www.ncbi.nlm.nih.
2 Internet Research gov/pmc/articles/PMC542
5771/#ref1
Community Eye Health Apr 01, 2016 https://www.ncbi.nlm.nih.
Journal gov/pmc/articles/PMC170
3
5904/

Online Patient Jul 04, 2017 https://www.slideshare.n

Scheduling System et/SamihaHaque2/online-
4 appointment-system

The Strategy That Will Oct, 2013 https://hbr.org/2013/10/t

5 Fix Health Care he-strategy-that-will-fix-
health-care

9. Appendices
Introduction:
Enhancing online patient care management is one of the aims of healthcare industry to improve
the healthcare system worldwide. As the population continues to grow, so too does the need for
healthcare services and options. Doctor Appointment System is an important component of
scheduling and managing appointments. Especially online appointment software has simplified
and automated the process of hospital management for all-size organizations. The proposed
system advances with online facilities that eliminate the chaos of traditional appointment
services. This system offers online appointment booking, to view doctors list, to cancel and
update appointments with an administrative portal to manage all the sections. It provides
advanced functionality to streamline the process thus easy access to personal hospital services
that help organizations to stay connected with their customers, clients, students and most
importantly patients and can result in significant time and monetary savings.

Aims:
The aim of patient scheduling service is to provide patients full access to manage their hospital
appointments which, facilitates with an online service for appointment reservation, updating and

Dec 02, 2019 Page 12 of 13

<Project code> Software Requirements Specifications

canceling management minimizing customer inconvenience and assuring a better healthcare.

Objectives:
 To develop a system that allows users to have control over their appointment making
service.
 To facilitate the patients with real time healthcare scheduling.
 To manage staff resources needed for managing appointments.
 To maximize operation hours.
 To make the use of online platform for less customer inconvenience and high productivity
among staff.
 To optimize time savings and monetary savings as both staff time and services translate into
expenses and revenue.

Dec 02, 2019 Page 13 of 13