Online Shopping Portal

Online Shopping Portal Version : 1.
0
Software Requirements Specification Date : March 1, 2017
Online Shopping Portal

Software Requirements
Specification
Online Shopping Portal Version : 1.0
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.4 References
1.5 Overview
2. Overall Description
3. Specific Requirements
3.1 Functionality
3.1.1 Logon Capabilities 8
3.1.2 Mobile Devices 8
3.1.3 Alerts 8
3.2 Usability
3.3 Reliability
3.3.1 Availability 9
3.3.2 Mean Time Between Failures (MTBF) 9
3.3.3 Mean Time to Repair (MTTR) 9
3.3.4 Accuracy 9
3.3.5 Maximum Bugs or Defect Rate 9
3.3.6 Access Reliability 9
3.4 Performance
3.4.1 Response Time 9
3.4.2 Administrator/Librarian Response 9
3.4.3 Throughput 9
3.4.4 Capacity 9
3.4.5 Resource Utilization 9
3.5 Supportability
3.5.1 Internet Protocols 9
3.5.2 Information Security Requirement 9
3.5.3 Billing System Data Compatibility 10
3.5.4 Maintenance 10
3.5.5 Standards 10
3.6 Design Constraints
3.6.1 Software Language Used 10
3.6.2 Development Tools 10
3.6.3 Class Libraries 10
3.7 On-line User Documentation and Help System Requirements
3.8 Purchased Components
3.9 Interfaces
3.9.1 User Interfaces 11
3.9.2 Hardware Interfaces 13
3.9.3 Software Interfaces 13
3.9.4 Communications Interfaces 13
3.10 Licensing Requirements
3.11 Legal, Copyright, and Other Notices

3.12 Applicable Standards
4. Supporting Information
1. Introduction
This document aims at defining the software requirements for Online
Shopping System. This document carries necessary information about
functional requirements, operational constraints, hardware and software specification to
develop desired software product. This is based on requirement statement of customer
and the perspectives of development about software product. Improved new features if
any can be added if needed and the document can be modified.
1.1 Purpose
The Shopping Cart needs to sell different types of products to customer
livingina n y p a r t o f t h e w o r l d . T h e w e b s i t e w i l l s h o w a l l
p r o d u c t s i n c a t e g o r i z e d m a n n e r . Customer can browse any
p r o d u c t f o r i t s p r i c e a n d o t h e r d e t a i l s a n d c a n o r d e r t h e product.
Orders needs to accompany with shipping & billing details. Customer has to pay
1.2 Scope
Purchasing and selling products and services over the internet without the need of
going physically to the market is what online shopping all about. Online shopping
is just like a retail store shopping that we do by going to the market, but it is done
through the internet. Online shopping has made shopping painless and added
more fun. Online stores offer product description, pictures, comparisons, price
and much more. Few examples of these are Amazon.com,
ebay.com, framt.com and the benefits of online shopping is that by having direct
access to consumer ,the online stores can offer products that cater to the needs of
consumer ,cookies can be used for tracking the customer selection over the
internet or what is of their interest when they visit the site again . Online shopping
makes use of digital technology for managing the flow of information, products,
and payment between consumer, site owners and suppliers. Online shopping can
be either B2B (business to business) or B2C (business to consumer).
Shopping cart is one of the important facility provided in online shopping, this
lets customer to browse different goods and services and once they select an item
to purchase they can place the item in shopping cart, and continue browsing till
the final selection. Customers can even remove the items from shopping cart that
were selected earlier before they place the final order. It reminds us of shopping
basket that we carry in departmental store.
1.3 Definitions, Acronyms and Abbreviations

