A PROJECT REPORT ON

RESTAURANT XYZ

DEVELOPED AT MIU

FOR THE PARTIAL FULLFILLMENT OF THE

REQUIREMENTS FOR THE

EXAM IN E-COMMERCE

First Semester First Year

IN

MIT

SUBMITTED BY

TURYATUNGA MICHEAL

SUBMITTED TO

MADAM KYOMUHENDO CHAROTTE

MIU
 ABSTRAT

The XYZ Restaurant Management system is a capstone project that aims

towards developing an all-in-one application that addresses the various
problems and challenges faced by high-end XYZ Restaurant owners today.

In order to achieve this goal, this project addresses various aspects of the
modern XYZ Restaurant Management System in Uganda.

All in all, this project main aim is to reduce the time overhead in high-end
management XYZ Restaurant s by providing an alternative to the traditional
management system based on physical record keeping and paper work.

"Online XYZ Restaurant Management System (ORMS)" is web application to

XYZ Restaurant management. This system wakes to provide service facility
to XYZ Restaurant and also to the customer. The services that are provided
is food ordering and reservation table management by the customer through
the system online, customer information management and waiter
information management, menu information management and report. Main
objective builds the system this is to provide ordering and reservation
service by online to the customer. With this system online, ordering and
reservation management will become easier and systematic to replace
traditional system where are still using paper. Furthermore, this system is
applicable any time and were also customer. During the development of
ORMS, the methodology being used is Prototyping model. Each process
during the development process is followed by each phase in Prototyping
model. Software and hardware used are AppServ, Macromedia Dreamweaver
8, Microsoft Visio 2003, Apache serve and MySQL database. Furthermore,
this project will develop for Restaurant XYZs management and enhance
business in system business by online. Others, this project to facilitate
customer for make online ordering and reservation.

i
Contents
ABSTRAT............................................................................................................................................... i
PROJECT PROFILE .......................................................................................................................... v
HARDWARE REQUIREMENTS .................................................................................................... vi
Technical Details Software (Requirements) ......................................................................... vi
1. Introduction ................................................................................................................................... 1
1.1 Introduction ........................................................................................................................ 1
1.2 Overview ................................................................................................................................... 1
1.3 Objective............................................................................................................................... 2
1.4 Scope ......................................................................................................................................... 2
1.5 Definitions ................................................................................................................................ 2
1.6 Additional Information ......................................................................................................... 2
2.0 General Description .................................................................................................................. 3
2.1 Functional Requirement ...................................................................................................... 3
2.2 Needs of XYZ Restaurant system ................................................................................. 3
2.3 The sequential phases in Waterfall model ................................................................................... 4
2.4 Tools and Technique used in building XYZ Restaurant system ..................................................... 5
2.5 Description .................................................................................................................................... 8
2.6 Technical Issues ............................................................................................................................ 9
2.6.1 Interface Requirement .......................................................................................................... 9
2.6.2 GUI ......................................................................................................................................... 9
2.6.3 Hardware Interface ............................................................................................................... 9
2.6.4 Software Interface................................................................................................................. 9
2.7 Performance Requirement ........................................................................................................ 10
2.8 Design Constrain......................................................................................................................... 10
2.9 Another Non-Functional requirement....................................................................................... 10
2.9.1 Security ................................................................................................................................ 10
2.9.2 Reliability ............................................................................................................................. 10
2.9.3 Availability ........................................................................................................................... 10
2.9.4 Maintainability .................................................................................................................... 11
2.9.5 Portability ............................................................................................................................ 11
2.10 Operational Scenario ............................................................................................................... 11
3.0TASK AND ACTIVITIES PERFORMED ................................................................................................. 12
3.1 Profile of Problems ..................................................................................................................... 12
3.2 Structure of the project.............................................................................................................. 12
3.3 Scope and Feasibility .................................................................................................................. 13

ii
 3.4 System Analysis .......................................................................................................................... 13
