A

PROJECT REPORT
ON
ONLINE FURNITURE SHOP MANAGEMENT
SYSTEM
Towards partial fulfilment of the requirement in
6th Semester B.Sc. IT 2022-23
Submitted By: -
200510102018 Diya Solanki
Submitted To: -
Parul Institute of Computer Application
Under the Guidance of
Prof. Vijya Tulsani

1
 Acknowledgement

The success and final outcome of this project required a lot of guidance and assistance from
many people and we are extremely privileged to have got this all along the completion of our
project. All that we have done is only due to such supervision and assistance and we would
not forget to thank them.

I respect and thank Dr. Priya Swaminarayan, Dean, FITCS for providing us an opportunity
to do the project work in BCA and giving us all support and guidance, which made us
complete the project duly. We are extremely thankful to Mam for providing her support and
guidance, although she had busy schedule managing the academic affairs.

We would not forget to remember Dr. Hina Chokshi, HOD, BCA department for her
encouragement and more over for her timely support and guidance till the completion of our
project work.

We owe our deep gratitude to our project guide Prof. Vijya Tulsani, who took keen interest
on our project work and guided us all along, till the completion of our project work by
providing all the necessary information for developing a good system.

I am thankful to and fortunate enough to get constant encouragement, support and guidance
from our Parents, all Teaching staffs of BCA Department which helped us in successfully
completing our project work. Also, we would like to extend our sincere esteems to all staff in
laboratory for their timely support.

Diya Solanki 200510102018

2
 PARUL INSTITUTE OF COMPUTER APPLICATION
CERTIFICATE

This is to certify that DIYA SOLANKI the student(s) of Parul Institute of

Computer Application, has/have satisfactorily completed the project entitled
“ONLILNE FURNITURE SHOP MANAGEMENT SYSTEM” as a part of
course curriculum in B.Sc. IT semester-VI for the academic year 2022-2023
under guidance of Prof. VIJYA TULSANI.

200510102018 Diya Solanki

Quality of work Grade Sign of Internal guide

Poor / Average / B /B+ / A / A+

Good /
Excellent

Date of submission:
HOD, Principal,
Dr. Hina Chokshi Dr.Priya Swaminarayan

3
 INDEX

Content Pg. No.

1. Company Profile 6

2. Project Profile 7

2.1. Project Definition 7

2.2. Project Description 8

2.3. Existing / Legacy System 9

2.4. Problem Statements 9

2.5. Needs for New system 9

2.6. Proposed System 9

2.7. Scope 9

2.8. Outcomes 10

2.9. Tools &Technology used with short justification 10

2.10 Project Plan 10

3. Requirement Analysis 11

3.1 Feasibility Study 11

3.2 Users of the System 12

3.3 Modules of the System 12

3.4 Process Model 12

3.5 Hardware & Software Requirements 13

3.6 Use Cases 13

4
 3.7 Use Case Diagram 14

4. Design 15

4.1 Use Case Scenarios 15

4.2 Diagrams [Structured] 16

4.3 Diagrams [OOAD] 25

4.4 Entity Relationship Diagram 28

4.5 Data Dictionary 29

5. Implementation 33

5.1 Form Layouts 33

5.2 Page Layouts 35

6. Testing 38

6.1 Test Strategy 38

6.2 Test Cases 40

7. Future Enhancement 45 q

8. Bibliography 46

5
1. COMPANY PROFILE

6
 2. PROJECT PROFILE

2.1 PROJECT DEFINITION:

It is an online furniture shop management system that allows users to check various furniture
available at the online store and purchase online. The project provides a list of furniture
products displayed online in various models and designs. The user may browse through
products as per categories. If the user likes a product, he may add it to a shopping cart. User
must register on the site before checking out so that he can log in with the same id and
password next time. User can select any payment option that he wishes to like credit card or
cash on delivery. User receives a copy of the shopping receipt on his email id once the
transaction is successful. Here we use JavaScript for entire frontend and PHP for Backend
and MySQL for lists and inventory data. Thus, the online furniture shopping project brings an
entire furniture shop online and makes it easy for both buyer and seller to make furniture
deals.

