Please enable JavaScript.

Coggle requires JavaScript to display documents.

IA1 Mind Map - Coggle Diagram

- - - - Reviews Table
        
        review_id (PK) (int)
        
        member_id (FK) (int)
        
        t_app_id (FK) (int)
        
        review_text (varchar)
        
        review_rating (float)
      - Members Table
        
        member_name (varchar)
        
        member_id (PK) (int)
        
        memberdesc (varchar
        
        club_position (varchar)
      - Apps
        
        gps_id (FK) (int)
        
        aas (FK) (int)
        
        t_app_id (PK) (int)
      - Google Play Store
        
        rating (float)
        
        reviews (varchar)
        
        category (varchar)
        
        size (float)
        
        app (varchar)
        
        installs (int)
        
        app_id (PK) (int)
        
        type (varchar)
        
        price (float)
        
        content_rating (varchar)
        
        genres (varchar)
        
        last_updated (varchar)
        
        andriod_ver
      - Apple App Store
        
        price (float)
        
        rating_count_tot (int)
        
        currency (varchar)
        
        rating_count_ver (int)
        
        size_bytes (int)
        
        user_rating (float)
        
        ver (varchar)
        
        track_name (varchar)
        
        id (PK) (int)
        
        cont_rating (varchar)
        
        prime_genre (varchar)
        
        sup_devices.num (int)
        
        ipadsc_urls.num (int)
        
        vpp.lc (int)
  - - - 0NF
      - 1NF
      - 2NF
      - 3NF
- - - - Definitions
        
        Are a specific list of actions controlled by code
        
        Could be for the user interface or data interface
        
        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.
        
        Also includes the requirements for the coded components
        
        Calculating, adding, storing and processing user data
        
        What the solution needs to do
  - - - Due date/deadline
      - Budgets
      - Availability of development team
      - ESRB Guidelines
      - Skills of development team
      - Technical capabilities of user enviornment
      - Legal constraints
  - - - Legal
        
        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
      - Economic
        
        Cost of creating and maintaining the solution
        
        Time limits
        
        Resources needed
        
        Administration of maintaining data validity/reliability/integrity after the project is deployed
      - Environmental
        
        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.
      - Aesthetic
        
        Are requirements that are derived from "organisational style guides" such as CARP, and market research about the target audience. "How it looks"
      - Non-functional requirements are "how it needs to do it" - are specific features about how the coded components should work
- - - - Multiple choice questions
      - Large amount of surveyed users
      - Usually performed in a digital medium
    - - Longer-form questions
      - Lower amount of distinct interviewees
      - Usually in person
    - - The four usability principles are:
        
        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
    - - Create a low-fidelity prototype (sketch) and evaluate the emotional reaction it could garner from the user by assessing its adherents to the elements and principles of visual communication.
      - Sketches & Drawings
    - - Elements
        
        Alignment
        
        Repitition
        
        Contrast
        
        Proximity
        
        Balance
        
        Harmony
        
        Hierarchy
      - Principles
        
        Space
        
        Line
        
        Colour
        
        Shape
        
        Texture
        
        Form
        
        Proportion
        
        Scale
  - - - Slideshow (A3 Pages)
        
        Adheres to standard grammar conventions
      - Video
        
        Structure of QCAA Example
        
        Video of Slideshow
        
        9-11 Minute
        
        no larger than 500MB
        
        in mp4, mov or avi file format
        
        Structure
        
        Exploration (0.5 minutes)
        
        User (3min)
        
        Introduction (0.5 minutes)
        
        Data (3min)
        
        Proposed Solution (3min)
        
        Conclusion (0.5min)
        
        Evaluation (0.5min)
        
        Acknowledgements (<0,5min)
      - Referencing of sources, using Harvard or APA
    - - Read the technical proposal (stimulus material) and present a proof of concept for a new web application.
        Document the use of the Digital Solutions problem-solving process in responding to the problem and generate the data-driven solution. The technical proposal provides further details about the requirements for the new web application.