MODULE NAME

ONLINE SHOPPING

Functional Requirement Document

COEPD
 Functional Requirement Document

1. Document Version Control List

Version Date Author Description

01 23-Dec-2019 Sreelakshmi P FRD Doc

2. Distribution List

Version Date Name Role Distribution

Purpose
01 24-Dec-2019 Sreelakshmi Senior BA Doc Owner
01 24-Dec-2019 Nilesh Project Manager Project Sponsor

Version Private & Confidential Page 1

 Functional Requirement Document

Contents
1. Document Version Control List...........................................................................................................1
2. Distribution List...................................................................................................................................1
3. Business Rules.....................................................................................................................................3
4. System Rules.......................................................................................................................................3
5. Control Flow........................................................................................................................................3
6. Purpose...............................................................................................................................................3
7. Project Background.............................................................................................................................3
8. Project Objective.................................................................................................................................3
9. Business Requirements.......................................................................................................................3
9.1. Stake Holder Requirements........................................................................................................4
10. Assumptions & Constraints.............................................................................................................4
11. Use Case Diagrams [UML]...............................................................................................................4
11.1. Actor Specific Use Case Diagrams...........................................................................................4
11.2. Use Case Specifications...........................................................................................................5
9. Activity Diagram......................................................................................................................................5
9.1. Process Specific Activity Diagrams..............................................................................................5
9.2. Activity Specification...................................................................................................................6
9.2.1. Basic Flow............................................................................................................................6
9.2.2. Alternative Flow..................................................................................................................6
9.2.3. Exception Flow....................................................................................................................6
10. Functional Requirements................................................................................................................6
11. Non Functional Requirements........................................................................................................6
12. Prototyping.....................................................................................................................................7
13. Master Tables..................................................................................................................................7
14. Notes...............................................................................................................................................7

Version Private & Confidential Page 2

 Functional Requirement Document

3. Business Rules
 All the state government policies for selling of goods are followed.
 Organization allows selling of goods, but with no exchange of goods.
 Organization allows selling of goods, but with no return of goods.

4. System Rules
 On confirming order, all items must be confirmed.
 On canceling order, all items of order will be cancelled.

5. Control Flow
Enter Order Number

Fetch Order details

Get Items,quantity,price

Invoke total price

Get customer details

6. Purpose
The purpose of this document is to specify all the functionality of the online shoppingfacility
provided by the organization.

Version Private & Confidential Page 3

 Functional Requirement Document

7. Project Background

Current System:

The organization aims at checking the order details i.e items contained in an order, the
respective prices of items and the quantity. It also checks the customer details.

Drawbacks:

 It is time consuming.
 Checking transactions is hectic and not efficient.

System Proposed:

 To make it more efficient and less time consuming and in order to make it more
systematic to track details, it is proposed to build a web application.

 Next it systematically gives all items of an order and provides total sales price and
display it.

 The screen also shows customer details like phone number.

8. Project Objective

Goal of proposed system:

 To make it more efficient and less time consuming and in order to make it more
systematic to track details, it is proposed to build a web application.

 Next it systematically gives all items of an order and provides total sales price and
display it.

 The screen also shows customer details like phone number.

9. Business Requirements
[Include all business requirements related to project to as listed below (or) module specific
requirements]

Version Private & Confidential Page 4

 Functional Requirement Document

9.1. Stake Holder Requirements

Stakeholder Requirements
Retailer 1.Screen to Input order number.
2.Screen to display order details and total
price.
3.Screen to display customer details.

10.Assumptions& Constraints
# List All Assumptions& Constraints Functional requirements are based on
1.Proper Network connections available at all retail shops.
2. Proper Network connections available at all retail shops.

3.Only 100000 customers can be attended in a day currently.

11.Use Case Diagrams [UML]

Version Private & Confidential Page 5

 Functional Requirement Document

11.1. Actor Specific Use Case Diagrams

-End1 -End2
-End7 Access Order
* *
Details
* «uses»
«uses»
Total order Price «extends»
Telephone Agent
«uses»
Order No Time
«uses» «uses»
Item No.

Quantity Unit price

-End8

«uses» Access Customer «uses»

* Details
Phone No
Customer Name

Version Private & Confidential Page 6

 Functional Requirement Document

SMS Email

-End4
Maintain Customer
Catalog
*
-End3
-End5 Alerts on Commit or
«uses» Cancel of order
*
*
-End6
Maintain Order
Catalog
*
Admin

Version Private & Confidential Page 7

 Functional Requirement Document

11.2. Use Case Specifications

Use Case ID : 01 Use Case Name:Access Order items UC Spec

Created By : Sreelakshmi References :
1. Use Case Description This System explains how telephone agent access
order details using the order registry for the
online shopping.

