Please enable JavaScript.
Coggle requires JavaScript to display documents.
ITRAIN - Coggle Diagram
ITRAIN
Functional Requirements
Registration
Confirmation Emails
External Applications
Barcode Readers
Mobile Phone Access
management
Official
Functions
Attend Events
View Events with all relative information displayed
Check-in Students
Request for a change within teams
Dashboard
View Attendance Records
View Upcoming events relevant
Student Metadata
Log-in
View who attended events, names and tallies
Non-Function Notes
Coaches or Nominated Delegate
Check-in students through mobile phone
Admin
Add Events
Date
time
location
officials hosting
Register Officials
Generate a notification for the official
Metadata from each event
attendance
participation
re-occuring no shows
Check-in Users
Manage Stored User Data
Change Event Details
Change teams
teams must have a minimum and maximum number of players
If a team has too little players then a swap has to occur
Players can be set as a "Fill" player and be in multiple teams
Student
Functions
Dashboard
Past Attendance
Basic metadata
Relevant upcoming events
Register Function
email integration
Login Function
Attend Events
Students can only attend an event once
View Events with all relative information displayed
Non-Function Notes
non-logged in user
View training Schedules
View Training Events
Able to check-in with an in person official
User Authentication
Students should not be able to log-in as an Admin or Official
Database
Users
role
students
official
admin
user_number
full_name
email_address
House
Pc Group
password
Teams
Events
Check-ins
non-functional requirements
security
User Proofing and Privacy
Rorting
Students should only be registered if they are present
Organizers are responsible for those who check-in
Individuals should not be able to register after or before an event start
User Proofing
All inputs need to be filtered
Only handle and store sanitized data
User Testing: This will ensure valid user feedback for improvements and suggestions
Error Prevention: Clear error messages
Data Security
Encrypted User Data
Australian Information Act
Hashed Passwords
Scalability --> The database should be able to handle large fluctuations in traffic
copyright
useability
demographic
Students
Coaches
Parents
Staff
Boundaries and Limitations
System will employ SECURITY of passwords - either hashing or encryption
User-proofing is necessary, only individuals can register their presence
"Rorting" the system will need to be prevented
Coding Languages
MySQL - manages the database within the system
PHP
Javascript
Html
Css
BootStrap
Performance and Reliability
The website should have minimal latency
The website should present minimal or no bugs
The website must work on both newer and older devices