Please enable JavaScript.

Coggle requires JavaScript to display documents.

Cafe, Usability principles - Coggle Diagram

- - - - Help screen
        
        The help screen feature helps the user by providing instructions on how to use the app.
      - Orders screen (for employees)
        
        The upcoming orders feature lets the employee see the items in the customer's cart
        
        The past orders feature lets the employee view past orders.
      - Cart screen
        
        The cart screen, which lets the user view the items selected and view the total price. The items selected by the user are also displayed on the upcoming orders label on the employee's screen
        
        The "place order" button sends the order summary to the employee's screen
        
        Another feature on the cart screen is that it generates a unique order ID for orders placed by the user.
      - Home screen
        
        "choose a combo" button which generates a combination of a food item and a drink which is within the price range (price range can be entered through the text bar)
        
        Search bar to search up items and 3 buttons to filter the results. On the screen, there are three buttons: "Drinks", "food" and "packaged drinks" which can be used to filter results based on category of items.
    - - Shopping cart screen
        
        The shopping cart screen complies with the usability principles of accessibility, effectiveness, utility, safety and learnability because there is a lot of space between buttons and the buttons are big. The screen successfully lets the user place the order because of its simple layout. The padlock icon next to the place order button indicates that the information is safe.
      - Orders screen
        
        The orders screen complies with the usability principles of effectiveness, utility because the app enables the employee to view upcoming orders, view current orders and remove the orders that have been completed with the help of bug buttons and an alert(effectiveness). All the features of the screen are easy to access because of big buttons and the positioning. For example, the upcoming orders label is right above the current orders table which makes it easy for the employee to differentiate between the upcoming orders and current orders (utility).
      - Home screen
        
        The home screen complies with the usability principles of effectiveness, learnability, and utility. The screen has all the necessary buttons and text fields in order to filter the data and add items to the cart (effectiveness). The features can be accessed through buttons that are placed correctly (The cluster of 4 buttons and positioning of logo was inspired by Domino's website). All the features in the prescribed criteria are included (utility). This screen is learnable because multiple icons are present. For example, there is a magnifying glass for the search bar. (learnability)
      - Overall app
        
        The overall app complies with multiple usability principles such as learnability, effectiveness, accessibility, and utility. The app successfully lets the user place an order quickly because there is only one mandatory input field and the design is simple (effectiveness). The design of the app is mainly inspired by dominos app (learnability). The app uses warm background colour (grey), the text colour is white(colour contrast) and the text size is big (accessibility). The app also has all the prescribed features and all the frequently used buttons are placed away from other buttons (utility)
    - - Different titles for each page and the title should be appropriate for each page. The app complies with both these guidelines.
      - Text fields have visible labels to allow interaction and the mandatory text fields are clearly indicated
      - The app also has appropriate colour contrast.
  - - - Help screen
      - Employee login screen
      - Shopping cart screen (Where all the items selected by the user are displayed)
      - Orders screen (only visible to the employees)
      - Home screen
      - Past orders screen
    - - Home screen
        
        Algorithm to generate a random order which is within price range provided by the user
        
        Algorithm to display data from database on the table cells
        
        Buttons to filter the data base. For example, the food button can be used to display the items that are food and the drinks won't be dispayed
        
        An alert algorithm which helps the user to confirm the selection
      - Shopping cart screen
        
        An algorithm that generates order ID and the order summary is displayed on the employee's screen
        
        Button which sends the confirmed order to the employee's screen
        
        An alert, which comes up when the user clicks on an item in the cart screen. The alert lets the user select any extras. (SC)
      - Employee login screen
        
        An algorithm which checks the username and password entered by the employee
      - Orders screen
        
        Algorithm to remove the orders displayed. For example, the ability to remove the order from the screen when the order has been delivered
    - - XCODE will be used to design the app and do all the coding. Language to code the prototype will be swift.
      - Language: SQL will be used to make the database and produce search results and any queries.
        Swift will be used to code the prototype
  - - - Searches
        
        A query to find the item that the user searched for. For example, when the user enters "Ham and cheese sandwich" in the search bar, the query should find the item which has the same name as the text entered by user and then display it.
        
        A query to find items which are in the category selected by the user. For example, when user clicks the "Food" button, the query should display items that are in the "Food" category.
        
        A query to add OrderID, price and name to a transient data table which can only be viewed by employees. For example, when a user orders items, enters his/her name, the menu, date and customer name should be added to data table
        
        A query to check if the username and password entered by the employees matches the username and password in the database.
    - - Category
      - Item name
      - Menu ID (unique primary key)
      - Price
      - Kilojoules
      - Veg/non veg
      - Halal/ not halal
      - Allergens
- - - - Shy and does not like to talk to people
      - Is vegetarian
    - - Works at the cafe, finds it inconvenient to use sticky notes to keep track of orders
      - Has peanut allergy.
    - - Likes to keep track of his energy intake
      - Likes to browse through what's on offer but has trouble making a decision