Module Code : CT026-3-1-SAAD –Systems Analysis & Design

Intake Code : APD-APU2F2211

Lecturer Name : Mr. Sivananthan Chelliah
Hand in Date :
Tutorial No. : T-19
Group No. : 1
Group Leader : Sk Abdur Rahman Ridoy

Student ID Student Name

TP061108 SK Abdur Rahman Ridoy
TP072860 Lim K’ng Wye
TP066555 Yuma Higa
TP066725 Yeoh Aun Liang
Systems Development Methods (CT046-3-2-SDM)

Table of Contents

1.0 Introduction ..........................................................................................................1

1.1 Background ................................................................................................................ 1

1.1.1 Logo .................................................................................................................................................2

1.2 Vision, Mission & Motto ............................................................................................. 2

1.2.1 Vision ...............................................................................................................................................2
1.2.2 Mission .............................................................................................................................................2
1.2.3 Motto ................................................................................................................................................2

1.3 Overview of the Business Process................................................................................ 3

1.4 Problem & Proposed Solution..................................................................................... 3

1.4.1 PIECES Framework ............................................................................................... 3

1.4.1.1 Performance.................................................................................................................................3
1.4.1.2 Information ..................................................................................................................................4
1.4.1.3 Economy......................................................................................................................................4
1.4.1.4 Control .........................................................................................................................................5
1.4.1.5 Efficiency ....................................................................................................................................6
1.4.1.6 Service .........................................................................................................................................7

1.5 Identify the Problems in the existing System: ............................................................. 7

1.6 Identify the scope, Aim and objectives of the proposed System:.................................. 7
1.6.1 Scope ................................................................................................................................................9
1.6.1.1 What the System Must Do.........................................................................................................10
1.6.1.2 What the System Should Do .....................................................................................................11
1.6.1.3 What the System Could Do .......................................................................................................11
1.6.1.4 What the System Won’t Do.......................................................................................................12
1.6.2 Aims & Objectives: ........................................................................................................................12

2.0 Project Planning .................................................................................................13

2.1 Project Management Table ....................................................................................... 13

2.2 Gantt Chart .............................................................................................................. 13

2.3 Workload Matrix ...................................................................................................... 13

