BANGLADESH COMPUTER COUNCIL

DIPLOMA IN ICT

Online E-COMMERCE Management System

By

ADNAN HASAN
LEON
REG NO: 6047/23

A Project Submitted in Partial Fulfillment of the Requirements for the

DIPLOMA IN ICT FROM BANGLADESH COMPUTER COUNCIL

February, 2024

i
 DECLARATION

We, hereby, declare that the work presented in this Project is the outcome of the
investigation performed by me under the supervision of Shohel Rana, Senior Lecturer,
Bangladesh Computer Council. We also declare that no part of this Project or thereof has
been or is being submitted elsewhere for the award of any degree or Diploma.

Countersigned Signature

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

( Shohel Rana ) ( Adnan Hasan Leon )

Supervisor

Candidates

ii
 ABSTRACT
The Online E-Commerce Management System provides convenience for customers. It
overcomes the disadvantages of the traditional queuing system. This system increases the
takeaway of products more than visitors. Therefore, this system enhances the speed and
standardization of taking the order from the customer. It provides a better communication
platform. The user’s details are noted electronically. This System sets up a menu online and the
customers easily place the order with a simple mouse click. By using the product menu online
anyone can easily track the orders, maintain the customer's database, and improve product
delivery service. This system allows the user to select the desired product items from the
displayed menu. The user orders the product items. The payment can be made online or pay-on-
delivery system. The user’s details are maintained confidential because it maintains a separate
account for each user.

iii
 ACKNOWLEDGEMENTS

First of all, we are thankful to Almighty Allah for his blessings for the successful completion of
our project. The pleasure that accompanies the flourishing achievement of any task would be
shortened without the mention of people whose continual cooperation made it possible, whose
constant guidance and encouragement crown all efforts with success.

We would like to express our gratitude to our respected Chairman MD Mofizur Rahman. We are
grateful to our honorable supervisor Shohel Rana, Senior Lecturer, Bangladesh Computer
Council for the guidance, inspiration, and constructive suggestions that helped me in the
preparation of this project. Although he was always loaded with several other activities, he gave
us more than enough time for this work. He not only gave us time but also proper guidance and
valuable advice whenever we faced some difficulties. His comments and guidance helped us in
preparing my project report.

We are also thankful to all of our teachers in the department who helped us in several ways by
providing various resources and moral support.

Last of all we are grateful to our family, who are, always with us in every step of life.

iv
 TABLE OF CONTENTS
ABSTRACT iii
ACKNOWLEDGMENTS iv
TABLE OF CONTENTS V
LIST OF FIGURES Vii
LIST OF TABLE X

Chapter 1: Introduction 1

1.1 Introduction ................................................................................................. 2

1.2 What is an Online E-Commerce Management System……… 2
1.3 Background of Study .................................................................................. 2
1.4 Objective of Project .................................................................................... 3
1.5 Scope of project …………………………………………………….. 3
1.6 Overview of document …………………………………………….... 4

Chapter 2: Requirement Gathering /Analysis 05

2.1 Requirement Analysis ............................................................................................ 06

2.2 System Requirements… .......................................................................................... 06

2.3 Software and Hardware Requirements…................................................................ 06

2.4 Software Requirements… ....................................................................................... 06

2.5 Hardware Requirements… .......................................................................................06

2.6 User Requirements .................................................................................................. 07

2.7 Functional Requirements… .................................................................................... 07

2.8 Nonfunctional Requirements .................................................................................. 08

2.9 Business Requirements… ....................................................................................... 08

2.10 Data and Category Requirements…...................................................................... 08

Chapter 3: Data Definition and Form Design 09
3.1 Data Definition… ..................................................................................................... 10

3.2 Database Online E-Commerce Management System… .......................................... 10

3.3 Table Structure for comment meta ........................................................................... 10

3.4 Table Structure for Comments .................................................................................10

3.5 Table Structure for Links ......................................................................................... 10

3.6 Table Structure for Newsletter… ............................................................................ 11

3.7 Table Structure for Newsletter Emails ..................................................................... 11

3.8 Table Structure for Newsletter Stats… ....................................................................11

3.9 Table Structure for options… ................................................................................... 12

3.10 Table Structure for Posts .......................................................................................... 12

3.11 Table Structure for Slider........................................................................................ 12

3.12 Table Structure for Static Slides ............................................................................. 13

3.13 Table Structure for Terms ....................................................................................... 13

3.14 Table Structure for User .......................................................................................... 13

3.15 Table Structure for order item .................................................................................. 13

3.16 Table Structure for tax Rate .....................................................................................14

3.17 Form Design .............................................................................................................. 14