2. Actor Telephone agent.

3. Pre-Conditions Online Shopping system should have active

network.
Online Shopping system should be connected
actively with order registry and customer catalog.

4. Basic Flow 1.Use case starts with telephone agent accessing

the order details from order registry.
2.Getting order instance from order No.wrt order
time.

3.Get all Items of the Order fetched.

4.Get Item No, Quantity and Unit price of each
Item.
5.Invoke Total order Sum to get total price of
order.

Version Private & Confidential Page 8

 Functional Requirement Document

5.Use case ends successfully.

5. Alternative Flow 5.1. Unable to fetch record for order No.

If unable to fetch record for order no. then,
Use case ends with failure condition.
5.2. Unable to fetch record for Item No.
If unable to fetch record for Item No, then
Use case ends with failure condition.
5.3. Unable to get total order price.
If unable to get total order price then,
Use case ends with failure condition.
6. Exceptional Flow Non
7. Post –Conditions 7.1Successful completion
Telephone agent will be able to get all details of
order wrt order No.
And internal logs updated successfully.
7.2 Failure Condition
The logs have been updated successfully.

8. Key Scenarios No response from Online Registry or Customer

Catalog.
9. Special Requirements [SpReq:WC-1]Online shopping system shall keep
a log including date and time, of all complete and
incomplete actions.

Use Case ID : 02 Use Case Name:Accessing Customer details

UCSpec
Created By : Sreelakshmi References :
1. Use Case Description This System explains how telephone agent access
customer details using the customer catalog for
the online shopping.

2. Actor Telephone agent.

3. Pre-Conditions Online Shopping system should have active

network.
Online Shopping system should be connected
actively with order registry and customer catalog.

4. Basic Flow 1.Use case starts with telephone agent accessing

the customer details from customer catalog.
2.Getting customer record from order customer
name and phone number.
3.Use case ends successfully.

Version Private & Confidential Page 9

 Functional Requirement Document

5. Alternative Flow 5.1. Unable to fetch record for customer name.

If unable to fetch customer record for customer
name then,
Use case ends with failure condition.
5.2. Unable to fetch record for phone no .
If unable to fetch customer record for phone no,
then
Use case ends with failure condition.

6. Exceptional Flow Non

7. Post –Conditions 7.1Successful completion
Telephone agent will be able to get all details of
customer wrt customer name and phone
number.
And internal logs updated successfully.
7.2 Failure Condition
The logs have been updated successfully.

8. Key Scenarios No response from Terminal.

9. Special Requirements [SpReq: WC-1] Online Shopping system shall keep

a log including date and time, of all complete and
incomplete actions.

Version Private & Confidential Page 10

 Functional Requirement Document

9. Activity Diagram

9.1. Process Specific Activity Diagrams

Use Order Registry Use Customer Catalog

Select order using order No Find Customer using customer name and phone no.

Access order items

Access Item no,Quantity and unit price

[Invoke total order price

]

[NO
]
Return Total order price

Version Private & Confidential Page 11

 Functional Requirement Document

9.2. Activity Specification

9.2.1. Basic Flow Process Steps :

Step 1 : Input Order number.
Step 2:Invoke total price.
Step 3:Input Customer name and phone number.
Step 4:Commit order or cancel order.
9.2.2. Alternative Flow Process Steps :
Step 1. Unable to input order number.
Step 2. Unable to invoke total price.
Step 3. Unable to input customer name or phone
number.
Step 4. Unable to Commit order or cancel order.

9.2.3. Exception Flow Process Steps:

Non

10.Functional Requirements
Functional Requirements are those the system needs to perform all those actions which come in
the development of the application are considered to be functional requirements.]

Requirements are prioritize as per below Standards

M-Must have S-Should have C- Could be in future W-Would like to

S.NO Req ID Description Priority

1 FR_1 Input Order number. M

2 FR_2 Invoke total price M

3 FR_3 Input Customer name M
and phone
4. FR_4 Commit order or M
cancel order.

11.Non Functional Requirements

S.NO Req ID Description
1 NFR_1 Should be available across all regions
2. NFR_2 Should be accessible 24*7.

Version Private & Confidential Page 12

 Functional Requirement Document

12.Prototyping

Version Private & Confidential Page 13

 Functional Requirement Document

Version Private & Confidential Page 14

 Functional Requirement Document

Version Private & Confidential Page 15

 Functional Requirement Document

13.Master Tables

1)Tbl_ItemDetails

2)Tbl_PurchaseDetails

3)Tbl_Customerdetails

14.Notes
This system aims to reduce the manual efforts wrt Selling/purchasing of items for the organization.

Version Private & Confidential Page 16