VISVESVARAYA TECHNOLOGICAL UNIVERSITY

Jnana Sangama, Belagavi – 590018

A Database Management System Mini Project Report On

“Online E-commerce Management System”

Submitted in Partial fulfilment of the Requirements for the V Semester of the
Degree of
Bachelor of Engineering In
ARTIFICIAL INTELLIGENCE & DATA SCIENCE ENGINEERING
By

Ankitha Poojary(4MW21AD008)
Anusha(4MW21AD010)
kripakshini(4MW21AD024)
adthi(4MW21AD002)

Under the Guidance of

Ms. P Vaidehi Nayantara
Asst. Prof, Dept. of AI & DS Engg.

DEPARTMENT OF ARTIFICIAL INTELLIGENCE & DATA SCIENCE

ENGINEERING

Shri Madhwa Vadiraja Institute of Technology & Management

Vishwothama Nagar, Bantakal-574115

March, 2024

1
 SHRI MADHWA VADIRAJA INSTITUTE OF TECHNOLOGY AND MANAGEMENT
(A Unit of Shri Sode Vadiraja Mutt Education Trust ®, Udupi) Vishwothama Nagar, BANTAKAL – 574 115,
Udupi District, Karnataka, INDIA

DEPARTMENT OF ARTIFICIAL INTELLIGENCE & DATA SCIENCE ENGG.

CERTIFICATE
Certified that the Database Management System Project Work titled ‘Blood Bank Management
System’ has been carried out by Ms.Roshini(4MW21AD051), Ms.Shravya S
Devadiga(4MW21AD051), Ms.Prathvika(4MW21AD036) and Ms.Rachana(4MW21AD041), who
are the bonafide students of Shri Madhwa Vadiraja Institute of Technology and Management, in
partial fulfillment for the award of Bachelor of Engineering in Artificial Intelligence & Data Science
engineering of Visvesvaraya Technological University, Belagavi during the year 202324. The
Database Management System Mini Project Report has been approved as it satisfies the academic
requirements with respect to the project work guidelines prescribed for the said Degree.

Ms. P Vaidehi Nayantara Mr. Nagaraja Rao

Project Guide Head
Dept. of AI- DS & ML Engg. Dept. of AI-DS & AI-ML Engg.

External Viva
Name of the examiners Signature with date
1.

2.

2
 ACKNOWLEDGEMENT

We extend our heartfelt appreciation to Dr. Thirumaleshwar Bhat, Head of the Department, Mr.
Nagaraja Rao, and faculty member Ms. P Vaidehi Nayantara, for their invaluable guidance,
mentorship, and unwavering support throughout the Blood Bank Management System project.

Our gratitude also goes to the dedicated development team whose hard work, collaboration, and
technical expertise were crucial in bringing the project to fruition. We are thankful for the support
and cooperation received from all stakeholders, including blood bank staff, healthcare
professionals, donors, and recipients, whose input helped tailor the system to meet end-users'
needs.

We also appreciate the contributions of the open-source community, whose resources and tools
facilitated the development process. Lastly, we express our gratitude to our friends and family
for their unwavering support and encouragement throughout this endeavor.

Together, the collaborative efforts of all involved parties have resulted in the successful
implementation of the Blood Bank Management System, addressing critical healthcare needs
within our community.

ROSHINI(4MW21AD044)

SHRAVYA S DEVADIGA (4MW21AD051)

PRATHVIKA (4MW21AD039)

RACHANA (4MW21AD041)

3
 ABSTRACT

In recent years there has been a large variety of e-commerce websites that had popped
up. E-commerce websites have helped both small and big businesses develop and evolve. E-
commerce websites have made it easy for small businesses to grow and expand their boundaries
by exporting their goods to distant places. It has also helped consumers who require certain
goods and or services.

In this era of internet, e-commerce is growing by leaps and bounds keeping the growth of brick-
and-mortar businesses in the dust. In many cases, brick-and-mortar businesses are resorting to
having a counterpart which is internet or e-commerce driven. People in the developed world and
a growing number of people in the developing world now use e-commerce websites on a daily
basis to make their everyday purchases. Still the proliferation of e-commerce in the under-
developed world is not that great and there is a lot to desire for. This paper outlines different
aspects of developing an e-commerce website and the optimum solution to the challenges
involved in developing one.

