The document describes a proposed touchscreen drive-thru ordering interface that aims to address issues with current systems. It outlines problems with speaking orders through an intercom and waiting for a server. The interface allows automatic ordering without waiting. It then discusses objectives to improve the ordering process, the McDonald's scope, intended novice users, tasks of ordering, canceling, changing quantities and special requests. A prototype was evaluated with users performing well and finding it attractive, easy to use and helpful.

1. TOUCHSCREEN DRIVE-THRU
INTERFACE
SCSJ-2 | SECTION 3 | HCI | The Mighty Midnight Maniacs

2. 1. NOR KHAIRUN AQILA BINTI JESMEN
A13CS0097
2. YASMIN BINTI ZAHIR HUSSAIN
A13CS0170
3. MARIA AMEINA BINTI AHMAD
A13HA0053
4. MUHAMMAD FARIDZUAN BIN JAMALUDIN
A13CS0071
5. ROSLAN LOGAN BIN ABDULLAH
A13CS0140
Team members

3. Problem
• With the current drive-thru system, consumers need to speak through an
intercom to place their order.
• Miscommunication between the customer and the server can cause errors in
orders and also confusion, in addition to the fact that people may feel self-
conscious when speaking to a box.
• The new drive-thru interface eliminates these problems. The drive-thru interface
also attempts to improve the ordering speed.
• Present systems require that a server(person in charge) be present to take an
order. Often times, a driver must wait for a server to appear, resulting in
inefficiency.
• With our computer drive-thru interface, drivers can automatically begin ordering
food without the need to wait for a server.

4. Objectives
• We recognized the need to improve the process of ordering food at a drive-thru
window of a fast food restaurant.
• The current drive-thru system has several drawbacks that we want to
improve and will allow customers to have direct control over making and
changing their orders.
• Our team decided to implement a touch screen interface drive-thru system with
the ultimate goal of providing users with a food-ordering interface that is
consistent, intuitive and easy to use.

5. Project Scope
• For this project, our team decided to use McDonald’s as the restaurant because
of its recognition and well-known drive-thru service.
• The drive-thru interface is designed to provide customers everything they need
to order their food.
• Note that users must still pay and pick up their order at the window.

6. Who are the users?
• The intended users for our drive-thru system are novice and casual users who are
able to drive (age over 18 in Malaysia), and seek quick quality service restaurant.
• Our system is developed to accommodate people with all different levels of
knowledge in computerized systems.
• Since McDonald’s is very popular in many different countries, our intended users
are spread all over the world.
• Our system can be implemented in any restaurant that offers a drive-thru service.

7. Tasks?
• Ordering
• Canceling Order
• Reduce Quantity of Order
• Special Request

8. Prototype Evaluation…

9. User Performance Measurements
Name of User Ummi Wahyuni Aiesah Rusli Hafiz Izzat C
Task 1(s) 34 46 41 29 26 25 21
Task 2(s) 19 23 24 19 18 17 16
Task 3(s) 31 44 35 31 34 24 23
Task 4(s) 33 37 35 27 32 29 24
Performance
Score(S) %
S1 61.76 45.65 51.22 72.41 80.77 84.00
S2 84.21 69.57 66.67 84.21 88.89 94.12
S3 74.19 52.27 65.71 74.19 67.65 95.83
S4 72.73 64.86 68.57 88.89 75.00 82.76

10. Task Performance for Task 1 : Ordering
0
10
20
30
40
50
60
70
80
90
Ummi Wahyuni Aiesah Rusli Hafiz Izzat
Performance Score %

11. Task Performance for
Task 2 : Canceling Order
0
10
20
30
40
50
60
70
80
90
100
Ummi Wahyuni Aiesah Rusli Hafiz Izzat
Performance Score %

12. Task Performance for
Task 3 : Reducing Quantity of Order
0
10
20
30
40
50
60
70
80
90
100
Ummi Wahyuni Aiesah Rusli Hafiz Izzat
Performance Score %

13. Task Performance for
Task 4 : Special Request
0
10
20
30
40
50
60
70
80
90
100
Ummi Wahyuni Aiesah Rusli Hafiz Izzat
Performance Score %

14. Subjective Measurements
User Experience Mean Standard Deviation
Attractive 4.50 0.50
Confusing 1.00 0.00
Easy 5.00 0.00
Annoying 1.17 0.67
Helpful 4.50 0.50
Challenging 1.33 0.47

15. Discussion
• The result is as expected as the system is meant to be easy to use and not complicated which makes
the system less challenging.
• In terms of performance, overall every user have passed of 50% of the user performance in terms of
time taken to complete each task.
• Every task has been completed 100% with ease and there are even certain users that perform as fast
as the expert of the system.
• By far, the hardest task would be task 4 which is the special request as it takes time to key in the
special order request.
• The easiest task would be task 2 which is cancelling order as it is quite straight forward and fast.
• Based on the performance score, the usability of our prototype is looking good as users doesn’t really
face critical problem.
• From the mean and the standard deviation, almost all of the user finds the system attractive, not
confusing, easy, not that annoying, quite helpful and not that challenging.
• We think we should improve the way user inputs the special request as it takes really long time for
user to key in so we might insert some defaults for the user to choose.

16. The Touchscreen Drive-
Thru Interface Demo..

17. Conclusion
• The design process was incredibly informative and the experience was an excellent
one. We learned a lot, not only technically related, but also in regards to time
management and teamwork.
• We learned about Usability and how important it is in the design process, as well as
imagining ourselves in the place of the users. Through our project we found that what
we necessarily thought was important and needed in an application wasn't exactly
what the user wanted and needed.
• This showed us how important prototyping is because a company that dives into a
project without actually taking the time to make a prototype may end up with
catastrophic sales if there is a certain feature that either is inconvenient to use,
doesn't do what it is intended to, or isn't included at all.
• By building the prototype of Touchscreen Drive Thru Interface, we definitely gained a
bunch of experience and not only learn more on prototyping but also the way we
work as a team.
• Users of our system were also very receptive to the idea of Touch Screen Drive Thru
Interface. Implementing this system for real in future would be a great deal for us.