VCE Software Development U3O2 Word Scramble: Needs, requirements, constraints and scope and Analytical tools and the software requirements specification (Modules 26–41)
Name:
Date:
Class:
🔤
Word scramble
Unscramble the letters and write each key term on the line.
1
ACORENDYS AADT
Data already collected by someone else, such as error logs, sales or incident reports. Analysts study it to find problems and needs, after checking it is current and reliable.
2
CTEMHITA NLSIAAYS
Sorting similar interview and survey responses into themes, then counting how often each appears, so the most common problems and wishes become the user needs.
3
CMOCNIOE SNCIATOTNR
A limit on money that restricts a solution, such as a fixed development budget, software licence fees, or the ongoing costs of hardware, hosting and staff.
4
ALLEG NNTOSICRTA
A law or regulation a solution must obey, such as privacy law, copyright and licensing rules, or industry regulations. It limits what the software can do and how it handles data.
5
CILSAO ICRNOTATNS
A limit on a solution from the needs, values or abilities of the people affected, such as accessibility, cultural expectations and user acceptance.
6
HNECATILC STCOTNNIAR
A limit set by technology, such as the hardware, operating system, network or existing software, that a solution must work within.
7
RVOEISN NYRBDOUA
A line that sets which features go in the current release and which wait for a later version. It also marks where the solution ends and other systems begin.
8
LTLACAYIAN OSOLT
Diagrams like context, data flow and use case diagrams that show how users, data and systems relate, so the existing system is understood before a solution is designed.
9
TXCTENO MDRAAGI
A Level 0 diagram that shows the whole system as one process in the centre, with external entities around it outside the system boundary.
10
TAAD OLFW
A labelled arrow on a context diagram showing data passing between an entity and the system. The arrowhead shows direction (input or output) and the label names the data.
Answer Key
VCE Software Development U3O2 · Modules 26–41
1ACORENDYS AADT → secondary data — Data already collected by someone else, such as error logs, sales or incident reports. Analysts study it to find problems and needs, after checking it is current and reliable.
2CTEMHITA NLSIAAYS → thematic analysis — Sorting similar interview and survey responses into themes, then counting how often each appears, so the most common problems and wishes become the user needs.
3CMOCNIOE SNCIATOTNR → economic constraint — A limit on money that restricts a solution, such as a fixed development budget, software licence fees, or the ongoing costs of hardware, hosting and staff.
4ALLEG NNTOSICRTA → legal constraint — A law or regulation a solution must obey, such as privacy law, copyright and licensing rules, or industry regulations. It limits what the software can do and how it handles data.
5CILSAO ICRNOTATNS → social constraint — A limit on a solution from the needs, values or abilities of the people affected, such as accessibility, cultural expectations and user acceptance.
6HNECATILC STCOTNNIAR → Technical constraint — A limit set by technology, such as the hardware, operating system, network or existing software, that a solution must work within.
7RVOEISN NYRBDOUA → version boundary — A line that sets which features go in the current release and which wait for a later version. It also marks where the solution ends and other systems begin.
8LTLACAYIAN OSOLT → analytical tools — Diagrams like context, data flow and use case diagrams that show how users, data and systems relate, so the existing system is understood before a solution is designed.
9TXCTENO MDRAAGI → context diagram — A Level 0 diagram that shows the whole system as one process in the centre, with external entities around it outside the system boundary.
10TAAD OLFW → data flow — A labelled arrow on a context diagram showing data passing between an entity and the system. The arrowhead shows direction (input or output) and the label names the data.