It consists of the planning process, which starts with determining the use case, domain modeling
and architectural pattern of the web application. The entire development process is primarily
divided into two parts: the front-end development and the back end development. The database
design is also discussed with an emphasis on its relational connectivity. This no-nonsense method
of developing an e-commerce website can be easily replicated and followed in developing e-
commerce websites in the developing and under-developed countries where computing
resources are scarce and expensive because of their socio-economic condition.

4
 TABLE OF CONTENTS

1 INTRODUCTION

1.1 Background and motivation.....................……..……………………………….1

1.2 Database Management System…………………………………………………1

1.3 Problem statement ..........……………………………………………………… 1

1.4 Objectives.......................................................... ..……………………………...1

2 REQUIREMENT SPECIFICATIONS

2.1 Hardware requirements………………………………………………………..3

16 2.2 Software requirements ………………………………………………………..3

3 DESIGN

3.1 Entity – Relationship diagram……………………….………………………...5

3.2 Description....………………………………………………………………….5

3.3 Schema diagram...……………………………………………………..............6

3.4 Database description....………………………………………………...............7

4 IMPLEMENTATION

4.1 Web-Based Application Implementation……………………………………...8

4.2 Desktop Application Implementation…………………………………………9

5 RESULTS 9

6 CONCLUSIONS AND FUTURE SCOPE 10

REFERENCES 11

APPENDIX

5
 Chapter 1
INTRODUCTION
1.1 BACKGROUND AND MOTIVATION

Computer plays an important role in our daily life. Anything we want we can get only in one mouse click. Speed,
reliability and accuracy of the computer make it a powerful tool for different purposes. A very important and
basic need of today’s modern business world is the quick availability and processing of information using
computer. One can easily get the type of required information within a fraction of a second.

The project that I have taken is also in this category which is used in our daily life whenever we want to
purchase some items we can easily get them at our home. E-commerce (electronic commerce) is the buying
and selling of goods and services, or the transmitting of funds or data, over an electronic network, primarily
the internet. These business transactions occur either as business-to-business (B2B), business-to-consumer
(B2C), consumer to-consumer or consumer-to-business. The terms e-commerce and e-business are often used
interchangeably. The term e-tail is also sometimes used in reference to the transactional processes for online
shopping.

Motivation:

Our motivation for undertaking this ecommerce management project stems from the relentless pursuit of
enhancing business efficacy in the digital age. Recognizing the dynamic nature of online commerce, we are
driven by the desire to empower businesses with cutting-edge solutions. The evolving consumer landscape
demands adaptability, and our motivation lies in equipping businesses with the tools and strategies needed to
thrive amidst these challenges. As we navigate through this project, envision a future where businesses not
only survive but excel in the ever-expanding realm of ecommerce.

1.2 DATABASE MANAGEMENT SYSTEM

The above project utilizes MySQL as its database management system (DBMS). MySQL is chosen for its
reliability, performance, scalability, and seamless integration with PHP, the server-side scripting language used
in the project. It offers robust security features and benefits from a large and active community for support
and resources.

1.3 PROBLEM STATEMENT

In the vast landscape of ecommerce, businesses encounter challenges ranging from operational inefficiencies

to evolving consumer expectations. Recognizing these hurdles, our project addresses the following key issues:

• Operational Inefficiencies: Streamlining and optimizing backend processes to enhance overall efficiency.

• Customer Engagement: Crafting strategies to consistently engage and satisfy the ever-changing

6
 preferences of online consumers.

• Data Security: Ensuring robust measures are in place to safeguard sensitive customer information
and maintain trust.

1.4 OBJECTIVES

Our objectives are clear and targeted towards overcoming the identified challenges:

1. Operational Excellence: Implementing technologies and methodologies to streamline operations and reduce
inefficiencies.

2. Enhanced Customer Experience: Developing customer-centric strategies to boost engagement, satisfaction

and loyalty.

3. Security Measures: Implementing state-of-the-art security protocols to protect both customer and business data,
fostering a secure online environment.

7
 Chapter 2

REQUIREMENT SPECIFICATIONS

2.1 Hardware Requirements

• Processor : Pentium IV
• RAM : 2GB
• Hard Disk : 50GB
• Input Devices : Keyboard, Mouse
• Output Devices : Monitor

