CASE STUDY

ON

Submitted to: Preeti Gupta Submitted by: Bhawesh Gupta

K1516-A17(11505323)
 Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
2. General Description
4.Product Function
5.Achievements
6.Supply chain Management
7.User Characteristics
8. Functional Requirement
9.Web Technology Used in Paytm
10.Hardware and Software Requirements
11.Performance Requirements
12. Interface Description
13. Other non Functional requirement
13.1 Availability
13.2 Security
13.3 Transferability
14. Data Flow Diagram
INTRODUCTION:-
Purpose:-

This document describe the software requirement for a online payment/shopping

website Paytm.com. so as to serve as a guide to the developers on one hand and a
software validation document for the prospective client on the other.

Scope:-

The function of Paytm is to support online payment, fund transfer, e-wallet and e-
commerce.

It is widely used payment gateways now a days asThey provide 45+ banks for net
banking.(one of the largest Payment Gateways in India.)

One also Rs 1 lakh plus money transfer (follow the KYC(know your customer )
rule and regulation) otherwise its RS 10000 .

General Description:-
Paytm is an Indian payment and commerce company. It is one of the largest is one
of the fastest growing Indian e-commerce shopping websites launched in 2010.
The name of the company who launched the Paytm is One97 communication.
Initially it is focused on Mobile and DTH recharging. The Company headquartered
in Noida, India. It gradually provided recharging and bill payment of various
portals including electricity bills, gas bills as well as telephone bills.

In 2014 Paytm has started the business same like as the facilities are getting from
the other E-Commerce company such as Flipkart, Amazon, and Snapdeal. Today,
it is India's most popular online destination for prepaid mobile & DTH recharges
and shopping, and its Android and iOS apps have been ranked among the most
popular apps.
Product Function:-
1. Provides online payment solution for mobile,DTH recharge.
2. Bill payment for electricity, gas, insurance, loan, water, Petrol, Toll
Tag,Metro.
3. Online Flight,Bus and Movie ticket payment system.
4. Online Fee can be paid via paytm.
5. Online shopping.
6. Pay using Paytm wallet(e-wallet).

Achievements :-
2014 – Paytm is Gold Winner at the MMA Smarties in the Mobile App

category.

2014 – Paytm is Silver Winner at the MMA Smarties in the mCommerce

category

2014 – Paytm wins the Best Mobile Money product at the 4th India Digital

Awards.

2013 – Paytm wins Knowledge Faber Best Mobile Wallet Program Award.

2013 – Paytm wins a special mention in m Billionth Awards in

mCommerce/mBusiness category.

2013 – Paytm is Gold Winner at the MMA Smarties for E-Commerce.

2012 – Paytm is recognized as the Most Innovative Startup of the Year at the
Entrepreneur India event organized by Franchise India
 Supply chain management of paytm.

User Characteristics:-
There are several users onPaytm :-

1 End User:-

No specific knowledge or skills are required from the end user.End user should
have basic idea about computer operations and Mobile application interface.

2.Seller

Who sells good on e-commerce sites. With more functionality then End user.
Functional Requirements:-

Functional requirement 1

User Must registered to Paytm for using Paytm services.

User Can create Paytmaccount using his mobile number and email account.

One user can register once using unique mobile number and email account.

Functional requirement 2

User must login Once by using in Paytmcredentials .In case user forgets his/her
password. password reset link or code will be sent to registered mobile number and
Email address.

Functional requirement 3

User must have enough account balance or Paytm balance to complete his/her
transaction.

Functional requirement 4

For online transaction using Debit card/Credit card user must enter Correct

Details mentioned on card.

And user should enter correct OTP.

Functional requirement 5

For shopping user must have at least one address in his/her address book. Or
address can be added before checkout.
Functional requirement 6

The system shall display detailed information of the selected products.

The system shall provide browsing options to see product details.

Functional requirement 7

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 display only 10 matching result on the current screen.

The system shall enable user to navigate between the search results.

The system shall notify the user when no matching product is found on the search.

Functional requirement 8

The system shall allow user to create profile and set his credential.

The system shall authenticate user credentials to view the profile.

The system shall allow user to update the profile information.

Function requirement 9

The system shall display both the active and completed order history in the
customer profile.

The system shall allow user to select the order from the order history.

The system shall display the detailed information about the selected order.

The system shall display the most frequently searched items by the user in the
profile.

The system shall allow user to register for newsletters and surveys in the profile.
Functional Requirement 10

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.

Functional Requirement 11

The system shall maintain customer email information as a required part of

customer profile.

The system shall send an order confirmation to the user through email.

Functional Requirement 12

The system shall display detailed invoice for current order once it is confirmed.

The system shall optionally allow user to print the invoice.

Functional Requirement 13

The system shall allow user to enter the order information for tracking.

The system shall display the current tracking information about the order.

Functional Requirement 14

The system shall display available payment methods for payment.

The system shall allow user to select the payment method for order.

Functional Requirement 15

The system shall display the orders that are eligible to change.

The system shall allow user to select the order to be changed.

The system shall allow user to cancel the order.

The system shall allow user to change shipping, payment method.

The system shall notify the user about any changes made to the order.

Functional Requirement 16

