Arbaminch University

E-Commerce management system

Department of Software Engineering

Course title : Introduction to DataBase

Individual Assignment
Name – Tekletsadik Aknaw
Id - NSR/2273/12

Submitted to – Amin
Submission date
 Contents

Introduction ------------------------------------------------------------------ ------1

Project Objective-------------------------------------------------------------------1
Scope --------------------------------------------------------------------------------1
Conceptual design -----------------------------------------------------------------2
Relationship sentence ------------------------------------------------------------ 2
Cardinality--------------------------------------------------------------------------3
Degree of Relationship -----------------------------------------------------------5
ER- Diagram -----------------------------------------------------------------------7
Meta Data and Constraints- ------------------------------------------------------8
 Introduction
In order to begin the process of drawing the ERD, I took some time to go around the Amazon
website. In order to make sure that I understood who the players were (buyers, sellers and
everything in between) but more importantly how each entity reacts with one another.
Dividing the ERD in terms of similar “actions/events” made more sense to us and helped us
comprehend further the matter at hand. I believe that I have maintained the data integrity while
keeping a clear and concise format to help the querying flow more efficiently.

Project Objective
To develop ERD for an easily Operative and user friendly, accurate, reliable and consistent system.
This would assure economic use of storage space consistency of the data stored.

Scope
The Scope of the E-commerce System Database is in accordance to the following perspectives:
 Basic Customer and Sellers Information [Name, phone_no, Email, Address……]
 Products with in categories for customer and managerial report.
 Transactions Proceeded for the products
 Delivery to the address of customer.
 Conceptual Design

Following the above specifications, the project will be clearly put as an Enhanced (Extended) Entity
Relationship Diagram to portray the Conceptual Design of E_ commerce system. For consistency,
each data group (mentioned in Scope above) is defined as a group of related data tables.
 CUSTOMER: The Customer Entity contains basic information about the patient
including Name, email and Address. It is related with Payment, Marketing Manager,
Wish list, and Cart.
 MARKETING MANAGER: The Marketing Manager Entity has both sellers and
customers information that is required for generating reports, taking actions and
managing orders for each customers who has paid transaction thus having a
“Manages of” relation with the customer and sellers entity.
 CARIER: the Carrier Entity contains basic information about a carrier i.e., Name,
carrier ID, Address and customers address to provide delivery.

 PAYMENT: Is the relationship between Customer Entity and Cart Entity. It provides
information on transaction process.

Relationship sentence
 One customer may be making one or more payments
 The payments could be made for the cart which is made of cart item and contains product
 One customer may add wish list as desired
 Marketing manager may manage many customer and seller information’s.
 The products are categorized.
Cardinalities

1:N

1:N

1:N

1:1

1:N

1:N
 1:1

1:N

` N:M

1:N

N:M

N:1
Degree of Relationship

Ternary Relationship (degree 3)

Binary Relationship
(Degree -2 )

Binary Relationship
(Degree -2 )
Binary Relationship
(Degree -2 )
 Binary Relationship
(Degree -2 )

Binary Relationship (Degree -2 )

Binary Relationship
(Degree -2 )

Binary Relationship
(Degree -2 )

Binary Relationship
(Degree -2

`
ER_ Diagram for E-Commerce system
Constraints and Meta Data
Table: Customer
 Cust_Id INT PRIMARY KEY NOT NULL
 first_name VARCHAR (50)
 last_name VARCHAR (50)
 phone_no VARCHAR (50)
 address VARCHAR (50)
Table: Payment
 payment_Id INT PRIMARY KEY
 Cust_Id INT FOREIGN KEY
 Order_Id INT FOREIGN KEY
 bill address VARCHAR (50)
 pay_date VARCHAR(50)
 total_amount MONEY
 pay_method VARCHAR(50)
Table: cart
 Order_ID PRIMARY KEY
Table: cart_item
 qty_wished VARCHAR(50)
 purchased VARCHAR (50)
 date_added VARCHAR (50)
Table: products
 product_Id INT PRIMARY KEY
 name VARCHAR (100)
 description VARCHAR(50)
 Price MONEY
 size MONEY
 available_unit INT
Table: catagories
 category_Id INT PRIMARY KEY
 category_name VARCHAR(50)
Table: carrier
 Carier_Id INT PRIMAR KEY
 Carrier_name VARCHAR (50)
 Carrier_email VARCHAR (50)
 Carrier_phone_no VARCHAR(50)

Table: sellers
 sellers_Id INT PRIMAR KEY
 sellers_name VARCHAR (50)
 sellers_address VARCHAR (50)
 sellers_phone_no VARCHAR(50)
 Table: marketing_manager
 manager_Id INT PRIMARY KEY
 sellers_Id INT FOREIGN KEY
 cust_Id INT FOREIGN KEY
 manager_name VARCHAR (50)
 manager_email VARCHAR (50)