TRIBHUVAN UNIVERSITY

Faculty of Bachelor of Information Management (BIM)

BRIGHTLAND COLLEGE
PASANGLAMU ROAD, NAPALGUNJ (NEPAL)

A Report on “E-Commerce”
“E-COMMERCE MANAGEMENT SYSTEM”
For
Software Project Management (IT 306)
8th semester Project report submitted in partial fulfilment of the requirements for the degree in
Bachelor of Information Management

Submitted By: Bibek Khadka (Symbol No: 12899/20)

TU Registration No. 7-2-543-33-2020

Under the supervision of:

Bhuwan Rai

1
 Acknowledgement

We, the undersigned, take great pleasure in expressing our heartfelt gratitude to all who have
volunteered their time to assist us in achieving project success.
We want to convey our appreciation to everyone who made it possible for us to finish this project.
Our heartfelt gratitude to the BIM department of Brightland College for supplying us with the
necessary information that enabled us to effectively finish our assignment.

This project has been a significant milestone in our professional development, and we are
committed to utilizing the skills and knowledge we have gained to achieve our career goals. We
hope to continue to collaborate with all of you in the future.
Thank you all for your support and encouragement.

2
 Abstract

Computers have become integral to modern society, enabling many aspects of life that we
now take for granted. Today, computers are extensively used in business, industry, science,
education, and more. One of the major advantages of computers is their speed, allowing them
to quickly provide useful information and facilitate new approaches to problem-solving and
data processing. Another key feature is their accuracy.

The project entitled “E-Commerce Website Management System” is a software package

designed to manage e-commerce websites efficiently. In today's digital age, online shopping
and transactions have become commonplace, making it essential to manage customer data
and transactions systematically. The system stores valid information of users who access the
website, recording user login and logout times. It maintains prepaid accounts for frequent
users, offering discounted rates while charging a fixed rate for one-time or less frequent users.
By using LAN connections, the system automates the process of managing user data and
transactions, automatically generating time and amount details at the server end after the user
logs out and providing a bill to the user.

The system comprises two modules: the Server Module and the Client Module. The Server
Module, handled by the administrator, allows for the creation of new accounts for prepaid
users and stores details of one-time or less frequent users. It also manages overall website
transactions and user data. The Client Module, handled by users themselves, requires users to
provide their user ID and password to access the website. Browsing time and transaction
amounts are recorded and sent to the Server Module upon user logout.

In this modern era, where e-commerce is rapidly growing, it is crucial to have an efficient
management system for online businesses. By implementing the E-Commerce Website
Management System, businesses can ensure secure, accurate, and efficient handling of user
data and transactions, ultimately enhancing user experience and operational efficiency.

3
 Contents
Contents
Contents
Under the supervision of: .................................................................................................................................. 1
Bhuwan Rai ....................................................................................................................................................... 1
Chapter I: Introduction ..........................................................................................................................................................5
1.1 Introduction to the system:................................................................................................................... 5
1.2 Problem Definition: ............................................................................................................................. 5
1.3 Objectives of the project: ..................................................................................................................... 5
1.4 Limitations of the project: .................................................................................................................... 6
1.5 Scope of project: .................................................................................................................................. 6
Chapter II: Project Planning .....................................................................................................................................................7
2.1 Work Breakdown Structure ................................................................................................................. 7
2.2 Schedule Gantt-Chart: ......................................................................................................................... 8
2.3. Risk Identification and Analysis for E-Commerce System ............................................................ 9
2.4 Analysis of System ............................................................................................................................ 10
2.5 Existing System ................................................................................................................................. 10
2.6 Feasibility Analysis of Project ........................................................................................................... 10
Chapter III: System Design .................................................................................................................................................. 11
3.1 Data Flow Diagram............................................................................................................................ 11
3.2 Use case Diagram .............................................................................................................................. 12
3.3 Sequence Diagram: ............................................................................................................................ 13
3.4 Activity Diagram for Online E-commerce System ............................................................................ 14
3.5 Class Diagram ................................................................................................................................... 16
3.6 ER Diagram ....................................................................................................................................... 17
3.7 Entities and Attributes ....................................................................................................................... 18
APPENDICES ................................................................................................................................................ 19
Conclusion: ......................................................................................................................................................................... 23
Reference......................................................................................................................................................... 24

4
 Chapter I: Introduction
1.1 Introduction to the system:

An e-commerce website is an online platform for businesses to sell products and services. It
features a user-friendly interface for browsing, selecting, and purchasing items with secure
payment options. The E-Commerce Website Management System efficiently manages inventory,
order processing, customer management, and payments, ensuring smooth operations and
enhanced user experience. It supports various business models like B2B and B2C, offering
functionalities such as bulk order processing and personalized shopping. This system is essential
for businesses aiming to establish or enhance their online presence, streamlining operations and
ensuring customer satisfaction.

1.2 Problem Definition:

The objective of the project is to automate the management of an e-commerce website. The
software must include features to handle user accounts, track login history, and manage online
transactions. It should assist website administrators in retrieving customer details and monitoring
usage patterns. The system should be capable of automating order processing, managing
inventory, and calculating daily sales and revenue. Additionally, it must facilitate seamless
customer interactions, including order placement, payment processing, and customer support, to
enhance the overall efficiency and profitability of the e-commerce platform.

1.3 Objectives of the project:

The objectives of this project are:

To provide an easy, reliable, and secure platform for online transactions and user interactions.
To create an engaging space for customers to browse, shop, and share their shopping
experiences.
To efficiently manage user accounts, transaction history, inventory, and customer support through
automation.
To offer a seamless and enjoyable online shopping experience that accommodates diverse
customer needs and preferences.
To streamline and automate processes, replacing manual and paper-based tasks to enhance
operational efficiency and accuracy.

5
 1.4 Limitations of the project:

• Offline Transactions: Transactions are processed in offline mode, limiting the ability to
capture and modify online data related to ID proof and charges.
• Report Generation: Offline reports for ID proof, customer information, and usage cannot be
generated due to batch mode execution.
• Security Risks: Potential vulnerabilities include identity theft, keylogging, network sniffing,
and invasion of privacy.

1.5 Scope of project:

The proposed e-commerce system has significant potential in today’s digital landscape. By
integrating advanced features, this system aims to enhance online transaction security and
streamline operations for businesses. While many firms are transitioning to computerized
solutions, e-commerce platforms often face challenges in maintaining reliability and
efficiency. This project seeks to address these gaps, offering a more reliable and robust
solution. The positive feedback received during the initial feasibility study underscores the
project's promise, paving the way for further development and implementation.

6
 Chapter II: Project Planning

2.1 Work Breakdown Structure

1. Planning Phase
1.1. Identify project objectives
1.2. Define scope and deliverables
1.3. Prepare Gantt chart
1.4. Identify risks and create a risk register

2. Analysis Phase
2.1. Study existing systems
2.2. Identify system requirements
2.3. Conduct feasibility analysis

3. Design Phase
3.1. Create system architecture
3.2. Design database (ER diagram, relationships)
3.3. Design user interface (wireframes)
3.4. Prepare UML diagrams (DFD, use case, class diagrams)

4. Development Phase
4.1. Set up the development environment
4.2. Develop login and user management module
4.3. Build product catalogue and search functionality
4.4. Develop a cart and checkout system
4.5. Create an admin panel for product management

5. Testing Phase
5.1. Unit testing of individual modules
5.2. Integration testing of combined modules
5.3. Conduct user acceptance testing (UAT)

6. Deployment Phase
6.1. Deploy system to server
6.2. Configure database and security measures
6.3. Launch live system

7. Documentation Phase
7.1. Prepare user manual
7.2. Write technical documentation
7.3. Compile final project report

8. Maintenance Phase
8.1. Monitor system performance
8.2. Address user feedback
8.2.1. Update and add new features as needed

7
2.2 Schedule Gantt-Chart:
2.2.1 Project schedule:

Task Start date End Date Duration

Planning 08/19/2024 9/1/2024 11

Analysis 9/2/2024 9/25/2024 23
Logical Design 9/28/2024 10/15/2024 18
Physical Design 10/20/2024 11/5/2024 15
Implementation 11/6/2024 11/25/2024 19
Testing 11/27/2024 12/9/2024 13

8
 2.2.2 Gantt Chart

08/19/ 09/10/2 09/30/2 10/19/2 11/9/2 11/29/

202 024 024 024 024 202

Planni
ng

Analy
sis

Logical
Design

Physical
Design

Implement
ation

Testi
ng

2.3. Risk Identification and Analysis for E-Commerce System

1. Potential Risks:
o Security breaches: Unauthorized access to sensitive user data.
▪ Likelihood: High
▪ Impact: High
o Server downtime: Service unavailability during peak hours.
▪ Likelihood: Medium
▪ Impact: High
o Scope creep: Uncontrolled feature additions during development.
▪ Likelihood: Medium
▪ Impact: Medium
2. Risk Mitigation Strategies:
o Security breaches: Implement SSL encryption, multi-factor authentication, and regular
security audits.
o Server downtime: Use scalable and reliable hosting solutions with load balancers.
o Scope creep: Define clear project scope, set milestones, and establish change request
protocols.