The system shall display the orders that are eligible to change.

The system shall allow user to select the order to be changed.

The system shall allow user to cancel the order

The system shall allow user to change shipping, payment method.

The system shall notify the user about any changes made to the order.

Functional Requirement 17

The system shall display the reviews and ratings of each product, when it is
selected.

The system shall enable the user to enter their reviews and ratings.

Functional Requirement 18

The system shall allow user to view detailed sitemap.

WEB TECHONOLOGY USED IN PAYTM:

SERVE

R SIDE PROGRAMMING LANGUAGE

 JAVASCRIPT

CLIENT SIDE PROGRAMMING LANGUAGE

 JAVASCRIPT
MARKUP LANGUAGE

 HTML
CHARACTER ENCODING

 UTF-8: UTF-8 (8-bit Unicode Transformation Format) is a variable-length

character encoding for Unicode, which is backwards compatible with ASCII.
EXTERNAL CSS

 External Cascading Style Sheets define style rules in a separate CSS file.

EMBEDDED CSS

 Embedded Cascading Style Sheets define a set of style rules in a <style>

element within a web page.

INLINE CSS

 Inline Cascading Style Sheets define style rules directly within an (X)HTML
element using the style attribute.

SESSION COOKIES

 Session cookies are temporary cookies, which are deleted when the user
closes the browser.
 EXTERNAL CSS

 External Cascading Style Sheets define style rules in a separate CSS file.
EMBEDDED CSS

 Embedded Cascading Style Sheets define a set of style rules in a <style>

element within a web page.
INLINE CSS

 Inline Cascading Style Sheets define style rules directly within an (X)HTML
element using the style attribute.
SESSION COOKIES

 Session cookies are temporary cookies, which are deleted when the user
closes the browser
HTTPONLY COOKIES

 Http Only cookies are used only in the HTTP protocol and not in client side
scripts, which may increase security.

NON-HTTPONLY COOKIES

 Non-Http Only cookies are used in the HTTP protocol and also in client side
scripts, which may be a security threat.

SECURE COOKIES

 Secure cookies are used only via an encrypted connections, which may
increase security.

HTTP STIRCT TRANSPORT SECURTIY

 HTTP Strict Transport Security (HSTS) defines a mechanism enabling web
sites to declare themselves

SSL CERTIFICATE AUTHORITY

 GeoTrust is a SSL certificate authority owned by Symantec. This includes

SSL certificates issues by the certification branch of Equifax, which was
acquired by GeoTrust.
 WEB SERVER

 NGINX - Nginx (pronounced as "engine X") is a lightweight open source

web server.

 NODE.JS - Node.js is a server-side JavaScript environment for writing

network programs such as web servers.

TOP LEVEL DOMAIN

 .COM - Commercial entities

Hardware and software requirements: -

1. Multimedia phone which can access Paytm mobile application

And Internet.
2. For PC user web browser supports Java Script and higher
And Internet connection.
3. Since the application must run over the internet, all the hardware shall
require to connect internet will be hardware interface for the system. As for
e.g. Modem, WAN – LAN, Ethernet Cross-Cable.

Performance Requirements:-

1. Error message should be displayed when credentials are invalid.

2. If transaction gets failed user should informed immediately.
3. After successful transaction Invoice or digital receipt should be generated.
4. Database should be update after every successful transaction.

User Interface:-

Paytm offers excellent GUI. Which is easy for user to understand and also provides
Fast payment option from Paytm wallet.

There shall be logical address of the system in IPv4 format.

The user interface for the software shall be compatible to any browser such as
Internet Explorer, Mozilla or Netscape Navigator by which user can access to the
system.

The user interface shall be implemented using any tool or software package like
Java Applet, MS Front Page, EJB etc.

Availability:-

Services provided by Paytm should be access 24 hours a day.

Security: -
While paying using Paytm.PCI DSS 2.0 security norms have been laid down by
payment card industry leaders like MasterCard, Visa, Discover and Amex.
Verisign certified 128-bit encryption technology ensures that any information you
enter when transacting on Paytm.com is sent in a Secure Socket Layer (SSL)
session and is encrypted to protect you against unintentional disclosure to third
parties.

Their digital wallet areapproved by the reserve bank of India(RBI). So people are
trusted on their Paytm wallet service. That means They follow all the rules and
regulation they are required to work e-wallet.

Data Tranfer related security:-

The system shall use secure sockets in all transactions that include any confidential
customer information.

The system shall automatically log out all customers after a period of inactivity.
The system shall confirm all transactions with the customer’s web browser.

The system shall not leave any cookies on the customer’s computer containing the
user’s password.

The system shall not leave any cookies on the customer’s computer containing any
of the user’s confidential information.

Data Storage security:-

The customer’s web browser shall never display a customer’s password. It shall
always be echoed with special characters representing typed characters.

The customer’s web browser shall never display a customer’s credit card number
after retrieving from the database. It shall always be shown with just the last 4
digits of the credit card number.

The system’s back-end servers shall never display a customer’s password. The
customer’s password may be reset but never shown.

The system’s back-end servers shall only be accessible to authenticated

administrators.

The system’s back-end databases shall be encrypted.

Transferability/Conversions: -

Paytm accounts are non-transferable.