CDAC Mumbai CareConnect

SOFTWARE REQUIREMENT SPECIFICATION

FOR
CARECONNECT
[21-11-2020]
CDAC, MUMBAI

Revision History:

Version. DATE Authored Reviewed REASON FOR CHANGE

By By

00 Team-48 1strelease

i
CDAC Mumbai CareConnect

Table of Contents

1. Introduction.....................................................................................................................................1
1.1 Purpose......................................................................................................................................1
1.2 Document Conventions.............................................................................................................1
1.3 Intended Audience and Reading Suggestions...........................................................................1
1.4 Product Scope........................................................................................................................... 2
1.5 References.................................................................................................................................2
2. Overall Description.........................................................................................................................2
2.1 Product Perspective...................................................................................................................2
2.2 Product Functions..................................................................................................................... 3
2.3 User Classes and Characteristics.............................................................................................. 3
2.4 Operating Environment.............................................................................................................3
2.5 Design and Implementation Constraints................................................................................... 4
2.6 UserDocumentation.................................................................................................................. 4
2.7 Assumptions and Dependencies............................................................................................... 4
3. External Interface Requirements.................................................................................................. 5
3.1 User Interfaces.......................................................................................................................... 5
3.2 Hardware Interfaces.................................................................................................................. 5
3.3 Software Interfaces................................................................................................................... 5
3.4 Communications Interfaces...................................................................................................... 5
4. System Features.............................................................................................................................. 6
4.1 System Feature1........................................................................................................................6
4.2 System Feature 2 (and so on)....................................................................................................6
5. Other Non-functional Requirements.............................................................................................7
5.1 Performance Requirements....................................................................................................... 7
5.2 Safety Requirements................................................................................................................. 7
5.3 Security Requirements.............................................................................................................. 7
5.4 Software Quality Attributes....................................................................................................... 8
6. Other Requirements....................................................................................................................... 9

ii
 CDAC Mumbai CareConnect

1. Introduction
1.1 Purpose

CareConnect is the Centralized and Integrated web application which helps you stay healthy.
It reminds you when to take your medications and about your doctor appointments. It also stores
information about your doctors, lab reports, and a variety of other medical information.It helps you to
keep track report health of user and as it is centralized system the records will stay within throughout
his life. Also it gives 24 * 7 chat box service.This will act as a cornerstone for the successful operation
of the healthcare facility.This facility is available across the whole hospital system and to the very end
user.

1.2 Document Convention

Headings:-
Text: -Bold
Font-Size: - 12
Highlighting: - Times New Roman

Sub Headings: -
Text: -Bold
Font-Size: - 12
Highlighting: - Times New Roman

Header: -
Text: - Simple
Font-Size: -10
Highlighting: - Times New Roman

Footer: -
Text: - Simple
Font-Size: -10
Highlighting: - Times New Roman

Intended Audience and Reading Suggestions

This document is intended for developers, users, testers and project managers for the
purpose of understanding the design of system in terms of different perspectives. Further, this
document contains functionalities and characteristics of system along with the working
environment. It also includes other information related to system such as external interface
requirements, features and other non - functional requirements.

1
CDAC Mumbai CareConnect

1.2 Product Scope

The key objective of this app is registering of hospitals, patients at the start, after which
they’ll get a unique ID which can be used by both, from patients side he/she could store
the medical history, test reports, any previous operations been done, name of doctor and
hospital consulted before. From doctor’s end, knowing the history of the patient before
arriving will make a clear cut picture for further consultation and thus wastage of time is
cleared here with proper and fast hospital management.The Admin can view and delete
patient and doctor and can schedule or cancel appointment

1.3 References

https://angular.io/
https://material.angularjs.org/
https://stackoverflow.com/
https://www.geeksforgeeks/
https://www.javatpoint.com/
https://spring.io/

2. Overall Description

2.1 Product Perspective

