The document describes an online shopping management system with the following key points: - It allows customers to browse products, add them to a shopping cart, and complete purchases by providing billing, shipping, and payment information. - The system will be built using HTML, CSS, Bootstrap, JavaScript, PHP, and MySQL. - It aims to address limitations of a previous manual system by providing an automated, centralized online shopping platform. - Features for customers include viewing product information without signing up, and feedback; administrators can manage products, orders, and reports.

1. 1

2. Project profile
Name
Online shopping management system.
Front end
Html,css,Bootstrap,javascript,ajax.
Back end
Oop ,php ,mysql.

3. About the Online Shopping management system
 An online shopping system is a virtual market place on the Internet
where customers can browse the catalog and select products of
interest.
 The selected items may be collected in a shopping cart. At checkout
time, the items in the shopping cart will be presented as an order. At
that time, more information will be needed to complete the transaction.
 Usually, the customer will be asked to fill or select a billing address, a
shipping address, a shipping option, and payment information such as
credit card number. An e-mail notification is sent to the customer as
soon as the order is placed.
3

4. Feasibility study
Technical
feasibility
Technical feasibility involves how difficult
will be to build and whether the firm has
enough experience using that technology.
Operational
feasibility
Is a measure of how well a proposed system
solve the problem user satisfies the
requirements .
Scheduler
feasibility
Typically this name estimating how long he
system will take to develop .

5. Current system
Disadvantage
Manual system.
More paper work.
Time consuming.
Not more secure.
Not centralized system.
More rate of error.
No information about all product.

6. Proposed system
Advantage
 Customer need not have to be member for seeing
product information.
 Details of inquiries made by customer also shown to
administrator and employees.
 Response is given to the customer based on the inquiry
type.
 Customer can navigate through the site and see the
product information without paying .
 Customer feedback is given to the employee.
 Customer has to be logged in for making an inquiry for
any products.

7. Hardware requirements
Processor Pentium 4 or later
System memory 512 mb
Hard disk 20 GB or above
Software requirements
Server-side Language OOP PHP
Client-side Language HTML, CSS, Bootstrap,
Javascript, Jquery , Ajax
DBMS Mysql
IDE Netbeans

8. Strategy used in this project
8
BUSINESS-TO-CONSUMER (B2C):
It is the model taking business and consumers
Interaction. The basic concept of this model is to sell
the product online to the consumers.
B2C is the direct trade between the company and
consumers. It provides direct selling through online.
For example: if you want to sell goods and services to
customer so that anybody can purchase any products
directly from supplier's website.

9. Structure Diagram
Customer
AccountProduct Order Payment
View
Search
View
Add
Update
Delete
ViewAdd Update Delete
Check
Conform
Online Shopping System
Add to cart
Structure Diagram for Customer Activities
Auction
Bid a product

10. Structure Diagram
Administrator
StaffOrder PaymentStock Delivery
View
Add
Update
Delete
View
Add
Update
Delete
View Shipment Delete
Check
Collect
Report Check
Status Check
Online Shopping System
Product
ViewAdd Update Delete
Structure Diagram for Administrator Activities
Auction
Manage
Auction

11. Process Flow Chart(user)
Start
Is the
Customer
new?
Customer inputs Details
Stop
Update
Customer
database
Yes
No
Customer ID
Add the new
Customer’s
record
Custome
r Register
Figure: Flow Chart Adding new Customer

12. Process Flow Chart(Administration)
Start
Open Product Entity form
Input name Type,
Price , Quantity
Are all inputs
valid?
Error
Message
Product ID = Last Product ID +1
Stock = Stock + Quantity
Save and Update
Stop
Update Product
Database
Yes
No
Figure: Flow Chart For Adding new products

13. Name of database table
Admin
Category
Customer
Manufacturer
Order
Order Details
13
Order Details
Payment
Product
Temporary cart
Shipping
User Profile

14. Database Design : Table
Table Design for Products
Field Name Data
Type
Size Justification Format Example
Product ID Alpha
Numeric
8 This is a unique key for
each products
identification
PRO#### PRO-0012
PRO-0065
PRO-1452
Products Name Text 30 This field keeps the name
of the products
Nokia,
Sony
Ericssion
Category Text 15 This field keep category of
products
Mobile,
Computer
Purchase Price Number Integer Products price is store in
the field
10024
15478
Sell Price Number Integer This field record the
products selling price
10200
16000
Description Text 100 This field describe the
products description
It is non serial

15. Database Design
Relationship Diagram

16. 16
Data Flow Diagram

17. Data Flow Diagram: Registration
Fig : Data Flow Diagram for Customer Registration

18. Data Flow Diagram: Login
Fig : Data Flow Diagram for Login

19. Data Flow Diagram: Add item Cart
Fig : Data Flow Diagram for Add item to cart

20. Data Flow Diagram: Payment
Fig : Data Flow Diagram for Payment Details

21. 21

22. 22

23. Product Details
23

24. Shipping Information
24

25. Payment
25

26. Future Plan
On this topic further study must be needed
future development for:
Will make more dynamic for the user.
Will make the site more popular add Auction.
Will make more user interactive.

27. Conclusion
This is design with kipping quality assurance at
extreme the system is developed with the latest
technology with the aspects of oop php integrates
utilities with keep ahead from the current area.
The documentation of the system is developed in the
view of re-engineer purposed.re-engineering and the
ability of system to prove efficiency in timely manner
for every long period.
27