2.2 Software Requirements

1. Operating System:
- The choice of operating system depends on the developer's preference and the server environment. Common
choices include:
- Windows: Often used for development environments, but less common for production servers.
- Linux (e.g., Ubuntu, CentOS, Debian): Widely used for web servers due to its stability, security, and cost-
effectiveness.
- macOS: Suitable for development environments and compatible with Unix-based server software.
2. Server Software:
- Apache or Nginx: These are popular web server software options that serve web pages to users' browsers.
They are capable of handling PHP requests and routing them to the appropriate files.
- PHP: A server-side scripting language used for creating dynamic web pages. PHP scripts embedded within
HTML files generate content dynamically based on user requests.
- MySQL: A relational database management system (RDBMS) used for storing and managing data.
MySQL organizes data into tables, allowing for efficient retrieval and manipulation using SQL queries.
3. Development Tools:
- Text Editor or IDE: Developers use text editors or integrated development environments (IDEs) to write and
edit PHP code and SQL queries. Popular options include Visual Studio Code, Sublime Text, PhpStorm, and Atom.
4. Web Browser:
- Any modern web browser (e.g., Chrome, Firefox, or Safari) for accessing the web application.
5. Security Software:
- Security tools for protecting the server and web application, such as firewall software, antivirus software,
and intrusion detection systems.

8
 Chapter 3
DESIGN

3.1 ENTITY-RELATIONSHIP DIAGRAM

3.2 DESCRIPTION
Entities:
A. User
--Represents users who want to buy products
--Attributes may include user_id (primary key), first name, last name, email, password, mobile, address 1,
address 2.
B. Brands
--Represents the brand of a product
--Attributes may include brand_id (primary key), brand_title.
C.cart

9
--Represents the products the user wishes to buy
--Attributes may include Id (primary key), p_id (foreign key), ip_add, user_id (foreign key), qty (foreign key).
d.orders
-- Represents the products purchased by the user
--Attributes may include order_id (primary key), user_id (foreign key), product _id (foreign key), qty (foreign
key).
E. categories
--Represents the different product section
--Attributes may include cat_id (primary key), cat_title.
F. Products
--Represents the items
--Attributes may include product_id (primary key), product_cat(foreign key), product brand(foreign key),
product price.

Relationships:
a. Donor Donates Blood:
- Many-to-Many relationship between Donor and Blood Donation entities.
- One donor can make multiple donations, and each donation can be made by multiple donors.
b. Blood Donation is Recorded in Stock:
- One-to-Many relationship between Blood Donation and Stock entities.
- Each blood donation contributes to the Stock, but one donation can only be recorded once in the Stock.
c. Stock Supplies Blood Request:
- One-to-Many relationship between Stock and Blood Request entities.
- The blood inventory supplies blood for multiple requests, but each request is fulfilled by a specific quantity
of blood from the inventory.
d. Recipient Receives Blood:
- One-to-Many relationship between Recipient and Blood Request entities.
- Each recipient can make multiple requests for blood, but each request is made by a specific recipient.

3.3 SCHEMA DIAGRAM

10
11
1. User Table:
- UserID (Primary Key): Unique identifier for each user.
- UserName: Name of the user.
- UserAddress: Address of the user for shipping or contact purposes.

2. Order Table:
- OrderID (Primary Key): Unique identifier for each order.
- UserID (Foreign Key): Relates each order to a specific user through the User table.
- ProductID (Foreign Key): Associates each order with a specific product from the Product
table.
- OrderDate: Date and time when the order was placed.

3. Product Table:
- ProductID (Primary Key): Unique identifier for each product.
- CategoryID (Foreign Key): Establishes a relationship with the ProdCategory table, classifying
products into categories.
- ProductName: Name of the product.
- ProductPrice: Price of the product.
- ProductBrand: Brand of the product.

4. ProdCategory Table:
- CategoryID (Primary Key): Unique identifier for each product category.
- CategoryName: Name of the product category.

5. Cart Table:
- CartID (Primary Key): Unique identifier for each shopping cart.
- UserID (Foreign Key): Associates each shopping cart with a specific user.
- ProductID (Foreign Key): Links each item in the shopping cart to a product from the Product
table.
- Quantity: Number of units of a specific product in the cart.

