VCE Data Analytics U4O1 Definitions Worksheet: Data quality and testing visualisations to Recording and assessing project progress (Modules 85–105)
Name:
Date:
Class:
✎
Key terms
Write what each term means, in your own words.
1
Visual inspection
2
representative chart
3
evaluation criterion
4
time frame
5
Responsibility
6
apply a criterion
7
user feedback survey
8
Adjusting tasks
9
Adjust time frames
10
annotation
11
role
12
change count
13
avoidable or unavoidable change
14
Impact of a change
Answer Key
VCE Data Analytics U4O1 · Modules 85–105 · Student wording will vary for definitions
1Visual inspection — Looking over a finished visualisation for layout, readability and formatting faults, such as overlapping or cut-off text, hard-to-read labels, poor alignment and spacing, on the target screen.
2representative chart — A chart whose plotted values, axis scales and categories all match the source data, so it shows the data truthfully and does not mislead the viewer.
3evaluation criterion — A measurable standard used to judge a solution, linked to a requirement and written so it can be answered with evidence, such as a target, a yes/no check or a rating.
4time frame — States when each evaluation activity will happen and how long it has, such as during or after the project, with dates linked to milestones.
5Responsibility — In an evaluation strategy, it names who carries out and reports on each evaluation task, such as the developer, the client or user, or an independent reviewer.
6apply a criterion — Test the solution against a criterion, record the result (met, partly met or not met) and justify the rating with evidence. Recommend improvements if it is not fully met.
7user feedback survey — Set questions you ask users after they try your solution. You record their ratings and comments, then sum up the answers to compare with your criteria.
8Adjusting tasks — Adding, removing, reordering or reassigning tasks when a project changes, and recording each change in the plan so the plan stays accurate and up to date.
9Adjust time frames — Update start dates, durations and deadlines when a task runs long or short, then check the knock-on effect on dependent tasks and work out the revised finish date.
10annotation — A short dated note on a project plan that records what changed and why, and keeps the original plan visible next to the actual dates.
11role — A job given to one team member with set tasks they are responsible for, so no task is missed and no two people do the same work twice.
12change count — The number of changes made to a project plan, tallied from its annotations. Few changes suggest the plan matched the work well; many suggest it did not.
13avoidable or unavoidable change — A change is avoidable if better planning, such as a poor estimate, could have prevented it. It is unavoidable if it came from outside the developer's control, like new requirements.
14Impact of a change — How much a change affected the finish date, the scope and the quality of the finished solution, such as delay, dropped features and extra effort.