Software Requirements

Specification
For

360 Total Security

Lovely Professional University

Acknowledgement
This project would not have been possible without the guidance and
support technical and personal of a number of people. I would like to
thank my subject teacher for helping me and guiding me out in this
project and giving me ideas and insights on how to make this project. I
went through many websites and also referred the “360 degree internet
security” official website for this.

-ii-
 Software Requirements Specification for <360 Security> - iii -

Table of Contents

1. Introduction ................................................................................ Error! Bookmark not defined.

1.1 Purpose.................................................................................................................................1
1.2 Document Conventions ........................................................................................................2
1.3 Intended Audience and Reading Suggestions ......................................................................2
1.4 Definitions, acronyms, abbreviations...................................................................................1
1.5 Scope………………………………………………………………………………………3
2. Overall Description ..................................................................................................................4
2.1 Product Perspective ..............................................................................................................4
2.2 Product Features...................................................................................................................5
2.3 User Classes and Characteristics..........................................................................................6
2.4 Operating Environment ........................................................................................................6
2.5 Design and Implementation Constraints ..............................................................................6
2.6 Assumptions and Dependencies ..........................................................................................7
3. Specific Requirements .............................................................................................................7
3.1 Functional Requirement .......................................................................................................7
3.2 Requirements of the bank computer for the ATM…………………………………………...11
4. External Interface Requirements .........................................................................................13
4.1 User Interfaces ...................................................................................................................13
4.2 Hardware Interfaces ...........................................................................................................14
4.3 Software Interfaces.............................................................................................................14
5. Other Nonfunctional Requirements .....................................................................................15
5.1 Performance Requirements ................................................................................................15
5.2 Safety Requirements ..........................................................................................................15
5.3 Security Requirements .......................................................................................................15
5.4 Software Quality Attributes ...............................................................................................15
6. Other Requirements ..............................................................................................................16
 Software Requirements Specification for <360 Total Security > Page 1

1. Introduction

1.1 Purpose

This document describes the software requirements and specification for an antivirus i.e. 360 Total
Securities. It provides a detailed overview of our software product, its parameters and goals. This
document describes the project's target audience and its user interface, hardware and software
requirements. It defines how our client, team and audience see the product and its functionality.
Nonetheless, it helps any designer and developer to assist in software delivery lifecycle (SDLC)
processes. The system can be divided into BOOST, CLEAN & ANTI-VIRUS.
 Software Requirements Specification for <360 Total Security > Page 2

1.2 Document Conventions: font: Times New Roman 12

1.3 Intended Audience and Reading Suggestions (Intended audience is defined as the group
of people for which a service or product is designed)

The document is intended for all the stakeholders’ customer and the developer (designers, testers,
maintainers). The reader is assumed to have basic knowledge of Malwares, Computer worms and
Trojans required. Knowledge and understanding of antivirus working is also required.

1.4 Definitions, abbreviations

Configuration It means a product which is available / Selected from a catalogue can be

customized.
FAQ Frequently Asked Questions
CRM Customer Relationship Management

1.4.1 Definitions

 360 Total Security

It is a free security protection against any virus, malware and computer worms. It is also designed to
provide protection against internet theft and allows the user to boost up device speed and clear junk
files at same time. It is available for various platforms like Windows, IOS and Android.

 Antivirus
Antivirus (or anti-virus) software is used to safeguard a computer from malware, including
viruses, computer worms, and Trojan horses. Antivirus software may also remove or
prevent spyware and adware, along with other forms of malicious programs.

 Virus

A piece of code which is capable of copying itself and typically has a detrimental effect,
such as corrupting the system or destroying data.

 Malware
 Software Requirements Specification for <360 Total Security > Page 3

It is software which is specifically designed to disrupt, damage, or gain authorized access to a

computer system.

 Trojans

It is a program designed to breach the security of a computer system while ostensibly performing
some innocuous function.

 Users

A person who uses or operates something. The person who works within the device based operating
environment

 Device
A thing made or adapted for a particular purpose, especially a piece of mechanical or
electronic equipment.

1.4.2 Abbreviations

Throughout this document the following abbreviations are used:

 k : is the maximum time for the software to be valid to use.

 m: is the maximum number of scans.

 n : is the minimum number of scans.

 t : is the total validity of the antivirus.

1.4.3 References

1. Wikipedia

