html5-img
1 / 42

Final Project Presentation

Final Project Presentation. 14 November 2007. Graham Hunter | Marc Pelteret | Tshifhiwa Ramuhaheli Supervisor: Hussein Suleman. Cellphone Shopper. Key aim of project: make grocery shopping easier by using technology Provide a tool for people Uses cellular telephony and the Internet

oatesm
Télécharger la présentation

Final Project Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Final Project Presentation 14 November 2007 Graham Hunter | Marc Pelteret | Tshifhiwa Ramuhaheli Supervisor: Hussein Suleman

  2. Cellphone Shopper • Key aim of project: make grocery shopping easier by using technology • Provide a tool for people • Uses cellular telephony and the Internet • Goal: allow household to share and manipulate shopping list stored on central server • Via a Web interface or cellphone Cellphone Shopper

  3. Some features • Manage and manipulate multiple lists • Check items off on cellphone as buy them • Give other users access to your lists • Attach notes to items • Reminders • Add and edit store layouts – can view list on cellphone according to layout of store Cellphone Shopper

  4. Cellphone Shopper

  5. Cellphone Shopper

  6. ApacheHTTP Server Web UIApp. Web Interface Web Front-end Server ApacheTomcat WebApp. MySQLDatabase Cellphone Interface CellphoneFront-end Back-end Server Cellphone Shopper

  7. Designing the system • User-centred design – involved users throughout project • Three design interviews: • Features • Interface prototype – both front-ends • Interface implementation – both front-ends • Interface interviews were focus groups involving usability “experts” – critiqued Cellphone Shopper

  8. ApacheTomcat WebApp. MySQLDatabase Server Back-end Cellphone Shopper

  9. Overview Provides a persistent store Implements the business logic Allows the interfaces to call functionality remotely Able to manage a medium amount of requests at once. Cellphone Shopper Cellphone Shopper Cellphone Shopper 9 9

  10. Web API Cellphone Shopper Cellphone Shopper • REST-based Web Service • Calls are made directly using URLs • Divided into four interfaces • User-Related • Create users, login users, get and set user details, let a user access a list • List-Related • Create a list, add items to a list, get a list of items in a list • Item-Related • Checkout items • Shop-Related • Add a shop layout to a shop Cellphone Shopper 10 10

  11. Web Service Cellphone Shopper Cellphone Shopper • Specification • @HttpMethod(value = "GET") @ProduceMime(value = "application/xml") @UriTemplate("User_Details") public String User_Details (@QueryParam("UserId") int UserId) { return XML } • Request • http://[IP]:[Port]/Server/resources/user/User_Details?UserId=4 • Response • <u id="4" n="Test" f="Graham" s="Hunter" e="test@" c=" 083354"/> Cellphone Shopper 11 11

  12. Examples Cellphone Shopper Cellphone Shopper User-Related • Request • /User_GetLists?UserId=4 • Response • <Lists><list id="6321" uid="1006" n="List" access="111" s="" sid="-1"/><list id="6322" uid="1006" n="Another List" access="111" s="" sid="-1"/></Lists> Cellphone Shopper 12 12

  13. Examples Cellphone Shopper Cellphone Shopper List-Related • Request • List_GetItems?ListId=3&UserId=3&OrderBy=Name • Response • <Items><I id="1" n=“Oranges" q="1" c="" sh="" sid="-1" p="0" u="0" usr="harry" uid="1006" dt="17-10-2007"> _</I><I id="2" n="Remind me" q="1" c="Reminder" sh="" sid="0" p="0" u="0" usr="harry" uid="1006" dt="19-10-2007">Update </I></Items> Cellphone Shopper 13 13

  14. Examples Cellphone Shopper Cellphone Shopper Item-Related • Request • /Item_Checkout?ItemId=1|2|3&ListId=1&UserId=3 • Response • <id> 1|2|3</id> Cellphone Shopper 14 14

  15. Persistence Cellphone Shopper Cellphone Shopper mySQL database POJOs retrieve and store data using JDBC User information is cached Cellphone Shopper 15 15

  16. Web Server Cellphone Shopper Cellphone Shopper • Jakarta Tomcat • Good documentation • Good Java support • Servlets • Manages • Connection Pooling • Monitors for orphaned database connections • Threads Cellphone Shopper 16 16

  17. Evaluation Cellphone Shopper Cellphone Shopper • Functional Testing • Available Web Service functions were tested throughout • Performance Testing • Database loaded with 5000 users • Tested using JMeter Cellphone Shopper 17 17

  18. ApacheHTTP Server Web UIApp. Web Interface Server Web Front-end ApacheTomcat WebApp. MySQLDatabase Back-end Server Cellphone Shopper

  19. Features • See news regarding reminders and list changes • Set-up and manage lists • Manipulate lists • Manage reminders • Add and edit shop layouts • Change preferences Cellphone Shopper

  20. Technology • Written using HTML, CSS and AJAX • AJAX: JavaScript, DOM and XML • Uses Yahoo! User Interface Library – AJAX interface widgets • Majority of it is client-side Cellphone Shopper Server: two PHP scripts for AJAX proxy

  21. Interface Cellphone Shopper

  22. Prototype interview • Number of possible features suggested; some implemented, others are future work • Two major ideas: • Trusted users • Use of icons – not present in the prototypes Cellphone Shopper

  23. Interface implementation • Several criticisms and suggestions Cellphone Shopper

  24. Evaluation: user testing • Direct observation evaluation • 7 users from three user classes: • Interface “experts” • People who are knowledgeable of computers and technology • People who are considered computer novices • Asked to perform a series of tasks to test as many of the features as possible and I observed them Cellphone Shopper

  25. Evaluation: heuristic eval. • Heuristic evaluation: structured evaluation by usability expert • Used Jakob Nielsen’s 10 heuristics • 3 experts evaluated the Web interface (all from Computer Science): • 2 PhD students • 1 second-year masters student Cellphone Shopper

  26. Evaluation: some results  Both sets of evaluators were happy with the interface on the whole  Interface does not indicate that is communicating with server and waiting for response  Most users spent time searching the screen to find functions • Particularly on shopping list editor page Cellphone Shopper

  27. Cellphone Interface ApacheHTTP Server Web UIApp. Web Interface Web Front-end Server ApacheTomcat WebApp. MySQLDatabase CellphoneFront-end Back-end Server Cellphone Shopper

  28. Cellphone interface The cellphone interface provides a way for users to: View and manipulate the shopping lists Add, edit and remove items Check items off the current list as they are bought The application is developed in J2ME Provides cross-platform portability Many Java-enable phones Cellphone Shopper Cellphone Shopper Cellphone Shopper 28 28

  29. Screenshots Cellphone Shopper Cellphone Shopper Cellphone Shopper 29 29

  30. Prototype interview Paper prototype Expert users Suggestions made: Having auto-complete for the item name Drop-down boxes for category and shop name Using strike-through for deleted items Using shortcut keys for the menu options Caching changes on phone and sending as a batch Cellphone Shopper Cellphone Shopper Cellphone Shopper 30 30

  31. Interface implementation Sun phone emulator This was done to assess the interface development since the first prototype To improve the usability of the interface Some of the expert users from the first session were involved All menu options available were run at least once Cellphone Shopper Cellphone Shopper Cellphone Shopper 31 31

  32. Suggestions made Grouping similar functions together Options 1,4,5 and 6 grouped to “View More Lists” Prototype Final Final Users were now able to view all the lists in one screen Cellphone Shopper Cellphone Shopper Cellphone Shopper 32 32

  33. Suggestions made Item fields were rearranged and ordered by importance Prototype Final Cellphone Shopper Cellphone Shopper Cellphone Shopper 33 33

  34. Suggestions made Hide unavailable options Left: viewing a list with itemsRight: viewing an empty list Cellphone Shopper Cellphone Shopper Cellphone Shopper 34 34

  35. Communication protocol Communication protocol used between front-end and back-end is SOAP over GPRS All requests made to server are through The GET request method for data retrieval and POST is used for sending updates to server Cellphone Shopper Cellphone Shopper Cellphone Shopper 35 35

  36. Communication protocol Messages passed are stripped-down XML To reduce the amount of traffic generated Changes made on the application are cached and then sent as a batch This reduces the cost of creating a connection with the server Cellphone Shopper Cellphone Shopper Cellphone Shopper 36 36

  37. Evaluation User testing 9 users were involved in the final testing of the developed interface Users were asked to perform a set of tasks covering the core features of the system For each new screen that a user encountered they were asked to explain what they think the various components on the screen are used for Cellphone Shopper Cellphone Shopper Cellphone Shopper 37 37

  38. Evaluation results Users were also asked to rate the difficulty of performing each task The user studies conducted showed that users were able to perform most operations without any difficulties The user interface can be considered to be Easy to use and Conforms to the design principles of usable interfaces. Cellphone Shopper Cellphone Shopper Cellphone Shopper 38 38

  39. Conclusions • Not perfect or entirely bug free • Majority of key features proposed for system have been implemented • Several useful features suggested by users and evaluators were also implemented • Missing features that were proposed: • Pre-population of the user’s shopping list based on their list history • Ability to view statistics about the list history Cellphone Shopper

  40. Project success factors  Interfaces have good aesthetics and are easy to use  Information retrieved from database on request of either interface, and translated to and sent in XML  Specified features implemented Cellphone Shopper

  41. Future work • Handle list synchronisation properly • Additional interfaces • Camera to photograph barcodes or camera-based recognition of products • WAP-like cellphone interface – broaden range of cellphones that can use system • Cellphone applications for Windows Mobile and Symbian • Community features Cellphone Shopper

  42. Final Project Presentation 14 November 2007 Graham Hunter | Marc Pelteret | Tshifhiwa Ramuhaheli Supervisor: Hussein Suleman

More Related