INDEX

1. Introduction

1.1 Purpose………………………………………………………………………
1.2 Scope...............................................................................................................
1.3 Definitions……………………………………………………………………
1.4 Overview……………………………………………………………………..
1.5 Process Model………………………………………………………………..

2 .Software Requirement Specification.

2.1 Overall Description………………………………………………………

2.1.1 Product perspective. …………………………………………………..
2.1.2 Product functions.. ………………………………………………………
2.1.3 User characteristics. ……………………………………………………
2.1.4 General Constraints………………………………………………………
2.1.5 Assumptions and Dependencies. …………………………………………
2.2 Data Flow Diagram... ………………………………………………………
2.2.1 DFD Level 0. ……………………………………………………………
2.2.2DFD Level 1……………………………………………………………
2.2.3 DFD Level 2: Reservation Module………………………………………
2.2.4 Data Dictionary……………………………………………………………
3. Project Management
3.1 Cost Estimations. ……………………………………………………………
3.1.1 Functional Point Estimation... ……………………………………………
1
3.1.2 Efforts……………………………………………………………
3.2 Risk Table……………………………………………………………
3.3 Timeline.. ……………………………………………………………

4 .Design Engineering.
4.1 Architectural Design. …………………………………………………………

5.References……………………………………………………………

6.Conclusion………………………………………………………

2
 1. Introduction

1.1 PURPOSE:

This document is meant to delineate the features of OSS, so as to serve as a guide

to the developers on one hand and a software .
validation document for the prospective client on the other. The Online Shopping
System (OSS) for electronics item shop web application is intended to provide
complete solutions for vendors as well as customers through a single get way
usingthe internet. It will enable vendors to setup online shops,
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:

This system allows the customer’s to maintain their cart for add or remove the
product over the internet

3
1.3 Definitions

OSS- Online shopping System (for electronics item

shop).
SRS- Software Requirement Specification
GUI- Graphical User Interface
Stakeholder- The person who will participate in system.
Ex. Customer, Administrator, Visitor etc.

1.4 Overview

This system provides an easy solution for customers to buy the product
without going to the shop and also to shop owner to sale the product.
This proposed system can be used by any naïve users and it does not
require any educational level, experience or technical expertise in
computer field but it will be of good use if user has the good knowledge
of how to operate a computer.

1.5 Process Model

Choosing the best process model depends on various factors such as project
requirements, timeline, budget, and level of flexibility needed. For an online
shopping cart system, the Rapid Application Development (RAD) model might
be the most suitable choice. Here's why:
Time to Market: RAD focuses on rapid prototyping and iterative development,
which can help in quickly delivering a functional online shopping cart system.
This is crucial in the fast-paced e-commerce industry where getting to market
quickly is essential.

Flexibility: RAD allows for changes and modifications throughout the

development process. In an online shopping cart system, requirements might
evolve based on user feedback or market trends. RAD's iterative approach
accommodates these changes more effectively than the Waterfall model.

4
2. Software Requirement Specification

2.1 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 to purchase them online without visiting the shop
physically.
The online shopping system will use the internet as the sole method for selling
goods to its consumers.

2.1.1 Product Perspective

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

5
2.1.2 Product Functions

Use case diagram:

6
2.1.3 User Characteristics

User should be familiar with the terms like login,register,order system etc.

2.1.4 Principle Actors

2 Principle Actors are Customer and Administrator

2.1.5 General Constraints

A full internet connection is required for OSS.

2.2 Data Flow Diagram

2.2.1 DFD Level 0

SELLER

Product confirmation
& payment receipt

Personal Details
ONLINE
SHOPPING & select product
SYSTEM

Order by Report
offff

ADMIN CUSTOMER

7
 2.2.2 DFD Level 1

LOGIN TABLE
DATA FOR
VERI
VERIFIED DATA

LOGIN VIEW
ADMIN ID & PASSWORD CUSTOME
R
REJECTED IF NOT DETAIL
MACHED

ADD&V
IEW
DELEVE
RY

ADD
PRODUC VIEW FEED
T BACK

Feed back
EDIT VIEW
PRODUCT Details
DAILY
SELL

Feedback
DELETE
PRODUCT
SELL DETAILS

Product Details
PRODUCT TABLE SELL TABLE

8
2.2.3 DFD Level 2

item databae
Item report
New item detail

ITEM
MASTER
MODULE
Category
Detail
add new Supplier Detail
category
Item
category
Supplie
edit category r
suppl
module er list

City & City & State

State
Add Edit City Module Detail

Add Edit State

9
2.2.4 DATA DICTIONARY

For Customer Table

Column_id + user_id + password + customer_name + sex + address +

date_of_birth + phone_no + email

For Feedback Table

Customer_id + feedback + feedback_date + feedback_no

For Courier Company Table

Comp_id + comp_name + phn_no + address + email_id + area_id

For Area Detail Table

Area_id + Area

For Category Table:

Category_id + Category_name + Category_n.

ForProduct Table:

Prod_id + Category_id + Product_name + Product_descp + Price + Availability

Quantity

For Temporary Table:

Product_id + Product_name + Price + Quantity + Customer_id + Order_no

10
For Login Table:

User_id + password + User_type

For Order Table:

Customer_id + Order_date + Order_new+ TotalItemPurchased + Totalbillamount

+ Bank_Name + Account_no + Pin_no + Mode_of_Payment + Comp_id

For Report Table

Order_no + Report + Customer_id + Report_no

For Order Detail Table:

Prod_id + Quantity + Order_date + Order_no

11
3.Project Management

3.1 Cost Estimations

3.1.1 Functional Point Estimation

External Inputs (EIs): 5

(User Login, Product Search, Product Specifications, Order Details, Payment

Details)

External Output (EOs): 5

(Product Specification, Order confirmation, Bill Generation, Feedback, Report

Generation)

External Inquiries: 3

(Fetching Product Details, Fetching Order Details, Calculating Purchase Details)

External Interface Files (EIFs): 0

Internal Logical Files (ILFs): 6

(Login Table, Product Table, Cart Details, Order Table, Order Detail Table,
Temporary Table)

12
3.2 Risk Table

Risks Ctegory Probability impact Mitigation

Large number PS 20% 4

of customer
than planned
Requirement 25% 3
Understanding PS

Customer will 70% 3

not meet PS
expected
product
Delivery BI 90% 2
deadline will be
tightened
Staff turnover ST 60% 1
will be high

Refunding of BI 50% 2
money

13
3.3 Timeline

14
4. Design Engineering

4.1 Architectural Design

15
5. References

https://www.google.com/search?q=conclusion+of+online+shopping+cart+system
+in+software+engineering&rlz=1C1UEAD_enIN1100IN1102&oq=co&gs_lcrp=
EgZjaHJvbWUqBggAEEUYOzIGCAAQRRg7MgYIARBFGEAyBggCEEUYO
TIGCAMQRRg7MgYIBBBFGDsyBggFEEUYPDIGCAYQRRg8MgYIBxBFG
DzSAQgyMzQ3ajBqN6gCALACAA&sourceid=chrome&ie=UTF-8

16
6. Conclusion

An ecommerce shopping cart is software that enables customers to make

purchases on a website. It takes the customer's payment, verifies the payment
method, processes the transaction, and completes the checkout process, all in a
matter of seconds.

17