Please enable JavaScript.

Coggle requires JavaScript to display documents.

Tuck shop App (Client Problem (Requirements (The mobile application must:,…

- - - - Order meals in advance
      - Select the correct tuckshop campus for collection
      - Provide a unique order number
      - Customise how the menu is displayed based on price and dietary requirements
      - Access a menu that is organised in a logical fashion
      - Enable users to see their student or staff userID
        
        User must be able to see remaining wallet balance
        
        User must be able to see order history
      - Order a randomly selected meal based on a the algorithm provided
      - Meet user experience guidelines and adhere to the BSHS visual identity guidelines
  - - - Shows trending meal items from restaurants
      - Allows user to add customised notes to their orders before proceeding to checkout
      - User can get suggestions based on nearest restaurants in their precinct
      - Displays the approximate time when the order will be ready
      - Users can access a “Your favourites” List based on most ordered meals
    - - User can choose from a wide variety of restaurants to order from
      - The app displays happy or unhappy messages for user feedback
      - Pop-up alerts to confirm purchase from the user
      - Shows current discounts available from restaurants
      - Shows total payments before the user proceeds to checkout
- - - - Algorithm will calculate a random meal when a user clicks on a button (Figure 2)
      - Algorithm will calculate a random drink when a user clicks on a button (Figure 2)
      - Algorithm will calculate a random snack when a user clicks on a button (Figure 2)
      - User will input their price bracket (Figure 2)
      - A WHILE statement will run if the price bracket (user input and declared as variable) is less than the order amount (variable)
    - - Required App Data
        
        Administrators must be able to upload Menu data to the app from a .csv file (dataset)
        
        Administrators are able to upload profile data to the app from a .csv file
        
        Create an order history database based on dataset information
        
        Menu Table
        
        MenuID - uniquely identifies a menu item (type and size elements)
        
        category - category of a menu item (e.g meal, drink or snack)
        
        Description - the description of the snack, item or drink
        
        Price - price of the snack, item or drink
        
        Halal - Does the item contain Halal in it?
        
        Vegetarian - is the snack suitable for vegetarians? (They don’t prefer anima products)
        
        Allergy_Info - either gluten free or not
        
        Profile Table
        
        UserID - the student or staff user ID (e.g jsmith52)
        
        Family - user’s surname
        
        Given - user’s first name
        
        Wallet - user’s available funds
        
        Email - user’s email address
        
        OrderID - user’s order number
        
        History Table
        
        OrderID - order number
        
        OrderTotal - the total price of an order
        
        UserLogin table
        
        UserID
        
        Password
    - - Algorithm must be made to read records from the menu.csv dataset and convert these values into a database table (terminal)
      - SQL command to create a history table
        SQL command to create a userLogin table
        SQL command to create a profile table
      - INSERT query for userID and password when the user signs up
      - SELECT EVERYTHING statement from userLogin to retrieve userID and password based on the user's input
      - SELECT EVERYTHING from menu WHERE price <3, category = 'breakfast' and halal = 'Y'; statement to sort the menu based on price, category and halal option.
  - - - Must display different icons to lead to different screen interfaces
      - Buttons must be unique
      - Font and text size must be clear and consistent
    - - Meals, Drinks, Snacks and Random item
    - - Must show the user’s previous orders made in a chronological order
    - - Responsive interface to improve efficiency throughout the app (Effectiveness)
      - The application must include appropriate attribution to images (Accessibility)
      - Inclusive language and terms for easy comprehension for the users (Accessibility)
      - Simple instructions for all users to comprehend (Effectiveness) E.g readable fonts and appropriate fonts)
      - Simplistic design of UI Components such as button layout (Effectiveness)
      - Concealing passwords when the user logs in to the app (Safety)
      - Centralised UI components such as a “Home Button” on the bottom of the screen to improve familiarisation across screens (Utility)
      - Use of voiceover to support hearing-impaired users who might use the app (Learnability)
    - - Page Titles
        
        Ensure that page titles are appropriate and relevant for the screen
        
        Ensure that page titles are different on every screen
      - Headings
        
        Ensure that headings are on every screen
        
        Ensure that headings are meaningful and contribute to hierarchy
      - Fields
        
        Must ensure that controls have a visible label to allow interaction for the user
        
        Forms of control are clear and indicated; do not rely on colour independently
      - Error Messages (validation messages for the user)
        
        Ensure that messages are clear and specific to for the user
        
        Ensure that print out messages do not disrupt the user experience
      - Accessibility options
        
        Ensure that instructions are clear for the user
        
        Instructions are at the top of of a function to ensure that the user relates to the functions of the app (e.g “Calculate” would be at the top
        
        For certain users, there must be a 5 second time limit for flashing or moving content; this function can be disabled and controlled by the user
    - - Logotype
        
        Must consistent of one typeface but use both light and bold from Helvetica Neue family
        
        Must use corporate blue in percentages
        Helvetica Neue Light (100%)
        Helvetica Neue Bold (75% and 60%)
      - Sub-Graphics
        
        Must be flexible in its use for modern applications
        
        Four blocks of solid colour (Blue, White, Navy Blue and Red)
        First Colour: Must be corporate blue
        
        Minimum of 10mm in height
      - Design Composition
        
        Elements must be legit aligned
        
        Logo must be aligned to the right
      - Logo
        
        Must not be overpowered or crowded by other elements
        
        Minimum size must be 10mm in height to ensure clarity and conciseness
- - - - Junior student who has limited time at lunch due to extra-curricular commitments
      - Spends too much time in the tuckshop queue and is often late to team meetings
      - Amy is a vegetarian and is disappointed when the tuckshop runs out of salad rolls
    - - Senior student who likes to shout his friends to tuckshop now and then
      - He wants to be able to see his wallet balance before offering to pay for his friends
    - - Mr T doesn’t mind the tuckshop queue but gets bored with having the same lunch
      - He likes to browse through what’s on offer but has trouble making a decision