Please enable JavaScript.

Coggle requires JavaScript to display documents.

Safe Travel in Queensland. - Coggle Diagram

- - - - Video Presentation (up to 6 minutes, MP4/MOV/AVI, max 500MB)
        
        Accompanying Script or Speaker Notes (PDF format, showing timing or relation to the video)
        
        References (following the school’s referencing style)
    - - Must Have Pages
        
        Login Page
        
        Admin Panel (View, add, edit, delete users/data)
        
        Possible Data Sources
        
        Insect image upload
        
        Date and Time
        
        Longtitude and Latitude
      - Algorithm
        
        Analyze feedback sentiment (e.g., to track user reactions)
        
        • Detect crowd densities for safety and capacity management
        
        • Provide an AI‐driven chatbot to answer frequently asked questions
        
        • Utilize automated alerts for emergencies or potential threats
        
        • Suggest activities or items based on user preferences (recommendation system)
    - - Comprehend & Describe
        
        User-interface components
        
        Existing solutions to similar problems
        
        Symbolise
        
        UI ideas using sketches, diagrams, or screenshots
        
        Explain
        
        Data structure and user experience relationships
        
        Usability considerations
  - - - Week 6: Mind map, application description, existing solutions research
        
        Week 7: Full draft submission (including audio draft)
        
        Week 9: Final submission (multimedia presentation with slides & script)
    - - Work must be original
        
        Progress monitoring by the teacher at key stages
        
        Draft submission required for feedback
        
        Plagiarism check via Daymap
- - - - learnability
        
        how easy a system is to learn
      - Safety
        
        ability for users to make errors and recover from the mistake - don't confuse safety with security
      - Utility
        
        ability of the system to provide all the functionality that users need
      - Effectiveness
        
        ability of users to use the system to do the work they need to do, includes reliability
    - - ability to be used by many different people, even people with disabilities
  - - - Line
        
        A line can be a starting place, a marker or trigger to change
      - Colour
        
        Choice of colour matters. Be consistent throughout application, and make sure colours chosen are compatible with each other (perhaps use a colour wheel)
      - Point
        
        Smallest element of visual communication, can be a dot but not necessarily circular
      - Space
        
        Used to support meaning or zone groups of data (i.e. space between elements). Used consistently to develop predictability
    - - Tone is light or dark variation of any colour
    - - Shapes can use lines (straight or curved) to develop two-dimensional zoning and the implied boundary of an object. Shapes are good for conveying structure around data. The simplest form of shapes with data is a table. Shapes could also be a circular icon to centre a user to a record button on a phone
    - - Texture refers to the tactile or inferred visual features of an object
    - - Can Give Depth
    - - Texture refers to the tactile or inferred visual features of an object
  - - - Elements should 'line up', commonly used in HTML sign up forms
    - - Contrast refers to opposing aesthetic qualities (i.e., what you see when you compare things that are different) and can be used for to create emphasis or focal point
    - - Where elements are positioned or grouped in relation to each other, perhaps 'clumping' elements near each other that have a perceived relationship (or avoiding those that don't)
    - - Elements should 'line up', commonly used in HTML sign up forms
    - - Repeated elements (such as page constructs, sections or product layouts) which helps predictability
    - - Hierarchy refers to the 'reading order' of a design
    - - Interpreting the proximity to make sure components as a whole provide valuable meaning and are complementary across the interface. For example, sometimes it is better to split datasets across screens for example to avoid confusion
- - - - • Provide different data displays depending on user roles
      - • Integrate external data (e.g., local transit updates, nearby services)
      - • Enable localization for different languages or regions
      - • Collect and analyze metrics (e.g., attendance, engagement, donations)
      - • Considerations:
      - • Respect cultural nuances, including religion, ethnicity, and diverse backgrounds
      - • Follow usability guidelines to accommodate various user groups
      - • Focus on local community needs