Software Requirements

Specification
For

QUIKR.COM

By Ashutosh

Lovely Professional University

Date :30/10/18
 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 Definitions, acronyms...........................................................................................................1
1.5 Scope……………………………………………………………………………………
2
2. Overall Description..................................................................................................................3
2.1 Product Perspective..............................................................................................................3
2.2 Product Features..................................................................................................................4
2.3 User Classes and Characteristics..........................................................................................5
2.4 Operating Environment........................................................................................................5
2.5 Design and Implementation Constraints...............................................................................5
2.6 Assumptions and Dependencies...........................................................................................7
3. Specific Requirements.............................................................................................................7
3.1 Functional Requirement.......................................................................................................7
3.2 Requirements of the bank computer for the software…………………………………  ………..7 
4. External Interface Requirements............................................................................................8
4.1 User Interfaces.....................................................................................................................8
4.2 Hardware Interfaces.............................................................................................................9
4.3 Software Interfaces..............................................................................................................9
5. Other Nonfunctional Requirements.......................................................................................9
5.1 Performance Requirements.................................................................................................11
5.2 Safety Requirements...........................................................................................................11
5.3 Security Requirements........................................................................................................11
5.4 Software Quality Attributes................................................................................................12
6. Other Requirements...............................................................................................................12
                      Page 1

Introduction

1.1 Purpose

This document describes the software requirements and specification for Quikr.com.

1.2 Document Conventions: font: TNR 11

1.3 Intended Audience and Reading Suggestions

The document is intended for all the stakeholders’ customer and the developer (designers, testers,
maintainers). The reader is assumed to have basic knowledge of banking accounts and account
services. Knowledge and understanding of UML diagrams is also required.

1.4 Definitions

1.4.1 Definitions

 Account
A single account on Quicker means a report or description of person details . Accounts may be of
various types with at least selling or buying. A customer can hold more than one account.

 QUIKR
Quikr is an Indian classified advertising platform. It was founded by Pranay Chulet and Jiby
Thomas in 2008, and as of 2013 reported 12 million listings.

 Feautures
                      Page 2

Quikr provides an online classified advertising platform for users to buy or sell goods and
services from each other. Other services offered include a missed call service,andinstant
messaging.

 Customer
The holder of one or more accounts in a site. A customer can consist of one or more persons or
corporations, the correspondence is not relevant to this problem. The same person holding an
account at a different place is considered a different customer.

 Deal
We only specified that QUICKR must work purchasing and buying of old products consists of house
and everything, we may also want to provide the flexibility to operate on accounts of different
customers. The different operations must balance properly.

1.5 Project Scope

The software supports a computerized shopping network to buy and sell products. The network
enables customers to complete simple purchasing services via automated Quikr. The Quikr provide
their own software for their own computers. The software requires appropriate record keeping and
security provisions.

Overall Description

1.6 Product Perspective

The Quikr network does not work independently. It works together with the different partners to sell
and buy and the software run by the network’s sellers.
Communication interface: The software creates communication interface between different people
for purchasing and selling products.
Software interface: The messages sent via the software network are specific to the target the seller
and buyer systems
Hardware interface: The software will run on a computer.
                      Page 3

User interfaces

Customer: The customer user interface should be used, such that 99.9% of all new users are able to
complete their work without any assistance.
Quickr Personnel: Security personnel are responsible for removing or blocking accounts. There
should be a simple interface (touch or double click to open).

Maintainer: The maintainer is responsible for adding new accounts to the network and solving 
problems for exixting accounts. 

1.7 Product Features

The software should work 24 hrs. The software identifies a customer by his/her email id and
password. It collects information about a simple account transaction (e.g., sales or purchase),
communicates the other customers.

1.8 User Classes and Characteristics

Characteristics: There are several users of the software network:

Customers are simply members of the general public with no special training.
Bank security personnel need have no special education or experience.
Maintainers must be experienced network administrators, to be able to connect new application to
the network.
                      Page 4

1.9 Operating Environment

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

 Ability to register (new users) and to log in (existing users)

 Ability to post product and services advertisements

 Ability to buy products and services (payment interface)

 Continuous power supply

 Ability to change user details

 Ability to take input from user

 Ability to validate user

1.10 Design and Implementation Constraints

 Register (create new account)

