Please enable JavaScript.

Coggle requires JavaScript to display documents.

DS IA3 - Part 1 - Coggle Diagram

- - - - The coded components and elements that make up the “front end"
    - - The coded components that make up the back end “back end”
    - - The components (such as DBMS) that are connected to the “front end” of the user interface via the server interface (“back end”).
  - - - Asynchronous JavaScript XML - is a web development architecture that updates small sections of the web app in the background so the page doesn’t need to be reloaded.
      - It makes the page load and process faster
      - We used this for our Google Map API, so it could continually update and process itself without having to continually reload the page.
      - Read page 304-305 in the textbook for more information.
    - - Extensible Markup Language (XML) is an extension to HTML.
      - It allows developers to create data tags for storing formatted data in a web page with a “hierarchical tree structure”.
      - Values are contained within key tags, which are contained within record tags, within dataset tags.
      - XML has pretty much been superseded by JSON.
    - - JavaScript Object Notation is a data exchange protocol that is standard now.
      - It stores data in key-value pairs (much like python dictionaries).
      - JSON protocol allows a connection to interact with online data
        
        JSON API - (client side) manages the data exchange using HTTP GET and POST requests.
        
        Data API - (server side) responds to the requests by sending the data as a JSON object.
      - Some Data APIs allow Parameters to be used to control access to the data or query a subset of it only
      - Parameters are passed to the web server as key-value pairs embedded in the URL request.
  - - - Stands for Representational State Transfer
      - It is a particular architecture for setting up a client-server relationship that uses JSON or XML formatted data to allow for access to a particular resource.
      - Rest uses the HTTP verbs - GET, POST, DELETE, PUT
      - It assumes a “state-less” approach - which takes every request as a standalone (self-descriptive) request.
      - It assumes data will be cached - where a cache is a reserved storage location that collects temporary data to help websites, browsers, and apps load faster. It’s the ‘quickest storage there is’.
  - - - Requests data
      - JSON dataset received
      - Date stamped data (ensures validity and relevance)
      - Asynchronous data exchange in real time
    - - Generates & sends the JSON data
      - API - only provide data requested
      - Database - data elements
      - Transmit/send relevant data
- - - - Are the three main security risks threatening digital solutions that exchange data. These include:
      - Confidentiality: The possibility that a person who is not authorised to see the data will do so when it is in transit.
      - Integrity: The possibility that someone may intercept the data message and modify or replace it with malicious intent.
  - - - Fingerprint identification on the data packet. Provides a mathematical result from the binary of the data. This result is sent with the message
    - - Hashing is the process of converting a given key into another value. A hash function is used to generate the new value according to a mathematical algorithm.
    - - Is the process that scrambles readable text so that it can only be read by the person who has the secret code or description key.
      - Asymmetric Encryption
        
        Asymmetric encryption works with two keys - one public and one private. The public key (the method of sending the data) is public to everyone. The private key is the only method of decrypting the data, and is kept private to ensure the exclusivity of the sent data.
      - Symmetric Encryption
        
        Symmetric encryption works on a single key and is therefore faster than the alternative asymmetric encryption. For symmetric encryption, the sender must share the private key with the receiver to access the sent data/information. This, however, is less secure than asymmetric encryption as hackers only need to get one of the keys for the information.
- - - - The API must provide a variety of API requests, with each providing different data
      - API must provide personal data about the member such as name, age, year level, boarder/non-boarder
      - Includes non-personal data such as competition results, competitor results, team they belong to, and the team names
      - Data must be normalised into third normal form
    - - Must be accessible on personal computers and mobile devices, through different web browsers
      - Feature a responsive web interface
    - - Code must retrieve data from the API
      - Must contain appropriate commenting
      - The code must be accurate and efficient
    - - You are asked to develop a prototype for the API using Python 3 and Flask. The API will access
      - The data from a local SQLite 3 database.
      - Web app must be based on python 3, Flask, and Bootstrap
      - You do not have to develop the user data entry for the web app; however, you are asked to create an SQLite database with test data
      - ● Both Flask servers are to run on your local computer.
      - ● The API must offer replies to a set of API requests providing a variety of data.