Please enable JavaScript.
Coggle requires JavaScript to display documents.
iSupport - Coggle Diagram
iSupport
User Experience
-
Student Persona
Dashboard
View House ranking (e.g Rediy is in 2nd place, 7 points behind Magee. Appearance of the dashboard is altered depending on House. E.g, Barrett will have some blue scattered throughout the dashboard, while Kearney student will have yellow.
View badge - depends on how many attends they have (every five/ten attends, they receive a higher ranked badge)
-
-
Information
View information such as upcoming events - the value of the event, event duration, location etc. - information about 1st teams (e.g First V Basketball players) May contain information relating to other cultural activities. Information about rewards (badges, tangible rewards such as tuckshop pass)
-
Organizer Persona
-
Dashboard
Relatively empty - line of text directing the organizer to the navbar button. Not much is needed on this page. Just a landing page with access to all the different pages.
Availabilities
Submit NA
Select day/s where they cannot take attends for events or specify a time range where they cannot take attends. Cannot during be the current week. Rosters are already made. Organizers will need to call admin/s a couple days before rostered event/s to allow admin/s to assign a new organizer.
-
-
Admin Persona
Add Organizers
Relative simple form with relevant inputs - details of the volunteered organizer (first name, surname, email address, etc.)
Dashboard
Relatively empty - line of text directing the organizer to the navbar button. Not much is needed on this page. Just a landing page with access to all the different pages.
Create Events
Relatively simple form with relevant inputs - event name, event start times and finish times, location, description etc.
Link to email
This will take admin to an inbox that will accept emails from organizers (admin will need to specify their chosen email address)
Summary of attendances
Will display attendances by chosen year/month. Reduces clutter by reducing the number of attendances that can be displayed on the screen. In a month there will already be hundreds of attendances to be displayed. As this is the case, could be further sorted down to house and/or year level.
Reducing the amount of scrolling one would have to do to see all events. If the admin wants to find attendance information for a specific house, they can sort the displayed information to do so.
Welcoming users by name, telling them they are 'Logged In as...'
Each user level will need to login, and each user will be able to log out.
Each user level has a collapsible navbar featured on all of their designated pages that displays links to the various pages they have access to
Functionality
Admin Only
-
-
-
If necessary, they can manage stored user data
Roster Management
Select an event and select available organizers to take attends for that event. Add orgid under the eid of the selected event
Organizer/Official Only
-
Availabilities
Submit NA - Select day/s where they cannot take attends for events or specify a time range where they cannot take attends. They will not be rostered for the events that occur duing these specified time/s
-
-
Students
Register page
If scode exists and the scode does not have a corresponding password, the password is put into the database for scode password column
-
-
Security
"Secure" Transaction? (using localhost so it's not really "secure") Final implementation of the system will use HTTPS
Block access to certain pages if they don't have a specific user level e.g Student Dashboard will block organizers and admins
Not specifying if the username or password is wrong, or saying that the username is already taken
-
-
-
Devices
Screen sizes - Phone, tablet, PC
The Design of the webpages should adapt to different screen sizes (Responsive Design - Bootstrap)
Affordances (Mouse/Touch/Graphics Card)
Must account for situations where certain affordance aren't present