3.5 System Design ............................................................................................................................ 14
3.5 Implementation.......................................................................................................................... 14
3.6 Test Generation .......................................................................................................................... 14
3.7 Specification Requirement ......................................................................................................... 14
4.0 Data Flow Diagrams .................................................................................................................... 15
Level-1 ............................................................................................................................................... 15
USE CASE FOR XYZ RESTAURANT MANAGEMENT ............................................................................ 16
STATECHART FOR XYZ RESTAURANT MANAGEMENT ....................................................................... 17
Sequence Diagram for customer ...................................................................................................... 18
SEQUENCE DIAGRAM FOR XYZ RESTAURANT MANAGEMENT ......................................................... 19
Schema Diagram ............................................................................................................................... 19
COMPONENT DAIGRAM FOR XYZ RESTAURANT MANAGEMENT ..................................................... 20
DEPLOYMENT DIAGRAM FOR XYZ RESTAURANT MANAGEMENT .................................................... 20
Database Life Cycle (BLC) .................................................................................................................. 21
ER DIAGRAM FOR XYZ RESTAURANT MANAGEMENT....................................................................... 21
CLASS DIAGRAM FOR XYZ RESTAURANT MANAGEMENT ................................................................. 22
ACTIVITY DIAGRAM FOR XYZ RESTAURANT MANAGEMENT ............................................................ 22
Use case Diagram of Ecommerce Conceptual model ....................................................................... 23
Conceptual Design ........................................................................................................................ 23
Use case Diagram of Ecommerce Logical model .............................................................................. 24
Logical Design................................................................................................................................ 24
Use case Diagram of Ecommerce physical model ............................................................................ 25
Web Application images: ...................................................................................................................... 26
Fig 1: website view (customer page) Home page ......................................................................... 26
Fig 2: (customer page) About us ................................................................................................... 26
Fig 3: (customer page) contact us ................................................................................................. 27
Fig 4: (customer page) Signup page .............................................................................................. 27
Fig 5: (customer page) Login page ................................................................................................ 28
Fig 6: (customer page) welcome page after login......................................................................... 28
Fig 7: (customer page) food items ................................................................................................ 29
Fig 8: (customer page) shopping cart ........................................................................................... 29
Fig 9: (customer page) payment methods .................................................................................... 30
Fig 10: (customer page) Credit Card Number ............................................................................... 30
Fig 11: (customer page) pay on delivery ....................................................................................... 31
Fig 12: (customer page) header and footer .................................................................................. 32

iii
Fig 13: (Admin page) login ............................................................................................................ 32
Fig 14: (Admin page) ..................................................................................................................... 33
Fig 15: (Admin page) view items ................................................................................................... 33
Fig 16: (Admin page) Add food ..................................................................................................... 34
Fig 17: (Admin page) Edit food...................................................................................................... 34
Fig 18: (Admin page) Delete food ................................................................................................. 35
Fig 19: (Admin page) view orders ................................................................................................. 35
Fig 20: (Admin page) Billings ......................................................................................................... 36
Fig 21: (Admin page) Sales ............................................................................................................ 36
Fig 22: (Admin page) Customers ................................................................................................... 37
Fig 23: (Admin page) Add Branch.................................................................................................. 37
Fig 24: (Admin page) Database list of database tables in the system .......................................... 38
Fig 25: (Admin page) tables displayed (desc)................................................................................ 38
Fig 26: (Admin page) if we select all from food ............................................................................ 39

iv
 PROJECT PROFILE

PROJECT: XYZ Restaurant Management System.

OBJECTIVE: Reduce Time Wastage at XYZ Restaurant

INSTITUTE: MIU

FRONT END: Bootstrap 4, jQuery,

PHP 7.1.3, Laravel 5.6, MySql, xampp, Css,

BACK END:
Workbench, Draw.IO

DOCUMENTATION TOOL: Ms-Word, Excel, Draw.io, workbench

