SOFTWARE REQUIREMENTS SPECIFICATION

FOR

VISHAL LOGIN SYSTEM

(V-MART)

PREPARED BY PARKSHIT SHARMA

SECTION: K21EH

ROLL NO: A34

Page i of 26
 Table of Contents

1. Introduction………………………………………………………………………..1

1.1 Purpose

1.2Scope

1.3Audience, Definitions, Acronyms and Abbreviations

1.3.1 Audience Definitions

1.3.2 Acronyms and Abbreviations

1.4References

1.5Technologies to be used

1.6Overview

2. Overall Description…………………………………………………………………9

2.1 Product Perspective

2.2 Product Functions

2.3 User Characteristics

2.4 Constraints

2.5 Operating Environment

3.Specific Requirements……………………………………………………………..11

3.1 Functional Requirements

3.2 Non-functional Requirements

3.2.1 Performance Requirements

3.2.2 Safety Requirements

3.2.3 Security Requirements

Page ii of 26
3.2.4 Error handling

4. Interfaces and Possible Scenarios…………………………………………………14

4.1 Customer's Interface

4.1.1 Login

4.1.2 Registration Interface

4.1.3 Personal Data Editing

4.1.4 Search

4.1.5 Add as favorites

4.1.6 Cart

4.1.7 Payment

4.1.8 Support

4.2 Interfaces for Shop Owner

4.3 Interfaces for Sales Manager

4.4 Interfaces for Accounts Manager

4.5 Interfaces for Purchase Manager

4.6 Interfaces for Customer care

4.7 Interface for Administrator

5. DATA FLOW DIAGRAMS…………………………………………………………………………………………19

5.1 0 level DFDs

5.2 1st level DFDs

5.3 2en level DFDs

6. TEST CASES…………………………………………………………………………………………………………….22

Page iii of 26
1. INTRODUCTION

V-Mart Retail Ltd retails readymade garments accessories etc. and is engaged in the
business of 'Value Retailing' through the chain of stores situated at various cities in
India. The company operates its retail stores under the V-Mart brand.V-Mart is one of
the pioneers in setting up stores across various small Indian towns and cities including
Sultanpur Ujjain Motihari. The company primarily operates in Tier-II and Tier-III cities
with a chain of 'value retail' departmental stores offering apparels general merchandise
and kirana catering to the entire family. The company has established stores in Metro
Tier-I Tier-II and Tier-III cities which are primarily located as standalone stores in high-
street areas and shopping hubs of such cities. The average size of the store is
approximately 8000 Sq. Ft. It follows the concept of `value retailing' to target the strata
of the population belonging to the expanding `aspiring class' and `middle class' based
on customer's socio-economic conditions purchasing power demographic details and
customer trends.

1.1 PURPOSE

Vishal login system provided the easy way of shopping from v mart store through
the online means of mode. By sitting just at one place we will we able to see the
product description and will be able to order it online efficiently.

The Online v mart is intended to provide complete solutions for vendors as

well as customers through a single gateway using the internet as the sole
medium. It will enable vendors to setup online fashion shops (garments,
accessories etc.), customer to browse through the shop and purchase them online
without having to visit the shop physically. The administration module will enable
a system administrator to approve and reject requests for new shops and
maintain various lists of shop category

1.2 SCOPE

INITIAL FUNTIONAL REQUIREMENTS:-

Page 4 of 26
 Secure registration and profile management facilities for Customers.
 Browsing through the e-store to see the items that are there in each category of
products like garments (ethnic , western etc.) and accessories.
 Adequate searching mechanisms for easy and quick access to particular products and
services.
 Creating a Shopping cart so that customers can shop ‘n’ no. of items and
checkout finally with the entire shopping carts. Customers can add or
delete items in the cart.
 Regular updates to registered customers of the V MART about new
arrivals.
 Uploading ‘Most Purchased’ Items in each category of products in the Shop.
 Strategic data and graphs for Administrators and Shop owners about
