• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
10 wrap around_conclusion
 

10 wrap around_conclusion

on

  • 425 views

 

Statistics

Views

Total Views
425
Views on SlideShare
425
Embed Views
0

Actions

Likes
0
Downloads
10
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Time-consuming knew from Literature review and justification approaches.
  • The last image adopted knowledge from Edexcel (2010),Dubey (2012) andGulati and Dubey (2012)
  • UAT: User acceptanceRAD: Rapid Application Development
  • HCI: Human–computer interactionER Diagram: Entity–relationship
  • ER: Entity-RelationshipUML: Unified Modeling LanguageAs-it (system): existing systemTo-be (system): new systemSW: SoftwareDB: Database
  • The first prototype developed in ASP.Net had features like on iPad.It was work around because the researcher could not finish developing on iPad in time.However, the first prototype was very useful to gain both implicit and explicit requirements.: http://aces-web.aces.shu.ac.uk/students/b0043132/03_emenu/02_ORDER/01_SearchOrder.aspxThe final prototype (Video presentations)Video presentation of e-menu on iPad for restaurant customer:http://www.youtube.com/watch?v=th5YlsYrHuYhttp://www.youtube.com/watch?v=bCsFiMHuG80Video presentation of e-menu on Website for restaurant staff:http://www.youtube.com/watch?v=HSqTJ5acxzwVideo presentation of innovative e-menu and its benefits:http://www.youtube.com/watch?v=-cBTICTa7bE
  • POS: Point of Sales
  • The dissertation portfolio is shared on internet at: www.innoemenu.com, including source codes and the database.

