a1 annotation knowledge

Download A1 annotation knowledge

Post on 15-May-2015



Entertainment & Humor

0 download

Embed Size (px)


  • 1. ANNOTATION OFKNOWLEDGE OFTHE DOMAIN Created byTraitet Th.Subject: E-menu on iPad for Thai restaurant Created Date31 July 2012Topic: AnnotationRevised Date7 Sep 2012 Revision No.1.0Content: Annotation of knowledge of the domain Document Name A01-001

2. 2 KEY KNOWLEDGE OF THE DOMAIN1. Electronic menu (e-menu) for restaurants2. Restaurant service process3. Software usability and Human-Computer Interaction (HCI)4. Software development methodologies and prototyping technique5. Mobile application development for e-menu on iOS or Android devices 3. 1) E-menu for Restaurants3 4. 4 1) E-MENU FOR RESTAURANTMain Objectives of e-menu (Jenie 2011) Display list of food and beverages including images Process the restaurant services from ordering to paymentThree general kinds of touch screen e-menu system (Conceptic nodate) Table side touch screen e-menu E-menu for waiting area Tablet e-menu Pictures are taken from Emenu USA (2011) and Conceptic (no date) 5. 51) E-MENU FOR RESTAURANT1 Table-side touch screen e-menuTable-side touch screen e-menu Equipment:Personal computer Installation: Need to modify tableBenefits No falling problemDisadvantages Difficult to install Difficult to install & Need to prepare electrical plugs at all tablesNeed electrical plugs Pictures are taken from Emenu USA (2011) and Conceptic (no date) 6. 61) E-MENU FOR RESTAURANT2E-menu for waiting area E-menu for waiting area Equipment: LCD TV with touch screen Installation: Need to prepare area to install Benefits Bigger images Less cost because it requires only one touch screenLCD TV Disadvantages Only one person can order at a time.Cannot order Not suitable for this case study restaurant becausecustomers can not order on their tables.at dining table Need extra space to install. Pictures are taken from Emenu USA (2011) and Conceptic (no date) 7. 7 1) E-MENU FOR RESTAURANT3Tablet e-menuTablet E-menu Equipment: Tablet e.g. iPad Installation:Dont need to modify tableBenefits Slim and small size Easy to install Build-in wireless connectionDisadvantages Small & Falling problem Smaller screen size than othersEasy to use Theft 8. 8 1) E-MENU FOR RESTAURANTAfter discussion with the restaurant manager and staff, we found that the tablet e-menu was the mostsuitable because it was smaller and simpler to install. Order at NoCompared Item SizeInstallationSummarytableIt is not suitable for this restaurant because 1E-menu at waiting area NoBigDifficultit is inconvenient for the customers.Table side touch screen e-It is difficult to install because of its size 2 YesMediumDifficultmenu and it needs power supply.It can order at the dinning table and 3Tablet e-menuYesSmall Easyit is cheaper and easier to install. Final decision with restaurant manager: Tablet e-menu 9. 2) RESTAURANT SERVICE PROCESS 9 10. 102) RESTAURANT SERVICE PROCESSAnalysis of a existing restaurant service processIssues of existing system1. Need to wait for waiting staff before giving order and making payment.2. Waiting staff must deliver order to kitchen and bar.E-menu system1. Order is send directly from a table to bar and kitchen. Process of taking order & making payment can be improve by e-menu. Pictures are adopted from Crowston, Rubleske and Howison (2006) 11. 11 2) RESTAURANT SERVICE PROCESSProblem: Personal contact between waiting staff and customers DescriptionService Request Diagram E-menu may reduce the personalcontact between customers andwaiting staff (Studentwebstaff 2009). Solution The system should have a service request feature to call waiting staff. Request Waiter Request Main BenefitsCourse Customers can request services Request Billeasier compared to the existingsystem. Customers dont want to look aroundto find a waiter.Solution: Customers can request a waiter from e-menu system.Benefits: Customers can easily request a waiter.Pictures are adopted from Crowston, Rubleske and Howison (2006) 12. 122 ) R E S TA U R A N T S E RV I C E P R O C E S S As-it or current system1. Ordering Issues 2 A waiter must spend time to ServiceRequesttake and transfer an order tothe kitchen and bar. Customers are less inclined to1order more food during busyOrderingtime. Paper-based menus haveinsufficient information e.g.pictures and details of food.2. Request Service Issues A waiter has to observecustomers when they want torequest a main course. The customers have to lookaround to request waiter andThese issues can be solved by e-menu systembill. 13. 132 ) R E S TA U R A N T S E RV I C E P R O C E S S New Service Process by e-menu system1. Ordering2- Order is transferred to bar andService Requestkitchen automatically.- Customers find it easy to ordermore food and beverages.- Customers can check their1order status.Ordering- Customers can select menuwith full details and pictures.2. Service request- Customers can request serviceon e-menu- Waiters have more time toprovide service.E-menu can enhance ordering and requesting services 14. 3) SOFTWARE USABILITY & HCI HCI: Human-Computer Interaction14 15. 15SOFTWARE USABILITY & HCI HCI: Human-Computer InteractionImproving Software Quality by HCI design Quality of software should support Users can use software without specialised business needs.IT knowledge HCI is an important factor to measure Easy to use & without long instruction a quality of software (Gulati and (Edexcel 2010)Dubey 2012 , Majid 2011) Touch screen interfaces can enhance usability because it is easy to use. Developing e-menu system should concern HCI design. 16. 16 SOFTWARE USABILITY & HCI How to measure HCI Design?Good HCI Design & Example of applyingNo DescriptionUsability the concept for e-menu1Visibility Know result of each operation Screen is updated after placing order Customers can always return to a previous2 FeedbackEasy to return to a previous screenscreen of e-menu.Easy to recognize when use software Make user-friendly and non-complex user3Memorabilityagaininterfaces4Learnability Easy to accomplish basic tasks Reduce unnecesaary steps as much as possible5 EfficiencyQuick to learn and perform tasks Make it be simple and easy to use6Satisfaction Pleasant to use softwarePut nice images and suitable colours (Norman and Nielsen 2011; Nielsen 1993) Above criteria should always be concerned when developing an e-menu application.However, only usability is insufficient. Developers must be aware of SW developmentmethodology. 17. 4) SOFTWARE DEVELOPMENTMETHODOLOGIES AND PROTOTYINGTECHNIQUE 17 18. 4 ) S O F T WAR E D E V E L O P M E N T 18METHODOLOGIESAN D P R O TO T Y P I N G T E C H N I Q U EComparison table among Waterfall, Agile and RAD with prototyping approachRAD withNo Compared ItemWaterfallAgileDescription Prototyping Waterfall approach clearly separates development1Traditional approach Yes No Noprocesses, and doesnt return to a previous stage. (Khan et al. 2011) Iterative process can improve a quality of application Uses iterative process2No Yes Yesand increase customer satisfaction (Hoffer, George and Valacich 2008). Agile and RAD use a iterative process, which is Software is likely fit with business3No Yes Yesflexible when a requirement is changed (Kendal needs.2011). RAD is an experimental method, which may result in4Experimental approach No NoYesinsufficiently understand the overall business requirements (Khan et al. 2011). Iterative process able to increase the overall cost and Able to increase the overall cost5No Yes Yestime. For example, after requirements are changed, a and implementation time project will need more time to develop (Cobb 2011). A large project needs a lot of developers and much time to implement. It is difficult to observe at a6Appropriate for a large projectYes YesNocustomer site and make a prototype at a short time (Meso and Jain 2011)The software development methodology is considered in the Justification of the approach section 19. 4 ) S O F T WAR E D E V E L O P M E N T 19METHODOLOGIES AN D P R O TO T Y P I N G T E C H N I Q U E Mapping RAD Modeling with e-menu development Capture RequirementsWhat?Observation Discussion Interview(Observation at the restaurant) Develop a final prototypes of e-menu application Where?2.5 months for prototype Quick Analysis and Design Iterate(UML and other design At a Thai casual dinning restaurant processdocuments) development How?Develop Prototype Observation at a restaurant to gather requirements(1st by .Net & 2nd by .NET & Discussion with manager to summarise needs Xcode) Develop the first prototype by .NET & Web services Develop the final prototype on iPad (Objective-c language on Customer Evaluation of PrototypexCode software) Throughout(Get feedback from observation, Observation, discussion and interviews developmentdiscussion and interviews) Observation to understand as-it system. process Discussion to gather requirements Interviews the restaurant manager, waiting staff and Develop Final Product chefs RAD Prototype Model (Sommerville 2004)Reason using .Net to develop the first prototype Saving time: Researcher is more familiar with .NET Testing web services: Website developed by .NET can test web services before integrating with xCode (iPad)Key concepts of RAD methodologyWhen? Gather requirements & evaluate prototype by observation, Developing and observing between July and August 2012discussion and interview. Presenting the first and final prototypes in July and August 2012, respectively. Working closely with users throughout the developing process. 20. 4) MOBILE APPLICATIONDEVELOPMENT FOR E-MENU ON iOSAND ANDROID DEVICES 20 21. 4 ) M O B I L E AP P L I C AT I O N D E V E L O P M E N T F O R21E - M E N U O N I O S AN D AN D R O I D D E V I C E SComparison table between Apples iOS and Google Andriod Objective To chose an effective way to develop a No Platform Apples iOS Googles Android prototype of e-menu system.1OwnerApple Google System analysis2Tablet devicesiPad Sam