the items that are popular in each category and age group.
 Maintaining database of regular customers of different needs.
 Shop employees are responsible for internal affairs like processing
orders, assure home delivery, getting customer's delivery-time feedback,
updating order's status and answering client's queries online.
 Feedback mechanism, so that customers can give feedback for the
product or service which they have purchased. Also facility rating of
individual products by relevant customers.
 Adequate payment mechanism and gateway for all popular credit cards,
cheques and other relevant payment options, as available from time to
time.

INITIAL NON FUNCTIONAL REQUIREMENTS:-

 Secure access of confidential data (user’s details).

 24 X 7 availability .
 Better component design to get better performance at peak time .
 Advertisement space where it will effectively catch the customer’s
attention and as a source of revenue.
 In addition to the above mentioned points, the following are planned to
be delivered if deemed necessary:

Page 5 of 26
  Warehousing within the very ambits of the project .
 More payment gateways.
 Dynamic price model by which prices can be changed based on demand
and supply.
 Each customer can build a “scrapbook”, where they can have a
collection of garments and accessories to create a specific look basing
on inbuilt templates. The scrapbook created will be visible to other users
who can like and/or comment on the style.
 This list is by no means, a final one. The final list will be dictated by
implementation constraints, market forces and most importantly, by end
user demands.

1.3 AUDIENCE DEFINITIONS, ACRONYMS AND ABBREVIATIONS

 Audience Definitions :- The intended readers of this document are the

developers of the site, testers, website owners, managers and
coordinators.
 Acronyms and Abbreviations:-

Acronym Meaning

v- mart Vishal login system

HTTP HYPER TEXT TRANSFER PROTOCOL
HTTPS Secure Hypertext Transfer Protocol
TCP/IP Transmission Control Protocol/Internet Protocol

1.4 REFERENCES

 FUNDAMENTALS OF SOFTWARE ENGINEERING BY RAJIB MALL

 SOFTWARE ENGINEERING BY IAN SOMARVILLE
 WWW.GOOGLE.COM

Page 6 of 26
TECHNOLOGIES TO BE USED :-

Programming languages:

 JAVA EE: Java Enterprise Edition is a programming platform4 part of

the Java Platform-for developing and running distributed multi-tier
architecture Java applications, based largely on modular software
components running on an application server.
 HTML, XML: Hyper Text Markup Language and Extensible markup
Language are the predominant markup languages for web pages. It
provides a means to describe the structure of text-based information in a
document and to supplement that text with interactive forms,
embedded images, and other objects.
 JavaScript: A client side scripting language used to create dynamic web
content and user interface.

1.6 OVERVIEW
The rest of this SRS is organized as follows:
 Section 2 gives an overall description of the software. It gives what level of
proficiency is expected of the user, some general constraints while making
the software and some assumptions and dependencies that are assumed.
 Section 3 gives specific requirements which the software is expected to
deliver. Functional requirements are given by the use case.
 Section 4 describes the various interfaces and possible scenarios.

2. OVERALL DESCRIPTION

2.1 Product Perspective

Page 7 of 26
 • Vishal login system is aimed towards the vendors who want to reach out to
the maximum cross-section of customer and common people who can be
potential customer. This project envisages bridging the gap between the seller,
the retailer and the customer. V-Mart should be user-friendly, ‘quick to learn’ and
reliable software for the above purpose. It is intended to be a stand-alone
product and should not depend on the availability of other software. It should
run on both UNIX and Windows based platform.

2.2 Product Functions

• User: Administrator

Functions: The Administrator is the super user and has complete control over
all the activities that can be performed. The application notifies the
administrator of all shop creation requests, and the administrator can then
approve or reject them. The administrator also manages the list of available
product categories. The administrator can also view and delete entries in
the guestbook.

• User: Shop Owner