3.18 Login Page................................................................................................................ 14

3.19 Home Page ............................................................................................................... 15

3.20 About us Page........................................................................................................... 15

3.21 Shop Page ................................................................................................................. 16

3.22 Search bar ................................................................................................................. 16

 3.23 Categories ................................................................................................................. 17

3.24 Social Share.............................................................................................................. 17

3.25 Footer Link ............................................................................................................... 17

Chapter 4: Maintenance 18
4.1 Software Maintenance............................................................................................. 19

4.2 Software Maintenance process ................................................................................ 19

4.3 Maintenance Activities… ........................................................................................ 20

4.4 Difficulties of Maintenance ..................................................................................... 21

Chapter 5: Conclusion and Future Work 22

5.1 Conclusion ................................................................................................................ 23

5.2 Limitations… ........................................................................................................... 23

5.3 Future Plans… .......................................................................................................... 23

 CHAPTER 1
INTRODUCTION

1
1.1 Introduction
This manuscript is proposing about all the features and dealings to develop the system.
Especially it is containing details about objectives, possibility, plan replica, primary and
functional requirements, database model and as final point coverage and analyzing the
mechanisms. Once analyzing the mechanisms of the task that would be performed, the
following point is to consider the problem and understand is framework. Online E-Commerce
management system is a project which is referred to as a set of detail methods that is being
used in handling the ordering process. Product ordering can be computerized or done
manually. Those helps the customer to order their product themselves which is known as the
customer self- ordering system. The customer self-ordering system can be defined as a
computerized system that is being used by customers to place their own orders in the
restaurant and allow the orders to be tracked, in order to prepare and deliver the product to
the computers. Admin is the most powerful user of the system [1].

1.2 What is Online E-Commerce

management system?
Online restaurant is a process of ordering product from a local restaurant or product
cooperative through a web page. Much like ordering consumer goods online, many of these
allow customers to keep accounts with them in order to make frequent ordering convenient. A
customer will search for a favourite restaurant, usually filtered via type of cuisine and choose
from available items, and choose delivery or pick-up. Payment can be amongst others either
by credit card or cash, with the restaurant returning a percentage to the online product
company.

1.3 Background of the project

The Online E-Commerce management system is one of the latest servicers most fast product
restaurants in the western world are adopting. With this method, product is ordered online
and delivered to the customer. This is made possible through the use of electronic payment
system. Customers pay with their credit cards, although credit card customers can be served
even before they make payment either through cash or cheque. So, the system designed in
this project will enable customers go online and place order for their product . Due to the
great increase in the awareness of internet and the technologies associated with it, several
opportunities are coming up on the web. So many businesses and companies now venture
into their business with ease because of the internet. One of such business that the internet
introduced is an online product ordering system. In today’s age of fast product and take out,
many restaurants have chosen to focus on quick preparation and speedy delivery of orders
rather than offering a rich dining experience. Until recently, most of this delivery orders were
placed over the phone, but there are many disadvantages to this system. It is possible for
anybody to order any goods via the internet and have the goods delivered at his/her doorsteps.

2
internet? This then leads to the discussion of the economic consequences of digital cash.
What I propose is an online ordering system originally designed for use in college cafeterias,
but just as applicable in any product delivery industry. The main advantage of this system is
that it greatly simplifies the ordering process for both the customer and the restaurant. The
system also greatly lightens the load on the restaurants end, as the entire process of taking
orders is automated. Once an order is placed on the webpage that will be designed, it is
placed into the database and then retrieved, in pretty much real-time, by a desktop application
on the restaurants end. The greatest advantage of this system is its FLEXIBILITY [1].

1.4 Objective of the project

This project Online restaurant aim to be developed and brought to the market for maximum
use and to create an avenue through the web where users can log on to our server and make a
selection of whatever goods or product they like and subsequently pay via the internet. The
following are the objectives this would bring:

1. The home page of this web interfile provides an avenue where customers will be able to
gather more and reliable information about what the fast product industry really does.

2. The products and services offered would provide the customers with all the different
categories of available products that they can choose and select from.

3. This will provide a user friendly environment between the customer and employee thus
increasing the efficiency of the product ordering system.

4. There will also be an online purchase form with which valued customers will be using to
get in touch with any of their request whenever the need arises.

5. It will also help for easy retrieval of orders made by the customers.

1.5 Scope of the project

In this project, a fast product company is designed to enable customers order for product and
get it delivered accordingly and also to reduce the long queues of customers at the counter
ordering for product and to reduce the work lord on the employees. The following things are
among other things that are discussed and what the website would handle:

1. About the fast product company

2. The fast product and the services offered there
3. Online purchase
4. Type of product provided [1].

