Software Requirements

Specification
for

Seed – Cancer Treatment

Planner
Version 1.0 approved

Prepared by

Aarsh Dhokai(180010116012)

Dharmam Savani(180010116049)

Seedomics Inc. & A.D.Patel Institute of Technology

15-04-2021

Table of Contents

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page 2

Table of Contents ii
Revision History ii
1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Product Scope 1
1.5 References 1
2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Functions 2
2.3 User Classes and Characteristics 2
2.4 Operating Environment 2
2.5 Design and Implementation Constraints 2
2.6 User Documentation 2
2.7 Assumptions and Dependencies 3
3. External Interface Requirements 3
3.1 User Interfaces 3
3.2 Hardware Interfaces 3
3.3 Software Interfaces 3
3.4 Communications Interfaces 3
4. System Features 4
4.1 System Feature 1 4
4.2 System Feature 2 (and so on) 4
5. Other Nonfunctional Requirements 4
5.1 Performance Requirements 4
5.2 Safety Requirements 5
5.3 Security Requirements 5
5.4 Software Quality Attributes 5
5.5 Business Rules 5
6. Other Requirements 5
Appendix A: Glossary 5
Appendix B: Analysis Models 5
Appendix C: To Be Determined List 6

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 3
Software Requirements Specification for <Project> Page 1

1. Introduction
1.1 Purpose
Seed – Cancer Treatment Planner is a product which is useful for oncologists, cancer patients,
cancer physicians. It helps oncologists and cancer physicians to make planning of treatment of
patients effectively and in minimal time along with the latest available clinical trials and medical
researches in the field of cancer.

1.2 Document Conventions

Every documentation should contain the same font and bold headings. Higher level requirements
like javascript enabled browsers and reasonable internet connection should be inherited by
following documentation.
Where the product word comes - Take It as Seed - Cancer Treatment Planner

1.3 Intended Audience and Reading Suggestions

User’s of the product are primarily oncologists and patients of cancer.

1.4 Product Scope

The objective of the product is to save the time of the oncologist to make a plan of efficient
treatment with the support of relevant clinical trials. This can make life easier for oncologists. Goal
of the product is not limited to cancer but for all available diseases. In this era of fast-growing
internet resources, the best researchers are going on in each part of the world, so in order to take
advantage of these researches and clinical trials this product is much useful. Using this product,
the latest research and treatment can be available to the last man of the society through the
doctor.

1.5 References
<List any other documents or Web addresses to which this SRS refers. These may include user
interface style guides, contracts, standards, system requirements specifications, use case
documents, or a vision and scope document. Provide enough information so that the reader could
access a copy of each reference, including title, author, version number, date, and source or
location.>

www.nccn.org/
This is the website from where pdf of cancer types are referred from.

www.nccn.org/education-research/nccn-oncology-research-program/clinical-trials
Software Requirements Specification for <Project> Page 2

This site is referred for finding relevant clinical trials .

2. Overall Description
2.1 Product Perspective
Product was primarily made for solving problems of oncologists while consulting a cancer patient.
This product is a system of its own. It is a full-proof ecosystem for oncologists.
The vision of Product is to save time for physicians while consulting patients, and to make sure that
patients are treated effectively. And Patients who have multiple options of treatment are able to
choose the perfect treatment option for them.

2.2 Product Functions

● View guidelines for different types of cancer.
● Search clinical guidelines automatically based on which guidelines are being referred.
● Help oncologists make decisions based on reports.
● Patients can see and analyze all the available treatment options.

2.3 User Classes and Characteristics

There is a first user class which is oncologists. They are well versed with cancer guidelines so they
need a basic tutorial of software at first. Website may be frequently used by doctors throughout the
day during consulting of cancer patients.

And also there is a patient user class which helps to provide an interface for patients.
Last one user class is for System Admin.

2.4 Operating Environment

software will run smoothly on any javascript supported browser. Mobiles and laptops both can
access the website provided there is internet connection. software contains a pdf viewer which
works dynamically on any according to the screen size of the device. Operating system doesn't
matter provided it has the latest browsers.

2.5 Design and Implementation Constraints

Website needs to load in 5 seconds because it will be used by oncologists very frequently. It
should be optimized such that despite slow internet it should work flawlessly on any device.
Product is also going to be used in smartphones which have low processing power and memory
that should also be taken into consideration.
Software Requirements Specification for <Project> Page 3

2.6 User Documentation

tutorials for using websites will be delivered to users thereby ensuring seamless experience of
users to learn using the website.

2.7 Assumptions and Dependencies

App contains a library of javascript to view pdf documents called pdfjs . Pdfjs is an open source
project which gets updated sporadically . Thus, we need to assume that changes made in pdf.js
will work perfectly with our app's components. There is also one more dependency i.e. google O-
authentication API which allows to user to login with any other social accounts.

3. External Interface Requirements

3.1 User Interfaces
User interface includes pdf viewer , search bar for clinical trials, drop down to choose type of
cancer. Scrolling of the pdf is smooth .
Window to select the options for oncologist which may lead to decision .

3.2 Hardware Interfaces

Devices which support the latest JavaScript browser should be compatible. Data is fetched from
the server as JSON format. Whenever a user selects a type of cancer or searches for clinical
trials , a http request is sent to the server which inturn sends http response containing proper file
files and json attached to it.

3.3 Software Interfaces

clinical trials search is connected with clinical guidelines because text is taken from guidelines and
searched for relevant clinical guidelines automatically.

3.4 Communications Interfaces

All the api calls will be done through HTTP method . Data returned as response is in form of JSON.
Pdf loaded will be using a lazy loading method to ensure that the website runs on minimal network
speed.

4. System Features
● Admin :- able to monitor subscription count, website visits , metric regarding customer
retention , able to update guidelines .
● Oncologists :- view guidelines , payment gateway for subscriptions , search clinical trials ,
get decisions based on reports.
Software Requirements Specification for <Project> Page 4

● patients :- view patient cancer guidelines , search guidelines for relevant precautions , get
reports from doctors.

4.1 clinical guidelines for oncologist:

4.1.1 Oncologists can view guidelines for different types of cancer easily and It has high priority
for product
4.1.2 Oncologists required a tool which can quickly fetch clinical guidelines .
4.1.3 pdf viewer is a functional requirement for guidelines. api which returns an appropriate pdf
according to requirement.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
● First few pages of guidelines should be able to load within 2 seconds because oncologist
need to refer to at least an index of pdf until whole pdf gets downloaded . so , lazy loading
technology should be used to load pdf.

● searching from pdf should be efficient and accurate because oncologist might forget exact
sentence of guidelines but they should get result of search accurate even if search
keywords are jumbled.

5.2 Safety Requirements

website should not be prone of cyber attacks which can be harmful to user’s data and confidential
information of oncologist.

5.3 Security Requirements

passwords of users should be encrypted and sufficient steps should be taken so that cyber attacks
cannot steal data from websites related to users . users should be double authenticated using otp .
Data regarding search of clinical trials should not be stored to maintain privacy of users.

5.4 Software Quality Attributes

website should be crash proof even on low power devices. website should be dynamic in context of
user interface which ensures that it runs seamlessly on any screen size. website should provide
latest updated guidelines to users.
Software Requirements Specification for <Project> Page 5

5.5 Business Rules

Data administrator needs to manually update guidelines if a web scraper which extracts pdf from
the web fails to provide results.

6. Other Requirements
node.js library used for pdf viewer is paid service. so ,to legally reuse code we need to pay to
respective developers a certain amount of money.

Appendix A: Glossary
oncologist : doctor who treats cancer patient.
clinical guidelines : it helps oncologist to decide what procedure to follow while consulting patient.
clinical trials : it shows trials conducted on patients and results.

Appendix B: Analysis Models

Appendix C: To Be Determined List