DEVELOPED BY: TURYATUNGA MICHEAL

GUIDED BY: GOOGLE

SUBMITTED TO: MADAM CHLT

v
 HARDWARE REQUIREMENTS

Technical Details Hardware (Requirements)

Hardware
Particulars
Requirements

Processor Brand Intel, Amd etc.

Processor Type I3 Processor +

Processor Speed 1.5 GHz +

RAM Size 2 GB +

Memory Type DDR3 +

Hard Drive Size 500 GB +

Technical Details Software (Requirements)

Particulars Software Requirements.

Operating System Windows, Linux, Mac, any

• Chrome* 36+
• Edge* 20+
Browser
• Mozilla Firefox 31+

Safari

vi
 1. Introduction

1.1 Introduction
XYZ Restaurant system is the process of ordering food from a website. The
product can be either ready-to-eat food (e.g., direct from a certified home-
kitchen, restaurant) or food that has not been specially prepared for direction
consumption (e.g., vegetables direct from a farm/garden, frozen meats. etc).
The aim of developing XYZ Restaurant system project is to replace the
traditional way of taking orders with computerized system. Another important
reason for developing this project is to prepare order summary reports quickly
and in correct format at any point of time when required.
XYZ Restaurant System has a very lot of scope. This PHP project can be used
by any restaurants or fast foods for customers for keeping their order records.
This project is easy, fast and accurate. It requires less disk space. XYZ
Restaurant System uses MYSQL Server as backend so there is not any chance
of data loss or data security. A customer can choose to have the food delivered
or for pick-up. The process consists of a customer scanning the menu items,
choosing an item, and finally choosing for pick-up or delivery. Payment is then
administered by paying with a credit card or debit card through the app or
website or in cash at the restaurant when going to pickup. The website
informs the customer of the food quality, duration of food preparation, and
when the food is ready for pick-up or the amount of time it will take for delivery

1.2 Overview
This document presents a detailed explanation of the objectives, features,
user interface and application of XYZ Restaurant Management System in real
life. It will also describe how the system will perform and under which it must
operate. In this document it will be also shown user interface. Both the
stakeholders and the developers of the system can benefit from this
document.

1
1.3 Objective
The main objective of this system is to manage the details of item category,
food, delivery address, sales, order, and shopping cart(billing). It manages all
the information about item category, customer, shopping cart, item
category. The project is totally built at administrative end and thus only the
administrator is guaranteed the access. The purpose is to build and
application program to reduce the managing of the item category, food
customers. It tracks all the delivery address ordered.

1.4 Scope
• This system will help to manage and run the XYZ Restaurant
business systematically.

• In the management system, we will provide an app that can be

used by the customers to order food.

• Customers can also give feedback through this app.

• So that owner of the XYZ Restaurant can evaluate the whole

system. This will ultimately lead to hire less waiters

1.5 Definitions
SRS- Software Requirement Specification

GUI- Graphical User Interface

Stockholder- The person who will participate in system

1.6 Additional Information

• System Admin is a person who is responsible for managing the whole
system and who has full access to the system.

• System User A person who is using or operating the system but with a
limited privilege.

• Database Collection of all the information monitored by this system.

• Field A cell within a form.

2
 2.0 General Description

It is known globally that, in today’s market, it is extremely difficult to start a

new small-scale business and live-through the competition from the well-
established and settled owners. In fast paced time of today, when everyone
is squeezed for time, the majority of people are finicky when it comes to
placing a food order. The customers of today are not only attracted because
placing an order online is very convenient but also because they have
visibility into the items offered, price and extremely simplified navigation for
the order.

2.1 Functional Requirement

This section provides requirement overview of the system. Various functional
modules that can be implemented by the system will be –

2.2 Needs of XYZ Restaurant system