OSS- Online shopping System (for furniture shop)
SRS- Software Requirement Specification
GUI- Graphical User Interface
Stackholder- The person who will participate in system
Ex. Customer, Administrator, Visitor etc.
1.4 Reference
srs-onlineshopping.blogspot.com
https://www.slideshare.net/gajapandiyan/online-shopping-16603063
https://www.utdallas.edu/~chung/RE/Presentations07S/...Doc/Docu
ments/SRS4.0.doc
docshare01.docshare.tips/files/24792/247923506.pdf
docshare01.docshare.tips/files/24792/247923506.pdf
www.freestudentprojects.com/...srs/online-shopping-system-
software-requirements/
cs.txstate.edu/~js236/201212/cs3398/samplesrs.pdf
1.5 Overview
This system provides an easy to solution customers to buy the product without
go to the shop and also shop owner to sale the product.
The SRS will provide a detailed description of the Online shopping portal. This
document will provide the outline of the requirements, overview of the
characteristics and constraints of the system.
One section of the SRS will provide the general factors that affect the product
and its requirements. It provides the background for those requirements. The
items such as product perspective, product function, user characteristics,
constraints, assumptions and dependencies and requirements subsets are
described in this section.
The other section of SRS contains all the software requirements mentioned in
section 2 in detail sufficient enough to enable designers to design the system to
satisfy the requirements and testers to test if the system satisfies those
requirements.
2. Overall Description
The Online Shopping system (OSS) application enables vendors to set up
online shops, customers to browse through the shops, and a system administrator
to approve and reject requests for new shops and maintain lists of shop categories.
Also the developer is designing an online shopping site to manage the items in the
shop and also help customers purchase them online without having to visit the
shop physically.The online shopping system will use the internet as the sole
method for selling goods to its consumers.
2.1 Product Perspective:
Relationship with other products and principal interfaces The interface
will be in 2 basic parts.
1. The businessmans interface for data deletion,entry and the management of
the policy set. The above encompasses all shopkeeper functions such as
changing the item information, managing the despatch time-table et al
2. The customers interface for buying goods and querying. This shall also
include a bulletin board which shall serve as a platform for selling
goods,and by extension thereby,auctions.The interfacee will provide for an
easy search so that the customer will be able to locate the product of his
choice easily.The data items in the shop will be organized in semantics
units called rooms which hold similar products.The rooms are themselves
have child rooms , a parent room and data items in the room .We are using
a tree datastructure for the same.
Both of the above interfaces shall make changes to the same underlying
database structure which in totality shall constitute an online shop.
This product aimed toward a person who dont want to visit the shop as
he might dont get time for that or might not interested in visiting there and
dealing with lot of formalities.
The proposed system is a solution carry out buying/ selling products
online.
2.2 Product Functions:

1. Enable customer to buy online.
2. Enable customer to easily browse through the products.
3. Enable customer to search products.
4. allowing customers to post queries and discuss products and sell through
us.
5. allow the businessman to manage the shop inventory.
6. allow the businessman to view graphs depicting previos sales etc.
7. allow the businesman to change the look and fel of the site with ease.
8. allow the shopkeeper to view different configuration options and update
them.
OSS should support this use case. The system allows the user to buy/sell products
online across internet connection globally.
2.3 User Characteristics:

User should be familiar with the terms like login,register,order system etc.
There are 3 kinds of users for the proposed system.
2.3.1 Administrators:
Administrators are the ones who adds or administers the categories for the products,
and administers the Vendors.
The administrator is the owner of this online shopping-cart application. One must have a
basic understanding of computers and the internet as well as prior knowledge for operating
the eclipse and Java programming languages. The administrator is responsible for
maintaining all the training documents required for the system. The administrator can
perform the following functions:
1. Assign or change the price of the items, update the items in the list, and delete the
items.
2. Assign sales tax for different states at the time of checkout.

