Please enable JavaScript.
Coggle requires JavaScript to display documents.
IA2 Mindmap - Coggle Diagram
IA2 Mindmap
User Experience
User Support
Banners will appear at the bottom of the page to visually notify users of certain processes that occur
These will be styled based on the nature of the message eg: (green - success, red - warning)
Navigation will be consistent throughout the solution as the navigation bar/ hamburger menu will not change
Navigation elements will be consistent throughout the solution meaning that a user can easily navigate the solution regardless of what page they are on
Accidental form resubmission will be avoided through the use of GET and POST variables, ensuring that the user's inputs are always intentional
Accessibility
Icons will be placed adjacent to text, ensuring that the user is familiar with each icon
-
Through the use of 'tabindex' global attribute, pages can be easily navigated strictly through keyboard use
It will also be ensured that this order of 'tabindex' is logical, and flows consistently throughout all pages
Secondary information that is hidden at first glance will be accessible through other forms eg: modals, popups etc.
This ensures that the simplicity of the interface doesn't interfere with the usability and helpfulness of the solution
Aria-labels will be given to each image, ensuring that screen-readers are able to comprehend images
-
-
When expressing text, abbreviations and symbols will be discouraged as oversimplification often decreases the solution's accessibility
Usability
Effectiveness
-
Inputs will be cleaned and checked before use, ensuring that a user's inputs are accurate and relevant to the process
It will be ensured that the solution focuses on error-prevention in that it will be difficult for a user to make a mistake
Solution's interface will be minimalistic, maximising the range of features available whilst also ensuring that the interface isn't cluttered
Learnability
-
Site layout will be consistent throughout all pages. Elements used in the interface will be mirrored throughout it, ensuring that the site feels 'connected' and 'linked'
-
-
Responsiveness
-
-
The Bootstrap 4 framework will be used to develop a mobile-first front-end. This framework simplifies web responsiveness
The layout of the solution on a mobile viewport is considered before the development of the larger viewport layout
Dynamically adjusts the sizing of images, text, columns, rows etc.
Brand tie-in
-
-
-
Terrace images will be placed throughout the solution, ensuring that the focus on Terrace is apparent
Navigation
Navigation elements will be located at the top of the page as either a hamburger menu or a standard navigation bar depending on the viewport of the device
-
Conditions
-
-
-
As this solution involves students, information of students must be kept secure
-
Password hashing, salting
-
-
Functionality
Security
-
-
-
Password salting
-
Ensures that although two passwords may have the same hash, their hashed value when a salt is appended is different
-
-
-
-
This salt is generated upon the creation of each stored credential rather than per user or system-wide.
File Uploads
This is essential as mentors are required to upload an image of their blue card when they register for the solution
The file extension of the image needs to be checked; however, this can be bypassed through the use of a double file extension
-
Password hashing
Passwords aren't stored as their original value. Once a user submits a password, it will be hashed.
Using SHA-256, inputted passwords are transformed into a 256-bit hash value that is usually represented as a hexadecimal number of 64 digits.
-
Processes
-
Admin
-
-
Can create sessions for individual students if need be or can simply create sessions for a common need
-
-
-
-
Boundaries
For student information, a provided .csv file will be used rather than direct integration with TASS
This integration with TASS allows for student data to be secure and always up to date (data is already authenticated)
-
To access the site as a mentor, your blue card must be approved by an admin ensuring that your access to the site is appropriate
To use the site, you must have verified your account through the email verification process
-
-
A student can't participate in a session that has already met it's maximum number of students (student limit)
-
Hardware/devices
Responsivity
When the viewport is decreased, the navigation bar will be restructured to fit the design of a hamburger menu rather than a normal navigation bar
The size of text, buttons, images, tables etc. will dynamically resize based on the viewport
Interface development is centered around rows and columns (bootstrap 4) allowing for content to easily resize and change layout for different viewport sizes.
In order to facilitate this web responsivity, bootstrap 4 will be used as a front-end framework for easy mobile-first web development
This aspect of responsivity contributes to the user friendliness and the usability of the solution as a wider range of devices can be used to access it, increasing its target audience
-
Platform
Solution will be platform independent as it will use bootstrap to dynamically restructure the page layout based on the device's viewport
On smaller devices, buttons and other elements will be made larger to still stand out on the smaller viewport
Audience
-
Mentor
-
-
In order to be able to use the system as a mentor, you must have a valid blue card that is approved
Has the ability to create and facilitate mentoring sessions with students to assist them with schoolwork
-
Data Requirements
External Datasets
Userbase
-
This is used as sample data to mockup a solution that would be applicable for a much larger number of students
In the final solution, the solution would be integrated with TASS, allowing for data to be constantly up to date and secure
-
Internal Datasets
Sessions
-
-
Extra session info -> (mentor, student limit, subject, etc.)
Users
Table that contains all user information for students, mentors and admins.
This table could be linked to a further two tables (students, mentors). This would remove the possible NULL fields in the users table. The information that is common to all users (username, password, etc.) will then be stored in the users table
Subjects
-
Simply a list with a subject id, subject name and a year level.
Year level column is important as various mentors may only be able to assist students up to a certain level for some subjects
-
Student sessions
-
-
Contains extra information regarding the student in relation to the session (attendance, notes, status etc.)