7
2.2 PROJECT DESCRIPTION:
The home décor and furniture industry has a great potential to increase the trend of interior
designing and room décor with various themes, colour matching furniture, etc. Nowadays,
many people are looking for a perfect home décor accessory as per room designing needs.
Searching physically shop by shop is not feasible for the customers.
This project "online furniture shop management system" includes both user and admin.
Software used are web browser which supports HTML, CSS and HTML5 versions of
JavaScript. In designing it includes home page log in credentials for user and admin login
for admin. After log in to the admin page, the admin has to enter username and password.
Admin can see the total customers, Total bookings and Total products in which admin can
also manage the number of products to be added or deleted. The user can log in or sign up
from the home page. If user is new to the website, it has to be sign up and fill there
required details in the registration form. Categories of different products are available for
the user for add to cart, buy now and it also shows the total of the product. After adding
the product to the cart user can also have the option of continue shopping. Once the user
done with the shopping, he/she have to conform the booking details which includes
booking id and all other information including customer's name, phone number, email,
city, etc. Then the user has to choose the payment details as cash on delivery or payment
by card. In card payment the user has to fill the card details and then proceed to payment.
After placing the order, the admin can see the placed order and can also the change status
to in progress, delivering or delivered. At last, the customer can also fill the feedback form
as receiving the order of the customer.

8
2.3 EXISTING/LEGACY SYSTEM:
 Making more categorize so that user can find appropriate product.
 Notify the user about the delivery progress.
 Sends receipts to the customer.
 Add mailing and texting feature.

2.4 PROBLEM STATEMENTS:

 Trust issue if the delivery going to be late.
 Issue of payment when the payment is done with the credit card.
 Problem of receiving the online receipt of the buying products.

2.5 NEEDS FOR NEW SYSTEM:

 It will be easy for the customer to get the details of the product.
 It also acts as a medium between customer and the admin(seller).
 Latest deals and discount update through mail.
 Easy managing panel.
 Providing the better user interface.

2.6 PROPOSED SYSTEM:

 Emailing system should be updated.
 Updating to the customers regularly until they get their product delivered.
 Admin should be updated about every product and their description and prices.
 Will provide better discounts and schemes to the customers.

2.7 SCOPE:
 Will attract customers from a very far distance.
 Also make sure that they get delivered their product on time.
 Also make sure to gain customer’s trust in short period of time.

2.8 OUTCOMES:
 It will be ease to do shopping from the home itself.
 They do not have to go for many shops to buy products.
 Also, their time will save through this online portal.
 Admin also don’t have to give every detail about the product.

9
2.9 TOOLS AND TECHNOLOGY USED WITH SHORT
JUSTIFICATION:
2.9.1 HARDWARE:
 Edition: Windows 11
 Processor: 11th Gen Intel Core
 RAM: 8 GB
 System type: 64-bit OS
(Easier for project management.)
2.9.2 SOFTWARE:
 Frontend: JavaScript
 Backend: PHP
(It is simple and understandable with a rich interface. It is versatile and
popular.)

2.9.3 OTHER:
 MySQL (data storing), HTML, CSS
 MS Office, MS PowerPoint
(It will protect the data and stores a good amount of data with security.)

2.10 PROJECT PLAN:

 Make understandable system for the admin so that he can update, edit and
delete easily.
 Also make sure that the user can easily handle his/her login interface and
makes order and payment easily.

10
 3. REQUIREMENT ANALYSIS

3.1 FEASIBILITY STUDY:

Feasibility is an analysis of an idea through a disciplined and documented process of thinking
through the idea from its logical beginning to its logical end. It is canted out in order to assess
the viability of a new project. It is primary and important thing in development of a project.
 Technical Feasibility
 Economic Feasibility
 Operational Feasibility