9
2.4 Analysis of System
System analysis involves identifying the current processes of the existing e-commerce
website, determining necessary changes and new features, and defining the exact
requirements for the proposed system. This process focuses on understanding, developing,
and agreeing on the user's needs. Effective system analysis provides an opportunity for
thorough communication with the user, establishing a shared understanding of what the
system should achieve and the relative importance of its various features through interactive
techniques.

2.5 Existing System

Currently, many e-commerce websites handle certain processes manually or with limited
automation, leading to inefficiencies and potential errors. Commonly, tasks such as order
processing, inventory management, customer service, and data analysis may not be fully
integrated or automated. The present system has the following limitations:

- Limited capabilities in generating comprehensive reports

- Excessive time consumption due to manual data entry and processing
- High potential for errors in order processing and inventory management
- Time-consuming retrieval of customer and order information
- Lack of an efficient billing system and manual calculation of financial metrics
- Repeated entry of frequent customer details
- Difficulty in managing and updating product listings

2.6 Feasibility Analysis of Project

During system analysis, the feasibility study of the proposed E-commerce Management
System is conducted to ensure that the proposed system is not a burden to the company.
This study can be categorized into three types:

Economic Feasibility Study

This study evaluates the economic impact of the system on the organization. Given that the
company has a limited budget for the research and development of the system,
expenditures must be justified. The developed system was designed to stay well within the
budget, achieved by using freely available technologies. Only customized products needed
to be purchased, ensuring that the system is cost-effective.

Technical Feasibility Study

This study assesses the technical requirements of the system. Any developed system should
not place excessive demands on the available technical resources. The proposed E-
11
 Chapter III: System Design

3.1 Data Flow Diagram

Level 0 DFD diagram (Context Diagram):

• This is the highest level of abstraction in DFD.
• It represents the entire system as a single process (or bubble).
• It shows the interaction between the system and external entities (like users, other systems,
etc.) through data flows.

13
3.2 Use case Diagram

In the Unified Modeling Language (UML), a use case diagram can summarize the
details of your system's users (also known as actors) and their interactions with the
system. To build one, you'll use a set of specialized symbols and connectors. An
effective use case diagram can help your team discuss and represent:

Scenarios in which your system or application interacts with people, organizations, or

external systems

Goals that your system or application helps those entities (known as actors) achieve

Use Use Case Actors Description Preconditions Postconditions

Case Name
ID
Allow customers to add The customer is
Add to selected products to their logged in and Item is added to the
UC1 Cart Customer shopping cart. browsing products. cart successfully.
Enables customers to
purchase items in their cart Order is placed, and
UC2 Checkout Customer using the payment system. Items are in the cart. payment is processed.
View Customer, Displays order details for Orders exist in the Order details are
UC4 Orders Admin customers and admins. database. displayed.
Allows admins to add, edit, Admin is logged in
Manage or delete products in the with appropriate The product catalogue
UC5 Products Admin catalogue. rights. is updated.

16
3.3 Sequence Diagram:

Sequence diagrams in UML provide a visual representation of interactions between objects or

actors within a system, illustrating the flow of messages over time. Objects are depicted as
lifelines, with messages shown as arrows between them, indicating the sequence of method calls
or events. Activation boxes denote the period during which an object is active, processing a
message. These diagrams are crucial for understanding and documenting the dynamic
behaviorof a system, aiding in system design, validation of use case scenarios, and debugging
during development. They are valuable for stakeholders to visualize and analyze how objects
collaborate to achieve specific functionalities, ensuring clarity and alignment across teams
throughout the software development lifecycle.

18
3.4 Activity Diagram for Online E-commerce System

An activity diagram for an online e-commerce system illustrates the sequence of activities
involved in typical user interactions and system processes. It begins with the initial activity and
shows how activities are interconnected through decision points, forks, and joins, depicting the
flow of control and data between different parts of the system. Activities such as browsing
products, adding items to the cart, checking out, and managing orders are represented as nodes,
with arrows indicating transitions between activities based on conditions or events.

19
An activity diagram for an online e-commerce system represents the following key activities and
their flow:

