WRAP AROUND

CONCLUSION

Project: E-menu on iPad for Thai restaurant

Topic: Conclusion

Content: Wrap around conclusion

Created by Traitet Th.

Created Date 6 Sep 2012

Revised Date 8 Sep 2012

Revision No. 1.0

Document Name C01-001

OVERVIEW OF RESEARCH

2

REQUEST QUESTIONS3

Every process was conducted to answer the research question and to achieve research objectives.

RESEARCH FRAMEWORK4

Research framework was designed to investigate & produce the research outcomes based on the research objectives.

ACTION PLAN5

Used action plan to manage time and issues happened in this project because many approaches in this project were time-consuming e.g. case study and observation.

KNOWLEDGE OF THE DOMAIN

6

1. KEY KNOWLEDGE7

1. Electronic menu (e-menu) for restaurants

2. Restaurant service process

3. Software usability and Human-Computer Interaction (HCI)

4. Software development methodologies and prototyping techniques

5. Mobile application development for e-menu on iOS or Android

devices

Five essential knowledge factors from literature review to conduct research.

However, it was also necessary to learn by doing to carry out the research outcomes.

8

Observatio

n

at a

Thai Dining

Restaurant

in UK

Make list of requirements

Design Database using ER-diagram

Design UML Use Case Diagram

Design Class Diagram

Design Workflow Diagram

Make Recommendatio

ns

The users’ perceptions on the e-menu prototype

Recommendations of e-menu application

development

SOFTWARE DEVELOPMENT PROCESSES FOR E-MENU APPLICATION

BASED ON RAD, PROTOTYING AND DIRECT OBSERVATIONO

bse

rvatio

n th

roughout th

e d

evelo

pm

ent p

roce

ss

Develop the first prototype

Design & develop e-menu web

and Web services for the first prototype on .NET

(ASP.NET Language)

Test System e.g. Web Services

Create the database

Present the first Prototype

Get feedbacks from the restaurant manager

Modify list of requirements & design documents,

and Web services

Develop the final Prototype

Create document to

test requirements

Develop the final prototype by Xcode on iPad

(Objective-C Language)

Develop web for back

office on .NET

Present the final Prototype

Interview restaurant staff; restaurant manager, waiting

staff and chefs

Present the final prototype by Videos, and Demo on iPad &

Web

Refine

docu

ments

Processes for producing research outcomes based on the research framework.

9

E-menu for restaurant

Restaurant Service Process

SW Usability & HCI

Software Dev. Methodology iOS & Andriod

List of Requirements

UML Use Case Diagram

UML Class Diagram

Entity–Relationship(ER) Diagram

Workflow Diagrams

DatabaseE-menu Application

on iPad (Xcode)

E-menuweb services

(ASP.Net)

E-menu website for staff (ASP.Net)

Presentation e-menu by Videos

Presentation of e-menu features on

Web

Presentation of e-menu features on iPad

Document for testing business

requirements

E-menu features based on business requirements

SW Usability & HCISoftware Dev. Methodology

System analysis & design documents

Key knowledge (E-menu prototype) Key knowledge (Software Development)

Prototype of e-menu application

Additional artifacts to demonstrate the prototype before interviews

Users’ perceptions on the e-menu prototype

Recommendation on e-menu development

Potential Outcome 1

Potential Outcome 2

Potential Outcome 3 Potential Outcome 4

Initial Objectives

MS Word & PowerPoint Files

(Literature Review)

PowerPoint and Visio Files

E-menu app on iPad& e-menu web

Video files &MS PowerPoint

MS PowerPoint & Word Files

Artifact Format

Additional Outcomes

STRUCTURE OF PORTFOLIO FOR

PRODUCING THE ARTEFACT OUTCOMES

Outcomes could be logically produced based on research processes.

OUTCOME#1: SYSTEM ANALYSIS

AND DESIGN DOCUMENTS10

Fu

nct

ion

al

req

uire

me

nt

Non