3.1.1 Technical Feasibility: It helps organizations determine whether the technical

resources meet capacity and whether the technical team can convert the ideas into working
system. Technical feasibility also involves the evaluation of the hardware, software, and other
technical requirement of the proposed system.

3.1.2 Economic Feasibility: This assessment typically involves a cost and benefits
analysis of the project and benefits associated with a project before financial resources are
allocated. It also server’s enhance project credibility helping decision making, determine the
positive economic benefits to the organization that the proposed project will be provided.

3.1.3 Operational Feasibility: This assessment involves undertaking a study to analyze

and determine whether and how well the organization’s needs can be met by completing the
project. Operational feasibility studies also examine how a project plan satisfies the
requirement identified in the requirement analysis phase of system development.

3.2 USERS OF THE SYSTEM:

 Admin
 User

3.3 MODULES OF THE SYSTEM:

 Product Categories
 Cart
 Credit Card Payment
 Email confirmation
 Feedback

3.4 PROCESS MODEL:

11
  User Registration: User can register on the system and get online account on site
 User Log In: User can log in to system and check various furniture data online.
 Admin Log In: Admin can log in to Admin site and makes changes in the website
like update, delete, edit, add, etc.
 Product Categories: The furniture is arranged and can be viewed in categories.
 Cart: Users can add furniture products to cart.
 Credit Card Payment: After total bill is calculated user can pay via credit card
online.
 Email confirmation: On successful payment a thank you message is sent to user.
 Feedback: After completing the process and the product is delivered to the
customer the user gets the mail of feedback about their experience of buying product.

3.5 HARDWARE AND SOFTWARE REQUIREMENTS:

Hardware Components Specification
Processor Intel core I3,/I5
RAM 4GB/8GB
Hard disk 512GB/1TB
Monitor 15.6 colour monitor or advance
Device Keyboard, Mouse

Name of component Specification

Operating System windows10
Software development kit Version 1.0
Programming language PHP, XAMPP

3.6 USE CASES:

A use case diagram is a dynamic or behaviour diagram in UML. Use case diagrams model
the functionality of a system using actors and use cases. Use cases are a set of actions,
services, and functions that the system needs to perform. In this context, a "system" is
something being developed or operated, such as a web site.

3.7 USE CASE DIAGRAM:

12
Figure 3.7 Use Case Diagram

13
 4.DESIGN
4.1 USECASE SCENARIOS:
This is the Use Case Diagram of Online Furniture Shop management system, which shows
where the admin can login to the system and work on the home screen and add, edit, delete
and update the system. It will even allow the admin to see the order of the furniture and even
check the delivery statue. After all work of the admin would be able to logout as well.
The user panel would be able to login and see the home page and would be able to search for
different categories of furniture. The ordering process and the payment should be done
together where the admin have provided them with a feedback system so they can improve in
future and after all this process they can logout as well.

4.2 DIAGRAMS [STRUCTURED]:

4.2.1 DATA FLOW DIAGRAM:
4.2.1.1 LEVEL 0:

Fig. 4.2.1 DFD level 0

14
4.2.1.2 LEVEL 1(ADMIN SIDE):

Fig. 4.1.2.1 Level 1(admin side)

15
4.2.1.3 LEVEL 1(USER SIDE):

Fig. 4.2.1.3 Level 1(User side)

16
4.2.1.4 LEVEL 2(ADMIN SIDE):

Fig. 4.2.1.4 Level 2(admin side)

17
4.2.1.5 LEVEL 2(ADMIN SIDE):

Fig. 4.2.1.5 Level 2(admin side)

18
4.2.1.6 LEVEL 2(ADMIN SIDE):

Fig. 4.2.1.6 Level 2(admin side)

19
4.2.1.7 LEVEL 2(USER SIDE):