Existing technologies in the market maintains the medical record of the patient and
maintains the medical history and schedule the appointment for the patient but As we all
know, that whenever a patients arrives to any hospital then he has to undergo various
formalities and tests, scheduled appointments and procedures of that particular hospital,
which takes ample time and ultimately holding up a bunch of files depicting the patient’s
medical history if so.
Keeping in mind these types of projects we developed “CareConnect”, to lighten the load
and making up the way directly to the doctor in an efficient and easiest way without any
delay, CareConnect is an perfect solution as it is a centralized app which connects patient
and doctor with a unique ID once registered and storing, updating as well as scheduling
another doctor of another hospital. So, the procedures and other formalities won’t be
done again.

2
CDAC Mumbai CareConnect

2.2 Product Functions

 The Patient will be able to maintain his medical history

 The Patient will be able to ask question on chatBox
 The Patient would able to search nearby hospitals
 The Doctor will able to see patient medical history
 The Doctor can cancel the appointment
 The Admin will able to control profiles of patient,doctors and can cancel the
appointments

2.3 User Class

Admin:
 This person will be able to access all the functions of the system. The Admin
will able to control profiles of patient,doctors and can cancel the appointments

Patient
 Patient can view his own profile. He can post his health issues in chatBox, will
be able to maintain his medical history and would able to search nearby
hospitals and book appointment of available doctors

Doctor:
 The Doctor will able to see patient medical history and can cancel the
appointment.Doctor can prescribe medications to health issues posted in
chatBox by patients

2.4 Operating Environment

 Hardware platform:
o Processor – Above Pentium 4, with clock speed of 2.0GHz
o RAM – 1 GB or above
o Hard Disk – Free disk space of above 1GB
 Software platform:
o Front-end: HTML, CSS, Bootstrap, Angular
o Back-end: MySQL ,Java , Spring boot
 Supported tools:
o Visual Code Studio, MySQL Workbench,Eclipse IDE,STS

3
CDAC Mumbai CareConnect

2.5 Design and Implementation Constraints

Constraints:

o User interface is only in English. No other language option is available

o User can log-in only with his assigned user-name and password
o Limited to HTTP/HTTPS
o Aadhar Card is Mandatory for authentication

2.6 User Documentation

User documentation mainly comprises of Help menu of application. It will

give all the minute details about the project, if any user has any query about any
module or functionality, one can refer it and see how to operate the application.
This report is then complete documentation of our project. It gives complete
details about the project, its functionality, users, software used, hardware
requirement,environment and soon.

2.7 Assumptions and Dependencies

 Assumptions
 There is an active internet connection with the system
 The system has internet browser installed
 Users know the English language, as the user interface will be provided in
English.

 Dependencies:
 The Patient and doctors needs to be register on the system
 Active Participation of doctors when query is posted by patient
 Admin needs to monitor the system 24 * 7

4
CDAC Mumbai CareConnect

3. External Interface Requirements

3.1 User Interfaces

The main element is web-pages using HTML, CSS, Angular Js. Multiple interfaces are
there like SignIn and SignUp pages, home pages of Patient, Admin, Doctor, and also the .Admin
will maintains the profiles of patient and doctor. Based on the availability of the doctors he can
schedule the appointments for the patient and also can cancel the appointment

3.2 Hardware Interfaces

In the hardware interface, the system interacts with hardware given the processor is above
P4 with clock speed of 2.0 GHz with 1 GB RAM and the Hard Disk with 1 GB free space in the
memory. In future enhancements, it can be made responsive to be able to work with mobile
devices as well.

3.3 Software Interfaces

In software interfaces, Java, Spring boot is the back-end technology used along with
MySQL Database. The front-end technologies include HTML, CSS, Bootstrap, Angular JS. Data
will be communicated between these interfaces accordingly.

3.4 Communications Interfaces

The main communication interface for interacting with the System will be the web Browser.

5
CDAC Mumbai CareConnect

4. System Features

4.1 Description

This app is initiated for the efficient working of our healthcare system without wastage of time and
money with proper patients-doctor relationship.
The key objective of this app is registering of hospitals, patients at the start, after which they’ll get a
unique ID which can be used by both, from patients side he/she could store the medical history, test
reports, any previous operations been done, name of doctor and hospital consulted before. From
doctor’s end, knowing the history of the patient before arriving will make a clear cut picture for
further consultation and thus wastage of time is cleared here with proper and fast hospital
management.