[
[ii]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Development Methods (CT046-3-2-SDM)

3.0 Feasibility Study ..................................................................................................13

3.1 Operational, Technical, Economic and Schedule Feasibility ..................................... 13

3.1.1 Operational Feasibility ...................................................................................................................13
3.1.2 Technical Feasibility ......................................................................................................................13
3.1.3 Economic Feasibility ......................................................................................................................14
3.1.4 Schedule Feasibility .......................................................................................................................15

4.0 Objective of the Proposed System .........................................................................15

4.1 Functional Requirements .......................................................................................... 15

4.2 Non-Functional Requirements .................................................................................. 15

4.2.1 Usability .........................................................................................................................................16
4.2.2 Reliability .......................................................................................................................................16
4.2.3 Security ..........................................................................................................................................16
4.2.4 Scalability.......................................................................................................................................16
4.2.5 Performance ...................................................................................................................................16

5.0 Design Diagram ..................................................................................................16

5.1 Context Diagram ...................................................................................................... 16

5.2 Level-0 DFD ............................................................................................................. 16

5.3 ERD .......................................................................................................................... 16

6.0 Interface Design ..................................................................................................17

6.1 Throw-Away Prototype ............................................................................................ 17

6.1.1 User Registration............................................................................................................................17
6.1.2 Menu Selection...............................................................................................................................17
6.1.3 Order Placement .............................................................................................................................17
6.1.4 Driver Tracking ..............................................................................................................................17
6.1.5 Online Payments ............................................................................................................................17
6.1.6 Reporting ........................................................................................................................................17

6.2 GUI Design ............................................................................................................... 17

6.2.1 Clear and Intuitive Navigation .......................................................................................................17
6.2.2 Consistent Design Elements...........................................................................................................18
6.2.3 Responsive Design .........................................................................................................................18
6.2.4 Error Handling and Notification ....................................................................................................18

[
[iii]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Development Methods (CT046-3-2-SDM)

6.2.5 Accessibility Considerations ..........................................................................................................18

[
[iv]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

1.0 Introduction
1.1 Background
Case Study: WAITERS ON WHEELS(WOW): COMPUTERIZED DELIVERY
TRACKING SYSTEM
Waiters on Wheels (WOW) is a restaurant meal-delivery service started in 1997 by Sue
and Tom Bickford. The Bickfords both worked for restaurants while in college and
always dreamed of opening their own restaurant. But unfortunately, the initial
investment was always out of reach. The Bickfords noticed that many restaurants offer
takeout food, and some restaurants, primarily pizzerias, offer home delivery service.
Many people they met, however, seemed to want home delivery service but with a more
complete food selection.
Waiter on Wheels was conceived as the best of both worlds for Sue and Tom – a
restaurant service but without the high initial investment. The Bickfords contracted with
a variety of well-known restaurants in town to accept orders from customers and to
deliver the complete meals. After the restaurant prepares the meal to order, it charges
Waiters on Wheels a wholesale price, and the customer pays retail plus a service charge
and tip. Waiters on Wheels started modestly, with only two restaurants and one delivery
driver working the dinner shift. Business rapidly expanded, and the Bickfords realized
they needed a customer computer system to support their business operations. They
hired your consultant firm to help them define what sort of a system they needed.
Sue described the current system as such “When a customer calls in wanting to order,
I need to record it and get the information to the right restaurant. I need to know which
driver to ask to pick up the order, so I need drivers to call in and tell me when they are
free. Sometimes customers call back wanting to change their orders, so I need to get
my hands on the original order and notify the restaurant to make the change.”
Tom continued, “The drivers get the copy of the bill directly from the restaurant when
they pick up the meal, which should agree with our calculations. The drivers collect the
amount plus a service charge. When drivers report in at closing, we add up the money
they have and compare it to the records we have. After all drivers report in, we need to
create a deposit slip for the bank for the day’s total receipts. At the end of each week,
we calculate what we owe each restaurant at the agreed-to-wholesale price and send
them a statement and check.”

[
[i]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

1.1.1 Logo

1.2 Vision, Mission & Motto

1.2.1 Vision
“To be the leading meal-delivery service, offering diverse culinary experiences
from local restaurants right to our customers’ doorsteps with the promise of
quality, convenience and exceptional service.”
1.2.2 Mission
“To simplify our customers’ lives as well as to satisfy our customers’ hunger by
providing them with a seamless online platform to order from a wide array of
local restaurants. We strive to ensure prompt and reliable delivery services that
exceed customer expectations every time.”
1.2.3 Motto
“Delivering Delight!”

[
[ii]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

The motto is a succinct and catchy phrase that encapsulates the company’s
commitment to delivering not just meals but also a delightful experience to its
customers. It complements the vision and mission by summarizing the
company’s overall ethos in a memorable way.
1.3 Overview of the Business Process
Waiters on Wheels acts as an intermediary between customers and partner restaurants,
offering a wider food selection and delivery service. The current system involves
manual processes for order management, driver coordination, payment collection, and
financial transactions. Our goal is to design and develop a computerized delivery
tracking system to streamline operations and improve efficiency.
1.4 Problem & Proposed Solution
1.4.1 PIECES Framework
The PIECES framework is a comprehensive approach used in information
system analysis to identify and address potential problems and challenges. It
focuses on six key dimensions: Performance, Information, Economy, Control,
Efficiency, and Service. By analysing each dimension, organizations can gain
valuable insights into the current system's shortcomings and propose effective
solutions. In this section, we will discuss each dimension of the PIECES
framework in detail.
1.4.1.1 Performance
1.4.1.1.1 Throughput: The current system lacks the necessary infrastructure
and processes to handle a high volume of orders. As a result, there
are delays in order processing, leading to customer dissatisfaction
and potential revenue loss.
1.4.1.1.2 Solution: Develop an online ordering system with automated order
routing. This solution will enable faster and more efficient order
processing by automatically assigning orders to the most suitable
drivers or restaurants. By optimizing the routing process, orders can
be processed more quickly, improving overall throughput.
1.4.1.1.3 Response Time: Customers expect real-time updates on the status of
their orders and the ability to make changes if needed. However, the

[
[iii]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

current system lacks efficient communication channels, resulting in

delays and frustration for customers.
1.4.1.1.4 Solution: Implement real-time communication between customers,
restaurants, and drivers. This can be achieved through a mobile
application or web portal that allows customers to track their orders,
receive updates on estimated delivery times, and make changes or
cancellations if necessary. By providing timely and transparent
information, response time can be significantly improved.
1.4.1.2 Information
1.4.1.2.1 Data Accuracy: The reliance on manual processes increases the
likelihood of human errors in recording and calculating orders. This
can result in inaccurate order details, incorrect billing, and potential
financial losses.
1.4.1.2.2 Solution: Introduce a centralized database to store and manage order
information. This will allow for automated data capture, validation,
and calculations, minimizing the risk of errors and ensuring data
accuracy. By automating these processes, the system can provide
more reliable and consistent information.
1.4.1.2.3 Information Access: Without a centralized system, stakeholders
such as customers, restaurants, and drivers may face challenges in
accessing up-to-date and relevant order information. This can lead
to miscommunication, order errors, and delays.
1.4.1.2.4 Solution: Create a secure web portal or mobile application where
stakeholders can access order details in real-time. By providing a
user-friendly interface and role-based access controls, customers can
view their order status, restaurants can access order details for
preparation, and drivers can receive clear instructions for delivery.
This improved information access enhances collaboration and
reduces errors.
1.4.1.3 Economy
1.4.1.3.1 Cost Efficiency: The reliance on manual calculations and
reconciliation processes can be time-consuming, error-prone, and

[
[iv]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

inefficient. This leads to additional costs and potential financial

discrepancies.
1.4.1.3.2 Solution: Automate financial calculations, payment collection, and
reconciliation processes. By integrating an automated payment
system, the system can accurately calculate the total order cost,
including service charges and taxes. This automation streamlines
financial processes, reduces human errors, and improves cost
efficiency.
1.4.1.3.3 Resource Optimization: The current system lacks an efficient
method for allocating drivers to orders, resulting in suboptimal
resource utilization and potentially inefficient delivery routes.
1.4.1.3.4 Solution: Implement a driver tracking system that optimizes driver
assignments based on factors such as location, availability, and order
volume. By leveraging real-time data and algorithms, the system can
dynamically assign drivers to orders, ensuring efficient resource
allocation and optimal delivery routes. This improves overall
resource optimization and reduces operational costs.
1.4.1.4 Control
1.4.1.4.1 Error Prevention: Relying on manual processes for order
management, calculations, and data entry increases the risk of
human errors. This can lead to order inaccuracies, financial
discrepancies, and potential customer dissatisfaction.
1.4.1.4.2 Solution: Incorporate validation checks and automated error
handling mechanisms into the system. By implementing data
validation rules and automated error detection, the system can
identify and prevent common errors, ensuring data integrity and
accuracy. Additionally, providing clear guidelines and training to
users can help minimize human errors during manual processes.
1.4.1.4.3 Compliance: Without proper control mechanisms in place, the
system may fail to comply with financial regulations, leading to
legal and financial consequences. This includes issues such as

[
[v]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

inaccurate financial reporting, improper handling of customer

payments, and non-compliance with data privacy regulations.
1.4.1.4.4 Solution: Implement control features and auditing mechanisms to
ensure compliance with financial regulations and policies. This
includes implementing secure payment processing, adhering to data
protection guidelines, and conducting regular audits to identify and
address any compliance gaps. By ensuring compliance, the system
can protect the company's reputation and avoid legal and financial
penalties.
1.4.1.5 Efficiency
1.4.1.5.1 Process Streamlining: The manual nature of the current system leads
to inefficiencies due to redundant tasks, excessive paperwork, and
manual data entry. This results in increased processing time, higher
labour costs, and a higher likelihood of errors.
1.4.1.5.2 Solution: Streamline the order management process by automating
repetitive tasks such as order routing, driver assignment, and
financial calculations. By implementing an integrated system that
automates these processes, the system can reduce manual
intervention, improve accuracy, and increase overall efficiency. This
streamlining improves operational efficiency, reduces costs, and
enhances customer satisfaction.
1.4.1.5.3 Task Automation: Manual tracking of order status, driver
availability, and delivery progress can be time-consuming and prone
to errors. This can result in delays in providing accurate updates to
customers and inefficient coordination between drivers and the
company.
1.4.1.5.4 Solution: Develop a driver tracking system that provides real-time
updates on order status, driver availability, and delivery progress. By
implementing GPS tracking or a similar technology, the system can
automate the tracking process and provide accurate and timely
updates to customers and stakeholders. This automation improves

[
[vi]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

task efficiency, reduces manual effort, and enhances overall

operational efficiency.
1.4.1.6 Service
1.4.1.6.1 Customer Experience: The current system lacks user-friendly
interfaces, real-time updates, and effective communication channels,
leading to a suboptimal customer experience. Customers may face
difficulties in placing orders, tracking their status, and
communicating with the company.
1.4.1.6.2 Solution: Enhance the customer experience through an intuitive
online ordering platform that provides a seamless ordering process.
Implement features such as real-time order tracking, automated
notifications, and customer support channels to address customer
inquiries and concerns promptly. By improving the customer
experience, the system can increase customer satisfaction and
loyalty.
1.4.1.6.3 Stakeholder Collaboration: The lack of efficient communication and
collaboration channels between customers, restaurants, drivers, and
the company can result in miscommunication, order errors, and
delays. This affects service quality and overall operational
efficiency.
1.4.1.6.4 Solution: Implement a communication platform that facilitates
seamless collaboration between customers, restaurants, and drivers.
This can include a messaging system, notifications, and shared order
information. By improving stakeholder collaboration, the system
can streamline operations, reduce errors, and enhance service
quality.
1.5 Identify the Problems in the existing System:
1.6 Identify the scope, Aim and objectives of the proposed System:
After a detailed analysis using the PIECES framework, the following problems have
been identified in the existing system:

[
[vii]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

Dimension Problem Cause Effect

Performance Inefficient order Lack of automated Delays in order

management order management processing and
process system inaccuracies

Lack of driver Lack of a driver Delays in driver

availability availability allocation and order
information tracking system deliveries

Information Fragmented Lack of a Data redundancy

customer centralized and difficulties in
information customer database accessing customer
profiles

Inadequate Lack of effective Miscommunication

information communication and order errors
sharing between channels and
stakeholders systems
Economy Manual Reliance on manual Financial
calculations and processes for inefficiencies and
reconciliation financial potential
processes calculations discrepancies

Manual driver Lack of an efficient Suboptimal

coordination and driver allocation resource allocation
scheduling system and inefficient
routes

Control Human errors and Reliance on manual Order inaccuracies,

inconsistencies in processes for order financial
manual processes management discrepancies,

[
[viii]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

customer
dissatisfaction

Absence of Lack of control Non-compliance

control features mechanisms with financial
and auditing leading to non- regulations and
mechanisms compliance potential penalties

Efficiency Multiple manual Lack of process Increased

steps and automation and processing time,
redundant tasks integration higher labor costs,
and errors

Manual order Lack of automated Inefficiencies and

tracking and status tracking and real- delays in providing
updates time updates accurate order
updates

Service Customer Inadequate user- Customer

challenges in friendly interfaces dissatisfaction and
order placement, and communication potential loss of
tracking, and channels business
communication
Limited Lack of efficient Miscommunication,
communication communication and order errors, and
and collaboration collaboration delays
among channels
stakeholders

1.6.1 Scope
The proposed system for Waiters on Wheels aims to automate and streamline
the entire order management and delivery process, providing an efficient and

[
[ix]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

user-friendly platform for customers, restaurant partners, drivers, and

administrators. The system's scope encompasses various functionalities and
features that enhance the overall experience and operational efficiency. The
following sections outline what the system must do, should do, could do, and
what it won't do.
1.6.1.1 What the System Must Do
a. Customer Registration
The system must allow customers to register online by providing their
personal information securely. This registration process will enable
customers to access the full range of services offered by Waiters on
Wheels.
b. Menu Selection and order Placement
Customers should be able to browse the menu, select desired items,
customize orders, and place them easily through the company's website
or mobile application. The system must accurately capture and store
order details.
c. Real-Time Order Tracking
The system must provide customers with real-time updates on the status
of their orders, from preparation to delivery. Customers should be able
to track the progress and estimated delivery time of their orders.
d. Driver Allocation
The system should have a driver management component that assigns
drivers to specific orders based on their availability, location, and
workload. This feature will ensure efficient delivery and optimal
utilization of driver resources.
e. Online Payment processing
The system must integrate secure online payment gateways to enable
customers to make convenient and secure payments for their orders. It
should support various payment methods and ensure the security of
sensitive customer information.
f. Financial Transactions

[
[x]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

The system should facilitate accurate financial transactions between

Waiters on Wheels, customers, and restaurant partners. It should
calculate and record the order total, service charges, and driver
payments, ensuring transparency and accuracy in financial transactions.
g. Reporting and Analysis
The system must generate comprehensive reports for Waiters on Wheels
and restaurant partners. These reports should include sales data, order
volumes, financial statements, and other relevant information to
facilitate analysis and decision-making.
1.6.1.2 What the System Should Do
a. Customer Feedback and Ratings
The system should provide a platform for customers to provide feedback
and ratings for their delivery experience. This feature will help improve
service quality and gather valuable insights for business enhancements.
b. Loyalty Programs and Discounts
The system should support loyalty programs and offer discounts or
promotional offers to incentivize customer engagement and loyalty.
These features can enhance customer retention and drive repeat
business.
c. Mobile Application for Drivers
The system should include a mobile application for drivers, enabling
them to update their availability status, receive order assignments,
navigate to delivery locations, and communicate with customers and the
support team.
d. Monthly Statements for Restaurant Partners
The system should generate monthly statements for restaurant partners,
providing a detailed breakdown of sales, order volumes, and financial
calculations. These statements will facilitate transparent and timely
payments to the restaurant partners.
1.6.1.3 What the System Could Do
a. Integration with Third-Party Delivery Platforms

[
[xi]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

The system could integrate with third-party delivery platforms to expand

the reach and customer base. This integration would allow Waiters on
Wheels to offer their services through popular delivery apps, reaching a
wider audience.
b. Customer Order History and Personalization
The system could maintain a customer order history, enabling
personalized recommendations based on their preferences and order
patterns. This feature can enhance the customer experience and
encourage repeat orders.
1.6.1.4 What the System Won’t Do
a. Physical Inventory Management: The system won't manage the physical
inventory of the partner restaurants. Instead, it will rely on the
restaurant's own inventory management systems to ensure the
availability of menu items.
b. Marketing and Advertising Campaigns: The system won't handle
marketing and advertising campaigns for Waiters on Wheels. Marketing
initiatives will be managed separately through appropriate channels.
c. Food Preparation: The system won't involve the actual food preparation
process. It will focus on facilitating the order management and delivery
aspects of the business.
1.6.2 Aims & Objectives:
1.6.2.1 Aims
a. Improve order accuracy and efficiency.
b. Enhance communication between customers, restaurants, and drivers.
c. Automate financial calculations and transactions.
d. Generate comprehensive reports for analysis and decision-making.
1.6.2.2 Objectives
a. Develop a user-friendly online ordering system with a menu selection
feature.
b. Implement a driver tracking system for efficient allocation and real-time
status updates.

[
[xii]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

c. Integrate secure online payment gateways for customer convenience and

payment processing.
d. Generate daily, weekly, and monthly sales reports for financial analysis
and performance tracking.
2.0 Project Planning
2.1 Project Management Table
2.2 Gantt Chart
2.3 Workload Matrix
3.0 Feasibility Study
3.1 Operational, Technical, Economic and Schedule Feasibility
Operational feasibility assesses whether the proposed system will meet the user's
requirements and expectations, and if it will integrate smoothly with existing
business processes. Key considerations include:
3.1.1 Operational Feasibility
Operational feasibility assesses whether the proposed system will meet
the user's requirements and expectations, and if it will integrate
smoothly with existing business processes. Key considerations include:
a. User Needs: The system should address the needs of all
stakeholders, including customers, restaurant partners, drivers,
and administrators. It should streamline operations, enhance
customer experience, and provide efficient tools for managing
orders and deliveries.
b. Business Process Integration: The system must integrate
seamlessly with existing business processes and systems. It
should not disrupt daily operations but enhance efficiency and
productivity.
c. Change Management: Operational feasibility examines the
organization's readiness for change. It considers factors such as
user training, user acceptance, and the ability to adapt to new
technologies and workflows.
3.1.2 Technical Feasibility

[
[xiii]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

Technical feasibility assesses whether the proposed system can be

implemented from a technical standpoint. It focuses on the system's
compatibility with the existing infrastructure, technology requirements,
and the availability of necessary resources. Key considerations include:
a. Hardware and Software: The system must be compatible with
the organization's existing hardware and software infrastructure.
It should not require significant hardware upgrades or expensive
software licenses.
b. Scalability: The system should have the potential to
accommodate future growth and increasing user demands. It
should be scalable and able to handle a growing customer base
and increasing order volumes.
c. Integration Capability: The system should support integration
with other systems or APIs, allowing data exchange and
interoperability with third-party platforms if required.
d. Security: Technical feasibility includes ensuring that the system
can meet security standards and protect sensitive customer
information, such as payment details and personal data.
3.1.3 Economic Feasibility
Economic feasibility evaluates the financial viability of the proposed
system. It analyses the costs and benefits associated with developing,
implementing, and maintaining the system. Key considerations include:
a. Cost Analysis: The feasibility study examines the estimated
costs involved in developing the system, including hardware,
software, development resources, training, and ongoing
maintenance costs.
b. Benefit Analysis: The study assesses the potential benefits of the
system, such as increased efficiency, cost savings, improved
customer satisfaction, and competitive advantage. It compares
the projected benefits with the estimated costs to determine the
system's return on investment (ROI).

[
[xiv]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

c. Payback Period: The feasibility study calculates the payback

period, which indicates the time required to recover the initial
investment through cost savings or increased revenue generated
by the system.
d. Risk Assessment: Economic feasibility involves identifying and
analysing potential risks and uncertainties that could impact the
financial success of the system. It includes factors such as market
conditions, competition, and regulatory changes.
3.1.4 Schedule Feasibility
Schedule feasibility evaluates whether the proposed system can be
developed and implemented within the desired timeline. It considers
factors such as resource availability, project complexity, and potential
dependencies. Key considerations include:
a. Project Timeline: The feasibility study assesses the estimated
time required for system development, testing, deployment, and
user training. It compares the project timeline with business
objectives and time constraints.
b. Resource Availability: The study analyses the availability of
skilled personnel, development tools, and infrastructure needed
for system development. It considers potential bottlenecks or
resource constraints that could impact the project timeline.
c. Dependencies: Schedule feasibility examines any dependencies
on external factors, such as regulatory approvals, data migration,
or integration with other systems. It identifies potential risks that
could cause delays or impact project milestones.
4.0 Objective of the Proposed System
4.1 Functional Requirements
Based on the requirements gathering process, the following functional requirements
have been identified
[Copy all functional requirements gathered by each team member and merge them
into a comprehensive list.]
4.2 Non-Functional Requirements

[
[xv]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

In addition to the functional requirements, the system should meet certain non-
functional requirements:
4.2.1 Usability
The system should have an intuitive user interface, easy navigation, and
clear instructions to ensure a positive user experience.
4.2.2 Reliability
The system should be reliable, ensuring minimal downtime and data
loss, and recovering quickly in case of failures.
4.2.3 Security
The system should incorporate robust security measures to protect
sensitive data, prevent unauthorized access, and ensure data privacy.
4.2.4 Scalability
The system should be designed to handle increasing user and order
volumes without compromising performance.
4.2.5 Performance
The system should deliver fast response times, efficient data processing,
and high availability to meet user expectations.
5.0 Design Diagram
5.1 Context Diagram
The context diagram provides an overview of the system and its interactions with
external entities. It illustrates the relationship between Waiters on Wheels,
customers, restaurants, and drivers.
[Insert the context diagram]
5.2 Level-0 DFD
The level-0 DFD represents the main processes and data flows within the system.
It shows how information flows between different components and stakeholders.
[Insert the level-0 DFD]
5.3 ERD
The entity relationship diagram (ERD) represents the data entities and their
relationships within the system. It provides a visual representation of the database
structure and entity associations.
[Insert the ERD]

[
[xvi]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

6.0 Interface Design

6.1 Throw-Away Prototype
For the proposed system, we have created a throw-away prototype that showcases
the main features and functionality. The prototype allows stakeholders to visualize
the system and provide feedback for further improvements.
The prototype includes the following features:
6.1.1 User Registration
Customers can create an account and register with Waiters on Wheels,
providing their personal information for order processing and delivery.
6.1.2 Menu Selection
Customers can browse the online menu, view available dishes, and make
selections based on their preferences.
6.1.3 Order Placement
Customers can add items to their cart, specify delivery details, and place
orders for delivery.
6.1.4 Driver Tracking
Drivers can log in to the system, update their availability status, view
assigned orders, and track their delivery routes.
6.1.5 Online Payments
Customers can securely make online payments for their orders using
various payment methods.
6.1.6 Reporting
The system generates daily, weekly, and monthly sales reports for
analysis and decision-making.
6.2 GUI Design
The graphical user interface (GUI) of the system follows modern design principles
and focuses on usability and intuitiveness. The input and output interfaces have
been carefully designed to provide a seamless user experience.
Key concepts and principles considered in GUI design include:
6.2.1 Clear and Intuitive Navigation

[
[xvii]
Level 1 Asia Pacific University of Technology & Innovation 2020
Systems Analysis & Design CT026-3-1-SAAD

The GUI ensures that users can easily navigate through different
sections of the system, such as menu selection, order placement, and
account management.
6.2.2 Consistent Design Elements
The interface maintains consistency in terms of colours, fonts, icons, and
layout throughout the system, providing a cohesive and professional
look.
6.2.3 Responsive Design
The GUI is designed to be responsive, adapting to different screen sizes
and devices, such as desktops, tablets, and mobile phones.
6.2.4 Error Handling and Notification
The interface includes appropriate error handling mechanisms and
notifications to guide users and provide feedback on their actions.
6.2.5 Accessibility Considerations
The GUI takes into account accessibility guidelines, ensuring that users
with disabilities can access and use the system effectively.

[
[xviii]
Level 1 Asia Pacific University of Technology & Innovation 2020