Fig. 4.2.1.7 Level 2(user side)

20
4.2.1.8 LEVEL 2(USER SIDE):

Fig. 4.2.1.8 Level 2(user side)

21
4.2.1.9 LEVEL 2(USER SIDE):

Fig 4.2.1.9 Level 2(user side)

22
4.2.3 FLOW CHART:

Fig.4.2.3 Flow Chart

23
4.3 DIAGRAMS [OOAD]:
4.3.1 CLASS DIAGRAM:

Fig. 4.3.1 Class Diagram

24
4.3.2 ACTIVITY DIAGRAM:
4.3.2.1 Admin side:

Fig. 4.3.2.1 Activity Diagram (admin side)

25
4.3.2.2 ACTIVITY DIAGRAM (user side)

Fig. 4.3.2.2 Activity Diagram (user side)

26
4.4 ENTITY RELATIONSHIP DIAGRAM:

Fig. 4.4 Entity Relationship Diagram

27
 4.5 DATA DICTIONARY
4.5.1 Table Name: Table Admin
Table Description: Admin personal details

Sr. Field Name Data Type Size Description Constraint Example

1 Id Int 11 Id of the admin Primary Key 1

2 Name Varchar 25 Name of the Not Null Admin

admin
3 Email Varchar 65 Admin email Foreign Key admin@ad
min.com
4 Password Varchar 20 Password for Not Null *******
Login
5 Create_date Time_stamp Current time Not Null 2022-12-18
stamp
6 Photo Varchar 200 Admin Image Not Null Admin.jpg

4.5.2 Table Name: Table Category

Table Description: Details about the category added in the website.
Sr.No Field Data Type Size Description Constraint Example
Name
1 Post_id Int 11 Id of post Foreign key 11
2 Name Varchar 50 Name of the Not Null Bedroom
Category Furniture
3 Cat_slug Varchar 20 Category Not Null Sofa
Name

28
4.5.3 Table Name: Table Cart
Table Description: Details of the product added in the cart
Sr. Field Name Data Size Description Constraint Example
No. Type
1 Id Int 10 Id of the category Primary key 10
2 User_id Int 11 Id of the user Default 9
3 Product_id Int 20 Id of the product Foreign Key 30

4.5.4 Table Name: Table Product

Table Description: Details of the Product and sales.
Sr. Field Name Data Siz Description Constraint Example
No. Type e

1 Id Int 10 Id of the Primary key 14

category
2 Sales_id Int 11 Id of the sales Default 9
3 Product_id Int 20 Id of the product Foreign Key 11
4 Quantity Int 20 Quantity of the Not Null 2
product
5 Stalk Int 10 Total Stalk Not Null 30
6 Amount Int 7 Rate of the Not Null Rs.27,000
products
7 Photo Varchar 200 Product Image Not Null chair.jpg

4.5.5 Table Name: Table Payment

Table Description: Details of the Payment.
Sr.No. Field Name Data Size Description Constrain Example
Type t
1 Sales_id Int 11 Id of the Primary 9
category key
2 User_id Int 11 Id of the user Default 9
3 Pay_id Int 20 Id of the Foreign 1KDFLLJF
payment Key H987698348
4 Name Varchar 50 Name of the Not Null Bedroom
Product Furniture
5 Product_id Int 25 Id of the Foreign 11
products Key
6 Address Varchar 100 Address of the Not Null Parul
user Universirty,
Vadodara,
Gujurat
4.5.6 Table Name: Table Sales
29
Table Description: Details of the sales.
Sr.No. Field Name Data Size Description Constrain Example
Type t
1 Sales_Id Int 11 Id of the Primary 9
category key
2 User_id Int 11 Id of the user Default 9
3 Pay_id Int 20 Id of the Foreign 1KDFLLJF
payment Key H987698348
4 Product_id Int 25 Id of the Foreign 11
products Key
5 Name Varchar 50 Name of the Not Null Bedroom
Product Furniture
6 Sales_date date Sale date Not null 2023-01-01
7 Amount Int 7 Total amount of Not Null Rs.1,50,000
ordered product
8 Quantity Int 20 Quantity of the Not Null 3
products
ordered
9 Address Varchar 100 Address of the Not Null Parul
user Universirty,
Vadodara,
Gujarat.

