VCE Software Development U3O2 Word Scramble: Project reasons and the brief to Needs, requirements, constraints and scope (Modules 12–24)
Name:
Date:
Class:
🔤
Word scramble
Unscramble the letters and write each key term on the line.
1
GTIRNILYIOA
How a proposed solution is new or different from existing software, such as unique features, while avoiding copying the work of others.
2
KATS DBAEONWRK
Splitting a whole project into small tasks, each with a clear outcome, a time estimate and an order (dependencies), so you can track progress as the work gets done.
3
ENGSNIEUCQ
Putting tasks in the order they must happen on a Gantt chart. Tasks that depend on others start after them, while independent tasks can run in parallel (at the same time).
4
IETM OLTCAOLAIN
The estimate of how long each task will take, shown on a Gantt chart as the length of its bar. Bars are measured in days or weeks and together set the total project length.
5
ENYENPDDCE
A link between two tasks where one cannot start or finish until the other is complete. The first is the predecessor, the next is the successor. Shown on a Gantt chart by an arrow.
6
TOLSMIENE
A marked checkpoint in a project plan, such as a finished prototype, showing a major piece of work is complete by its deadline. Used to check progress.
7
LIACTRIC HPAT
The longest chain of dependent tasks in a project. It sets the shortest possible finish time, and any delay to a task on it delays the whole project. Tasks off it have float.
8
TROEJCP GOL
A record of each work session: the date, what was done, any problems and the next step. It shows actual progress against the plan and evidences why the plan changed.
9
NGTTA RAHTC
A bar chart built by listing tasks, estimating durations, ordering them by dependency, then marking milestones and the critical path on a timeline.
10
VGEIBOSNR
Watching a user do a task to see where they get stuck, without helping or interrupting. You write down what you see instead of just asking them what they think.
Answer Key
VCE Software Development U3O2 · Modules 12–24
1GTIRNILYIOA → originality — How a proposed solution is new or different from existing software, such as unique features, while avoiding copying the work of others.
2KATS DBAEONWRK → task breakdown — Splitting a whole project into small tasks, each with a clear outcome, a time estimate and an order (dependencies), so you can track progress as the work gets done.
3ENGSNIEUCQ → Sequencing — Putting tasks in the order they must happen on a Gantt chart. Tasks that depend on others start after them, while independent tasks can run in parallel (at the same time).
4IETM OLTCAOLAIN → time allocation — The estimate of how long each task will take, shown on a Gantt chart as the length of its bar. Bars are measured in days or weeks and together set the total project length.
5ENYENPDDCE → dependency — A link between two tasks where one cannot start or finish until the other is complete. The first is the predecessor, the next is the successor. Shown on a Gantt chart by an arrow.
6TOLSMIENE → milestone — A marked checkpoint in a project plan, such as a finished prototype, showing a major piece of work is complete by its deadline. Used to check progress.
7LIACTRIC HPAT → critical path — The longest chain of dependent tasks in a project. It sets the shortest possible finish time, and any delay to a task on it delays the whole project. Tasks off it have float.
8TROEJCP GOL → project log — A record of each work session: the date, what was done, any problems and the next step. It shows actual progress against the plan and evidences why the plan changed.
9NGTTA RAHTC → Gantt chart — A bar chart built by listing tasks, estimating durations, ordering them by dependency, then marking milestones and the critical path on a timeline.
10VGEIBOSNR → observing — Watching a user do a task to see where they get stuck, without helping or interrupting. You write down what you see instead of just asking them what they think.