Functions: Any user can submit a shop creation request through the application.
When the request is approved by the Administrator, the requester is notified,
and from there on is given the role of Shop Owner. The Shop Owner is
responsible for setting up the shop and maintaining it. The job involves
managing the sub-categories of the items in the shop. Also, the shop owner
can add or remove items from his shop. The Shop Owner can view different
reports that give details of the sales and orders specific to his shop. The Shop
Owner can also decide to close shop and remove it from the website

•User: Customer/Guests

Page 8 of 26
Functions: A Customer can browse through the shops and choose products to
place in a virtual shopping cart. The shopping cart details can be viewed and items
can be removed from the cart. To proceed with the purchase, the customer is
prompted to login. Also, the customer can modify personal profile
information (such as phone number and shipping address) stored by the
application. The customer can also view the status of any previous orders, and
cancel any order that has not been shipped yet.

• User: Employees

Functions: Purchase department under a Purchase manager to overlook

purchasing activities if warehousing needs arise.

Functions: Sales department under a Sales manager who will look after the
sale of products and services, the most important activity.

Functions: Accounts department under an Accounts manager to look after

the accounting activities of the enterprise

2.3 User characteristics

• The user should be familiar with the Shopping Mall related terminology like
Shopping cart/Checking out/Transaction etc.

• The user should be familiar with the Internet.

2.4 Constraints

• There is no maintainability of back up so availability will get affected.

• Limited to HTTP/HTTPS.

• Real-life credit card validation and Banking system is not implemented.

• No multilingual support

2.5 Operating Environment

Page 9 of 26
The V MART is a website that shall operate in all famous browsers, for a model
we are taking Google Chrome only.

3. SPECIFIC REQUIREMENTS

3.1 Functional Requirements

Administrator:

1. Database Management: Control the database and keep track of all records of
customers and employee details.

2. Contact and Giving Permission to Vendors: Contact with the vendors and give
permission to sell their product under the site after testing the product’s quality.
3. View all details: View the details of all employees and control the whole site.

4. Advertising the Site: Responsible for making advertisements for the site.

Customers:

5. Login: Customers must have a valid login id to enter into the site.

6. Registration: New users can sign up by creating new ID.

7. View and edit Own Details: Can view/edit his personal details, payment details,
and details about services provided.

8. Choosing and comparing products: Can view all available products and can
compare them and make a choice for purchasing products.

9. Purchasing: Can purchase any product through valid credit card.

10. Giving Feedback to Customer Care: Can give feedback to the 24X7 Customer
Care Service center about their impression for the site and services.

11. Logout: Customer must logout of the site after purchasing products.

Visitors:

Page 10 of 26
12. Visiting the Site: Can only visit the site without registration.

Shop Owner:

13. Taking Permission from Administrator: Vendors must take permission from
the Administrator for selling their products under the site. Administrator will test
product’s quality according to its market price to permit vendor for selling
purpose.

14. Consulting with Administrator: Can consult with the Administrator regarding
product9s quality and advertisements.

15. Advertising Vendor’s Own Products: Responsible for making advertisements of

his products, but the site will not be responsible for any kind of advertisements
about products

Sales Manager:

16. View customer details: View the personal details of the customer.

17. Managing Sales to Customers: Responsible for properly allocating the selected
product according to the customer’s choice and delivering product to the
customer.

18. View Product Stocks: Keep track of each product item9s stocks for selling
purpose.

19. Contacting with Administrator: Responsible for informing administrator when

any product item’s stock goes under the minimum level.

Purchase Manager:

20. Consulting with Administrator: Taking permission from the Administrator for
the product to be purchased from vendor.

21. Product Stock Management: Responsible for managing stocks of each product
items.

Page 11 of 26
Accounts Manager:

22. Regulating Payments: Keep track of all the payment transactions made by the
customers and update the payment information.

23. Consulting with Banks: Responsible for contacting the banks for the validation
of the a/c number provided by the customer while purchasing and make the
transaction from the given a/c.

24. Consulting with Administrator: Consult with the Administrator about the
payment details of the customers for the updating of the database.

Customer Care:

25. Getting Feedback from the Customers: Responsible for receiving complaints,
queries and feedback from the customers.