Helps customer to order their food at any time. The customers will be able to
order their favourite dishes at any point of time, and as we have pointed out
earlier, that time is a minimal option, and restaurants must have a specified
system through which they can serve a huge number of customers while
making their work smoother. Ordering.co is one of the best platforms which
provides all of these platforms along with numerous innovative features
which has turned countless small and large businesses into an inspiring
leader in the online marketplace.

3
2.3 The sequential phases in Waterfall model

Requirement Gathering and analysis − All possible requirements of the

system to be developed are captured in this phase and documented in a
requirement specification document.
System Design − The requirement specifications from first phase are
studied in this phase and the system design is prepared. This system design
helps in specifying hardware and system requirements and helps in defining
the overall system architecture.

Implementation − With inputs from the system design, the system is first
developed in small programs called units, which are integrated in the next
phase. Each unit is developed and tested for its functionality, which is
referred to as Unit Testing.

Integration and Testing − All the units developed in the implementation

phase are integrated into a system after testing of each unit. Post integration
the entire system is tested for any faults and failures.

4
Deployment of system − Once the functional and non-functional testing is
done; the product is deployed in the customer environment or released into
the market.

Maintenance − There are some issues which come up in the client

environment. To fix those issues, patches are released. Also, to enhance the
product some better versions are released. Maintenance is done to deliver
these changes in the customer environment.

2.4 Tools and Technique used in building XYZ Restaurant system

• Php, Xampp, Mysqli, HTML, Bootstrap, Sublime text, Git hub, Java
Script, Css, Draw.io, Workbench, Microsoft Office

Php
Hypertext Pre-processor (or simply PHP) is a server-side scripting language
designed for Web development, but also used as a general-purpose
programming language. It was originally created by Rasmus Lerdorf in
1994,] the PHP reference implementation is now produced by The PHP
Group. PHP originally stood for Personal Home Page,] but it now stands for
the recursive acronym PHP: Hypertext Pre-processor.
PHP code may be embedded into HTML code, or it can be used in
combination with various web template systems, web content management
systems, and web frameworks. PHP code is usually processed by a PHP
interpreter implemented as a module in the web server or as a Common
Gateway Interface (CGI) executable. The web server combines the results of
the interpreted and executed PHP code, which may be any type of data,
including images, with the generated web page. PHP code may also be
executed with a command-line interface (CLI) and can be used to implement
standalone graphical applications.
Xampp
XAMPP is a free and open-source cross-platform web server solution stack
package developed by Apache Friends, consisting mainly of the Apache
HTTP Server, MariaDB database, and interpreters for scripts written in the

5
PHP and Perl programming languages. XAMPP stands for Cross-Platform (X),
Apache (A), MariaDB (M), PHP (P) and Perl (P). It is a simple, lightweight
Apache distribution that makes it extremely easy for developers to create a
local web server for testing and deployment purposes. Everything needed to
set up a web server – server application (Apache), database (MariaDB), and
scripting language (PHP) – is included in an extractable file. XAMPP is also
cross-platform, which means it works equally well on
Linux, Mac and Windows. Since most actual web server deployments use
the same components as XAMPP, it makes transitioning from a local test
server to a live server extremely easy as well.
Mysqli
MySQL Workbench is a unified visual tool for database architects,
developers, and DBAs. MySQL Workbench provides data modelling, SQL
development, and comprehensive administration tools for server
configuration, user administration, backup, and much more. MySQL
Workbench is available on Windows, Linux and Mac OS X.
HTML
Hypertext Markup Language (HTML) is the standard markup language for
creating web pages and web applications. With Cascading Style Sheets (CSS)
and JavaScript, it forms a triad of cornerstone technologies for the World
Wide Web.[4]
Web browsers receive HTML documents from a web server or from local
storage and render the documents into multimedia web pages. HTML
describes the structure of a web page semantically and originally included
cues for the appearance of the document.
HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects such as interactive forms may be
embedded into the rendered page. HTML provides a means to create
structured documents by denoting structural semantics for text such as
headings, paragraphs, lists, links, quotes and other items.
Bootstrap
Bootstrap is a free and open-source front-end framework for designing
websites and web applications. It contains HTML- and CSS-based design

