Document of Software Requirements Specification Project 2022

Running head: DOCUMENT OF SRS
DOCUMENT OF SRS
Enter the name of the Student:
Enter the name of the University:
Author note:

1DOCUMENT OF SRS
Table of Contents
1. Introduction............................................................................................................................2
1.1 Purpose.............................................................................................................................2
1.2. Scope...............................................................................................................................2
2. Overall Description................................................................................................................2
2.1. Product Perspective.........................................................................................................2
3. External Requirements...........................................................................................................3
3.1. User interfaces.............................................................................................................3
3.2. Hardware interfaces....................................................................................................4
3.3. Software Interfaces......................................................................................................5
3.4. Communications Interfaces.........................................................................................5
4. Specific Requirements...........................................................................................................6
4.1. Functional Requirements................................................................................................6
4.2. Non-Functional Requirements........................................................................................6

2DOCUMENT OF SRS
1. Introduction
The SRS that is the Software Requirements Specification is the document which is
captured the total description regarding the process of proposed system how it is predictable
to perform. In this document, several types of requirements are captured such as Functional,
Operational, Quality, Safety and many more.
1.1 Purpose
The purpose of the selected project is to establish a system of clinic management that is a
cloud-based also this need to install in all partner medical clinics as the solution of Saas that
is Software-as-a-Service.
1.2. Scope
This document is applied to the Cloud-based clinic management system. This
software enables to help with the clinic for their daily operation by delivering several
functions such as medicine control, reports, patient area, staff and many more. This software
can help the doctor for checking or updating the history of any patient. There is the login
feature, by this the patient
2. Overall Description
2.1. Product Perspective
In the context of the clinical facility in which the operations are performed manually also
digitally, this solution is an independent framework which contains three main components
that are System, Clinic and the User.
System: This has several functions which are as follows:
i) Add clinic.

3DOCUMENT OF SRS
ii) Run clinic.
iii) View all.
Clinic: Using this system of clinic management, resulting functions are implemented in this
project that is as follows:
i) Patient Registration.
ii) Medicine record.
iii) Patient history.
iv) Appointment.
v) Employees record.
vi) Backup.
User: In this system, three types of users are present which are as follows:
i) Patient.
ii) Doctor.
iii) Admin or Reception.
3. External Requirements
3.1. User interfaces
This interface that is delivered to the user should be user friendly also this should deliver the
optional interactive assistance for every service that is listed. The interface of this system
delivers a menu and some screens are noticed which are as follows:
i) A screen for login is delivered in the very beginning to enter into this system by giving the
username and password.

4DOCUMENT OF SRS
ii) Any unsuccessful login is led to the reattempt screen that is maximum three for yet again
giving similar information.
iii) For the admin or reception, the screen will show having the options to shut down this
system, reboot system, disable some service and block the system.
iv) After login to this system, the screen is shown with several options concerning the
particular user such as a doctor, patient and admin.
v) The patients can register their name in this system by providing some personal details, also
arrange the appointment with any preferred doctor, choose any specific clinic from the list of
the clinics and make the payment also check the diagnosis of the doctor.
vi) The doctors can use this system for doing the check-up, also add the prescription or
suggest the medicine and the treatment recommendation to patients, also they can make the
medical certificate, also check the former medical history of any particular patient.
vii) The admin can arrange also adjust the bookings, update the details of the patient, print the
tax invoice and record all the history of payment.
3.2. Hardware interfaces
Several components of hardware interfaces are present for this cloud-based system
such as the CPU, the network and the storage. Also, some hardware requirements that are
needed fo efficient also the effective running of this system are as follows:
Hardware The requirement of minimum
system
Processor 1 GHz speed
Memory (RAM) 2 G RAM
Hard Disk Drive Space 10 G hard drive

5DOCUMENT OF SRS
Display Any type of monitor can serve.
Table 1: Hardware Interfaces
(Source: Created by author)
3.3. Software Interfaces
Several components of software interfaces are present for this cloud-based system
such as the databases for storing the data, the webserver and application server. The software
requirements that are recommended for enabling this system to run which are as follows:
Software The requirement of minimum
system
Programming language Visual C#
Database Management System Microsoft SQL Server
Runtime Environment Visual Studio
Operating System Windows 8.1 and above
Web Browser Any web browser, for example, Google
Chrome, Internet Explorer, Mozilla Firefox
and many more.
Table 2: Software Interfaces
(Source: Created by author)
3.4. Communications Interfaces
This system is essential to communicate with all the clinics that are connected with
this system for the referral function of this system. For this reason, the TCP/IP protocol is

6DOCUMENT OF SRS
needed to use for communication and the FTP that is the File Transfer Protocol is used to
transfer the data.
4. Specific Requirements
This segment is delivered a proper overview of requirements and the requirements are
of two types, functional and non-functional requirements which are discussed below.
4.1. Functional Requirements
 The system is required to permit several clinics for adding by using this same system.
 It is needed to help with the clinic with the regular operation by several functions.
 It has numerous access authorities for different users groups to allow seeing the
system.
 It is required to register all the patient who visits the clinic for the first time.
 It is required to show the stock levels of all medicine.
 This system should permit the patients for making appointments through the website
or phone.
 Doctors are added prescription, prepared medical certificates and many more things
by using this system.
 Patients are referred to additional clinics that are using this system also for the
requirements of medical or capacity.
 The information is communicated between patient and clinic.
4.2. Non-Functional Requirements
i) Site Performance:
 The time for skipping any page is less than 3 seconds and for searching the results it is
less than 1 minute.

7DOCUMENT OF SRS
ii) Reliability:
 If maintenance is needed then the mechanism of disaster response is required.
iii) Security:
 Accessing also the operation of data is required based on user permission.
 Every user is required to establish the username also password for login in this
system.
 The data should not be tampered or stolen within the process of uploading, processing
and transferring.
iv) Privacy:
 The information of the patient should be confidential between registered clinics and
doctors.
v) Back up:
 This system is required to back up the user data regularly to avoid the loss.