Customize Duniya Web Application
FRS
Document Revision History:
Date Version Description Author
29-12-2022 1.0 Customize Duniya web application Tejaswi B
Table of Contents:
Index Description Page No:
1 Introduction
2 Purpose
3 Scope
4 Definitions, Acronyms and Abbreviations
5 Overview
6 Over all description
7 Product perspective
8 Product functions
9 Constraints
10 Specific requirements
11 Technology stack
12 Functional requirements
13 User Module
14 Vendor Module
1. Introduction
1.1 Purpose:
The purpose of this document is to give a detailed description of the requirements for the
“CUSTOMISE DUNIYA” web application. It illustrates the purpose and complete declaration
for the development of the system. It will also explain system constraints, functionalities. This
document is primarily intended its approval and a reference for developing the entire system for
the development team
1.2 Scope:
It is a multi-vendor e commerce where vendors will be uploading the products and user will
purchase them and here there are three modules like user, vendor, and admin and we will have a
web application to perform their activities
This system allows the customer to maintain their cart to add or remove the product and it is to
provide quality products to the customers and allow making easy and quick purchase and
performing sales and the business through website and it is to be designed with a database
capable of maintaining inventory up to date and all the payments done through debit card, credit
card and relevant payment modes.
● Should be user friendly
● Easy to maintain by admin
● Access to registered users and guests
Administrators can use the “Admin Panel” to monitor the entire actions carried out by the users,
other accessible members of the panel and manage all the information.
Furthermore, the application needs an Internet connection to fetch and display all the categories.
All system information is maintained in the database, which is located in the admin panel. The
application also has the capability of representing both the summary and detailed information
about products for below-mentioned users.
1.3 Definitions, Acronyms, and Abbreviations:
Table 1 - Definitions
Term Definition
User Someone who interacts with the application
Admin System administrator who is given specific permission for managing and
controlling the system
Desc Description
1.4 Overview:
This document provides an overview of the business, design, functional requirements of the
project including the system functionality related to the application. Further, this document also
deals with the different specification techniques used in order to specify the requirements more
precisely for different audience
2. Overall description:
It is aimed towards the vendors who want to reach out to the maximum cross section of
customers and common people who can be potential customers. It should be user friendly and
quick to learn. It is bridging the gap between the vendor and customer.
2.1 Product perspective:
The system consists of following Modules/interfaces:
● User Interface
● Vendor Interface
● Administrator panel
The web application will be used to find products from different locations based on the user's
preferred location, while the admin panel is used for managing the information about the
products, users and system as a whole.
The application will need to take the preferred location of the end user within the mobile phone
or laptop, which in turn provide the products accordingly. It will need somewhere to store the
data, for that a database will be used. Both the application and the admin panel will
communicate with the database. The application will only use the database to get the data
while the admin panel will add the modified data. All of the communication will go over the
“Internet”.
In-case of lost internet connection, few features (Client Specification) of the application should
work progressively.
Vendor is the one who can register in the web application and vendor will do the registration
process and add the details in the application and add products.
The admin is the one who takes care of all admin activities and finally the end user will use the
application and purchase the products.
2.2 Product Functions:
Admin: The admin is the super user and has complete control over all the activities that can be
performed the application notifies the admin of all the store creation requests and the admin can
approve or reject them the admin also manages all the list of available gift categories the admin
can also view and delete the entries.
Vendor: Any vendor can submit a request for store creation through the app when the request is
approved by the admin and the requester is notified. The job involves managing the sub
categories of gifts and maintaining them and can also add or remove the items. The vendor can
also view the reports that give the details of the store .
Customer: A customer can browse through the store and choose a gift and every details of the
products and can add or remove the item from the cart and add in the shopping cart and to
proceed further the customer is need to login and also customer can have the profile and its is
stored in application and the customer can also view the status of any previous orders and can
cancel any order
2.3 Constraints:
The application is constrained by the system interface with internet connection. Since the
application fetches data from the database over the internet for the functionalities to run. It
should perform the functionalities even in the offline mode by storing the data in the database.
Both the web application and the admin panel will be constrained by the capacity of the
database. Since the database is shared between both applications.
3. Specific Requirements:
3.1 Technology Stack:
1) FRS Documentation: Google Drive document / Word Document
2) API Development: Web Portal Development:
3) Quality Analytics: Manual testing & update in Azure tool
4) Deliverables: Web portal, Backend Admin panel
4. Functional Requirements:
4.1. User Module:
FR - 1
TITLE: User Registration
DESC: Once the user opens the website the registration should be done
Registration Process:
1. Full name
2. Email Id
3. Password
4. Confirm Password
5. City
6. Country
7. Phone Number
8. Address
9. Terms and Conditions
Validations:
1. Password must contain at least 6 characters
2. Password must contain at least 1 lowercase and uppercase
3. Password must contain at least one number
4. Without accepting terms and conditions the application should not allow for registration
and if the user clicks on terms and conditions the app should be redirected to terms and
conditions.
5. If you already have an account login directly using the email/ mobile number and
password.
6. New password and confirm password should be the same.
FR - 2
TITLE: User Login
DESC: User should be able to Login
1. Mobile Number/Email
2. Password
3. Forgot Password
If user enter valid mobile number/email id with valid password after clicking on Submit button,
system will be verifying that weather entered password matched for correct user Mobile
number/email id then only application allows to login. If entered details mismatched in database
application it will show as Incorrect login credentials.
Validations:
1. User should give the mobile number/email id
2. Password should match with given mobile number/email id
3. When we register email id/mobile number for the login that should match with the
registered mobile/email id then only it should allow.
FR - 3
TITLE: Profile
DESC: User should be able to Login and user will create a profile
1. Full name
2. Email ID
3. Address
4. Age
5. City
6. State
7. Country
8. Update
Validations:
1. Full name should accept minimum 3 characters
2. Full names should not allow numbers, special characters, and it should on be
alphabetic i.e., A-Z, a-z.
3. Full name field should be case sensitive
4. Only letters and space should be allowed for name, landmark, city.
5. Only numbers should be allowed in pin code
FR - 4
TITLE: products
DESC: Once the user login the user can select the different products and can place an order.
Items to be placed for an order
1. Fashion: shirts, jeans, trousers, T-shirts, suits and blazers, indo western and more
2. Gadgets: Mobiles, Tabs, Airpods, Wireless headset
3. Accessories: belts, watches, toys, handbags, hats, headwear and more.
Validations:
1. The system should display all the products
2. Detailed information of selected products
3. It should enable to use one more product to add
4. Order confirmation should be displayed
5. Quantity, color, size should able to be selected
6. on successful order, order confirmation should be displayed in application as well it
should send email or SMS
FR – 5 payments: once the user logins and the user add the products to the cart and if the
user can navigate to the payment page and there will be options like the user can pay through
debit card/ credit card, UPi’s , net banking, cod.
Validations: the payment whether it is successful or un-successful the system should display a
message
FR_6
TITLE: Notifications
DESC: All Shipping related information should be received through notifications like Product
order, received by seller, Product delivered, order completed, return request raised by buyer, if
product return shipped by user, return shipment received, subscription expiry notifications.
Validations
1. Image should be added for all order related notifications
2. Time & date should mandatory for each notification
FR - 7
TITLE: Reminders
DESC: There will be some reminders like birthdays, wedding anniversary it will also show in
which day and which week the birthday and wedding anniversary are there it will provide a
notification with the name of the person.
Validations:
