Scribd
Upload
15 views

Dbms C

The document describes the development of an e-commerce website project submitted by three students. It includes an introduction describing the purpose and features of the online shopping system. It also includes entity relationship diagrams and examples of SQL queries for implementing the database tables.

Uploaded by

anilvs2004
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
15 views

Dbms C

The document describes the development of an e-commerce website project submitted by three students. It includes an introduction describing the purpose and features of the online shopping system. It also includes entity relationship diagrams and examples of SQL queries for implementing the database tables.

Uploaded by

anilvs2004
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

SCHOOL OF ENGINEERING AND TECHNOLOGY

DATABASE MANAGEMENT SYSTEM REPORT ON

“E-COMMERCE WBSITE DEVOLPMENT ”

Submitted in partial fulfilment of the requirements for the award of degree


in

BACHELOR OF TECHNOLOGY

IN
COMPUTER SCIENCE AND ENGINEERING

SUBMITTED BY-

ANILA VS-22BBTCS028
ABHISHEK MT-22BBTCS00d8
AKASH A-22BBTCS019

Dr. Kalyan Nagraj


Assist.Professor of CSE Dept
SOET, CMRU, Bengaluru.

Department of Computer Science and Engineering


Off Hennur - Bagalur Main Road,
6Near Kempegowda International Airport, Chagalahatti, Bangalore, Karnataka-562149

SCHOOL OF ENGINEERING AND TECHOLOGY


Chagalahatti, Bengaluru, Karnataka-562149

Department of Computer Science and Engineering

CERTIFICATE

Certified that the Project Work entitled ANILA VS,ABHISHEM MT,AKASH


A bonafide students of SCHOOL OF ENGINEERING AND
TECHNOLOGY, in partial fulfillment for the award of BACHELOR OF
TECHNOLOGY in Computer Science and Engineering of CMR
UNIVERSITY, Bengaluru for 4th Semester course 4CSGC2021 –
DATABASE MANAGEMENT SYSTEM during the academic year 2024 -
2025. It is certified that all corrections/suggestions indicated for the Internal
Assessment have been incorporated in the report. The project has been approved
as it satisfies the academic requirements in respect of project work prescribed
for the said degree.

Signature of course In-charge Signature of HOD

……………………… …………………..

Dept.of CSE Dept.of CSE


SOET,CMRU,Bengalore SOET,CMRU,Bengalore

Name of the Examiners: Signature with


Date

1…………………….. …………………
……
2…………………….. …………………
……

DECLARATION

We, ANILA VS( USN 22BBTCS028)ABHISHEK MT(22BBTCS008)


AKASH A(22BBTCS019) bering students of Bachelor of Technology, Computer
Science and Engineering, CMR University, Bengaluru, hereby declare that the
Project Work entitled “ONLINE SHOPPING SYSTEM” submitted by us, for the
award of the Bachelor’s degree in Computer Science and Engineering to CMR
University is a record of bonafide work carried out independently by us under the
supervision and guidance of Dr. Kalyan Nagraj Assint.Professor Dept of CSE,
CMR University. We further declare that the work reported in this mini project
work has not been submitted and will not be submitted, either in part or in full, for
the award of any other degree in this university or any other institute or University.

Place: Bengaluru ANILA VS


(22BBTCS028)

ABHISHEK MT
(22BBTCS008)
Date:

AKASH A

(22BBTCS019)
INTRODUCTION
E-COMMERCE WBSITE DEVOLPMENT :

In the era of digitalization, online shopping has become an integral part of


everyday life for consumers worldwide. The convenience of browsing and
purchasing products from the comfort of one's own home has revolutionized the retail
industry. To meet the growing demand and provide a seamless shopping experience,
the development of efficient and robust online shopping systems is essential.

The Online Shopping System is a comprehensive e-commerce platform designed


to facilitate the buying and selling of goods and services over the internet. This project
aims to create a dynamic and user-friendly online marketplace that connects
consumers with vendors, offering a wide range of products across various categories

The Online Shopping System of its backbone is database, which stores and
organizes all relevant data efficiently. The database schema composed tables for
customer, products, orders, payments, reviews, catagory and administrative
functions. Relationships between these entities are established to ensure data
integrity and optimize system performance.
ER DIAGRAM :
SAMPLE QUERIES:
Table Creations:

ORDER;
CREATE TABLE orders (
order_id NUMBER PRIMARY KEY,
product_name VARCHAR2(100)
)

USER;
CREATE TABLE users (
user_id NUMBER PRIMARY
KEY, user_name
VARCHAR2(100),
user_address VARCHAR2(255)
)
CART;
CREATE TABLE cart ( cart_id
NUMBER PRIMARY KEY,
user_name VARCHAR2(100),
product_name
VARCHAR2(100)
)

Product:
CREATE TABLE product (
product_id NUMBER PRIMARY
KEY, product_category
VARCHAR2(100),
product_name VARCHAR2(100),
product_price NUMBER,
product_brand VARCHAR2(100)
)

ITEM_PURCAHSED;
CREATE TABLE item_purchased (
ref_no NUMBER PRIMARY KEY,
user_name VARCHAR2(100),
product_name VARCHAR2(100),
price NUMBER, purchase_date
DATE
)

PRODUCT AND ORDER;

INSERT INTO rerupts (rerupt_id, product_id, order_id)


SELECT
ROW_NUMBER() OVER (ORDER BY p.product_id, o.order_id) AS
rerupt_id, p.product_id, o.order_id FROM
product p
JOIN
orders o ON p.product_name = o.product_name
ORDER AND USER; CREATE
TABLE attr ( attr_id
NUMBER PRIMARY KEY,
user_id NUMBER, order_id
NUMBER,
FOREIGN KEY (user_id) REFERENCES users(user_id),
FOREIGN KEY (order_id) REFERENCES orders(order_id)
)

PURCAHSED AND CART;


INSERT INTO purchased (purchase_id, cart_id, order_id, user_name, product_name)
SELECT
ROW_NUMBER() OVER (ORDER BY c.cart_id, o.order_id) AS purchase_id,
c.cart_id,
o.order_id,
c.user_name,
o.product_name
FROM cart c
JOIN orders o ON c.product_name = o.product_name

USEFUL SQL QUERIES;

DESCENDING ORDER;
ASCENDING ORDER

NORMALIZATION:
Table ORDERS

1NF (First Normal Form):


To ensure 1NF, each column in the table must contain values, and each column must contain only a
single value per record.

2NF (Second Normal Form):

To achieve 2NF, a table must first satisfy 1NF, and then all non-key attributes must be fully
functional dependent on the primary key. In simpler terms, all attributes must rely on the
entire primary key, not on a part of it
3NF (Third Normal Form):

To achieve 3NF, a table must first satisfy 2NF, and then it must ensure that there are no transitive
dependencies; that is, no non-key attribute should depend on another non-key attribute.The original
table is already in 3NF because there are no transitive dependencies. Each non-key attribute
(product_name) depends directly on the primary key (order_id)

Table USER;

CART;
1NF (First Normal Form):
In the first normal form, each column should contain atomic values, meaning no column should have
multiple values or repeating groups. The table is already in 1NF since each column contains atomic
values.

2NF (Second Normal Form):


In the second normal form, every non-prime attribute (attributes not part of the primary key)
should be fully functionally dependent on the entire primary key. Since all attributes depend on the
primary key this table is already in 2NF.

3NF (Third Normal Form):


In the third normal form, there should be no transitive dependencies. ". Therefore, the table is already
in 3NF
PRODUCT
1NF (First Normal Form):
In the first normal form, each column should contain atomic values, meaning no column should have
multiple values or repeating groups. The table is already in 1NF since each column contains atomic
values.

2NF (Second Normal Form):


In the second normal form, every non-prime attribute (attributes not part of the primary key) should be
fully functionally dependent on the entire primary key. Since all attributes depend on the composite
primary key , this table is already in 2NF.

3NF (Third Normal Form):


the third normal form, there should be no transitive dependencies. ". Therefore, the table is already in
3NF
ITEM PURCHASED

1NF (First Normal Form):


In the first normal form, each column should contain atomic values, meaning no column should have
multiple values or repeating groups. The table is already in 1NF since each column contains atomic
values.
2NF (Second Normal Form):
In the second normal form, every non-prime attribute (attributes not part of the primary key) should be
fully functionally dependent on the entire primary key. Since all attributes depend on the primary key
(productId), this table is already in 2NF.
3NF (Third Normal Form):
In the third normal form, there should be no transitive dependencies. columns are directly related to
the product and do not cause transitive dependencies. Therefore, the table is already in 3NF.

You might also like