30
4.5.7 Table Name: Table User
Table Description: User personal details
Sr. Field Name Data Type Size Description Constraint Example
No.
1 Id Int 11 Id of the Primary key 1
admin
2 Name Varchar 25 Name of the Not null Diya
admin solanki
3 Email Varchar 65 Admin email Not null Diya@12
3
4 Password Varchar 20 Password for Not null *******
log in *
5 Create_date Time_Stamp Current Not null 2023-01-
TimeStamp 25
6 Photo Varchar 200 Admin image Not null Female1.
jpg
7 Address Varchar 100 Address of the Not null Surat,guj
user
8 Contact no. Varchar 20 Users contact Not null 9876543
number 210

31
 5. IMPLEMENTATION
5.1 Form Layouts
5.1.1 Log In Page:

F
ig. 5.1.1 Log In Page

32
Fig. 5.1.2 Registration Page

33
5.2 Page Layouts
5.2.1 Home Page:

Fig: 5.2.1 Page Layout (Home Page)

Fig. 5.2.2 Page Layout(About Us)

34
Fig: 5.2.3 Page Layout(Contact Us)

Fig. 5.2.4 Page Layout(Category)

35
 Fig. 5.2.5 Page Layout(Search)

Fig. 5.2.6 Page Layout(admin side)

36
 Fi
g. 5.2.7 Page Layout (Category List)

Fig. 5.2.8 Page Layout (Product List)

37
Fig. : 5.2.9 Page Layout(subscriber and social media)

Fig. : 5.2.10 Page Layout (Cart)

38
 Fig. : 5.2.11 Page Layout(Users)

Fig.: 5.2.12 Page Layout(sales history)

39
 6. TESTING
6.1 Test Strategy
A test strategy is an outline that describes the testing approach of the software development
cycle. The purpose of a test strategy is to provide a rational deduction from organizational,
high-level objectives to actual test activities to meet those objectives from a quality assurance
perspective.

Types of testing strategies:

 Analytical strategy: An analytical strategy specifies the long term decisions an
organisation makes about how it uses its data to take actions that satisfy its
organizational vision and mission; specifically, the selection of analytic opportunities
by an organization and the integration of its analytic operations, analytic infrastructure
and analytic models to achieve its mission and vision.
 Model based strategy: Model based testing is a testing technique where run time
behaviour of a software under test is checked against predictions made by a formal
specification or model. In other means, it describes how system behaves in response
to an action (determined by a model). Supply action, and see, if the system responds
as per the expectation.
 Methodical strategy: The testing module approach also contains the change
management process involving the modification request submission, pattern to be
used and activity to manage the request.
 Standards complaint or Process complaint strategy: The complete complaint
management process is conducive to achieving two goals that is customer satisfaction
is supposed to reduce customer dissatisfaction and ideally even strengthen customer
loyalty.
 Reactive strategy: Reactive Test Strategy A test strategy whereby the test team waits
to design and implement tests until the software is received, reacting to the actual
system under test.
 Consultative strategy: Consultative strategy As the name suggests, this testing
technique uses consultations from key stake holders as input to decide the scope of
test conditions as in the case of user directed testing. Let us consider a situation where
the compatibility of any web based application with possible browsers is to be tested.
 Regression averse strategy: Regression-averse testing strategies (such as extensive
automation) Motivated by a desire to avoid regression of existing capabilities.
Includes reuse of existing test-ware (especially test cases and test data), extensive
automation of regression tests and standard test suites.

