Please enable JavaScript.
Coggle requires JavaScript to display documents.
STATE HIGH ONLINE TUCKSHOP SYSTEM (SHOTS) (IMPACTS (Positive reception of…
STATE HIGH ONLINE TUCKSHOP SYSTEM (SHOTS)
CLIENT
CONSTRAINTS
App must be developed within an 8-week timeframe
Features of the app are limited by the data provided by the stimulus
REQUIREMENTS
App must incorporate a pre-ordering feature for users
Orders must be given a unique order number
Users must be able to access their profile user their staff or student ID
Users must be able to filter the menu based on price and dietary requirements
App's menu must be organised in "a logical fashion"
Users must be able to randomly order a meal based on an algorithm provided in the stimulus
Users need to be able to select the collection point of their meal (e.g. upper-campus canteen)
App must be developed as a mobile application
EXISTING SOLUTIONS
UBER EATS
Food delivery app that, while not competing with SHOTS, has an intuitive user interface layout that could be mimicked to improve usability
Insightful use of notifications to alert the user of their order progress
Strong use of table views to display menus in an easy-to-browse manner
USER REQUIREMENTS
PRESCRIBED
AMY
Limited lunch time due to commitments
Canteen queue is too long for schedule
Vegetarian; disappointed when canteen runs out of vegetarian food
Junior student
GUS
Would like to be able to see his wallet balance
Allergic to peanuts
Senior student
MR. T
Teacher
Gets bored with having the same lunch over and over again
Has trouble making a decision but likes to browse
SELF-PRESCRIBED
STUDENTS
App should disclose whether a canteen item is halal, vegan, vegetarian or gluten-free and should disclose whether an item contains nuts
App should disclose the quantity of each item at the canteen
IMPACTS
Positive reception of SHOTS will result in shorter canteen queues and a less busy canteen store
SHOTS can make the canteen much more efficient and save students' lunch time through its preordering system
Less staff will be required to process payments in the canteen
Pre-orders will improve the accuracy of the canteen's safety stock and inventory demand calculation (as consumer demand can be predetermined)
DEVELOPMENT
DATA
DATA ACCESS
Admins will be able to access menu item details and manage user account details (credit card information will not be stored server-side, the user can utilise Apple Pay to store payment information)
Users will be able to view and edit their own personal information, and will be able to view menu details but not edit them
DATA RETRIEVAL
Data will be stored in an SQLite 3 database and retrieved through SQLite 3 queries and statements
Requests for data retrieval will be done through Swift algorithms (which incorporates SQL queries) in the XCode IDE
CODING ENVIRONMENT
DEVELOPMENT TOOLS
App will be developed using the XCode IDE for iOS, specifically the iPhone 11
Databases to be created and edited using SQLite 3. Extensive knowledge of relevant queries and statements such as "INSERT INTO", "SELECT *", "DELETE" etc. is required.
KEY ALGORITHMS / QUERIES
Algorithm comprising of SQL queries and Xcode functions will be required to generate a random canteen item recommendation for the user
Algorithm comprising of SQL queries and Xcode functions will be required to allow the user to add items to a cart and order using their preferred payment method
USER INTERFACE
WEB CONTENT ACCESSIBILITY GUIDELINES 2.1 (EFFECTIVENESS, ACCESSIBILITY, UTILITY)
The visual presentation of text and images of text must have a contrast ratio of at least 4.5:1
The visual presentation of UI components and graphical objects must have a contrast ratio of at least 3:1 against adjacent colour(s)
Do not design content in a way that is known to cause seizures or physical reactions
SCREENS
MAIN SCREEN
Screen that greets the user when opening the app, includes direct access to all other screens apart from checkout
Should utilise the recommendation algorithm to suggest a menu item for the user
VIEW CART SCREEN
Should show all the items the user has ordered, the cost and quantity; user should select payment option here as well
CHECKOUT SCREEN
User processes his / her payment here using their selected payment method
SEARCH SCREEN
Allows the user to search for a particular menu item by name or by category
ORDER HISTORY SCREEN
Shows the user's order history, including the quantity of items and total order cost
SETTINGS SCREEN
Should include settings to permanently filter out certain items so the user does not need to do it every time (e.g. gluten free, halal)
USABILITY PRINCIPLES
App should be laid out in an intuitive manner with headings, subheadings to guide the user; buttons should be visible and easy to understand and touch (EFFECTIVENESS, ACCESSIBILITY, LEARNABILITY, UTILITY)
App should not record, store or ask for information of the user that is not necessary for the app to function. Information that is important and can be stored (e.g. payment details) should be extremely secured and only stored at the discretion of the user. (SECURITY)
App should be use colours that do not inhibit or reduce the visibility of text or other aesthetic features (UTILITY, ACCESSIBILITY