Please enable JavaScript.
Coggle requires JavaScript to display documents.
Tuckshop - Technical proposal - Coggle Diagram
Tuckshop - Technical proposal
Devices
Web application should be accessible from all platforms including smartphone, pc, smart tv, smart watch or any other web accessible technologies
Design should be device and screen size responsive
Functionality
food waste considerations, what happens if a student. parent orders but the food is not picked up. what happens if a student has ordered but is away that day?
Ordering process - excluding the technological considerations should function effectively as a "click and collect" system.
Prevent gaming / rorting of system by students
Data Management
SQL Database
Data design
Foreign and primary key considerations
Primary identifier: snumber/ adminnumber / convenernumber
order is compiled from user data and order data, into an order list which is effectively a receipt containing menu ids, student ids, date/time under an "order id", the data from this table will then be used in compiling the convener view and product requirments
security consideratons
basic psudocode process has been created for a verifying of student existence on the database and sign up process
In a final implementation use of hashing and encryption techniques is intended
Contained within the database should be all user ordering data, this will be arranged within SQL "tables" such as: a "students" table as well as tables for both user users that being "convener" and "administrator", ideally using sample data their should be the list of all students within a register table.
Note: No active connections should exist between the web application database and the terrace student management system TASS nor should payment processing be handled in the database
Accessibility
simple design and descriptions of available products
images as well as descriptive texts
web design and user principals should be followed, e.g navigation bar and helpful directioning