SHREE SWAMINARYAN COLLEGE OF COMPUTER SCIENCE

(Affiliated to M. k. Bhavnagar University)

GURUKUL CAMPUS, SARDARNAGAR, BHAVNAGAR-364001

House of Jewellery
PREPARED BY :
JAY JASANI [ 25260086 ]
JEM JETANI [ 25260094 ]

GUIDED BY :
NIRAV DAVE

SUBMITTED TO :
SHREE SWAMINARAYAN COLLEGE OF COMPUTER SCIENCE

FOR DEGREE OF :
BCA
 TABLE OF CONTAIN
1. INTRODUCTION :
1.1 Background
1.2 Objective
1.3 Purpose and Scope

2. REQUIREMENT :
2.1 Hardware and Software Requirement

3. SYSTEM DESIGN :
3.1 Data Flow Diagram
3.2 ER Diagram
3.3 Data Dictionary

4. INPUT / OUTPUT DESIGN

5. TESTING :
5.1 Introduction
5.2 Tast Case

6. CONCLUSION :
6.1 Limitation of system
6.2 Future Enhancement

7. BIBLIOGRAPHY
 1.INTRODUCTIO
N
1.1 Background :

 Jewellery is used in whole world and part of most of the cultures.

 House of jewellery is website which helps the seller to sell and advertise their jewellery as well as people to find
and buy latest design jewellery with different categories like Gold, Silver, Diamond, platinum.

 We are developing “HOJ” a project to providing solution of such issues that will be arise in our day to day life.

 A website where people can get easily search to jewellery according to their choice of favourite style and they can
inquiry as well easily.

1.2 Objective :

 The main objective of this project is to develop an interactive and dynamic website that provides the customer with
an on-the-click functionality to search for their desired products over a wide range of jewellery products and buy them
easily and at any time according to the user’s convenience.
  Features & functionality:

 To shop online in the comfort of your home, without having to step out of the door.

 To be able to easily save money and compare prices from website to website and Explore jewellery.

 Search and categorizes jewellery like men & women.

1.3 Purpose and Scope :

 According to report of IBEF ,As of February 2021, India's gold and diamond trade contributed ~7.5% to India's
Gross Domestic Product (GDP) and 14% to India's total merchandise exports. The gem and jewellery sector is
likely to employ ~8.23 million persons by 2022, from ~5 million in 2020.

 So that we develop “House of jewellery” it is facilitates user by providing an easy search mechanism to search his
desired product on the basis of product name, category and brand.

 The scope of this system is to provide user comfortable environment of Purchasing and selling products and services
over the internet without the need of going physically to the market is what online shopping all about.
 2. REQUIREMENT :
2.1 Hardware and Software Requirement :

i. Hardware :

Component Requirement
Processor Core to due OR Upgraded
RAM 1 GB
HDD space 512 MB
System type 64 bit OS al

ii. Software :

 SERVER : XAMMP

 EDITOR : Notepad/Notepad++

 OS : Windows 7 or Upgrade
 3. SYSTEM DESIGN :

3.1 Data Flow Diagram[DFD] :

Context Level DFD

First Level DFD for Admin
 Second Level DFD for Admin

Admin 2st Level Diagram (Process 3) Admin 2st Level Diagram (Process 4)
First Level DFD for User :
 Second Level DFD for User

User 2st Level Diagram (Process 4)

User 2st Level Diagram (Process 5)
 3.2 ER Diagram :

 Relationship :-
 A relationship is represented by diamond shape in ER diagram; it shows the relationship among entities.
There are four types of relationships.

There are several notation systems, which are similar but vary in a few specifics.

a) One to One relationship

b) One to Many relationship

c) Many to one relationship

d) Many to Many relationship

A) One to One relationship :

 In this type of relationship one entity depend on another only one entity. And it is rarely seen in real world. Such as one
student depend on one particular course.

B) One to Many relationship :

 In this type of relationship ONE entity depend on many entities. Such as one student depend on many another faculties.
C) Many to one relationship :-

In this type of relationship many entities depend on other only one entity. Such as many faculties depend on one principle
or head.

D) Many to Many relationship :-

 In this type of relationship MANY entities depend on other many entities.

ER Diagram
3.3 Data Dictionary :

Table 1: Product :

sr
Field name Datatype Size Constraint Description
no
1 Product_id Int 4 Primary Key Auto Increment of ID

2 Product_cat Varchar 15 Not NULL To Store Product Category

3 Product_title Varchar 25 Not NULL To Store Product title

4 Product_price Int 7 Not NULL To Store Product Price

5 Product_desc Text - Not NULL To Store Product Descripiton

6 Product_img Text - Not NULL To Store Product Image

7 Product_keywords Text - Not NULL To Store Product Keyword For Search

 Table 2: Admin_info :

