Introduction

Computers and electronic systems make their way to the area of society, where data
and knowledge are the key needs. The actual analysis of the system becomes very
useful to its users because the manipulation and use of the data in a practical manner is
the need of any enterprise.

General 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.

Scope
The paper is the one that defines the specifications along with the device interfaces. It
is intended for use by the developers and will act as the basis for validating the final
device delivered.

Overview
The method allows shopping merchandise, items, and services electronically by picking
the products specified on the website (E-Commerce site).

Overall description
Product Perspective

The suggested framework is a solution for the online purchase/sale of goods.

Product Functions

The device helps users to purchase/sell goods online through a global internet connection.

User Characteristics

There are 3 forms of users for the suggested system.

 Administrators:

Administrators are people who add or control categories for goods and are responsible for
administering the Vendors.

 Vendors/Sellers :

Vendors/Sellers will link their goods to the index, which will be displayed on the website
to end-users, or inform consumers who can purchase the products by choosing the one
they need. Vendors will have unique rights over end-users and will have the right to
handle the items they add.

 End Users/Customers:

The end customer will be the one who visits the website and orders items online from
those added by the Vendors/Sellers.

General Constraints

 The key restriction here will be to verify the validity of the purchaser, which is
not always feasible. Security threats may be involved.

 The built framework can run on any platform (Unix, Linux, Mac, Windows,
etc.) that includes a web browser that supports PHP, JavaScript, and AJAX.
Assumptions and Dependencies

 The details related to the product, customer, payment, and service transaction
are provided manually.

 The administrator is created in the system already.

 Roles and tasks are predefined.

External Interface Requirements

User Interfaces:

Each part of the user interface is designed to be as user-friendly as possible. The fonts
and buttons used are designed to be very quick and easy to load on web pages. The pages
will be kept light in space so that it won’t take a long time to load the tab.

Hardware Interfaces :
 Processor: Pentium or Higher.
 RAM: 312MB or Higher.

Software Interfaces :
 Operating System: Unix, Linux, Mac, Windows, etc.
 Development tool: PHP: Hypertext Preprocessor, JavaScript, Ajax
 Database: MySQL

Communication Interface
The ordering system of the website shall give an e-mail confirmation to the
customer that the goods purchased will be sent to the mailing address along with
the identity of the buyer.

Functional Requirements
1.Master Maintenance

This module consists of information on goods and services. This requires two
submodules, Commodity Master and Price Master.

2. Product Master :

Product master provides details about a single product, such as product number, object,
name, category, product photos, definition, specifications, requirements on items to be
featured on the website.

3. Price master :

Price Masterworks with the quality of the goods, discounts applicable to the individual
product of the vendor/seller.

4. Transactions :

All transactions carried out on the website will be monitored and handled by this module.
Transactions in the form of ownership of the Shopping Cart.

5. Reporting:

This module deals with the management of the report of the whole framework. This
comprises three Stock Report, Order Report, and Distribution Report sub-modules.
After all transaction the system can generate the portable document file (.pdf) and
then sent one copy to the customer’s Email-address and another one for the system
data base to calculate the monthly transaction .

 Order Report : Order Report would include the list of items ordered and the
description of the consumer who requested the goods, which are not shipped.

 Delivery Report : Delivery Reports will produce a list of items that are shipped to
consumers.

6. Housekeeping Module:
This module deals with data backup for potential comparisons and thus reduces the size
of the archive

7. Registration
If customer wants to buy the product then he/she must be registered, unregistered
user can’t go to the shopping cart. 
8. Login
Customer logins to the system by entering valid user id and password for  the
shopping.
9. Changes to Cart
Changes to cart means the customer after login or registration can make order or
cancel order of the product from the shopping cart.  
10. Payment
For customer there are many type of secure billing will be prepaid as debit or credit
card, post paid as after shipping, check or bank draft. The security will provide by
the third party like Pay-Pal etc.   
11. Logout 
  After the payment or surf the product the customer will logged out.
12. Technical Issues
This system will work on client-server architecture. It will require an internet
server and which will be able to run PHP application. The system should support
some commonly used browser such as IE etc.

Non Functional requirement

1. Security
2. Reliability
3. Maintainability
4. Portability
5. Extensibility
6. Reusability
7. Compatibility
8. Resource Utilization
 Performance Requirement
There is no performance requirement in this system because the server    request
and response is depended on the end user internet connection.

Product Perspective
Product aimed toward a person who don’t want to visit the shop as he might don’t
get time for that or might not interested in visiting there and dealing with lot of
formalities.

Design Constraints
There are few restrictions that the device has to meet. They’re:

 Both inputs should be reviewed for validation and messages should be issued
for erroneous results. Invalid data should be skipped and error messages should be
given.

 The information given by the vendor during registration should be maintained

in the database.

 When submitting items to the scheme, the mandatory fields must be reviewed
for validity as to whether the provider has entered the necessary data in these
mandatory fields. If this is not the case, the right error message should be shown or the
data should be stored in the archive for later retrieval.

 Both mandatory fields should be filled in by the customer when ordering

products from the cart.

Technical Issues
This system will work on client-server architecture. It will require an internet server
and which will be able to run PHP application. The system should support some
commonly used browser such as IE, mozzila firefox,chrome etc.