3. View the history of the customers who purchased the items.
2.3.2 Vendors/Sellers :
Vendors/Sellers will add their products to the database, which will be seen in the
website to the end users or say customers who can buy the products by selecting the one
they need. Vendors will have the special privileges than the end users, and have ability to
manage the products added by them.
2.3.3 End Users/Customers:
The end user will be the one who visits the website and buys products online from the
ones added by the Vendors/Sellers.
The users of this online shopping-cart application are all customers who would shop to test
the application. These users are anyone with shopping experience and the know-how to
browse through a shopping-cart application. They must have basic understandings about
computers and the internet. The users should be able to perform the following functions using
this system:
1. View, browse, and select a category on the home page.
2. View, add, and update items in the cart.
3. Delete items from the cart.
4. Check out the items from the application or continue shopping.
5. Sign-on/login using a username and password.
6. Place the order by completing the order form.

2.4 Principle Actors:

2 Principle Actors are Customer and Administrator.
2.5 General Constraints:
The main constraint here would be the checking the genuineness of the buyer,
which is not always possible. There can be security risks involved.
The developed system should run under any platform (Unix, Linux, Mac,
Windows etc.. ) that contains a web browser which supports PHP, JavaScript
and AJAX.
A full internet connection is required for OSS.
2.6 Assumptions and Dependencies:
The details related to the product, customer, payment and service transaction provided
manually.
Administrator is created in the system already.
Roles and tasks are predefined.
Working of OSS need Internet Connection.
2.7 UML Diagrams:

Fig. 1. Online Shopping Cart Application System Use-Case Diagram
Fig. 2. Sequence Diagram for how admin add category.

Fig. 3. Sequence Diagram for how users data registered.

Fig. 4. Activity diagram for Registration.

Fig. 5. Activity diagram for Login.
2. Specific Requirements
3.1 Functional Requirements :
3.1.1 Login Facility:

The System shall provide with the Login Capabilities. Without login
capabilities, people can browse the items available on the system.
3.1.2 Add/delete/Save order from cart:

User can add/delete/save particular items in cart.
Selected items will be displayed in the cart.
3.1.3 Track Order:

User can get the location of the particular order through track id.
Track id will be given to the customer through message and email-id.
3.1.4 Cancel Order:

User can cancel the particular order if he placed order by mistake or found that
particular item is available in another shopping site at a lower rate.
He cancel the order if he is not sure about it.
3.1.5 Searching Item:

User can search for the particular item in the search bar.
3.1.6 Single-Page, Fast Checkout

Actually paying for a purchase online is the last hurdle a shopper must traverse
before completing an order. A shopper interested in buying wants to complete
this step as quickly as possible, and a merchant should try to get out of the way.
Just like the supermarket, online shoppers are looking for the shortest line,
Volusion said on its website.
One of the simplest methods to speeding checkout is to limit the checkout form
to as few fields as possible and keep the entire form on a single page to avoid
loading a new page at each stage of the checkout process.
3.1.7 Coupons and Discounts
In this environment, an online merchant must be able to process coupon and
discount codes, so that deal crazy shoppers can get their savings fix.
3.1.8 Product Import and Export
A few years ago, it would not have occurred to me that a shopping cart should
have good product import and export capabilities, but now this is a must-have
feature. Whether one is exporting product data to a shopping comparison site or a
Facebook store or synchronizing inventory from an online store to a physical
location, the ability to easily transfer price, inventory, or product updates in to or
out of a shopping cart is essential.
CUSTOMERS DOMAIN
1. Browsing Through Items: The customer will be given a web interface which
allows easy browsing through the different rooms.Basically the items in the
shop are well organised and well presented so that a user can find his required
item easily.
2. Item Selection: When a customer selects an item authorisation takes place he
will be prompted for password or if he is an unregisterd user he may give his
credit-card number and other information and
3. Basket Remittanceand Updation:The customer is allowed to
update/change/add to his basket with due authorisation after which when he
remits the basket and the items are sent to the despatch table.
4. Queries and discussions: The customer is allowed to post queries about

