Rashtreeya Sikshana Samithi Trust

R. V. COLLEGE OF ENGINEERING
[Autonomous Institution Affiliated to VTU, Belagavi]
Bengaluru-560059

DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING
DATABASE MANAGEMENT SYSTEM (LAB)
PROJECT TOPIC: E-COMMERCE DATABASE MANAGEMENT SYSTEM

TEAM MEMBERS:
VANSH GOEL 1RV22CS223
VIJAYSHREE V M 1RV22CS232
YASH LOHIA 1RV22CS237
 1.INTRODUCTION
The E-commerce Database Management System project is designed to efficiently manage and analyze transactional
and operational data for online retail platforms. It incorporates key entities such as Order IDs, date of sale, order
status, fulfilment processes, sales figures, sales channels, shipping service levels, SKU (Stock Keeping Units), and
product styles. By storing and organizing these data points, the system ensures seamless order tracking and
enhanced operational transparency.

In addition to data management, the system will include robust analytics capabilities, enabling the generation of
visual insights through bar graphs, pie charts, line graphs, and other interactive visualizations. These tools will help
identify trends in sales, fulfilment efficiency, channel performance, and product popularity. The system will support
decision-making processes by providing a clear and dynamic overview of key metrics, thereby improving operational
efficiency and strategic planning for the e-commerce business.

The E-commerce Database Management System can project a wide array of insights and metrics by leveraging its
integrated data and visualization capabilities. These projections include:

1. Sales Trends and Performance: Bar graphs and line charts can illustrate daily, weekly, or monthly sales
trends, enabling businesses to identify peak shopping periods and seasonal demand.
2. Order Fulfilment and delivery analysis: Visualizations like pie charts can depict the proportion of orders in
various statuses (e.g., shipped, delivered, pending), while bar graphs can show delivery times by shipping
service level to assess fulfilment efficiency.
3. Product popularity and inventory insights: SKU-level sales data can be projected in histograms or heatmaps,
helping identify the most popular styles and products requiring restocking.
4. Channel performance metrics: Sales by channel (e.g., website, mobile app, marketplaces) can be broken
down into comparative graphs, aiding in determining the most effective sales platforms.
5. Revenue breakdown: Charts can provide insights into revenue distribution across categories like product
types, regions, or sales channels, helping to prioritize profitable areas.
6. Shipping Service level breakdown: Service levels (e.g., standard, expedited) can be analysed to compare
costs, delivery times, and customer satisfaction, guiding policy optimizations.
7. Customer behaviour patterns: Analysing repeated orders, abandoned carts, or preferred styles provides a
clear picture of customer preferences and areas for retention improvement.
8. Operational Bottlenecks: Dashboards can flag delays in fulfilment, high return rates, or underperforming
SKUs for targeted interventions.

These projections will empower businesses to make informed, data-driven decisions that enhance customer
satisfaction, optimize resources, and drive profitability.
 2.ER DIAGRAM
An ER Diagram (Entity-Relationship Diagram) is a visual representation of a database's structure,
illustrating how entities (tables) are related to each other. An Entity-Relationship Diagram (ERD)
graphically depicts the structure of a database by modeling its entities (objects or concepts), their attributes
(properties), and the relationships (associations) between them. Entities are represented as rectangles,
attributes as ovals connected to their entities, and relationships as diamonds linking entities. ERDs are
essential for database design, as they provide a clear framework for organizing and managing data.
An ER Diagram (ERD) serves as a blueprint for database design, illustrating the logical structure of the
database. Entities can be classified into three types: strong entities (independent of other entities), weak
entities (dependent on a parent entity), and associative entities (representing many-to-many relationships).
Relationships are categorized as one-to-one (1:1), one-to-many (1:N), or many-to-many (M:N),
depending on how entities interact.
Attributes can further include key attributes (unique identifiers like primary keys), composite attributes
(attributes composed of multiple parts), multivalued attributes (attributes with multiple values), and
derived attributes (calculated from other attributes).
ERDs also incorporate cardinality to define the minimum and maximum number of relationships between
entities and may include generalization, specialization, and aggregation to model hierarchical or complex
relationships. This tool is crucial for ensuring consistency and efficiency in database systems before
implementation.
 3.DATA FLOW DIAGRAM

3.1 LEVEL 0 DFD:

A Level 0 Data Flow Diagram (DFD), also called a Context Diagram, is the simplest form of a DFD. It provides an
overview of the entire system by representing it as a single process, showing how it interacts with external entities
(such as users, organizations, or other systems) via data flows. This level does not include internal system details and
focuses on illustrating the system's scope, inputs, and outputs.
LEVEL 0 DFD FOR E-COMMERCE DATABASE MANAGEMENT SYSTEM

3.2 LEVEL 1 DFD:

A Level 1 Data Flow Diagram (DFD) expands on the Level 0 DFD by breaking down the single process
into its main sub-processes or functions. It provides a more detailed view of the system, showing how data
flows between these sub-processes, external entities, and data stores. This level helps in understanding the
internal workings and major operations within the system.
LEVEL 1 DFD FOR E-COMMERCE DATABASE MANAGEMENT SYSTEM
 4.NORMALIZATIONS

The dataset is in First Normal Form (1NF) because it satisfies the following requirements:
1. Atomicity of Data:
o Each column contains only atomic values, meaning there are no repeating
groups or arrays in any field. For instance, fields like Order_ID, SKU, Qty, ship-
city, etc., contain singular, indivisible values.
2. Unique Rows:
o Each row in the dataset is uniquely identified by the Order_ID or a composite
key like Order_ID + SKU. This ensures there is no duplicate data.
3. No Repeating Groups:
o There are no repeating columns or nested data structures. Each attribute in the
dataset holds one value per record.
Thus, the dataset is in 1NF because all data is stored in a tabular format, with unique rows,
atomic values, and no repeating groups.