26. Providing Solutions to Customers: Provide feasible solutions to the customers

on their complaints and queries.

3.2 Non-functional Requirements

Performance Requirements

1. The system shall accommodate high number of items and users without any
fault.

2. Responses to view information shall take no longer than 5 seconds to appear

on the screen.

Safety Requirements

3. System use shall not cause any harm to human users.

Security Requirements

4. System will use secured database

5. Normal users can just read information but they cannot edit or modify
anything except their personal and some other information.

Page 12 of 26
6. System will have different types of users and every user has access constraints.

Error handling

7. V Mart shall handle expected and non-expected errors in ways that prevent
loss in information and long downtime period.

Usability

8. Regardless of the size, the website of v mart should be easy to use for even a
non-technical user.

4. Interfaces Possible Scenarios

4.1 Customer’s Interface:

4.1.1 Login:

This interface will consist of two compulsory fields namely, “User Name” and
“Password”. There will also be options for “New User’s Registration” which will
redirect to “Registration” page and a “Forgot Password” option in case a user
forgets the password. If the password entered is correct the Main User Interface
opens up else an error message is displayed.

4.1.2 Registration Interface:

The user will enter his personal details like Name, User Name, Password, Date Of
Birth, Address, Registration Type, etc. Users will be warned about any mistakes on
data format or any other constrains by validation notes and error messages.
When the button "save" button is clicked, the server will check if the username or
email is already taken and alert the user. If everything is entered correctly and
saved a new user will be created.

4.1.3 Personal Data Editing:

Page 13 of 26
If any member wants to change his personal information he can enter his profile
by clicking on his name at the top right of the main page and he will be directed to
the personal details editing page.

4.1.4. Search

The customer can enter the type of item he is looking for and the specifications
he is interested in them he can click on ‘Search’. User can also use advanced
search for more options. For eg: the user can filter the results basing on various
aspects such as size, color , material, brand etc. and also they can sort the product
display according to their wish (relevance, price in ascending or descending,
popularity)

4.1.5 Add as favorites

The user can shortlist his/her favorite item as a list for future reference.

4.1.6 Cart

This will be a space for the customer where he/she can store the items he/she
wishes to buy. The user can also remove items from cart prior to checkout. Once
the user decides to buy the items it cart, the user is directed to the payment page
for making payment.

4.1.7 Payment

The user given options with various modes of payment (online payment through
credit/debit cards, via net or mobile banking or cash on delivery) out of which he
chooses one. The chose mode of transaction is carried therefore by proper
verification and authentication of bank details.

4.1.8 Support

The user can contact with the customer care via phone call or via messages. User
can ask for an assistance or can give feedback on a particular aspect.

4.2 Interface for Shop owner

Page 14 of 26
The shop owner will have a different login id using which he can access his
account that contains a control panel that allows him to contact the
administrator, set up/ maintain shop etc. This control panel will allow the shop
owner to do the following things:

• Request the admin for a permission to set up a shop.

• Set up the catalog for his shop and upload it so that the admin can make it
visible in the website.

• Add/Remove items. The corresponding changes will be done in the database by

the Admin.

• Create advertisements for his products.

• Generate a sales report.

• Discontinue the shop.

4.3 Interface for sales manager

The sales manager will have a different login id using which he can access his
account that contains a control panel that allows him to contact the administrator
and manage sales.

This control panel will allow the sales manager to do the following things:

• Maintain the product database so that the same or different kinds of products
are properly maintained with their unique id, so that when a customer orders a
product, the same product gets allocated without causing any inconsistency to
the database.

• Generate current order shipping status and upload it time to time and provide
an expected delivery date. In case a user cancels a particular order, the same is
taken care of by the sales manager and proper order status is changed and
reflected back.

• Promote sales by associating products with offers and discounts.

Page 15 of 26
• Contact the admin.

4.4 Interface for Accounts manager