sr
Field name Datatype Size Constraint Description
no
1 Admin_id Int 3 Primary Key Auto Increment of ID

2 Admin_name Varchar 25 Not NULL To Store Name ofAdmin

3 Email Varchar 30 Not NULL To Store E-mail ofAdmin

4 Password Varchar 25 Not NULL To Store Password ofAdmin

 Table 3: User_info :

sr
Field name Datatype Size Constraint Description
no
1 User_id Int 4 Primary Key Auto Increment of ID

2 First_name Varchar 25 Not NULL To Store First Name of Use

3 Last_name Varchar 20 Not NULL To Store Last Name of User

4 Email Varchar 30 Not NULL To Store E-mail address of User

5 Password Varchar 25 Not NULL To Store Password of User

6 Mobile Varchar 10 Not NULL To User Mobile number

7 Address1 Varchar 100 Not NULL To Store Address of User

8 Address2 Varchar 100 - To Store Other Address of User

 Table 4: Order products :

sr
Field name Datatype Size Constraint Description
no
1 Order_pro_id Int 4 Primary Key Auto Increment of ID

2 Order_id int 10 Foreign Key To Store order ID

3 Product_id int 10 Foreign Key To Store Product ID

4 Qty int 3 Not NULL To Store Quantity of Product

5 Amt int 7 Not NULL To Store Amount of Product

 Table 5: Order_info :

sr no Field name Datatype Size Constraint Description

1 Order_id Int 4 Primary Key Auto Increment of ID
2 User_id Int 10 Foreign Key To Store User ID
3 F_name Varchar 25 Not NULL To Store First Name of User
4 Email Varchar 30 Not NULL To Store E-mail Address of User
5 Address Varchar 100 Not NULL To Store Address of User
6 City Varchar 20 Not NULL To Store City of User
7 State Varchar 20 Not NULL To Store State of User
8 Zip Int 6 Not NULL To Store Pincode of User
9 Cardname Varchar 30 Not NULL To Store Card Name
10 Cardnumber Varchar 16 Not NULL To Store Card Number
11 expdate datetime - Not NULL To Store Card Expiry date
12 Product_count Int 3 Not NULL To Store Product Counting Number of User
13 Total_amt Int 7 Not NULL To Store Total Amount of User

14 Cvv Int 3 Not NULL To Store CVV number of Card

 Table 6: Category :

sr
Field name Datatype Size Constraint Description
no
1 Cat_id Int 2 Primary Key Auto Increment of ID

2 Cat_title Varchar 25 Not NULL To Store Category Title

 Table 7: Cart :

sr
Field name Datatype Size Constraint Description
no
1 Id Int 4 Primary Key Auto Increment of ID

2 User_id int 10 Foreign Key To Stores User ID

3 Product_id int 10 Foreign Key To Stores Product ID

4 Qty int 3 Not NULL To Stores Product Quantity

5 Ip_add Varchar 30 - To Stores Ip Address

 Table 8 : User_info_backup :

sr
Field name Datatype Size Constraint Description
no
1 User_id Int 4 Primary Key Auto Increment of ID

2 First_name Varchar 25 Not NULL To Store First Name of Use

3 Last_name Varchar 20 Not NULL To Store Last Name of User

4 Email Varchar 30 Not NULL To Store E-mail address of User

5 Password Varchar 25 Not NULL To Store Password of User

6 Mobile Varchar 10 Not NULL To User Mobile number

7 Address1 Varchar 100 Not NULL To Store Address of User

8 Address2 Varchar 100 - To Store Other Address of User

 4. INPUT / OUTPUT DESIGN :

Input Design :

Registration_Form
Login_Form
Cart _Menu
Checkout
Payment
Add_User
Add_Product
Edit_User
Edit_Product
Output Design :

Admin_Dashboard
Manage Product
Manage_User
Home page
Footer
Catogory
 5. TESTING :

5.1 Introduction :

Software Testing is a method to check whether the actual software product matches expected requirements and to ensure
that software product is Defect free.

It involves execution of software/system components using manual or automated tools to evaluate one or more properties
of interest.

The purpose of software testing is to identify errors, gaps or missing requirements in contrast to actual requirements.

Errors can be present in the software due to the following reason :

 Programming errors :

 Programmers can make mistakes while developing the source code.

 Unclear requirements :

 The user is not clear about the desired requirements or the developers are unable to understand the user requirements in a
clear and concise Manner.
 Software complexity :

 The greater the complexity of the software, the more the scope of committing an error (especially by an inexperienced
developer)

 Changing requirements :

 The users usually keep on changing their requirements, and it becomes difficult to handle such changes in the later stage
of development process. Therefore, there are chances of making mistakes while incorporating these changes in the software.

 Time pressures :

 Maintaining schedule of software projects is difficult. When deadlines are not met, the attempt to speed up the work
causes errors.

 Poorly documented code :

 If the code is not well documented or well written, then maintaining and modifying it becomes difficult. This causes