10 wrap around_conclusion 10 wrap around_conclusion Presentation Transcript

  • WRAP AROUND CONCLUSION Created by Traitet Th.Project: E-menu on iPad for Thai restaurant Created Date 6 Sep 2012Topic: Conclusion Revised Date 8 Sep 2012 Revision No. 1.0Content: Wrap around conclusion Document Name C01-001
  • OVERVIEW OF RESEARCH 2
  • 3 REQUEST QUESTIONS Every process was conducted to answer the research question and to achieve research objectives.
  • 4 RESEARCH FRAMEWORK Research framework was designed to investigate & produce the research outcomes based on the research objectives.
  • 5 ACTION PLAN Used action plan to manage time and issues happened in this projectbecause many approaches in this project were time-consuming e.g. case study and observation.
  • KNOWLEDGE OF THE DOMAIN 6
  • 7 1. KEY KNOWLEDGE1. Electronic menu (e-menu) for restaurants2. Restaurant service process3. Software usability and Human-Computer Interaction (HCI)4. Software development methodologies and prototyping techniques5. 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.
  • SOFTWARE DEVELOPMENT PROCESSES FOR E-MENU APPLICATION BASED ON RAD, PROTOTYING AND DIRECT OBSERVATION Design Make list of Design UML Design Database Design Class requirements Use Case Workflow Observation throughout the development process using ER- Diagram Diagram Diagram diagram Refine documents Design & develop e-menu web Test SystemDevelop the first Create the and Web services for e.g. Web prototype database the first prototype on .NET Services (ASP.NET Language) Observation Modify list of requirements &Present the first Get feedbacks from design documents, at a Prototype the restaurant manager and Web services Thai Dining Create Develop the final prototype by DevelopDevelop the final document to Xcode on iPad web for back Prototype test (Objective-C Language) office on .NET requirements Restaurant Interview restaurant staff; in UKPresent the final Present the final prototype by restaurant manager, waiting staff Prototype Videos, and Demo on iPad & Web and chefs Make The users’ perceptions Recommendations of e-menuRecommendation on the e-menu prototype application development s 8 Processes for producing research outcomes based on the research framework.
  • STRUCTURE OF PORTFOLIO FOR PRODUCING THE ARTEFACT OUTCOMES 9 Artifact Format Initial Objectives Key knowledge (E-menu prototype) Key knowledge (Software Development)MS Word & PowerPoint E-menu for Restaurant SW Usability & Software Dev. Files (Literature iOS & Andriod restaurant Service Process HCI Methodology Review) Potential Outcome 1 System analysis & design documents PowerPoint List of UML Use Case UML Class Entity–Relationship Workflow and Visio Files Requirements Diagram Diagram (ER) Diagram Diagrams Potential Outcome 2 Prototype of e-menu application E-menu E-menu app on iPad E-menu Application E-menu website Database web services & e-menu web on iPad (Xcode) for staff (ASP.Net) (ASP.Net) Additional artifacts to demonstrate the prototype before interviews Additional Outcomes Presentation of e- Document for testing Video files & Presentation e-menu Presentation of e-menu menu features on business requirements MS PowerPoint by Videos features on iPad Web Users’ perceptions Recommendation on the e-menu prototype Potential Outcome 3 on e-menu development Potential Outcome 4 MS PowerPoint Software Dev. E-menu features based on business requirements SW Usability & HCI & Word Files Methodology Outcomes could be logically produced based on research processes.
  • OUTCOME#1: SYSTEM ANALYSIS AND 10 DESIGN DOCUMENTS List of Requirements UML Use case diagram Workflow diagram E-menu Database & Applications UML Use case diagram Process diagram (as-it)requirement Functional ER diagram Process diagram (to-be)Non-functional requirement Gather requirements by direct observation. Develop DB and SW based Design and analyse system from above information & diagrams. on these documents.
  • 11 O UTC O ME# 2 : E -MEN U PRO TO TYPE The first version of e-menu prototype (ASP.Net) The final version of e-menu prototype (Xcode) Main menu for ordering Preview menu details Main menu for ordering Preview menu details Confirm Order Check Order Status Confirm Order Check Order Status Available at: www.innoemenu.com until 31 January 2013 View demo. at: http://www.youtube.com/watch?v=bCsFiMHuG80 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 O U T C O ME# 3 : U SER S’ P ER C EP T IO N S (B A SED O N E - MEN U F EAT U R ES)No Issues Description Countermeasure Doesnt support Chinese language1 Language Design e-menu to support multiple languages. Doesnt support Thai language for chefs Cannot enter quantity on the main menu Design e-menu so that users add quantity on the main2 Order quantity screen menu. Customer order3 Cannot enter a customer order comment Design e-menu so that users can add comments. comment4 Request main course Difficult to request "Main Course" Add a button to request "Main Course". Cannot separate set menu to actual Design new database to support separating items for5 Order set menu menu items for chefs set menus.6 Progress status Cannot show progress status Add progress status when system is being operated.7 User instruction guide Doesn’t have user instruction guide Add user instruction guide in the application. Cannot combine tables based on8 Combine dinning tables Add function combining tables in the web application. reservation Sorting of menu9 Drinks should be the first category Move the "Drinks" category as the first item. categories 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.
  • OUTCOME#3: USERS’ PERCEPTIONS13 (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.
  • O U T C O M E # 4 : R E C O M M E N D AT I O N S R E G A R D I N G TO 14 E-MENU DEVELOPMENT Developing using ASP.Net and Xcode Developing based on MVC concept to separateUser ASP.Net Web services to communicate with iOS business logic and user interfaces platform.Benefit: Support developing e-menu on other platform Benefits: Enhance testability, maintainability devices e.g. Android devices and flexibility
  • LIMITATIONS AND RECOMMENDATIONSFOR FURTHER RESEARCH 15
  • LIMITATIONS AND RECOMMENDATIONS 16 FOR FURTHER RESEARCHNo Limitation Recommendation for future research Did not interview restaurant customers on their perceptions of increased convenience Study the restaurant customers perceptions1 and customer service, based on this prototype. which were suggested by restaurant staff. Did not interview elderly people on their perceptions of ordering meals using iPad, Study the elderly customers perceptions based on2 which was an issue mentioned by restaurant this prototype. staff. Did not analyse investment feasibility of e-menu, in terms of high cost. Conduct research to feasibility study on investment3 Which was also an issue raised by of e-menu system. restaurant staff. Did not develop specific features, such as Study of other recommended features whether they integrating with POS system, advertising are business needs, or not?,4 new promotions, registering membership, based on software design & analysis documents, and other features recommended by and source code in this portfolio. restaurant staff.
  • RESEARCH CONTRIBUTION 17
  • 18 RESEARCH CONTRIBUTIONNo Outcomes Contribute to Description System analysis and1 design documents Software practitioners and developers who are interested in This portfolio will be useful when Restaurant e-menu2 software development, especially for producing the final production of an e- prototype mobile application, restaurant system menu system in the future Recommendations and RAD methodology.3 regarding to e-menu development The users’ perceptions can help them Restaurant owners and people who to make decisions with regards to4 Users perceptions would like to start a restaurant implementation of the e-menu system business. to improve their service efficiency and customer satisfaction. The dissertation portfolio including source code is also shared on internet at: www.innoemenu.com
  • 19 G EN ERISIN G THE RESULT IN RESEA RC H This case study research Focusing A Thai casual dinning restaurant E-menu application on iPad in UK Generalisati Other kinds of Other kinds of e- Other countries e.g. menu e.g. e-menurestaurant e.g. fast E-menu application on Thailand, Europe for waiting area or food restaurants, on Android devices countries. tableside e-menu. cafes and pubs Above generalising items could also conduct on further research.
  • SOME RESEARCH ANSWERS 20
  • 21 SOME RESEARCH ANSWERS 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 DescriptionUse of appropriate approaches RAD approach is an effective way to develop e-menu because it RAD methodology with 1 allows an e-menu application to be developed close to business prototyping problems areas in a short time. Direct observation is a useful approach that enables system analyst 2 Direct Observation to investigate requirements, near the problem areas. MVC design help a developer to make it easy 3 MVC Design to maintain source code and test application. Benefits of e-menu suggested by restaurant staff are the main points Users perceptions: that a developer should carefully consider including all features 5 Benefits of e-menu related to those benefits. E.g. e-menu features must able to reduce human error and enhance customer service.
  • 22 SOME RESEARCH ANSWERS No Answer the question Description Issues of e-menu must be considered when developing e-menu system because they might be significant obstacles against project success. Users perceptions:Recommendations to develop e-menu 6 Issues of e-menu For example, how to reduce cost of e-menu system and how e-menu can support elderly people? Users perceptions: 7 Additional features are requirements that e-menu could provide. Additional features List of requirements are a significant answer of this research question. 8 List of requirements Therefore, developing e-menu should focus on the list of requirements first. System analysis and design Making these documents is an significant process 9 documents. in developing an e-menu application.
  • 23 REFERENCES • 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