products available and discuss products sold online.
5. Ability to sell:The customers themselves must be allowed to sell some item
through the website.
BUSINESSMAN'S DOMAIN
1. Shop Modification: He has an interface to add items to his shop and make
modifications to items like prices etc.
2. Easy configurator:The businessman must be able to configure his shop.
3. Graphical view tool:The businessman must be able to graphically view the
saleslogfs and othe statistaicl reports in form of pie charts/bar diagrms etc so
that he can make business decisions.
3.2 Non Functional Requirement:
3.2.1 Usability
Prioritize the important functions of the system based on usage patterns.
Frequently used functions should be tested for usability, as should complex and
critical functions. Be sure to create a requirement for this.
1.1.1.1Graphical User Interface
The system shall provide a uniform look and feel between all the web pages.
The system shall provide a digital image for each product in the product catalog.
The system shall provide use of icons and toolbars.
1.1.1.2Accessibility
The system shall provide multi language support.
3.2.2 Security
The system use SSL (secured socket layer) in all transactions that include
any confidential customer information.
Sensitive data will be encrypted before being sent over insecure
connections like the internet.
3.2.2.1 Data Transfer
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 customers web
browser.
The system shall not leave any cookies on the customers computer
containing the users password.
The system shall not leave any cookies on the customers computer
containing any of the users confidential information.
3.2.2.2 Data Storage
The customers web browser shall never display a customers password.
It shall always be echoed with special characters representing typed
characters.
The customers web browser shall never display a customers 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 systems back-end servers shall never display a customers password.
The customers password may be reset but never shown.
The systems back-end servers shall only be accessible to authenticated
administrators.
The systems back-end databases shall be encrypted.
3.2.3 Availability
The system should be available at all times, meaning the user can access it using
a web browser, only restricted by the down time of the server on which the system
runs. In case of a of a hardware failure or database corruption, a replacement page
will be shown. Also in case of a hardware failure or database corruption, backups
of the database should be retrieved from the server and saved by the administrator.
Then the service will be restarted. It means 24 X 7 availability.
1.1.3.1 Internet Service Provider
The system shall provide a contractual agreement with an internet
service provider for T3 access with 99.9999% availability.
The system shall provide a contractual agreement with an internet
service provider who can provide 99.999% availability through their
network facilities onto the internet.
3.2.4 Maintainability
A commercial database is used for maintaining the database and the application
server takes care of the site. In case of a failure, a re-initialization of the program
will be done. Also the software design is being done with modularity in mind so
that maintainability can be done efficiently.
3.2.5 Portability
The application is HTML and scripting language based. So The end-user part is
fully portable and any system using any web browser should be able to use the
features of the system, including any hardware platform that is available or will be
available in the future.
An end-user is use this system on any OS; either it is Windows or Linux.
The system shall run on PC, Laptops, and PDA etc.
3.2.6 Reliability
The system provides storage of all databases on redundant computers with
automatic switchover.
The reliability of the overall program depends on the reliability of the separate
components. The main pillar of reliability of the system is the backup of the
database which is continuously maintained and updated to reflect the most recent
changes.
Thus the overall stability of the system depends on the stability of container
and its underlying operating system.
Some Quality Attributes are expected from users and developers and represents
some characteristics are known as Non-Functional Requirements.
3.1 Sorting Item:

Sorting of items will be there on the basis of popularity, price, customer
reviews, relativity, deal type, discounts, availability and category.
3.2 Suggestions based on Search:

User can see Suggestions related to the particular item he searched for.
User also get suggestion of the name of the item he typed in search bar
by scroll view of related items below this in the form of list.
3.3 Filters:
Filters will be based on the category user searched for. Examples such as
Brand, Price, Specification, Colour etc .
3.4 Recently Viewed:
This will help user to view items he lastly viewed on the system. This
will also help customers to order items based on their last search.
3.5 Alerts/Notifications:
User get messages and emails regarding order placed and delivered
by the system. Through this
user can get details of the order and he/she can estimate on which day it
will be delivered.
3.6 24*7 Customer Care:
User can get any information regarding any product or item. User can
also get information about return policy and cancel order.
3.3 Master Maintenance :
3.3.1 This module consists of information about the products and services. This
includes two sub-modules, Product master and Price master.
3.3.1.1 Product Master :