4.2 Functional Requirements

4.2.1 Patient

o The system will allow patient to ask questions and put forth their doubts.
o The system will allow doctors to answer the questions.
o The system will show who has posted the question and who has answered the question.

4.2.2 Doctors History

o The system should maintain a log of the doctors profile.
o The system will thus help us automate the process of manual appointment.
o Thus, using this system, we will be able to save a lot of time and energy.

4.2.3 Patient Authentication

o The system shall display medical history of patient with Aadharcard OTP authentication.

4.2.4 Medical History

The system shall allow the Doctors to view the medical history of the patient with the
Aadharcard OTP authentication of the patient

6
CDAC Mumbai CareConnect

5. Performance Requirements
The system should store all the database records of each patient, doctors and admin
properly and the application should be available for use 24*7 through the server. Also, the
application should be user friendly with a proper user interface which makes it easy for the user
to understand. All the options should be present in properly accessible places for user
convenience.

5.1 Safety Requirements

All login ids and passwords of the patient, doctors and especially admin should be
protected for privacy using whatever constraints required in the database or the application. In
case any admin access account is hacked by any intruder, user id and passwords of all the admin
personnel should be changed and new passwords should be issued to all patient and the doctors.
Patient and doctors records are to be backed up securely across database servers. In case
database is hacked by someone and data is deleted a backup server should be present for such
purpose.

5.2 Security Requirements

All passwords of the administrators should be protected for privacy using whatever
constraints required in the database or the application. Transactions regarding patient and doctor
records should be carried out properly. Only admin will have access rights to the patient data
according to the need for E.g.: - patient medical history. The database should be protected from
attacks and unauthorized access. The interface should be protected from attacks. All passwords
should be stored as a secure hash of the administrator password.

7
CDAC Mumbai CareConnect

5.3 Software Quality Attributes

5.3.1Availability
The system should run on a variety of operating systems that support the JavaScript
language. The system should run on a variety of hardware.

5.3.2 Accessibility
The software will be accessible to admin, patient and doctors.

5.3.3 Compatibility
The software will be compatible with multiple platforms.

5.3.4 Durability
The software will be tested for working with multiple users.

5.3.5 Effectiveness
The software will be made to handle operations effectively.

5.3.6 Maintainability
The system should be easy to maintain. There should be a clear separation between the
interface and the business logic code. There should be a clear separation between the data access
objects that map the database and the business logic code.

8
CDAC Mumbai CareConnect

6. Other Requirements
 Appendix A: Glossary

o SRS: Software Requirement Specification

o GUI: Graphical User Interface
o P4: Pentium4
o SQL: Structured Query Language
o HTML: Hyper Text Markup Language
o CSS: Cascading Style Sheet

9
 CDAC Mumbai CareConnect

Appendix B: Analysis Models

a) Use Case Diagram:

10
CDAC Mumbai CareConnect

b) Class Diagram:

11
CDAC Mumbai CareConnect

c) Activity Diagram:

12
CDAC Mumbai CareConnect

d) Sequence Diagram1.1:

13
CDAC Mumbai CareConnect

Sequence Diagram 1.2:

14
CDAC Mumbai CareConnect

Sequence Diagram 1.3:

15
 CDAC Mumbai CareConnect

7.Team Task List

Task Assigned To Reviewed Status

Project Introduction Samrat Sinare Yes Completed

Overall Description Samrat Sinare Yes Completed

External Interface
Requirements Ankita Gourkhede Yes Completed

System Features Mahesh Khairnar Yes Completed

Other Nonfunctional Akshay Sabale

Requirements Yes Completed

Use Case Diagram Ankita Gourkhede, Yes Completed

Akshay Sabale

Class Diagram Whole Team. Yes Completed

Activity Diagram Whole Team Yes Completed

Sequence Diagram Niket Katkar , Yes Completed

Mahesh Khairnar

Formatting of Niket Katkar

document Yes Completed

16
CDAC Mumbai CareConnect

17