-fun

ctio

nal

requ

irem

ent

List of Requirements

Gather requirements by direct observation.Design and analyse system from above information & diagrams.

Develop DB and SW based on these documents.

UML Use case diagram

ER diagram

UML Use case diagram

Workflow diagram

Process diagram (as-it)

Process diagram (to-be)

E-menu Database & Applications

11

The first version of e-menu prototype (ASP.Net)

Main menu for ordering Preview menu details

Confirm Order Check Order Status

Available at: www.innoemenu.com until 31 January 2013

The final version of e-menu prototype (Xcode)

Main menu for ordering

Preview menu details

Confirm Order Check Order Status

View demo. at: http://www.youtube.com/watch?v=bCsFiMHuG80

OUTCOME#2: E-MENU PROTOTYPE

The first version of prototype was developed only in ASP.Net to reduce development time.It could also test Web services before integrating with Xcode (iPad application).

12 OUTCOME#3: USERS’ PERCEPTIONS

(BASED ON E-MENU FEATURES)

No Issues Description Countermeasure

1 LanguageDoesn't support Chinese language

Design e-menu to support multiple languages.Doesn't support Thai language for

chefs

2 Order quantityCannot enter quantity on the main

menu screenDesign e-menu so that users add quantity on

the main menu.

3Customer order

commentCannot enter a customer order

commentDesign e-menu so that users can add

comments.

4 Request main course Difficult to request "Main Course" Add a button to request "Main Course".

5 Order set menuCannot separate set menu to actual

menu items for chefsDesign new database to support separating

items for set menus.

6 Progress status Cannot show progress statusAdd progress status when system is being

operated.

7User instruction

guideDoesn’t have user instruction guide Add user instruction guide in the application.

8Combine dinning

tablesCannot combine tables based on

reservationAdd function combining tables in the web

application.

9Sorting of menu

categoriesDrinks should be the first category Move the "Drinks" category as the first item.

Users’ perceptions based on e-menu features would be very useful when producing a real e-menu application in the future to enhance functionalities of e-menu application.

13

OUTCOME#3: USERS’ PERCEPTIONS

(GENERAL PERCEPTIONS ON E-MENU

SYSTEM)

Convenience Improving customer service Preventing human error

Convenience, improving service and preventing human error.

But it has high cost and may not be convenient for elderly people.

14

OUTCOME#4: RECOMMENDATIONS

REGARDING TO

E-MENU DEVELOPMENT

Developing using ASP.Net and Xcode User ASP.Net Web services to communicate with iOS

platform.

Benefit: Support developing e-menu on other platform devices e.g. Android devices

Developing based on MVC concept to separate business logic and user interfaces

Benefits: Enhance testability, maintainability and flexibility

LIMITATIONS AND

RECOMMENDATIONS FOR FURTHER

RESEARCH

15

LIMITATIONS AND

RECOMMENDATIONS FOR

FURTHER RESEARCH

16

No Limitation Recommendation for future research

1

Did not interview restaurant customers on their perceptions of

increased convenience and customer service,

which were suggested by restaurant staff.

Study the restaurant customers' perceptions based on this prototype.

2

Did not interview elderly people on their perceptions of ordering meals

using iPad, which was an issue mentioned by restaurant staff.

Study the elderly customers' perceptions based on this prototype.

3

Did not analyse investment feasibility of e-menu, in terms of high cost.

Which was also an issue raised by restaurant staff.

Conduct research to feasibility study on investment of e-menu system.

4

Did not develop specific features, such as integrating with POS system,

advertising new promotions, registering membership, and other

features recommended by restaurant staff.

Study of other recommended features whether they are business needs, or not?,

based on software design & analysis documents, and source code in this portfolio.

RESEARCH CONTRIBUTION

17

RESEARCH CONTRIBUTION18

No Outcomes Contribute to Description

1System analysis

and design documents Software practitioners and

developers who are interested in software development,

especially for mobile application, restaurant system