6
templates for typography, forms, buttons, navigation and other interface
components, as well as optional JavaScript extensions. Unlike many web
frameworks, it concerns itself with front-end development only.
Java Script
JavaScript often abbreviated as JS, is a high-level, interpreted programming
language. It is a language which is also characterized as dynamic, weakly
typed, prototype-based and multi-paradigm.
Alongside HTML and CSS, JavaScript is one of the three core technologies of
the World Wide Web. JavaScript enables interactive web pages and thus is
an essential part of web applications. The vast majority of websites use it,
and all major web browsers have a dedicated JavaScript engine to execute it.
Sublime Text 7
Sublime Text is a proprietary cross-platform source code editor with a
Python application programming interface (API). It natively supports many
programming languages and markup languages, and functions can be
added by users with plugins, typically community-built and maintained
under free-software licenses.
GitHub
GitHub is a web-based hosting service for version control using Git. It is
mostly used for computer code. It offers all of the distributed version control
and source code management (SCM) functionality of Git as well as adding its
own features. It provides access control and several collaboration features
such as bug tracking, feature requests, task management, and wikis for
every project.
GitHub offers plans for both private repositories and free accounts which are
commonly used to host open-source software projects.
Css
Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a markup language like HTML.
CSS is a cornerstone technology of the World Wide Web, alongside HTML
and JavaScript.
CSS is designed to enable the separation of presentation and content,
including layout, colors, and fonts. This separation can improve content

7
accessibility, provide more flexibility and control in the specification of
presentation characteristics, enable multiple web pages to share formatting
by specifying the relevant CSS in a separate css file, and reduce complexity
and repetition in the structural content.
Workbench
Workbench is designed to meet the operational needs of project-
oriented businesses and anyone responsible for delivering projects.
In this case I will use workbench to design my ERD diagrams and their
relationships then I will use it to create a database.

2.5 Description
Registration

If customer wants to order the food, then he/she must be registered,

unregistered user can’t go to the ordering page.

Login

Customer logins to the system by entering valid user id and password for
the ordering.

Payment

For customer there is now only one option for payment i.e Cash on delivery.
Later on, other options like credit, debit card, third party payment app like
Paytm or PayPal will also be available.

Logout

After the payment or surf the product, the customer will be logged out.

Order Confirmation

After all transaction the system can generate the confirmation message of
product and will send it on the customer mobile number and Email.

8
2.6 Technical Issues
This system will work on client-server architecture. It will require an
internet server and which will be able to run PHP application. The system
should support some commonly used browser such as IE, Google chrome
etc.

2.6.1 Interface Requirement

Various interfaces for the product could be-

1. Login Page

2. Registration Form

3. There will be a screen displaying information about menu that the

XYZ Restaurant have.

4. After all process the system will send the confirmation message to
customer.

2.6.2 GUI
1. Login Page

2. Registration Form

3. Product Page, Make Order

4. Shopping Cart

5. Confirmation

2.6.3 Hardware Interface

The System must run over the internet, all the hardware shall require to
connect internet will be hardware interface for the system. As for e.g.
Modem, WAN – LAN, Ethernet Cross-Cable.

2.6.4 Software Interface

The system is on server so it requires the any scripting language like PHP,
Java Script etc. The system requires Data Base also for the store the any
transaction of the system like MYSQL etc. system also require DNS (domain

9
name space) for the naming on the internet. At the last user need web
browser for interact with the system.

2.7 Performance Requirement

There is no performance requirement in this system because the server
request and response are depended on the end user internet connection.

2.8 Design Constrain

The system shall be built using a standard web page development tool that
conforms to Microsoft’s GUI standards like HTML, XML etc.

2.9 Another Non-Functional requirement