The Accounts manager will have a different login id using which he can access his
account that contains a control panel that allows him to contact the administrator
and manage various transactions and accounts.

This control panel will allow the Accounts manager to do the following things:

• Keep track of payment transactions differentiated by their unique id and

associated with corresponding user and update payment information.

• Contact he bank for account validation.

• Contact Administrator.

4.5 Interface for purchase manager

The Purchase manager will have a different login id using which he can access his
account that contains a control panel that allows him to contact the administrator
and manage various purchases for the warehouse.

This control panel will allow the Purchase manager to do the following things:

• Whenever the stocks in warehouse goes under a critical value, the system alerts
the purchase manager about it and he contacts the administrator seeking
permission to make a purchase from a particular vendor.

• Contact a vendor for making a purchase

4.6 Interface for customer care

A customer care employee will have a different login id using which he can access
his account that contains a control panel that allows him to contact the
administrator and manage various queries and feedbacks from the customer.

Page 16 of 26
This control panel will allow a customer care employee to do the following things:
• Read feedbacks from a particular customer and let the administrator know
about it.

• Provide solutions to the queries posted by the customer.

• Contact administrator.

4.7 Interface for Administrator

The administrator will have a different login id using which he can access his
account that contains a control panel that allows him to contact each and every
aspect of the system.

This control panel will allow the administrator to do the following things:

• Access and view the customer database.

• Access and view the database of vendors, go through their requests for shop
creation and reply them back with acceptance /dismissal of their request.

• Access and view the employee database and manage them.

• Make the catalog (that is visible to the customers), taking the design of
corresponding shop owners in consideration .

• Grant/ Reject purchase permit to purchase manager.

• Manage employee salary.

• Contact employees.

Page 17 of 26
5. DATA FLOW DIAGRAMS (DFDS)

5.1 ZERO LEVEL DFD

This is the Zero Level DFD of V-MART, where we have elaborated the high
level process of Shopping System. It’s a basic overview of the whole Online
Shopping System or process being analyzed or modeled. It’s designed to
be an at-a-glance view of Product, Delivery and Confirm Order showing the
system as a single high-level process, with its relationship to external
entities of Shopping, Shopping Cart and Order.

CUSTOMER
MANAGEMENT

SHOPPING
PAYMENT
MANAGEMENT
MANAGEMENT

V-MART

SYSTEM USER
ORDER MANAGEMENT
MANANGEMENT

LOGIN MANAGEMENT

Page 18 of 26
5.2 FIRST LEVEL DFDS

First Level DFD (1st Level) of V MART shows how the system is divided
into sub-systems (processes), each of which deals with one or more of the
data flows to or from an external agent, and which together provide all of
the functionality of the Online Shopping System as a whole. It also
identifies internal data stores of Confirm Order, Delivery, Product, Payment,
Order that must be present in order for the Shopping System to do its job,
and shows the flow of data between the various parts of Shopping, Order,
Delivery, Confirm Order, Product of the system.

CUSTOMER GENERATE
MANAGEMENT SHOPPING REPORT

SHOPPING GENERATE
MANAGEMENT SHOPPING CART
REPORT

ORDER
GENERATE
MANANGEMENT
PRODUCT REPORT
V-MART
LOGIN GENERATE
MANAGEMENT SHIPPING REPORT

PAYMENT CHECK USER LOGIN

MANAGEMENT DEAILS

S SYSTEM USER GENERATE SYSTEM

MANAGEMENT USER REPORT

Page 19 of 26
 5.3 SECOND LEVEL DFDS

DFD Level 2 then goes one step deeper into parts of Level 1 of Shopping
System. It may require more functionalities of Shopping System to reach
the necessary level of detail about the Shopping System functioning. First
Level DFD (1st Level) of Online Shopping System shows how the system is
divided into sub-systems (processes).

CHECK
LOG IN ROLES OF
ADMIN MANANGE PRODUCT DETAILS
TO ACCESS
SYSTEM

MANAGE SHOPPING CART