2. 360 security site (http://360security.com /about-us)

3. Youtube
 Software Requirements Specification for <360 Total Security > Page 4

1.5 Project Scope

This is computer software used to prevent, detect and remove malicious software. Antivirus
software was originally developed to detect and remove computer viruses, hence the name.
However, with the proliferation of other kinds of malware, antivirus software started to provide
protection from other computer threats.

Overall Description

1.6 Product Perspective

The 360 Total Security does not work independently. It works together with the system Kernel and
the operating system installed in the device.

Communication interface: The 360 Total Security communicate with the service provider via a
communication network.

Software interface: The software will run on any device based on Windows, Android and IOS

Hardware interface: The software will run on any device.

User interfaces:

Customer: The customer user interface should be used, such that 99.9% of all new product users
are able to remove and filter the threats without any assistance.
 Software Requirements Specification for <360 Total Security > Page 5

Software Security Personnel: Software security personnel are responsible for removing deposits
and adding new updates. There should be a simple interface (e.g., a switch or button) that they can
use to initialize the scan whenever they restock.

Maintainer: The maintainer is responsible for adding new updates to the softwares and servicing
existing version of software. A maintainer should be possible to add a new update to the software
within 1 week.

1.7 Product Features

The 360 Total Security provides real time protection every time. The software identifies a user by a
software version and key. It collects information about a simple account registration details(e.g.,
deposit, withdrawal, transfer, bill payment), communicates the transaction information to the
customers bank, and dispenses cash to the customer. The banks provide their own software for their
own computers. The bank software requires appropriate record keeping and security provisions. The
software must handle concurrent accesses to the same account correctly.
 Software Requirements Specification for <360 Total Security > Page 6

1.8 User Classes and Characteristics

Characteristics: There are several users of the 360 Total Security.

Customers are simply members of the general public with no special training.

Software security personnel need have no special education or experience.

Maintainers must be experienced network administrators, to be able to get new updates to the
softwares.

1.9 Operating Environment

The hardware, software and technology used should have following specifications:

 Ability to run the 360 Total securities.

 Ability to install all the files of the software.

 Touch screen for convenience or via mechanical keyboard.

 Keypad (in case touchpad fails)

 Continuous power supply

 Ability to connect to service provider.

 Ability to take input from user

 Ability to validate software

1.10 Design and Implementation Constraints

 Registration

Validate Antivirus:

 Validate for Software Expiration Date

 Validate that the software expiration date is later than today's date

 If software is expired, prompt error message "This version is expired"

Validate for Stolen software copy:

 Software Requirements Specification for <360 Total Security > Page 7

 Validate that the software is not stolen

 If the software is not genuine, prompt error message, "This version is already in use"

Validate for Expired Software:

 Validate that the software is not expired

 If software is expired, prompt error message, "This version is already expired”

Validate for Pirate Software:

 Validate that the software is not pirated version.

 If software is invalid , prompt error message "This is not a valid version"

Validate Serial Key:

 Validate that the serial key is not blank

 If serial key is blank, prompt error message "Please provide serial key"

 Validate that the password entered matches the password on file

 If password does not match, prompt error message "Invalid Serial Key"

Outdates Software Version:

 If number of consecutive unsuccessful logins exceeds three attempts, terminate software

 Maintain Consecutive Unsuccessful Login Counter

 Increment Login Counter

 For every consecutive Login attempt, increment logic counter by 1.

 Reset login counter to 0 after login is successful.

 Get validity information

 Run the software

2.6 Assumptions and Dependencies

 Hardware never fails

 Limited number of scans

 Software Requirements Specification for <360 Total Security > Page 8

 Custom Drive Scan.

2. Specific Requirements

2.1 Functional Requirements

The functional requirements are organized in two sections First requirements of the software and
second requirements of the device.

2.1.1 Requirements of the 360 Total Security

The requirements for 360 Total Security are organized in the following way General requirements,
requirements for authorization, requirements for a validation.

General

Functional requirement 1:

 Description: Initialize parameters t, k, m, n

 Input: 360 Total Security is initialized with t duration, k, m, n are entered

 Processing: Storing the parameters.

 Output: Parameters are set.

Functional requirement 2:

 Description: If no software in the device, the system should display initial display.

Functional requirement 3:

 Description: If the software is running out of validation, no extra features should be

accepted. An error message is displayed.

 Input: Software is run.

 Processing: The requirements of software are less than t.

 Output: Display an error message. Terminate the run task.

 Authorization: The authorization starts after a user has run the software in the device
 Software Requirements Specification for <360 Total Security > Page 9

Functional requirement 4:

 Description: The software has to check if the entered key is valid serial key.

 Input: Customer runs the scan.

 Processing: Check if it is a valid software version. It will be valid if

 The information on the software copy be read.

 It is not expired.

 Output: Display error message and terminates the installation.

Functional requirement 5:

 Description: If it is valid, the software should read the serial number and linked address.

 Input: Valid version.

 Processing: Read the serial number.

 Output: Initiate authorization dialog

Functional requirement 6:

 Description: The serial number should be logged.

 Input: Serial number from dialog box.

 Processing: Log the number.

 Output: Update to log file.

Functional requirement 7:

 Description Authorization dialog: The user is requested to enter his serial key. The 360
Total Securities verifies information and password with the service provider.

 Input: Password from user, serial key from the product.

 Processing: Send serial number and password to service provider, receive response from
team.
 Software Requirements Specification for <360 Total Security > Page 10

 Output: Accept or reject authorization form .

Functional requirement 8:

 Description: Different negative answers from service provider for authorization dialog.

 Input: Response from team or authorization dialog:

-“bad password” if the password was wrong.

- bad bank code” if the serial key is not supported by the service provider.

-“bad account” if there are problems with the account.

 Processing: If the antivirus gets any of these messages from the bank computer, the software
copy will be terminated and the user will get the relevant error message.

 Output: Installation will cancel and error message is displayed.

Functional requirement 9:

 Description: If password and serial number are ok, the authorization process is finished.

 Input: The software gets accept from the team for authorization process.

 Processing: Finishing authorization.

 Output: Start installing.

Functional requirement 10:

 Description: If a serial key entered more than three times in a row in a software and the
password was wrong each time, a message will be displayed that the customer should call
the team.

 Input: Entering a wrong serial key for the fourth time in succession

 Processing: Initiate authorization process Response from service provider is to keep the
genuine software.

 Output: Display error message that the customer should call the service provider.
 Software Requirements Specification for <360 Total Security > Page 11

Functions: These are the requirements for the different functions the 360 Total Security should
provide after authorization.

2.1.2 Requirements of the 360 Total security.

Authorization

The antivirus gets verified by its developer via internet from anywhere around the world.

Functional requirement 1:

 Description: The software provider checks if the antivirus has valid serial key. A serial key
is valid if the software was issued by the developer’s team themselves only.

 Input: Request from the software provider to verify software copy (Serial number and
password.)

 Processing: Check if the software was issued by them only.

 Output: Valid or invalid serial key.

Functional requirement 2:

 Description: If it is not a valid serial key, the 360 Security will send a message to the main
developer team.

 Input: Invalid serial key

 Processing: Process message

 Output: The software sends the message “Invalid Serial Key” to the Device.

Functional requirement 3:

 Description: The installed software checks if the Serial key is valid for a valid antivirus
copy.

 Input: Request from the service provider to verify password.

 Processing: Check serial key of the customer.

 Output: Valid or invalid password.

 Software Requirements Specification for <360 Total Security > Page 12

Functional requirement 4:

 Description: If it is not a valid serial key, the service provider will send a message to the
device.

 Input: Invalid password.

 Processing: Process message. Update count for invalid key for the account.

 Output: The bank computer sends the message “Invalid Serial Key” to the ATM.

Functional requirement 5:

 Description: If it is valid software and a valid serial key but there are problems with the
account, the bank will send a message to the device that there are problems.

 Input: Valid version and serial key.

 Processing: Process message.

 Output: The service provider sends “Invalid Version” to the ATM.

Functional requirement 6:

 Description: If it is valid software with a valid key and there are no problems with the
product the service provider will send a message to the team that everything is ok.

 Input: Valid product password and key.

 Processing: Process message.

 Output: Send Verified to the Device.

Functional requirement 7:

 Description: Update software after its version get expires.

 Software Requirements Specification for <360 Total Security > Page 13

 Input: Response from device about updating antivirus.

 Processing: Updates software.

 Output: Updated

Functional requirement 8:

 Description: Each software has a limit k for which it can protect the device from any
external threats.

 Input: Request to process validation.

 Processing: Check if the validity of the software doesn’t exceed k

 Output: If the validity exceeds the limit, the software will stop protecting device from
threats. .

Functional requirement 9:

 Description: The 360 Total Security only provides security for their own computer and their
own devices.

3. External Interface Requirements

3.1 User Interfaces

The user interface should be intuitive, such that 99.9% of all new users are able to understand the
software working to scan any drive.
 Software Requirements Specification for <360 Total Security > Page 14

3.2 Hardware Interfaces

The hardware should have following specifications:

 Ability to read the hard drive and flash drives too.

 Ability to detect real time connected device.

 Touch screen for convenience.

 Keypad (in case touchpad fails)

 Continuous power supply

 Ability to connect to secured server.

 Ability to take instruction from user

 Ability to validate user

3.3 Software Interfaces

The software interfaces are specific to the target protection against any threats.
 Software Requirements Specification for <360 Total Security > Page 15

4. Other Nonfunctional Requirements

4.1 Performance Requirements

 It must be able to perform in adverse conditions like high/low ram usage etc.

 Good internet connection.

 Device should have enough ram.

4.2 Safety Requirements

 Do not lose the serial key.

 Must be registered with a provided serial key in the kit.

 Must have a registered E-mail linked to the software.

 There must be a registered phone number.

 Carefully select the installation option during installation.

4.3 Security Requirements

 Users accessibility is censured in all the ways.

 Users are advised that antivirus should be genuine.

 Users are advised update the software as soon as the new update is available.

 Only one antivirus should be installed at a time in a single device.

4.4 Software Quality Attributes

Security

Performance

5.4.1 Availability: The Antivirus should have a real time protection and run behind every process.
 Software Requirements Specification for <360 Total Security > Page 16

5.4.2 Security: The antivirus should provide maximal security .In order to make that much more
transparent there are the following requirements:

1. It must be impossible to plug into the network.

5.4.3 Maintainability:
Maintain customer profile:

The system shall allow user to create profile.

The system shall authenticate user credentials to view the profile.

Provide Customer Support:

The system shall provide online help, FAQ’s customer support, and sitemap options for customer
support.
The system shall allow user to select the support type he wants.
The system shall allow user to enter the customer and product information for the support.
The system shall display the customer support contact numbers on the screen.
The system shall allow user to enter the contact number for support personnel to call.
The system shall display the online help upon request.
The system shall display the FAQ’s upon request.

Email confirmation:
The system shall maintain customer email information.

Provide Search facility:

The system shall enable user to enter the search text on the screen.
The system shall enable user to select multiple options on the screen to search.
The system shall display all the matching products based on the search
The system shall notify the user when no matching product is found on the search.
 Software Requirements Specification for <360 Total Security > Page 17

6. Other Requirements

6.1 Data Base

The 360 Total Security must be able to access the data base in order to get regular updates to
perform action against new threats which tends to affect the working of any device and all the last
scan details.

6.2 Data Flow Diagram

A data flow diagram (DFD) maps out the flow of information for any process or system. It uses
defined symbols like rectangles, circles and arrows, plus short text labels, to show data inputs,
outputs, storage points and the routes between each destination. Data flowcharts can range from
simple, even hand-drawn process overviews, to in-depth, multi-level DFDs that dig progressively
deeper into how the data is handled. They can be used to analyze an existing system or model a new
one. Like all the best diagrams and charts, a DFD can often visually “say” things that would be hard
to explain in words
 Software Requirements Specification for <360 Total Security > Page 18

6.3 Class Diagram

A class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's classes, their attributes, operations (or
methods), and the relationships among objects.