3
1.6 Overview of Document
In chapter 1 we talk about basic things of our project report, what is Online E-Commerce
management system, scope of this project, objective of this document etc. we also give
an overall preview of this document in this chapter.

In Chapter 2 we describe how we analysis the system model, which model we follow to
do this project. According to the software development life cycle we follow the waterfall
model for complete our project.

In Chapter 3 we describe the requirements gathering procedure and its constraints.

Methodological explanation of the project battered near peripheral viewers. This section
includes information such as data requirements, functional requirements and an over-all
narrative of the system and its interaction with users from the perspective of the
customer.

In Chapter 4 we describe the system design parts designed by unified model language,
we fully document this part to understand easily for the users.

In Chapter 5 we discuss and give some tables structures and screenshots of our system
for the form design and helps customer to use this system easily.

In Chapter 6 we describe the maintenance procedure of this project. We also discuss

about the activities and problem phases of maintenance.

Finally at the end in Chapter 7 we give the conclusion of this document and talk about
limitations and future plans what we will implement in future we hope so.

4
 CHAPTER 2
REQUIREMENT GATHERING/ANALYSIS

5
2.1 Requirement Analysis
Requirements analysis in systems engineering and software engineering, encompasses those
tasks that go into determining the needs or conditions to meet for a new or altered product or
project, taking account of the possibly conflicting requirements of the
various stakeholders, analysing, documenting, validating and managing software or system
requirements.[2]
Requirements analysis is critical to the success or failure of a systems or software
project.[3] The requirements should be documented, actionable, measurable, testable,
traceable, related to identified business needs or opportunities, and defined to a level of detail
sufficient for system design [5].

2.2 System Requirement

Our system can be used in windows XP, windows 7, and windows 8 with 32 bit, and 64 bit
operating system and also supported for other platform such as Linux OS X.

• For Windows XP based computers, a 486 / 66 MHz or higher processor with 8 MB.
• For Windows 7 and Windows 8 based computers, higher processor with 2 GB RAM.

2.3 Software and Hardware Requirements

2.4 Software Requirements:
• Web server software: Apache Tomcat, Wamp.
• Server-side scripting tool: PHP-5.6.
• Database tools: MYSQL DBMS.
• Compatible operating system: Windows, Mac.
• Front end design tool: Html5, CSS3, Java script, Word press, J Query.
• Software tools: Wordpress CMS, Revolution Slider, Newsletter subscription,
Wocommerce, Social sharing.

2.5 Hardware Requirements:

• Hardware recommended by all the software needed.
• RAM: 256MB or more
• Hard Drive: 10 GB or more
• Communication hardware to serve client requests

6
2.6 User Requirements
To deliver the best service to the users we tried to find out the user's necessities which are
below:

Administrator Aspect:

• Monitoring the whole system from the admin panel.

• Taking back up of the database.
• Creating, deleting, and modifying the records.
• Add users to the admin panel.
• Add customers and other staff.
• Keeping the customer’s records like their details.
• Organizing their member registration system.
• Approve the notice to post.
• Monitoring the transaction system.

Customer Aspect:

• Signing in and signing up to the system.

• Changing their password.
• Resetting forgot password.

2.7 Functional Requirements

In Software engineering and systems engineering, a functional requirement defines the
function of a system or its components. A function is described as a set of inputs, the
behavior, and outputs.
Functional requirements may be calculations, technical details, data manipulation and
processing, and other specific functionality that define what a system is supposed to
accomplish.[1] Behavioral requirements describing all the cases where the system uses the
functional requirements are captured in use cases. Functional requirements are supported
by non-functional requirements (also known as quality requirements), which impose
constraints on the design or implementation (such as performance requirements, security, or
reliability). Generally, functional requirements are expressed in the form "system must do
<requirement>", while non-functional requirements are "system shall be <requirement>". The
plan for implementing functional requirements is detailed in the system design. The plan for
implementing non-functional requirements is detailed in the system architecture.
As defined in requirements engineering, functional requirements specify particular results of
a system. This should be contrasted with non-functional requirements which specify overall
characteristics such as cost and reliability. Functional requirements drive the application
architecture of a system, while non-functional requirements drive the technical architecture of
a system [6].

7
2.8 Non-functional Requirements
In systems engineering and requirements engineering, a non-functional requirement is a
requirement that specifies criteria that can be used to judge the operation of a system, rather
than specific behaviors. They are contrasted with functional requirements that define specific
behaviors or functions. The plan for implementing functional requirements is detailed in the
system design. The plan for implementing non-functional requirements is detailed in the
system architecture because they are usually Architecturally Significant Requirements. [7].

