Please enable JavaScript.

Coggle requires JavaScript to display documents.

DS Mindmap - Part 2 - Coggle Diagram

- - - - A ‘jitter’ can occur when the data sent and the data deceived do not match, possibly resulting in unwanted glitchy effects, screen flickering, or a poor performance. Given that this is a problem on the user’s end, there is little the proposed solution can implement to prevent this issue besides streamlining all processes where possible.
    - - Latency’ refers to the time it takes to travel from one place to another - it can be influenced by serialisation (size of the packet/speed of the network), propagation (low internet cabling), switching (routers or switches being used during data transmission), and queuing (busy routes).
  - - - RESTful
    - - JSON
    - - Flask
    - - SQLite
  - - - Search By:
        
        Student/Player Profiles
        
        Player Profile Page
        
        Customised by relevant student
        
        Card that links to the team page of their team
        
        Some data (such as user bio) is private unless user is logged in
        
        Competition Search
        
        Results Page
        
        Scrollable cards displaying the competition name, result, and year
        
        Displays relevant team logo and a link to the teams page
        
        Filterable/sortable by alphabetical, date, and result
    - - Topmost table
        
        Displays Team logo
        
        Team members
        
        Team captain
      - Displays team results
      - A promotional video for the team with ability to upload if user is the team leader
    - - Displays cards of all members
      - Filterable alphabetically, by team, or by grade
    - - Features
        
        Introductory Information
        
        Album of team cards that link to their respective team page
        
        Pedestal Placements table
      - Link to login card
        
        Username and password field
        
        "Remember Me" option
- - - - result_id PK
      - team_id FK
      - competition_id FK
      - game
      - placing
      - year
    - - team_id PK
      - team_anme
      - team_logo
      - prom_video
    - - member_id PK
      - team_id FK
      - team_leader
      - username
      - password
      - first_name
      - last_name
      - grad_year
      - address
      - boarder
      - personal_email
      - school_email
      - biography
    - - competition_id PK
      - competition_name
      - competition_year
- - - - Integrity
        
        Hacking to alter data
      - Availability
        
        Breach of private user information
      - Confidentiality
        
        Improper storage of sensitive user information
  - - - As explored on the previous slide, encryption not only adheres to SDC5, but prevents unauthorised eyes from interpreting stored data in a database without an encryption key.
    - - By hashing the sensitive and more desirable information in the database, a message digest can be used to ensure that no information was tampered with or altered from its original state.
    - - This threat could be defended through the implementation of a reliable login system. This would allow the web application to separate the two different types of users and distribute their privileges accordingly. To protect this system, all stored usernames and passwords must be encrypted and hashed, as well as be updated regularly, so even if the attacker uses a VPN, the data is protected.