Product master includes the information about particular product, such as
product number, item, name, category, images of products, description, features,
constraints of products, which are to be displayed on the website.
3.3.1.2 Price master :
Price master deals with the cost of the product, discounts applicable for the
particular product of a vendor/seller.
3.3.2 Transactions :
All transactions undergoing in the website will be controlled and managed by this
module. Transactions in the sense, Shopping Cart management.
3.3.3 Reporting :
This module deals with report management of the entire system. This includes three sub-
modules Stock Report, Order Report and Delivery Report.
3.3.3.1 Order Report :

Order Report will have the list of products ordered and the customer
details who have bought that product, which are undelivered.
3.3.3.2 Delivery Report :

Delivery Reports will generate products list, which are delivered to
customers.
3.3.4 Housekeeping Module:
This module deals with backing up of data for future references and hence to reduce the
database size
3.4 Performance
Performance is measured in terms of the output provided by the application.
Requirement specification plays an important part in the analysis of a system. Only

when the requirement specifications are properly given, it is possible to design a
system, which will fit into required environment. It rests largely in the part of the
users of the existing system to give the requirement specifications because they are
the people who finally use the system. This is because the requirements have to be
known during the initial stages so that the system can be designed according to
those requirements. It is very difficult to change the system once it has
been designed and on the other hand designing a system, which does not cater to th
e requirements of the user, is of no use. We dont have an exact idea for the
performance requirements at this stage. Maybe at this stage we must say.
1. a powerful server : A large number of the html les are dynamically generated. This
puts a lot of load on the server. It is imperative that server must be powerful enough.
2. A good HDD (fast and big) are essential for a shop
3. The shop must be well connected to the net by a good connection so that a large
number of customers can use the shop together.
3.4.1 Supportability
The system needs to be cost-effective to maintain. Maintainability requirements may

cover diverse levels of documentation, such as system documentation, as well as test
documentation, e.g. which test cases and test plans will accompany the system.
3.5 Design Constraints :
There are few constraints that the system should follow. They are:
All the inputs should be checked for validation and messages should be given for the
improper data. The invalid data are to be ignored and error messages should be given.
Details provided by the vendor during his sign up should be stored in database.
While adding the products to the system, mandatory fields must be checked for
validation whether the vendor has filled appropriate data in these mandatory fields. If
not, proper error message should be displayed or else the data is to be stored in
database for later retrieval.
All mandatory fields should be filled by customer, while buying the items from the
cart.
3.5.1 Web Based Product
There are no memory requirements.

The computers must be equipped with web browsers such as Internet explorer.
The product must be stored in such a way that allows the client easy access to it.
Response time for loading the product should take no longer than five minutes.
A general knowledge of basic computer skills is required to use the product
System Workflow
2. DATA DICTONARY
After carefully understanding the requirements of the client the entire data-
storage requirements are divided into tables. The below tables are normalized to avoidany
anomalies during the course of data entry.
4.1 Category Table

Column Name Data Type Key constraint

Cat_id Int Primary key Not Null
Cat_name Char(20) Not Null
4.2 Product Table
Column Name Data Type Key constraint Extra

Primary key Not Auto_increame
prod_id Int
Null nt
Foreign keyNot -
Cat_id Char(20)
Null
Prod_name Char(20) Not Null -
price int Not Null -
Add_date date NotNull -
Prod_descp Char(40) Null -
image image Not Null -
4.3 User Table

user_id Int Primary key Not Null
user_name Char(20) Not Null
Phone _no int Not Null
email Char(20) Not Null
password Nchar(30) Not Null
Current_address Nchar(40) Not Null
4.4 PaymentTable

user_id Int forgin key Not Null
ammount int Foreign key Not Null
Method Type Int Not Null
COD Bool
Net Banking Bool
ByCard Bool
4.5 Order Table