errors to occur.
5.2 Tast Case :

A. Test Case 1: Login

Test Case ID 1

Test Case Name Verify Login

Definition Enter Valid username and Valid Password

pre- Condition Need a Valid username and Password to do Login

1. Enter Username
Test Steps 2.Enter Password
3.Click Login

Test Data Valid username and Valid Password

Expected Result Successful Login, Main Screen of Application should Display

Actual Result Successful Login, Main Screen of Application Display

Status Pass/Fail Pass

Test Case ID 2

Test Case Name Verify Login

Definition Enter Valid username and InValid Password

pre- Condition Need a Valid username and Password to do Login

1. Enter Username
Test Steps 2.Enter Password
3.Click Login

Test Data Valid username and Invalid Password

Expected Result No Matched Username/ Password

Actual Result No Matched Username/ Password

Status Pass/Fail Pass

Test Case ID 3

Test Case Name Verify Login

Definition Enter Invalid username and valid password

pre- Condition Need a Valid username and Password to do Login

1. Enter Username
Test Steps 2.Enter Password
3.Click Login

Test Data Invalid username Valid Password

Expected Result No Matched Username/ Password

Actual Result No Matched Username/ Password

Status Pass/Fail Pass

Test Case ID 4

Test Case Name Verify Login

Definition Enter Invalid username and Invalid password

pre- Condition Need a Valid username and Password to do Login

1. Enter Username
Test Steps 2.Enter Password
3.Click Login

Test Data Invalid username InValid Password

Expected Result No Matched Username/ Password

Actual Result No Matched Username/ Password

Status Pass/Fail Pass

 B. Test Case 2: User Registration

Test Case ID 1

Test Case Name Verify User Registration Detail

Definition Enter valid name, email, new password

pre- Condition Need valid Data to be entered

1. Enter name
2. Enter email
Test Steps
3. Enter Password
4. Click Sign up

Test Data Valid name, valid email, valid password

Expected Result uccessful, User Added Successfully

Actual Result uccessful, User Added Successfully

Status Pass/Fail Pass

Test Case ID 2

Test Case Name Verify User Registration Detail

Definition Entering Nothing, Required Fields are blank

pre- Condition -

Test Steps Click Sign up

Test Data Nothing to enter Required fields are blank

Expected Result Fill required field

Actual Result Fill required field

Status Pass/Fail Pass

Test Case ID 3

Test Case Name Verify User Registration Detail

enter name, already registered email, new
Definition
password
pre- Condition Need Data to be entered

1. Enter name
2. Enter email
Test Steps
3. Enter Password
4. Click Sign up
Valid name, already registered email, valid
Test Data
password

Expected Result Email ID Already Registered

Actual Result Email ID Already Registered

Status Pass/Fail Pass

 C. Test Case 3: Add product

Test Case ID 1

Test Case Name Verify product Detail

Definition Enter valid and correct data

pre- Condition Need valid text and number Data to be entered

1. Enter Valid Data in appropriate fields

Test Steps
2. Click Submit

Test Data Valid Text and Number Data

Expected Result Successful, Product Added Successfull

Actual Result Successful, Product Added Successfull

Status Pass/Fail Pass

Test Case ID 2

Test Case Name Verify product Detail

Definition Enter invalid and incorrect data

pre- Condition Need text and number Data to be entered

Test Steps Enter invalid Data in fields

Test Data Invalid Text and Number Data

Expected Result Enter Valid Data

Actual Result Enter Valid Data

Status Pass/Fail Pass

Test Case ID 3

Test Case Name Verify product Detail

Definition Entering Nothing, image Required Fields are blank

pre- Condition -

Test Steps Click Submit

Test Data Nothing to enter, Required fields are blank

Expected Result Fill required Field, Image must be select

Actual Result Fill required Field, Image must be select

Status Pass/Fail Pass

 6. CONCLUSION :

6.1 Limitation of system :

 Any system will never complete always there is a chance of improving it. it is because of many reasons for example, due
to lack of technologies or current requirement of user is limited and much more.

 As the current environment there is always need for the new demands or requirement emerge so that is why the system
which is today looking complete, in future may incompletely need to expand features and technology.

 6.2 Future enhancements :

 Multilingual support can be provided so that it can be understandable by the person of any language.

 More graphics can be added to make it more user-friendly and understandable.

 Admin side Manage & backup versions of documents online.

 Live jewellery rate of international market.

 Provide facility chat boat and E-bill for better utilization of system.

 Visiter book appoinment and video call facility.

 7. BIBLIOGRAPHY :

 Visited websites :

 www.stackoverflow.com

 www.getbootstrap.com

 www.fontawesome.com

 www.w3schools.com

 www.tutorialspoint.com

 BOOK :

 - The complete reference PHP

 - MySQL/PHP database application