and RAD methodology.

This portfolio will be useful when producing the final production of an e-menu system in the future

2Restaurant e-

menu prototype

3

Recommendations regarding to e-

menu development

4 Users' perceptionsRestaurant owners and people

who would like to start a restaurant business.

The users’ perceptions can help them to make decisions with

regards to implementation of the e-menu system to improve their service efficiency and customer

satisfaction.

The dissertation portfolio including source code is also shared on internet at: www.innoemenu.com

19 GENERISING THE RESULT IN RESEARCH

This case study research

A Thai casual dinning restaurant

in UKE-menu application on iPad

Other kinds of restaurant e.g.

fast food restaurants, cafes

and pubs

Other countries e.g. Thailand,

Europe countries.

E-menu application on

Android devices

Other kinds of e-menu e.g. e-menu for waiting area or tableside e-menu.

Focu

sin

gG

en

era

lisa

tion

Above generalising items could also conduct on further research.

SOME RESEARCH ANSWERS

20

SOME RESEARCH ANSWERS21

How can a prototype of an electronic menu (e-menu) application be developed for the casual dining restaurant industry to meet business

requirements?

No Answer the question Description

1RAD methodology with

prototyping

RAD approach is an effective way to develop e-menu because it allows an e-menu application to be developed

close to business problems areas in a short time.

2 Direct ObservationDirect observation is a useful approach that enables system analyst to investigate requirements, near the problem areas.

3 MVC DesignMVC design help a developer to make it easy to maintain source code and test application.

5Users' perceptions: Benefits of e-menu

Benefits of e-menu suggested by restaurant staff are the main points

that a developer should carefully consider including all features related to those benefits. E.g. e-menu features must able to reduce human error and enhance customer

service.

Use

of

ap

pro

pria

te a

pp

roa

che

s

SOME RESEARCH ANSWERS

22

No Answer the question Description

6Users' perceptions:

Issues of e-menu

Issues of e-menu must be considered when developing e-menu system because they might be significant obstacles

against project success.

For example, how to reduce cost of e-menu system andhow e-menu can support elderly people?

7Users' perceptions: Additional features

Additional features are requirements that e-menu could provide.

8 List of requirements

List of requirements are a significant answer of this research question.

Therefore, developing e-menu should focus on the list of requirements first.

9System analysis and design documents.

Making these documents is an significant process in developing an e-menu application.

Rec

omm

enda

tions

to

deve

lop

e-m

enu

REFERENCES23

• EDEXCEL (2010). Human Computer Interaction. [online]. Last accessed 7 August at: http://www.edexcel.com/migrationdocuments/BTEC%20Nationals%20from%202010/Unit-23-Human-Computer-Interaction.pdf.

• GULATI, Anubha and DUBEY, Sanjay Kumar (2012). Critical Analysis on Usability Evaluation Techniques. [online]. International Journal of Engineering Science and Technology (IJEST), 4(3), 990-997. Article from IJEST last accessed 3 September 2012 at: http://www.ijest.info/docs/IJEST12-04-03-118.pdf.

• KHAN, Asif Irshad, et al. (2011). Comprehensive study of commonly practiced heavy and light weight software methodologies. [online]. International Journal of Computer Science, 8(4), 441-450. Article from TechRepublic last accessed 3 September 2012 at: http://www.techrepublic.com/whitepapers/a-comprehensive-study-of-commonly-practiced-heavy-and-light-weight-software-methodologies/3809811/post.

• MAJID, Rogayah Abd, et al. (2011). Users’ frustration and HCI in the software development life cycle. [online]. International Journal of Information Processing and Management, 2 (1.5), 44-48. Article from Human and Sciences Research Center last accessed 8 August at: http://www.humanpub.org/ijipm/ppl/4_%20IJIPM%20Vol2%20No.1-4.pdf.

• YIN, Robert K. (2010). Application of case study research. 3rd ed., London, SAGE Publications.

THANK YOU VERY MUCH

24