Please enable JavaScript.
Coggle requires JavaScript to display documents.
Eat Safe Search BNE - Coggle Diagram
Eat Safe Search BNE
The Client
-
-
Constraints
Developer Environment
-
-
-
Legalities, such as copyright
-
Criteria
Prescribed
· Allow the admin user to modify the dataset to see all records, retrieve, insert, update and delete records. (PC1)
· Allow the guest user to filter the dataset by suburb, eat safe rating and permit name (PC2)
· The function to validate or deny admin access to the data manipulation based on correct/incorrect login details inputted on the user login popup with a maximum number of failed attempts being 3. Login errors are followed by feedback popup error boxes. (PC3)
-
· Must be compatible for all mobile devices (Portable laptops, phones, tablets etc) (PC5)
· The application must comply with the provided accessibility guidelines adapted from the Australian Accessibility Standards, including window titles, window headings, elements, error (or validation) messages, accessibility options. (PC6)
Self-determined
· The user(guest, admin) must be able to efficiently complete an accurate interaction with the data
-
· The Eat Safe data, while not private or sensitive, should be protected so changes cannot be made by unauthorised/unauthenticated users(which would render the data useless), increasing the level of data safety
-
-
· A high level of portability must be ensured and maintained to increase responsiveness on tablets, laptops and mobile phones.
· Efficient both in reference to the speed the solution completes a task at, and the reduction of time spent, and resources consumed in the solution's generation
-
· Confirmation must be sought from the user before completing an interaction, as the user may not have intended to initiate the function
· The system must be maintainable to an extent where potential problems can be fixed almost instantly.
· The code used to generate the solution must be accurate, effective, maintainable, reliable and efficient. (SC16)
· The eatSafe data must be refined and cleaned through an accurate process to render it processable (SC17)
.
• The data in the database must be up-to-date, accurate and reliable. (SC20
-
-
The Developer
-
User Experience
Flow of functionality
Home page
-
-
Admin Login
-
If Admin login attempts is 3, lock them out
The User
Personas
Persona 1 - Ian
Goals - to have access to a Mobile app that lets him check if a business has an adequate eat safe rating before eating there
-
-
Persona 2 - Alex
Goals - To have the Food Permit dataset in a mobile application to immediately update records on her phone (Admin)
-
Digital Literacy - Well versed, uses an iPad Pro and Windows 10 Laptop
Persona 3 - Chaya
Goals - To have a web application to let her immediately check if a business has a valid permit and an eat safety rating for her job
-
Digital Literacy - Low. She can use an iMac for some causes but has no familiarity with other devices or systems
Impacts
-
Personal
• Application spreads awareness on healthy and clean eating
• Application provides transparency on food safety which could lead to businesses improving their food practices.
Social
• By having up to date data, the society of Brisbane is able to make informed decisions on where to eat.
Ethical
Ethical
• Data centres consume electricity, which could pollute the environment
-
-