2.9 Business Requirements

Business requirements in the context of software engineering or software development are

about eliciting and documenting business requirements of business users such as customers,
employees, and vendors early in the development cycle of a system to guide the design of the
future system. Business requirements are often captured by business analysts, who analyze
business activities and processes, and often study the As-is process to define a target To-be
process.
Business requirements often include

• Business context, scope, and background, including reasons for change

• Key business stakeholders that have requirements
• Success factors for a future/target state
• Constraints imposed by the business or other systems
• Business process models and analysis, often using flowchart notations to depict either 'as-
is' or 'to-be' business processes
• Logical data model and data dictionary references
• Glossaries of business terms and local jargon
• Data flow diagrams to illustrate how data flows through the information systems
(different from flowcharts depicting algorithmic flow of business activities) [8].

2.10 Data and Category Requirements

There are dissimilar classes of users namely admin, customer, and other staff. Depending
upon the category of users the access rights are obvious. It means if the user is an
administrator then he/she can be able to adjust the data delete, add, etc. All other users expect
the restaurant only have the right to save the info about the database. The database stores the
details of the customer’s proper time. Admin should be able to update restaurant records.

8
 CHAPTER 3
DATA DEFINITIONS AND FORM DESIGN

9
3.1 Data Definition
This section describes the tables that are used in the Online E-Commerce management system.

3.2 Database Restaurant Online Management System

Different types of information tables that are used in this system are discussed.

3.4 Table structure for comment

meta
The comment metadata is the information you provide to viewers about each comment.

3.5 Table structure for comments

A comment is a text note added to the source code to provide explanatory information, usually
about the function of the code.

10
 3.6 Table structure for links
A link is a selectable connection from one word, picture, or information object to another.

3.7 Table structure for newsletter

A newsletter is a regularly distributed publication generally about one main topic that is of
interest to its subscribers

3.8 Table structure for newsletter emails

The email newsletter is a powerful marketing and communication tool that has various useful
functions. It reminds your users about you; it informs users about your products; it tells them
what you have been up to; and it helps you build a unique relationship with them.

11
 3.9 Table structure for newsletter stats
Newsletter stats (statistics) a number of newsletter open rate and CTR statistics. Statistics and
studies show the benefits of email marketing.

3.10 Table structure for options

An option is a contract that gives the buyer the right, but not the obligation, to buy or sell an
underlying asset at a specific price on or before a certain date.

3.11 Table structure for posts

A post refers to an article published on an Internet newsgroup, forum, or other bulletin board
area. It is also the act of publishing such a message.

12
 3.12 Table structure for slides
Slides the images horizontally or vertically (usually horizontally) ... of all or featured images
are up to the designer of the application in mind.

3.13 Table structure for static slides

a website design has static or sliding banners is one of those. meaning it will require a user to
either wait for the slide

3.14 Table structure for term

Taxonomy is a set of terms that describe various types of military operations and equipment.

3.15 Table structure for users

A user is another name of an account capable of logging into a computer or service.

13
3.16 Table structure for order items
Product shipping classes are a great way to group similar products for shipping. For
example, if your store sells a couple of very large, bulky items you may want to put them in
their own shipping class with their own unique shipping cost.

3.17 Table structure for tax rate

Tax rates are one of the first tasks you want to perform when setting up a store. Taxes can be
a complex matter, but WooCommerce aims to make setup as straightforward as possible.

3.18 Login page

Logins are used to gain access to and control of computers, networks, and bulletin boards, as
well as other services and devices.

Figure: 5.1 Login page

14
 3.19 Home page
A home page or a start page is the initial or main web page of a website or a browser. The
initial page of a website is sometimes called the main page as well.

Figure: 5.2 Home page

3.20 Search bar

A search box is usually a single-line text box with the dedicated function of accepting user input to be a Web
search engine

Figure: 5.5 Search bar

15
3.21 About Us page
About Us pages should provide information about the Restaurant. This is important as it will
define the parameters of what is allowed.

Figure: 5.3 About Us page

3.22 Shop page

“Shop” page which will be used to display your recent products but also used in the themes.

Figure: 5.4 Shop page

16
 3.23 Categories
A class or division of people or things regarded as having particular shared characteristics.

3.24 Social Share

Sending photos, videos, product recommendations, and Web site links to friends with social
networking accounts.

Figure: 5.9 Social Share

3.25 Footer Link

Site after site that we visited lately has been showing a tendency to use footer links to run
their internal SEO link structure and anchor text.

17
 CHAPTER 4
MAINTENANCE

