Because this is a "presentation" genre you should NOT be "reading your slides", as the content on text printed on these slides will be included in your desktop capture video. 

This means viewers are free to pause the video and read at their leisure, provided they are given the chance to do so - so no 'super fast' clicking either!

This will ensure your pre-recorded presentation does not go over 11 minutes, and that your spoken communication is "value adding", "commentating" or "emphasising" the content viewable on each slide (i.e. not "reading" the slides word for word).

Complete this in PowerPoint and write your "speakers notes" below each slide. When this is complete, submit both a desktop video capture of your presentation and a PDF printout of your PowerPoint slideshow showing speakers notes. (I will additionally take a copy of your PowerPoint file, although this will not be submitted to QCAA).

-----------------------------------------------------------------------
| Scaffolding Headings for PowerPoint (with explanations and timings) |
-----------------------------------------------------------------------

PROBLEM IDENTIFICATION AND DATA ANALYSIS (suggested up to 2 minutes):
- take / restate requirements from task sheet, for example "This technical proposal is for a new, innovative web application utilizing Brisbane City Council data that improves the economic / environmental liveability of Brisbane." 
- present (recognise) 2 different data sources and describe (description in your own words) from the BCC open data portal, remember to reference (URL)!
- dataset analysis (point analysis, good / bad, and most importantly potential ideas for usage)
- make a justified decision on dataset / solution by evaluating personal, social and economic impacts and considerations of each (be succinct)
- with analysis of "relevant contextual information", propose your 1 solution:
  - identify risks to the project (these may be real or simulated), based on the previous personal, social and economic impacts and considerations 
  - research (keep this quick):
    - existing solutions to similar problems (be brief - very short)
    - tech stack (showing development tools)
    - define scope of the problem, assumptions, constraints and / or limitations (of the environment)


##### roughly 2 minutes to here, by now you have locked in your 1 idea! #####


SOLUTION REQUIREMENTS AND SEPECIFICATIONS (suggested up to 2 minutes, explain each of these, there are 4 items here so perhaps 30 seconds each):
- DETERMINE essential Prescribed and Self-determined Criteria (!IMPORTANT)
- DFD
  - determination of external entities and their interactions with system (level 0)
  - determination of data flow, data stores and processes (level 1)
- ERD
  - determination of tables and fields
  - normalisation? (not required, but always welcome)
  - relationships (cardinality / modality / crows feet notation)
- CREATE table statements + Data (i.e., Table) Dictionary explaining table / field usage:
  - field names, data types, other constraints (NOT NULL / UNIQUE etc)
  - any foreign key constraints (PARENT / CHILD tables, CASCADE changes)?


##### roughly 4 minutes to here #####


USER EXPERIENCE (suggested up to 2 minutes)
- recognition and description of useability principles
- rough sketches to determine GUIs (sketchy GUIs / pencil / preliminary / 'mock-ups')
- recognition and description of user-interface components in GUI sketches
  - form controls: list boxes, text fields, combo boxes, sliders, etc.
- tag and annotate with useability principles
  - explain ideas (meaning has each useability principle been applied)
- explain interrelationships between data structures and user experience. Do this by annotating links between user-interface components or rendered content, and your table definitions (i.e. where the data comes from or goes to)


##### roughly 6 minutes to here #####


ALGORITHMS AND PROGRAMMING COMPONENTS (suggested up to 2 minutes)
- determine (i.e. write) SQL statements and algorithms pseudocode (consistent wording, indenting, syllabus standard)
  - include a 'worthy' selection of SQL and algorithms that range SIMPLE to COMPLEX
  - keep modular! (separate)
- description of programming elements (meta information)
  - add comments / annotations to SQL and pseudocode (as you would in regular code), describing how what have written actually works
  - if you can, evaluate your algorithmic scalability (did you use variables or structures that can be easily manipulated, or easily increased in size or complexity to accommodate feature creep or repurposing), efficiency (what is the worst case run-time), ability to tolerate fault (recover from error), or other technical / systems criteria (from theory) wherever possible
  - EXPLICITLY COMMUNICATE ANY REFINEMENTS (with reasoning) TO SQL / ALGORITHMS
  - identify programming component relationships to the structure of the problem, meaning:
    - explicitly identify event triggers for algorithms in the GUIs
    - explicitly identify SQL relationships to both table definitions and algorithms, for example, expected return data types of an SQL query to its method call


##### roughly 8 minutes to here, but if you can save time above do it, as the next section DEMONSTRATION will likely be the longest ##### 


LOW-FIDELITY PROTOTYPE DEMONSTRATION (suggested up to 3 minutes but can go slightly over as evaluation can be sped up if necessary)
- bring what you have done to life (via fake interface controls, colours and more "pretty" GUI versions than the mock-ups / rough sketches drawn earlier) - DO NOT CODE ANYTHING SERVER-SIDE OR CLIENT-SIDE. 
- populate with real data to make it look real
- promote the useability principles when talking (accessibility, effectiveness, safety, utility, learnability, and any others that warrant a mention) in your demonstration, particularly elements such as help / error recovery / assistive compatibility (such as containers marked with html5 semantic elements) / screen size adaptiveness and responsiveness (resizable / stacking containers etc)
- continuous evaluation of refinements (e.g. from the original outline sketches) and recommendations as per the problem-solving process in Digital Solutions


##### roughly 10 minutes to here, but if you are racing, you can speed up the evaluation section to perhaps less than 30 secs #####


EVALUATION (this will be quick - as you won't be reading it, just leave it up on screen for long enough that it can be paused by the viewer.)
- addressing 1 ISMG criteria: "critical evaluation of impacts, components and low-fidelity prototypes against effective prescribed and self-determined criteria to make refinements and astute recommendations justified by data."

  - evaluation of:
    - impacts (include personal, social and economic impacts.. and though not required, perhaps consider ethical, legal, sustainability impacts?)
    - components (include algorithm accuracy and efficiency.. and consider other measures of algorithms, SQL and UI components studied in class)
    - low-fidelity prototype (include user-interface.. consider UX)
  - AGAINST:
    - prescribed criteria
    - self-determined criteria
  - TO MAKE:
    - refinements (you can 'tag' these throughout, explicitly label them 'refinements', and refer back to them where possible)
    - recommendations (for now and future)
  - JUSTIFIED BY DATA. (IMPORTANT! testing - quantitative / anecdotal)


REFERENCE LIST (IMPORTANT! must have at least 1 or 2 references)
  - proper academic standard referencing

*** finally: spell-check, proof read and remove any scaffold notes ***


##### maximum 11 minutes from start to end, do not go a second over or it will be sent back for redaction #####