Please enable JavaScript.
Coggle requires JavaScript to display documents.
FIA2 - Terrace Support System - Coggle Diagram
FIA2 - Terrace Support System
User Interface
Pages
Dashboard: a basic overview of attended and upcoming events, points earned by student's house, number of points earned by student; since all of this information should already be in the DB, the code should simply retrieve this information and display it in some sort of table to the user
Events - The user should be able to see a list of past and upcoming events in one list preferably. Bootstrap cards should be used to display the information. Ideally, events that have occurred in the past should be greyed out, with upcoming events emphasised.
Leaderboards - A list of all relevant leaderboards; student leaderboards, house leaderboards, etc. This page will allow encourage the student to participate more, and to regularly attend house events
Profile - this page should display information regarding a student's involvement in the Support program; a summary of points, attended events, badges (if applicable), and other applicable information
Contact/FAQ - A contact/FAQ page should be made available to users, in order for them to seek help if need be
The UI for the system should be relatively basic, with only basic information for users; nothing more than necessary should be displayed to the user. Considering that Year 5, 6, 7 (young) students will be using the system, a difficult-to-use and complicated system will be of no use to these students
Coding/Programming
PHP
HTML
SQL
Styling/Theme/Aesthetics
Should be somewhat Terrace-styled (refer to the Terrace style guide), and should not just be a Bootstrap site
Colours: Red, black, grey (in some instances)
Data
MySQL
Tables
Attendance - should show which users have attended which events; this could be achieved by, say, have USER_ID attended EVENT_ID at time_date, where the USER_ID and EVENT_ID then become the primary key of the table, with these primary keys as the foreign keys, as well.
Events - e.g. event_id, event_name, time_date, etc. - this table should have everything in relation to the events table
Users - e.g. user_id, username, first name, etc.; note that this table should be applicable for both teachers AND organisers AND admin (there should only be one admin account, really)
Will be connected to by MeekroDB; MeekroDB is the method by which information is retrieved from the MySQL database
MeekroDB
Limitations, Boundaries
Organisers may be added by the admin/s (ideally, this should be a feature of the system), however, this may be difficult to implement
A teacher registration (and admin registration process, even) would be relatively messy, considering that separate registration processes would have to be developed; as such, for this implementation of the system, only a student registration process will be implemented