18
4.1 Software Maintenance
Software maintenance in software engineering is the modification of a software product after
delivery to correct faults, improve performance, or other attributes.[1]
A common perception of maintenance is that it merely involves fixing defects. However, one
study indicated that over 80% of maintenance effort is used for non-corrective actions.[2] This
perception is perpetuated by users submitting problem reports that in reality are functionality
enhancements to the system. More recent studies put the bug-fixing proportion closer to 21%.
[16].

4.2 Software Maintenance Process

This section describes the six software maintenance processes:

1. The implementation process contains software preparation and transition activities,

such as the conception and creation of the maintenance plan; the preparation for
handling problems identified during development; and the follow-up on product
configuration management.
2. The problem and modification analysis process, which is executed once the
application has become the responsibility of the maintenance group. The maintenance
programmer must analyze each request, confirm it (by reproducing the situation) and
check its validity, investigate it and propose a solution, document the request and the
solution proposal, and finally, obtain all the required authorizations to apply the
modifications.
3. The process considering the implementation of the modification itself.
4. The process acceptance of the modification, by confirming the modified work with
the individual who submitted the request in order to make sure the modification
provided a solution.
5. The migration process (platform migration, for example) is exceptional and is not part
of daily maintenance tasks. If the software must be ported to another platform
without any change in functionality, this process will be used and a maintenance
project team is likely to be assigned to this task.
6. Finally, the last maintenance process, also an event that does not occur on a daily
basis, is the retirement of a piece of software [16].

The maintenance process model described in IEEE, the Standard for Software Maintenance,
starts the software maintenance effort during the post-delivery stage and discusses items such
as planning for maintenance and measures outside the process model. That process model
with the IEEE maintenance faces is depicted in Figure.

19
 Figure: 6.1 Maintenance process model

4.3 Maintenance Activities

In the late 1970s, a famous and widely cited survey study by Lientz and Swanson exposed the
very high fraction of life-cycle costs that were being expended on maintenance. They
categorized maintenance activities into four classes:

• Adaptive Maintenance
• Corrective Maintenance
• Perfective Maintenance
• Preventive Maintenance

Corrective maintenance: Reactive modification of a software product performed after

delivery to correct discovered problems.

Adaptive maintenance: Modification of a software product performed after delivery to keep a

software product usable in a changed or changing environment.

Perfective maintenance: Modification of a software product after delivery to improve

performance or maintainability.

20
Preventive maintenance: Modification of a software product after delivery to detect and
correct latent faults in the software product before they become effective faults.

There is also a notion of pre-delivery/pre-release maintenance which is all the good things
you do to lower the total cost of ownership of the software. Things like compliance with
coding standards that include software maintainability goals. The management of coupling
and cohesion of the software. The attainment of software supportability goals (SAE JA1004,
JA1005, and JA1006 for example). Note also that some academic institutions are carrying out
research to quantify the cost of ongoing software maintenance due to the lack of resources
such as design documents and system/software comprehension training and resources
(multiply costs by approx. 1.5-2.0 where there is no design data available) [16].

Figure: 6.2 Maintenance Activities

4.4 Difficulties of Maintenance

There are four key difficulties that can sluggish down the maintenance process.

• Formless code
• Maintenance programmers having inadequate knowledge of the system
• Documentation being inattentive
• Out-of-date or inadequate

The achievement of the maintenance stage trusts on these problems being earlier in the life
sequence. In our system, we try to follow the maintenance phases to complete those activities.
The code is structured and we have adequate knowledge about programming [16].

21
CHAPTER 5
CONCLUSION

22
5.1 Conclusion
The Online E-Commerce management system (ORMS) is for computerizing the working in a
restaurant. It is a great improvement over the manual system. The computerization of the
system has sped up the process. In the current system, the front office management is very
slow. The restaurant managing system was thoroughly checked and tested with dummy data
and thus is found to be very reliable. The software takes care of all the requirements of an
average restaurant and is capable of providing easy and effective storage of information
related to customers that come to the restaurant. It provides home delivery facilities to the
customer. It also billing facilities such as cash on or pay with brash. The system also provides
location flexibility in Dhaka city.

5.2 Limitations
For upcoming improvement, there are some proposals to advance our project abilities.

• There is no email verification system.

• There is no online bill payment system.
• There is no security protection such as SSL, or Sitelock.
• The SMS alert system is not available right now.
• There is no online secured payment-getting system.

5.3 Future Plans

• We will add more features to improve our project.
• There will be an email verification system.
• We will add an SSL security system.
• A new product update newsletter will be added.
• SMS alert system is easier for the customer.
• We also work on online payment gateway integration.
• Additionally, it is just a beginning. Supplementary systems may be used in various other
types of reviewing processes.

23
24