2.9.1 Security
The system must automatically log out all customers after a period of
inactivity.

The system should not leave any cookies on the customer’s computer
containing the user’s password.

The system’s back-end servers shall only be accessible to authenticated

administrators.

2.9.2 Reliability
The system provides storage of all databases on redundant computers with
automatic switchover.

The reliability of the overall program depends on the reliability of the

separate components. The main pillar of reliability of the system is the
backup of the database which is continuously maintained and updated to
reflect the most recent changes.

Thus, the overall stability of the system depends on the stability of container
and its underlying operating system.

2.9.3 Availability
The system should be available at all times, meaning the user can access it
using a web browser, only restricted by the down time of the server on which
the system runs. In case of a of a hardware failure or database corruption, a
replacement page will be shown. Also, in case of a hardware failure or

10
database corruption, backups of the database should be retrieved from the
server and saved by the administrator. Then the service will be restarted. It
means 24 X 7 availability.

2.9.4 Maintainability
A commercial database is used for maintaining the database and the
application server takes care of the site. In case of a failure, a re-
initialization of the program will be done. Also, the software design is being
done with modularity in mind so that maintainability can be done efficiently.

2.9.5 Portability
The application is HTML and scripting language based. So, The end-user
part is fully portable and any system using any web browser should be able
to use the features of the system, including any hardware platform that is
available or will be available in the future. An end-user is use this system on
any OS; either it is Windows or Linux. The system shall run on PC, Laptops,
and PDA etc.

2.10 Operational Scenario

The customer wants to buy item. The system shows all product categories to
customer. If customer select item, then they listed in shopping cart for
buying. The payment will made with Cash on delivery and Online payments

11
 3.0TASK AND ACTIVITIES PERFORMED
3.1 Profile of Problems
In the present system all work is done on paper. The order report, food
category and food are stored in register and at the end of the session the
reports are generated. We are not interested in generating report in the
middle of the session or as per the requirement because it takes more time
in calculation. The existing system is not user friendly because the retrieval
of data is very slow and data is not maintained efficiently. We require more
calculations to generate the report so it is generated at the end of the
session. All calculations to generate report is done manually so there is
greater chance of errors.

3.2 Structure of the project

• Before Login
• Login
• Register
• Administrator Login
• About Us
• Contact Us
• After Administrator Login
• Edit Website Details
• Add Food Items
• Remove food Items
• Add Restaurants
• Delete Restaurant
• Logout
• After User Login
• My Profile
• Menu
• Search Food Items
• My Cart
• Order
• Logout

12
3.3 Scope and Feasibility
This activity is also known as the feasibility study. It begins with a request
from the user for a new system. It involves the following:
• Identify the responsible user for a new system
• Clarify the user request
• Identify deficiencies in the current system
• Establish goals and objectives for the new system
• Determine the feasibility for the new system
• Prepare a project charter that will be used to guide the remainder of
the Project

3.4 System Analysis

It is a process of collecting and interpreting facts, identifying the problems,
and decomposition of a system into its components.
System analysis is conducted for the purpose of studying a system or its
parts in order to identify its objectives. It is a problem-solving technique that
improves the system and ensures that all the components of the system
work efficiently to accomplish their purpose.
The objective of the system analysis activity is to develop structured system
specification for the proposed system. The structured system specification
should describe what the proposed system would do; independent of the
technology, which will be used to implement these requirements. The
structured system specification will be used to implement these
requirements.
The essential model may itself consist of multiple models, modelling
different aspect of the system. The data flow diagrams may model the data
and their relationships and the state transition diagram may model time
dependent behaviour of the system. The essential model thus consists of the
following.
• Context diagram
• Levelled data flow diagrams
• Process specification for elementary bubbles
• Data dictionary for the flow and stores on the DFDs.

13
3.5 System Design
System design involves transformation of the user implementation model
into software design. The design specification of the proposed system
consists of the following:
• Database scheme
• Structure charts
• Pseudo codes for the modules in structure charts