Take Input:

 Input for Name

 Input for email id and phone number

 Validate email and phnone number for previous existence , if exist prompt message,”Email id
or phone number already exist .Please Login “

Log in

Validate credentials:

 Validate that email and password is not wrong

 If wrong prompt message , "email or password is wrong "

Validate for Disabled Account:

                      Page 5

 Validate that the card is not disabled

 If account is disabled, prompt error message, "Account has been Disabled"

Validate for Locked Account:

 Validate that the account is not locked

 If account is locked, prompt error message "Account is locked"

2.6Assumptions and Dependencies

 All time internet connection

 Device is capable of running software

 Limited number of sales per day

 Limited number of purchases per day

2. Specific Requirements

2.1 Functional Requirements

The functional requirements are:

2.1.1 Requirements of the software

Functional requirement 1:

3. Description: The software should display all the products and services offered on the
index page.

Functional requirement 2:

 Description: If a product is sold out , It should not be visible to the customers for
purchasing
                      Page 6

 Processing:

 Output:

 Functional requirement 3:

 Description: If any of the service is not available, it should not be visible to the customers.

 Input: Clicked on book button.

 Processing: Service is not available.

 Output: Display service not available.

Functional requirement 4:

 Description: The software has to check if the entered address and contact number is correct.

 Input: Customer enters the address and phone number.

Processing: Check if it is a valid address and contact number.

 Output: Display please enter valid address and contact number.

Functional requirement 5:

 Description: Check if the area/locality is serviceable.

 Input: Choose service, enter time , valid address and contact details.

 Processing: Arranging service at entered time and address.

 Output: Service Arranged.

Functional requirement 6:

 Description: The user (seller) should be able to view products for sell near by

 Input: Clicks on buy now button.

 Processing: Validate user details and connects with seller

 Output: Connected with seller for further communication

Functional requirement 7:

 Description Authorization dialog: The user (buyer) should be able to view the details about
product and contents and cost.
Functional requirement 8:

 Description: The buyer should be able to view categorized products.

                      Page 7

 Input: Selects a specific category.

 Processing: searches for the product in the specified category.

 Output: Displays available products near by.

Functional requirement 9:

 Description: The user(seller) should be able to post ads.

 Input: The user select product and upload the pictures write description.

 Processing: Processing pictures and description.

 Output: Advertisement posted.

Functional requirement 10:

 Description:The seller should post the ads in categorized manner.

Functional requirement 11:

 Description: The user (seller) should be able to edit product details after posting.

 Input: Edit product category, name , pictures.

 Processing: Replace old details with new details.

 Output : Display updated product information.

Functional requirement 12:

 Description: The user (seller and buyer both) should be able to report frauds.

 Input: Enter the profile of the customer.

 Processing: Reporting fraud user.

 Output: User reported.

Functional requirement 13:

 Description: The user should be able to contact support in case they face any error.

 Input: User select the query or problem faced.

 Process: Contacting support.

 Output: Problem Solved.

                      Page 8

4. External Interface Requirements

4.1 User Interfaces

The customer user interface should be intuitive, such that 99.9% of all new QUICKR users are able
to complete their orders without any assistance

4.2 Hardware Interfaces

The hardware should have following specifications:

 Ability to run software flawlessly

 Ability to perform all the operations

 Continuous power supply

 Ability to connect to main network

 Ability to take input from user

 Ability to validate user

4.3 Software Interfaces

The software interfaces are specific to the target banking software systems.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

 It must be able to perform on hardware having basic requirements.

 Uninterrupted interrupted connections.

                      Page 9

 High data transfer rate.

5.2 Safety Requirements

 Users must change the profile password timely.

 Users must not share the password or sensitive information with other.

 Must have a support contact button.

5.3 Security Requirements

 Users accessibility is censured in all the ways .

 Users are advised to change their password timely.

 Users are advised not to tell their password to anyone

5.4 Software Quality Attributes

           Security.

           Performance.

5.4.1 Availability: The software network has to be available 24 hours a day.

5.4.2 Security: The software network should provide maximal security .In order to make that much
more transparent there are the following requirements:
1. It must be impossible to break into the network.
5.4.3 Maintainability: Only maintainers are allowed to connect new account to the main network.
                      Page 10

6. Other Requirements

6.1 Data Base

The software must be able to use several data formats according to the data formats that are
provided by the data bases.