6. Payment Table:
- PaymentID (Primary Key): Unique identifier for each payment transaction.
- OrderID (Foreign Key): Connects each payment to a specific order.
- PaymentAmount: Amount paid for the order.
- PaymentDate: Date and time when the payment was processed.

12
This detailed schema provides a comprehensive structure for managing user information,
orders, products, categories, shopping carts, payment.

3.4 DATABASE DESCRIPTION

Donor Table:
Attributes: donor_id (Primary Key), name, contact_information, blood_type, donation_history.
Stock Table:
Attributes: Donor_id (Primary Key), Date of Donation, Blood group, Amount of Blood.
Blood Table:
Attributes: Blood_no (Primary Key), Donor_id(Foreign Key), Date of Expiry, Lab Test Results.

13
 Chapter 4
IMPLEMENTATION
4.1 Web-Based Application Implementation:

● Technology Stack: PHP for server-side scripting, MySQL for database management,
HTML/CSS/JavaScript for the user interface, Apache or Nginx as the web server.
● Description: This implementation involves developing a web-based application accessible
through a web browser. Users can access the system from any device with internet access.
● Features:
-User authentication and authorization.
-Donor and recipient management.
-Blood donation recording and inventory tracking.
-Blood request management.
-Reporting and analytics.
● Advantages:
Accessibility from anywhere with an internet connection.
No need to install additional software on client devices.
Easier to deploy updates and improvements.
● Considerations:
Requires a stable internet connection for access.
Security measures need to be robust to protect sensitive medical data.

4.2 Desktop Application Implementation:

● Technology Stack: Java, Python, or C# for desktop application development, MySQL or SQLite for
database management.
● Description: This implementation involves developing a standalone desktop application that users install
on their computers. The application provides similar functionalities to the webbased version but runs
locally on the user's device.

14
● Features:
Offline access to functionalities.
Data synchronization with a central server for updates and reporting. User-friendly
interface optimized for desktop use.
● Advantages:
Can work offline, making it suitable for areas with limited internet access.
May offer better performance and responsiveness compared to web-based applications.
● Considerations:
Requires installation on each user's device.
Updates and maintenance may be more challenging to deploy.
Data synchronization and backup mechanisms need to be implemented for data consistency and
security.

15
16
17
 Chapter 5
RESULTS

18
19
20
 Chapter 6

CONCLUSION AND FUTURE SCOPE

Conclusion:
In concluding our ecommerce management project, we find ourselves at the intersection of innovation and practicality.
Through the strategic combination of CSS and Bootstrap for the front end, and JavaScript, MySQL, and PHP for the back
end, we have crafted a robust and responsive ecosystem for online business operations.

This journey has been marked by a commitment to addressing challenges, from operational inefficiencies to customer
engagement and data security. Our frontend technologies contribute to an engaging user experience, while the backend
technologies ensure data integrity and efficient processing.

As we look forward, our ecommerce management system stands as a testament to the synergy of technology and
business acumen. The seamless connection between the front end and back end, facilitated by PHP, exemplifies our
dedication to creating a comprehensive solution for businesses navigating the complexities of online commerce.

In essence, our project is not just a culmination of technologies; it represents a forward-looking approach to empower
businesses in the digital age. Through this harmonious blend of frontend aesthetics and backend functionality, we aspire
to propel businesses towards sustained success in the ever-evolving landscape of ecommerce.
Future Scope:
The project has a very vast scope in future. The project can be implemented on intranet in future. Project can be
updated in near future as and when requirement for the same arises, as it is very flexible in terms of expansion.
With the proposed software of database Space Manager ready and fully functional the client is now able to
manage and hence run the entire work in a much better, accurate and error free manner.
The following are the future scope for the project.
● Should be added payment gateway
● Can be added inventory management system
● Can be added multiple branches
● Can be added multilingual to this site
● And many features can be added this project to make it more robust.

21
REFERENCES
1. World Health Organization. (2021). Blood Transfusion Safety. Retrieved from
[https://www.who.int/news-room/fact-sheets/detail/blood-transfusion-safety]

2. American Red Cross. (2021). Blood Donation Process. Retrieved

from
https://www.redcrossblood.org/donate-blood/how-to-donate.html

22