FORGET DETAILS
PASSWORD
MANAGE CUSTOMER DETAILS
MANAGE
CHECK MODULE
CREDENTIALS S MANAGE SHIPPING DETAILS

MANAGE PAYMENT DETAILS

SEND
EMAIL
TO USER MANAGE ORDER DETAILS

MANAGE REPORT

MANAGE SYSTEM ADMINS MANAGE ROLE OF USER MANAGE USER PERMISSION

Page 20 of 26
6. TESTCASES

Test Case#: 1 Test Case Name: login

System: V MART Subsystem:
Designed By: Parkshit sharma Design Date: 05/10/22
Executed By: N/A Execution Date:
Short Description: test to login to the website

Pre-conditions: The user has valid username and password .

The system will display the main menu.

Step Action Expected System Pass/Fail Comment

Response
1 Click on ‘log in’ button The system displays a
message asking the user to
enter the username and
password
2 Enter the valid username It will ask to click on log in
and password after filling credentials
3 Click log in again System will display the
main menu
4 Check the post conditions

Post- conditions:
1. User is successfully logged in o the main menu.

Page 21 of 26
Test Case#: 2 Test Case Name: Forget Password
System: V Mart Subsystem:
Designed By: Parkshit Sharma Design Date:05/10/22
Executed By: Execution Date:
Short Description: Recover The Password If Forgotten.

Pre-conditions: user has valid username but password forgotten.

System displays forget password option to recover it.

Step Action Expected System Pass/Fail Comment

Response
1 Click on ‘forget password’System ask user to enter
the mobile no. linked with
account.
2 Enter mobile no. System will send the OTP
to the entered no to
recover the account
3 Enter the OTP received Now system will show the
interface to change the
password.
4 Enter the new password Now the password will be
twice changed successfully
5 Check the post conditions

Post- conditions: the new password is saved n the database and user can log in
with new password to access main menu

Page 22 of 26
Test Case#: 3 Test Case Name: Cart
System: V Mart Subsystem:
Desinged By: Parkshit sharma Design Date: 06/10/2022
Executed By: Execution Date:
Short Description: product add to cart

Pre-conditions: user has selected the item to be purchased and want to proceed
for further process of buying

Step Action Expected System Pass/Fail Comment

Response
1 Click on the “add to cart”
Cart icon will indicate the
no. of products added
2. Now click on cart icon Window will be opened
with products selected
3. Continue for the further Payment , address
process as required selection etc.
4. Check the post condition

Post- conditions: Product I successfully added to the cart.

Page 23 of 26
Test Case#: 4 Test Case Name: filter
System: V Mart Subsystem:
Designed By: Parkshit Sharma Design Date:
Executed By: Execution Date:
Short Description: check weather filter option is working

Pre-conditions: user want some selected products to be shown according to his

preferences in different fields.

Step Action Expected System Pass/Fail Comment

Response
1 Click on the filter option There will be list of filters
to be applied
2 Select the particular filter It will mark the filters with
and set according to tick.
preference (multiple can
be selected).
3 Select apply filter option It will apply the filter to
database .
4 Check the post condition

Post- conditions: Now the user will be able to see the selected items only umder
their selected filters.

Page 24 of 26
Test Case#: 5 Test Case Name: Checkout
System V Mart Subsystem:
Desinged By: Parkshit sharma Design Date: 06/10/2022
Executed By: Execution Date:
Short Description: checking out for the sale

Pre-conditions: user is all ready with the choices of his products and now want to
confirm it by checking out. User has added products to the cart.

Step Action Expected System Pass/Fail Comment

Response
1 Now click on “checkout” Address window will open
in cart to select the shipping
address.
2 Add relevant address and Now the payment gateway
click continue will be opened with all info
of product.
3 Select the method of It will give the confirmation
payment and proceed message to user
4 Check the post
conditions.

Post- conditions: check out is successful and user has got the confirmation
message by main and as well as in their account .

Page 25 of 26
*********END OF PROJECT***********

Page 26 of 26