VCE Data Analysis Word Scramble: Requirements, constraints and scope and Design tools for databases, spreadsheets and visualisations (Modules 68–80)
Name:
Date:
Class:
🔤
Word scramble
Unscramble the letters and write each key term on the line.
1
CEPSO
The boundary of what a solution will and will not include. Features inside the boundary are in ______. Features left out, or saved for later, are out of ______.
2
URMSQEIERNET TILS
A list that sorts what a solution must do (requirements) from the limits it must work within (constraints), for one problem. Each item should be clear and testable.
3
REETPIGRITNN A EBFIR
Reading a teacher's brief to find the data, calculations and outputs needed, the constraints that limit the solution, and what is out of scope.
4
PIO RHTAC
A three-column table listing a solution's inputs (data entered), the processes applied to that data, and the outputs it produces, such as a total or report.
5
TNODAEATN GIAADMR
A diagram of a database or spreadsheet with labels and notes on its parts, such as tables, fields, data types, cells, formulas and validation, explaining what each part does.
6
HDAETSEPRES CMPU-OK
A sketch of a spreadsheet's worksheet names, header labels, data areas, formatting and result cells, drawn before building to show how it will look and where results will go.
7
UYERQ GDIENS
A plan for a database query that lists the table, the fields to show, the criteria used to filter records and the sort order, written before the query is built.
8
DSLEFI, ETIIRACR, TROS
The three parts of a query design: which fields to show, which records match the criteria (using AND/OR), and how results are sorted, so the output meets the requirement.
9
RTIEPTGEIRNN A SDNGEI
Reading a design's IPO chart, annotations, mock-ups and query designs together to work out what must be built, and checking it matches the requirements.
Answer Key
VCE Data Analysis · Modules 68–80
1CEPSO → scope — The boundary of what a solution will and will not include. Features inside the boundary are in scope. Features left out, or saved for later, are out of scope.
2URMSQEIERNET TILS → requirements list — A list that sorts what a solution must do (requirements) from the limits it must work within (constraints), for one problem. Each item should be clear and testable.
3REETPIGRITNN A EBFIR → Interpreting a brief — Reading a teacher's brief to find the data, calculations and outputs needed, the constraints that limit the solution, and what is out of scope.
4PIO RHTAC → IPO chart — A three-column table listing a solution's inputs (data entered), the processes applied to that data, and the outputs it produces, such as a total or report.
5TNODAEATN GIAADMR → annotated diagram — A diagram of a database or spreadsheet with labels and notes on its parts, such as tables, fields, data types, cells, formulas and validation, explaining what each part does.
6HDAETSEPRES CMPU-OK → spreadsheet mock-up — A sketch of a spreadsheet's worksheet names, header labels, data areas, formatting and result cells, drawn before building to show how it will look and where results will go.
7UYERQ GDIENS → Query design — A plan for a database query that lists the table, the fields to show, the criteria used to filter records and the sort order, written before the query is built.
8DSLEFI, ETIIRACR, TROS → Fields, Criteria, Sort — The three parts of a query design: which fields to show, which records match the criteria (using AND/OR), and how results are sorted, so the output meets the requirement.
9RTIEPTGEIRNN A SDNGEI → Interpreting a design — Reading a design's IPO chart, annotations, mock-ups and query designs together to work out what must be built, and checking it matches the requirements.