Please enable JavaScript.

Coggle requires JavaScript to display documents.

IA1 Practise Mind Map - Coggle Diagram

- - - - API Data?
      - Open Data?
      - User Data?
- - - - Learnability and Effectiveness
        
        Users must be able to access data quickly, with the input and output fields must be presented clearly with easy access.
        
        Design Principles (CARP) - Contrast, Alignment, Repetition and Proximity.
      - Utility
        
        Portability and Responsiveness of Website - it is usable and visually appealing across multiple devices.
      - Accessibility
        
        How accessible the web app is to all different kinds of user groups. This can be achieved through:
        
        Text colour contrast - not only visually appealing but it can impact the website's functionality in transmitting information.
        
        Screen reading - which is easily defined navbars, buttons and headers for ease of access.
        
        Accessible/applicable images - Image files with an 'alt' tag as well as images that are aesthetically complementary to the website.
      - Safety
        
        The web app must have measures to create a safe environment for the user.
        
        Hiding user data
        
        Warnings/Pop-ups that ask for the user's private details
  - - - Alignment
      - Repitition
      - Contrast
      - Proximity
      - Balance
      - Harmony
      - Hierarchy
    - - Space
      - Line
      - Colour
      - Shape
      - Texture
      - Form
      - Proportion
      - Scale
- - - - For the user interface, it could include the equipment used, how they'll interact with the solution and specific text/data field that they'l see on a visual display
      - For the data interface, it could focus on datasets, file formatting, data structure, cleaning up the data, restructuring and the collection of more data.
    - - Calculating, adding, storing and processing user data
  - - - Intellectual property
      - Copyright
      - This will appear in each ongoing section for non-functional requirements:
        
        Adheres to the data privacy act of 1998
        
        States that users must give permission before data can be stored about them
        
        Requires a privacy policy page explaining what the data will be used for
        
        "Personal data stored on a web server is governed by the specific data privacy laws of the country where the server is hosted"
      - Existing contractural arrangements
    - - Cost of creating and maintaining the solution
        
        Time limits
        
        Resources needed
        
        Administration of maintaining data validity/reliability/integrity after the project is deployed
    - - Pertains to the environment in which the project will be made/published
        
        For example:
        
        There's no point making a game for the original xbox if no one uses it anymore.
    - - Are requirements that are derived from "organisational style guides" such as CARP, and market research about the target audience. "How it looks"
  - - - Due date/deadline
      - Budgets
      - Availability of development team
      - ESRB Guidelines
      - Skills of development team
      - Technical capabilities of user enviornment
      - Legal constraints