40
6.2 Test Cases
Project Name: Online Furniture Shop Management System

6.2.1 Module 1(Log in)

Test Case ID: TC_OFSMS_001
Test Case Description: Verify the login Functionality of Customer and Admin Log In.
Pre-Conditions: Valid URL test data.
Post-Condition: User should see the home page.
Test Steps: Description: Expected Actual Status: Input:
Results: Status:
1.Enter Valid Enter the Successful As Pass Username:
Username Valid result Expected Admin@admin.c
2. Enter Valid Username and om
Password password Password:
3. Click on Log In password
Button

41
Test Case ID: TC_OFSMS_002
Test Case Description: Verify the Log In Functionality of Customer and Admin Log In.
Pre-Conditions: Valid URL test data.
Post Conditions: Error message “invalid username and invalid password”
Test Steps: Description: Expected Actual Status Input:
Results: Status: :
1.Enter Valid Enter the A popup Invalid Fail Username:
username valid message to status admin@123.com
2. Enter invalid username and show an Password:
password invalid error password12
3. Click on Log password
In Button

Test Case ID: TC_OFSMS_003

Test Case Description: Verify the Log In Functionality of Customer and Admin Log In.
Pre-Conditions: Valid URL test data.
Post Conditions: Error message “invalid password”
Test Steps: Description: Expected Actual Status: Input:
Results: Status:
1.Enter Valid Enter the A popup Invalid Fail Username:
username valid message to status Admin@admin.
2. Enter invalid username show an Of password com
password and invalid error Password:
3. Click on Log password password
In Button

42
Test Case ID: TC_OFSMS_003
Test Case Description: Verify the Log In Functionality of Customer and Admin Log In.
Pre-Conditions: Valid URL test data.
Post Conditions: Error message “invalid password”
Test Strategy: Description: Expected Actual Status: Input:
Results: Status:
1.Enter Valid Enter the A popup Invalid Fail Username:
username valid message to status Admin@admin.
2. Enter invalid username and show an Of com
password invalid error password Password:
3. Click on Log password password
In Button

6.2.2 Module 2(Log Out):

Test Case ID: TC_OFSMS_001
Test Case Description: Verify the Log out Functionality of Customer and Admin Log out.
Pre-Conditions: Valid URL test data.
Post Conditions: User should see the home page.
Test Strategy: Description: Expected Actual Status: Input:
Results: Status:
Click on Log Clicking the Successful As Pass Username:
Out Button log out button result Expected Admin@admin.co
m
Password:
password

43
6.2.3 Module 3(Online Payment):
Test Case ID: TC_OFSMS_001
Test Case Description: Submitting the payment by clicking on the submit.
Pre-Conditions: Sender log in and pay
Post Conditions: User should be able to do the payment after log in.
Test Strategy: Description: Expected Actual Status: Input:
Results: Status:
1.Enter Valid Enter the Successful As Pass Username:
username and valid result Expected Admin@admi
password username and n.com
2. Check the cart invalid Password:
to do they process password. password
3. Then click on Give the
the payment payment
button. according to
4. Give the bank the total
details and then
pay.

44
 7. FUTURE ENHANCEMENT

The future scope of our project we can give more advance software for this website
more facility. This project time duration was only six months. In this interval we developed
our project. In future if we get chance we will develop this website for large volume. As for
other future developments we regularly update our databases. More than that sensibility level
could be added and also will provide more proper online transaction. Lastly, we make sure
That it makes a secure delivery.

45
 9. BIBLIOGRAPHY

Website:
1. www.w3schools.com
2. www.codecademy.com

Book:
1. PHP and MYSQL by Laura Thomson
2. Learning PHP high performance by Altaf Hussain
3. Learning PHP, MySQL, JavaScript, CSS and HTML: A Step-by-Step Guide to
Creating Dynamic Website- Nixon Robin

Other Resources:
1. www.Freecodecamp.org
2. www.udemy.com

46