Purpose of Class Diagrams

1. Shows static structure of classifiers in a system

2. Diagram provides basic notation for other structure diagrams prescribed by UML

3. Helpful for developers and other team members too

4. Business Analysts can use class diagrams to model systems from business perspective
 Software Requirements Specification for <360 Total Security > Page 19

6.4 Use Case Diagram

A use case diagram at its simplest is a representation of a user's interaction with the system that
shows the relationship between the user and the different use cases in which the user is involved. A
use case diagram can identify the different types of users of a system and the different use cases and
will often be accompanied by other types of diagrams as well.
 Software Requirements Specification for <360 Total Security > Page 20

6.5 Test Cases

Test Module: Login Test By: Sahil Sharma

Test priority: High Test case ID: Login-1A

Pre-requisite: Valid user account Description: First a user has to enter a valid e-mail
address and password to login.

Sr. Action Input Expected Actual Result Status

No. Results

1. Launch https://www.360total 360 Total 360 Total Pass

Application security.com/en/ Security Home Security Home
Page Page (launch
or open the mobile successful)
application

2. Enter E-mail id : Login Success Login Success Pass

correct e- [email protected]
mail & (login
Password: ******* successful)
password
 Software Requirements Specification for <360 Total Security > Page 21

Test Module: Quick Scan Test By: Sahil Sharma

Test priority: Medium Test case ID: Scan-1B

Pre-requisite: NA Description: Quick Scan and advance analysis.

Precondition selected files and report to analysis.

Sr. Action Input Expected Actual Result Status

No. Results

1. Quick Scan Checks common Quick Scan Quick Scan Pass

areas for computers Window or tab Window or tab
viruses (Quick scan
successful)

2. Analysis After the Quick Different Different Pass

report Scan user can check statistics of statistics of
the analysis report quick scan quick scan (Analysis
result result report
Launched)
 Software Requirements Specification for <360 Total Security > Page 22

Test Module: Clean Junk Files Test By: Sahil Sharma

Test priority: Medium Test case ID: Clean-1C

Pre-requisite: NA Description: Clean junk Files and remove ads

Sr. Action Input Expected Actual Result Status

No. Results

1. Clean Junk Temporary files Junk Files Junk Files Pass

Files which are created removal removal
while installing the window pops window pops (Junk Files
softwares out out deleted
successfully)

2. Remove Asks for several Remove or Remove or Pass

Ads permissions alter alter
advertising advertising (Ads
content content removed)