3.5 Implementation
This activity includes programming, testing and integration of modules into
a progressively more complete system. Implementation is the process of
collect all the required parts and assembles them into a major product.

3.6 Test Generation

This activity generates a set of test data, which can be used to test the new
system before accepting it. In the test generation phase, all the parts are
come which are to be tested to ensure that system does not produce any
error. If there are some errors then we remove them and further it goes for
accepting.

3.7 Specification Requirement

External Interfaces
This interface will be actual interface through which the user will
communication with the application and perform the desired tasks.

Admin login
I.D:
Role: Admin wishes to login to the system
Precondition: Username and Password
Success end Condition: Main option of screen display
Failed end Condition: User has entered incorrect Username and password

14
4.0 Data Flow Diagrams
Level-0

Level-1

15
USE CASE FOR XYZ RESTAURANT MANAGEMENT

16
STATECHART FOR XYZ RESTAURANT MANAGEMENT

17
Sequence Diagram for customer

18
SEQUENCE DIAGRAM FOR XYZ RESTAURANT MANAGEMENT

Schema Diagram

19
COMPONENT DAIGRAM FOR XYZ RESTAURANT MANAGEMENT

DEPLOYMENT DIAGRAM FOR XYZ RESTAURANT MANAGEMENT

20
Database Life Cycle (BLC)
According to Rob and Coronel (2004), Database Life Cycle (DBLC) contains
six
phases which are; database initial study, database design, implementation
and loading,
testing and evaluation, operation, and maintenance and evaluation. Figure
2.6 shows the
mechanism of DBLC and explanation for each of the phases.

ER DIAGRAM FOR XYZ RESTAURANT MANAGEMENT

21
CLASS DIAGRAM FOR XYZ RESTAURANT MANAGEMENT

ACTIVITY DIAGRAM FOR XYZ RESTAURANT MANAGEMENT

22
Use case Diagram of Ecommerce Conceptual model
Conceptual Design
Data modelling is used to create an abstract database structure. The system
that wants to be built must produce a report, queries data and database
manipulating must be run smoothly.
Besides, the system can produce the report, queries data, online ordering
result which is calculated price by the system. Administrator will keep track
of all data inserted into the database. Customer also can insert their data
and save direct into database. Furthermore, the system can be used to
update the database, manipulating and retrieve data.

23
Use case Diagram of Ecommerce Logical model
Logical Design
Context Diagram and Data Flow Diagram (DFD) are designed based on
ORMS
system that wanted to be built. Microsoft Visio 2003 is used to design both
of the
diagrams. Before identified the business rules, entities must be listed.

24
Use case Diagram of Ecommerce physical model

25
Web Application images:
Fig 1: website view (customer page) Home page

Fig 2: (customer page) About us

26
Fig 3: (customer page) contact us

Fig 4: (customer page) Signup page

27
Fig 5: (customer page) Login page

Fig 6: (customer page) welcome page after login

28
Fig 7: (customer page) food items

Fig 8: (customer page) shopping cart

29
Fig 9: (customer page) payment methods

Fig 10: (customer page) Credit Card Number

30
Fig 10.1: (customer page) Mobile Money

Fig 11: (customer page) pay on delivery

31
Fig 12: (customer page) header and footer

Fig 13: (Admin page) login

32
Fig 14: (Admin page)

Fig 15: (Admin page) view items

33
Fig 16: (Admin page) Add food

Fig 17: (Admin page) Edit food

34
Fig 18: (Admin page) Delete food

Fig 19: (Admin page) view orders

35
Fig 20: (Admin page) Billings

Fig 21: (Admin page) Sales

36
Fig 22: (Admin page) Customers

Fig 23: (Admin page) Add Branch

37
Fig 24: (Admin page) Database list of database tables in the system

Fig 25: (Admin page) tables displayed (desc)

38
Fig 26: (Admin page) if we select all from food

39