evaluating information from multiple perspectives. Simple language and limited scientific words in response to talking to audience, reading texts suited to the audience, surveys and observing audience answering questions. the prototype including giving them options to choose. Designs two lists of questions and asks users which one would be best to use. show the relationship between user decisions; includes codes to show input and output. Each answer is a score that is developed on a scale in relation to other answers (for example, uses a scale from ‘No impact’ to ‘Disaster’ in order to give responses a numerical answer. Algorithm is shown using colour coding or shapes to distinguish between input and outputs. making changes based on the feedback and final prototype. Observes and takes note of what the users are doing, identifying when they do something makes changes as required and then re-checks the prototype. why the algorithm is sequenced and operates in a particular way, giving examples of Explains the steps using words such as input, output and algorithm. Shares with audience why they designed elements based on feedback and research. Proficient Designs questions Asks for feedback from Creates an algorithm Observes and Articulates why the
after evaluating information from more than one source. Simple language and limited scientific words in response to talking to audience and reading texts suited to the audience. users about different elements of the prototype. Asks people to check questions make sense and are easily understood during development. that works, making alterations as needed. Uses symbols to explain process. The same number of options is at each step and the most popular response identifies feedback. Uses symbols such as arrows to show in the algorithm. questions making changes based on the feedback. Observes and takes note of what the user is doing, identifying when they do something making changes as required. algorithm is sequenced and operates in a particular way. Explains the steps and can explain why a user would get specific feedback. Designs questions using some understanding of audience. Simple language and limited scientific in response to talking to audience. Considers the user when developing prototype. Lists questions in order to show the process of the algorithm. Limits number of steps in the algorithm to keep it simple. Chooses to reduce the number of steps as they find the algorithm Observes user or asks questions but does not take in feedback. May take notes of user but does not use this to make changes. Models how the paper prototype works. follows the steps of the algorithm.
too difficult. Emerging Develops questions prior knowledge of the audience. Simple language and limited scientific words are used without consulting with audience. Develops a prototype by listing elements. Relevant questions are developed in an ad hoc manner with no clear order. Attempts to create steps but these are not sequential or connected. Steps are simple and answers are not consistent. Uses prior knowledge to make changes, or uses self as an example. Relies on own experiences following the algorithm to test prototype. Asks for support to follow the steps of the prototype. Completes some steps but becomes unsure at times.