Please enable JavaScript.

Coggle requires JavaScript to display documents.

FIA2: Retreat - Coggle Diagram

- - - - Knowledge in only limited amounts of coding languages (Python, Html, PHP, CSS, SQL)
    - - Computers, Internet and Software (XAMPP, Sublime Text, Bootstap, MeekroDB), Teacher Feedback & Consultation
    - - As per Australian Privacy Principles, care must be taken when collecting and storing user information.
  - - - Ability to create an account through registration
        
        Student information must already be included in student base of possible attendees. Administrators will have to alter student base if a student wants to register although does not appear in student base.
      - Link between registered accounts and student base
        
        System must be able to store identifiers when user logs in. These identifiers allow for the user to be inputted into different tables (i.e. event attendees) and for the user information to be outputted without storing it twice to optimise table layout.
    - - Text readable by screen readers
        
        All text must be formatted in such a way that screen readers work without errors while reading. This includes table data that may come from an array.
      - Alt text for images
        
        For vision impaired, system must include alt texts on images so that screen readers can successfully identify all components displayed on screen.
  - - - All data collected and stored in databases must be correctly formatted and include all information. Certain pieces of data have been seen to cut off when importing csv file into database and must be restored either manually or by the admin.
    - - Data taken from database and displayed on screen must be understandable. This includes changing formatting and displaying data as strings or integers rather an arrays. MeekroDB Quickstart offers support for such task (i.e. converting database table into html table).
  - - - Visual identity must be consistent with all images used. Only authorised images may be included and no alterations can be conducted to such images.
    - - All text displayed to the users must follow Terrace typography requirements.
- - - - Accessbility
        
        How well does the interface cater for users with other needs (like screen readers for the blind), mobility challenged (big buttons etc)?
      - Effectiveness
        
        How well the interface does the job it was designed to do?
      - Safety
        
        How does the interface protect user and admin data and further protect from harmful scripts and data breaches occuring?
      - Utility
        
        How effective it is at providing effective services for the user?
      - Learnabilty
        
        How quickly can users be comfortable using the system?
      - Responsiveness
        
        Will it dynamically re-adjust to the size/capability of the display device?
      - Portability
        
        How platform independent is it?
    - - Register
        
        Register page is specifically for students attending retreats. Data is collected and stored in the userbase table.
      - Events attendance
        
        Organisers are able to select events that they are designated to run granted that the event is currently running. Organisers then allow students to scan their student ID's to attend events. Measures must be taken to ensure students can't attend an event multiple times.
      - Events
        
        Information
        
        Point Leaderboard
        
        Admins are able to view a leaderboard that shows the total number of points (including scaling) for each house. Additionally, house deans may be allowed to see how many students from their house attended events.
        
        Attends
        
        Start and End dates are displayed so that users are able to decide which retreat works best for them.
      - Login
        
        Login allows users, organisers and admins to access their respective pages.
  - - - CSV file into Database
        
        Supplied CSV file must be formatted correctly (remove double-quotes, remove spaces, remove unnecessary commas). Then userbase table must be created from script. Table must conform to the order of data in CSV file. File must be imported and possibly edited to display correct data.
    - - Specific Gmail account must be created and settings changed to allow for script to access it.
    - - SQL database must be made containing required tables. Tables must be created by scripts and stored in document so that errors can be resolved or altering tables is substantially easier.
  - - - Userbase / students
        
        Code
        
        FK
        
        name
        
        yr
        
        pc
        
        house
        
        email
        
        Userbase contains all students of GT and core details about them. These are all the possible attendees of the events and is uploaded onto the database by a CSV file
      - Attends
        
        event
        
        attendee
        
        attend date
        
        Attends table stores all attended events and includes the event (eid) and the attendee (student code) as well as the date and time attended
      - Events
        
        eid
        
        FK
        
        date start
        
        date end
        
        points
        
        event name
        
        organiser
        
        Events are managed by admins and would likely be uploaded prior to each term. Each event is assigned an organiser who manages the attendances for the event. Additionally, events have point scaling, which allows admins to get more support for certain events
      - Users
        
        uid
        
        user type
        
        login
        
        password
        
        username
        
        email
        
        Users table allows user, either student, organiser or admin, to log into the system. Students are able to see which events they've attended, organisers can record attends for events and admins are able to view points leaderboards, input events and add organisers
- - - - Session variables will be used to store sections of code that are only important for one login. This includes the snumber of who is logged in and allows the system to identify the user when interacting with such components like the retreat selection. Further, the 2FA code will be stored in session so that each time the a new user attempts to register it will change, increasing the security of the system.
    - - Databases will store information that must be recorded outside of one session use of the website. This includes registered users, who attends which retreat and the information for each retreat.