Please enable JavaScript.

Coggle requires JavaScript to display documents.

IA1 Terrace - Coggle Diagram

- - - - The online shop will be responsive (work on multiple viewports)
      - Elements will adjust based on varying viewport sizes
      - Online shop can be run on multiple different platforms
    - - Site will be operable on different sized viewports
      - A responsive framework (eg: Bootstrap 4) will be used to achieve complete responsiveness
      - Hamburger menu will replace normal navigation bar on a smaller viewport
    - - The interface will be minimalistic in order to maximise the variety of features available without cluttering the interface too much
    - - The same colour scheme and font families will be used
      - Site layout for the shop will remain consistent across all pages
      - Buttons will accompany links to instruct the purpose of a button
  - - - Orange for a warning element (eg: student incorrectly adding products to cart)
      - A red banner will be used on the page to indicate an error (eg: Incorrect student information for login system)
      - Green banner to indicate that the user has completed an action successfully (eg: successfully logged in)
- - - - already authenticated data (TASS)
  - - - Manages users data
      - Able to register shop attendants
      - Can change the price of products - modify items table
      - Manage inventory - stock level, reorder point, reorder quantity stored in items table
      - Generate summaries as sales reports
      - See/change all aspects of the stored data within their scope
    - - Mediate Sales
      - Compile orders from purchase orders - use order status in database
      - Able to observe the perpetual record of sales
    - - Logged-in
        
        Have student ID to link purchases and orders
        
        Purchases are made on the site
        
        Collected and paid for on pickup
        
        Payment Method is stored upon ordering
      - Anonymous
        
        Can browse products
        
        Can't purchase items - no information to track purchases
  - - - The current user's cart information will be stored using a multi-dimensional array in a session variable - this will work for both anonymous and signed-in users.
  - - - In order to protect the user's personal details (name contact info etc.) all of their information will be encrypted.
        
        Symmetric Encryption
        
        Uses a secret key which is applied to the content to change it in a particular way.
        
        Sender and receiver must know the secret key in order to unlock the information. This poses a risk to the information if someone has access to the key when they shouldn't.
        
        Asymmetric Encryption
        
        Slower than symmetric encryption; however, you don't have to worry about passing public keys over the internet.
        
        With asymmetric encryption, two related keys are used (key-pair). One of the keys is available to the public so you can encrypt the data. Then there is another key which is then kept secret
        
        Any message that is encrypted by using the private key can only be decrypted by using the matching public key.
    - - Gurantees to the user that they are accessing the server they are supposed to
        
        Adds a level of trust to the user so that they are more likely to user your site
    - - Header that tells the browser to limit the amount of Script executed on the page
        
        Protects against XSS attacks
    - - Add a 'salt' to the start or the end of a password before hashing
        
        A salt is a fixed-length cryptographically strong random value
      - Can mitigate the damage that a rainbow table or a dictionary attack could do
      - Makes passwords look non-deterministic
      - Since a salt is not an encryption key, it can be stored in the table right next to the hash
      - To prevent identical password hashes when users use the same password, different salts are used to make the passwords seem different
      - Create these salts using a cryptographically secure pseudorandom number generator (CSPRNG)
      - A salt is generated upon the creation of each stored credential rather than per user or system-wide
- - - - Allows for mobile-first front-end development
- - - - would integrate into TASS for further implementation
      - Used for parent account authentication using student's email and sid
    - - Provides the item information needed to flesh out the product-related tables
  - - - Table that contains all the information of parents who have signed up for the online uniform shop.
    - - This table contains all of the basic information for each item of the shop.
      - This information is created from the uniform shop price list which is given externally
      - Reorder point and reorder quantity are added to this table
    - - This table contains variations of each item with sizes and stock levels attributed to it.
      - Each item in this table has its own 'barcode' which is used to identify each item
    - - This table contains all of the basic transaction information for an order. It will have an ID which will link to the receipt contents table
    - - This table contains information of each product purchased in an order.
      - The item price will also be recorded in this table just in case the price for an item changes in the future
    - - This is simply used to authenticate a parent's account with their son's student ID
      - The parent will enter their son's snumber and an email will be sent to them with a code to verify the parents account
- - - - Logged-in
      - Anonymous