ord_id Int Primary key Not Null
Prod_id int Forgin Key Not Null
price int Forgin key Not Null
Add_date date Not Null
quantity int Not Null
Total amount int Not Null
Shipping_address Nchar(40) Not Null
4.6 Feedback Table

user_id Int Forgin key Not Null
Type Char(20) Not Null
feedback Char(100) Not Null
comment Char(20) Not Null
Feedback_date date Not Null
4.7 Promotion code

prod_id Int Forgin key Not Null
user_id Int Forgin key Not Null
Cat_id Int Primary key Not Null
Cat_name Char(20) Not Null
3. Interface Requirements :
5.1 User Interfaces:

Each part of the user interface intends to be as user friendly as possible.
The fonts and buttons used will be intended to be very fast and easy to load on
web pages. The pages will be kept light in space so that it wont take a long time
for the page to load.
User Registration Screen:

Logon Screen Prototype:

Home page of Online Shopping System Screen:

Buy and add to cart Screen:

Search products by catagories Screen:

5.2 Hardware Interfaces :
Processor : Pentium or Higher.
RAM : 312MB or Higher.
5.3 Software Interfaces :
Operating System : Unix, Linux, Mac, Windows etc..
Development tool : PHP : Hypertext Preprocessor, JavaScript, Ajax
Data Base : MySQL
5.4 Communication Interface :
The Website Order system shall send an e-mail confirmation to the customer that
the items they ordered will be delivered to the shipping address along with user
identification.

Online Shopping Portal

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Online Shopping Portal

Загружено:

Авторское право:

Доступные форматы

Online Shopping Portal Version : 1.

Online Shopping Portal

3.11 Legal, Copyright, and Other Notices

1.3 Definitions, Acronyms and Abbreviations

2.2 Product Functions:

2.3 User Characteristics:

2. Assign sales tax for different states at the time of checkout.

3. View the history of the customers who purchased the items.

2.3.3 End Users/Customers:

1. View, browse, and select a category on the home page.

2. View, add, and update items in the cart.

3. Delete items from the cart.

4. Check out the items from the application or continue shopping.

5. Sign-on/login using a username and password.

6. Place the order by completing the order form.

2.4 Principle Actors:

Administrator is created in the system already.

Roles and tasks are predefined.

Working of OSS need Internet Connection.

2.7 UML Diagrams:

Fig. 2. Sequence Diagram for how admin add category.

Fig. 3. Sequence Diagram for how users data registered.

Fig. 4. Activity diagram for Registration.

Fig. 5. Activity diagram for Login.

3.1.1 Login Facility:

3.1.2 Add/delete/Save order from cart:

3.1.3 Track Order:

3.1.4 Cancel Order:

3.1.5 Searching Item:

3.1.6 Single-Page, Fast Checkout

4. Queries and discussions: The customer is allowed to post queries about

3.2 Non Functional Requirement:

3.1 Sorting Item:

3.2 Suggestions based on Search:

3.3 Master Maintenance :

3.3.1.1 Product Master :

3.3.1.2 Price master :

3.3.3.1 Order Report :

3.3.3.2 Delivery Report :

Requirement specification plays an important part in the analysis of a system. Only

2. A good HDD (fast and big) are essential for a shop

The system needs to be cost-effective to maintain. Maintainability requirements may

3.5 Design Constraints :

3.5.1 Web Based Product

There are no memory requirements.

4.1 Category Table

Column Name Data Type Key constraint

4.2 Product Table

Column Name Data Type Key constraint Extra

4.3 User Table

Column Name Data Type Key constraint

Column Name Data Type Key constraint

4.5 Order Table

Column Name Data Type Key constraint

4.6 Feedback Table

Column Name Data Type Key constraint

Column Name Data Type Key constraint

5.1 User Interfaces:

User Registration Screen:

Logon Screen Prototype:

Home page of Online Shopping System Screen:

Buy and add to cart Screen:

Search products by catagories Screen:

5.2 Hardware Interfaces :