1. Start:
o The starting point of the process.
2. Browse Products:
o Customers browse and search for products.
3. View Product Details:
o Customers view detailed information about a selected product.
4. Add to Cart:
o Customers add selected products to their shopping carts.
5. View Cart:
o Customers review the items in their shopping cart.
6. Proceed to Checkout:
o Customers initiate the checkout process.
7. Enter Shipping Information:
o Customers provide shipping details.
8. Enter Payment Information:
o Customers provide payment details.
9. Confirm Order:
o Customers review and confirm their orders.
10. Process Payment:
o The system processes the payment through a payment gateway.
11. Generate Order:
o The system generates and stores the order details.
12. Send Confirmation Email:
o The system sends an order confirmation email to the customer.
13. Manage Orders:
o Admin manages orders, updating statuses and handling issues.
14. End:
o The endpoint of the process.

20
3.5 Class Diagram

The most widely used UML diagram is the class diagram. It is the building block of all object-
oriented software systems. We use class diagrams to depict the static structure of a system by
showing the system’s classes, their methods and attributes. Class diagrams also help us
identify relationships between different classes or objects.
The Class Diagram for our system is shown below:

21
 3.6 ER Diagram

The Entity Relational Model is a model for identifying entities to be represented in the database
and representation of how those entities are related. The ER data model specifies enterprise
schema that represents the overall logical structure of a database graphically.

22
3.7 Entities and Attributes

1. Customer
o Attributes:
▪ CustomerID: Unique identifier for each customer (Primary Key).
▪ Name: Customer's full name.
▪ Email: Customer's email address for contact and login.
▪ Address: Shipping address for orders.
▪ Phone: Contact number.
o Description: Represents the users who interact with the system, making
purchases and managing their accounts.
2. Product
o Attributes:
▪ ProductID: Unique identifier for each product (Primary Key).
▪ Name: Name of the product.
▪ Description: Detailed information about the product.
▪ Price: Cost of the product.
▪ StockQuantity: Number of items available in stock.
o Description: Represents items available for sale in the online store.
3. Order
o Attributes:
▪ OrderID: Unique identifier for each order (Primary Key).
▪ OrderDate: Date when the order was placed.
▪ TotalAmount: Total cost of the order.
▪ Status: Current status of the order (e.g., Pending, Shipped, Delivered).
o Description: Represents a purchase transaction made by a customer.
4. OrderItem
o Attributes:
▪ OrderItemID: Unique identifier for each order item (Primary Key).
▪ Quantity: Number of units of the product ordered.
▪ UnitPrice: Price per unit of the product at the time of order.
o Description: Represents individual products within an order.
5. Payment
o Attributes:
▪ PaymentID: Unique identifier for each payment (Primary Key).
▪ Amount: Amount paid.
▪ PaymentDate: Date when the payment was made.
▪ PaymentMethod: Method used for payment (e.g., Credit Card, PayPal).
o Description: Represents the payment details for an order.
6. Category
o Attributes:
▪ CategoryID: Unique identifier for each category (Primary Key).
▪ Name: Name of the category.
▪ Description: Description of the category.
o Description: Represents different categories or types of products.

23
 APPENDICES

Fig. Login (Admin)

Fig. Dashboard
Fig. Manage Ticket Type

Fig. Add Ticket

 Fig. View details of ticket

Fig. View payment (Normal Ticket)

Fig. View Payment (Foreigner Ticket)

Fig. View Reports

Fig. View Ticket Id search

 Conclusion:
• Improved Performance: Compared to the existing manual system, the new e-commerce
platform operates much faster, enhancing overall efficiency.

• Better Feedback: The system provides improved feedback mechanisms, ensuring users
receive timely responses to their queries and actions.

• Timely and Accurate Information: The platform delivers timely and accurate information,
aiding in better decision-making and customer service.

• Consistent Processing Speed: The system offers greater processing speed consistency,
ensuring smooth and reliable user experience.

• Reduced Errors: The likelihood of errors is significantly lower with the automated
system, improving accuracy and reliability.

• Enhanced Security: The platform provides high security, preventing unauthorized access
and protecting sensitive data.

• Time Efficiency: The overall time required for various processes is reduced, making
operations more efficient.

• User-Friendly Interface: The forms and interfaces are designed to be very user-friendly,
ensuring ease of use for all users.

• Ease of Operation: The system is straightforward to operate, reducing the learning curve
and increasing user sati

33
 Reference

1. https://www.scribd.com/document/440242116/Ecommerce-Management-
Systemhttps://www.researchgate.net/
2. https://github.com/Saurabh-pec/Ecommerce-Management-DBMS_Project
3. https://att.aptisi.or.id/index.php/att/article/view/73
4. https://www.sciencedirect.com/science/article/abs/pii/S0925527301001918
5. https://www.geeksforgeeks.org/
6. https://chatgpt.com/
7. https://images.google.com/
8. KEC Book