VCE Software Development U3O1 Crossword: Naming conventions and internal documentation and Pseudocode (Modules 48–71)
Name:
Date:
Class:
✎
Crossword
Read each clue and write the matching term in the grid. Numbers in brackets show the letters in each word.
1
2
3
4
5
6
7
8
9
10
Across
- 3. A consistent rule for ______ code structures: snake_case verbs for functions and methods (get_total), CamelCase nouns for classes (StudentRecord). Pick one style and stick to it. Word 2 of: ______ __________ (10)
- 6. Word 4 of the term in 5 Down: # array used _______ ____ is fixed (4)
- 8. Comments inside the code, like a header with purpose, author and date, and notes on each function, that help others (or you later) understand and safely change the program. Word 1 of: ________ documentation (8)
- 9. A naming style where a variable name starts with a short lower-case prefix showing its data type, e.g. strName, intAge, fltPrice, blnPassed. Word 2 of: Hungarian ________ (8)
- 10. Word 2 of the term in 2 Down: __________ (4)
Down
- 1. A triple-quoted string on the first line of a function or class body. It documents what the code does, its parameters and its return value. help() displays it. (9)
- 2. A naming convention that writes every letter in lower ______ and joins words with underscores, e.g. student_first_name. Python uses it for variables and functions. Word 1 of: __________ (5)
- 4. Word 1 of the term in 3 Across: ______ __________ (6)
- 5. A comment that explains what a variable, array, record or algorithm is for and why it was chosen, rather than just repeating what the code does. Word 3 of: # array used _______ ____ is fixed (7)
- 7. A Python statement that does nothing. It fills a stub's empty body, often beside a # TODO comment, so the program still runs while the real code is written later. (4)
Answer Key
VCE Software Development U3O1 · Modules 48–71
1D
O
2S
3C
O
4N
V
E
N
T
I
O
N
5B
S
A
A
6S
I
Z
E
T
M
K
7P
C
R
8I
N
T
E
R
N
A
L
9N
O
T
A
T
I
O
N
S
U
N
G
10C
A
S
E
S
G
E
Across
3CONVENTION — A consistent rule for ______ code structures: snake_case verbs for functions and methods (get_total), CamelCase nouns for classes (StudentRecord). Pick one style and stick to it. Word 2 of: ______ __________
6SIZE — Word 4 of the term in 5 Down: # array used _______ ____ is fixed
8INTERNAL — Comments inside the code, like a header with purpose, author and date, and notes on each function, that help others (or you later) understand and safely change the program. Word 1 of: ________ documentation
9NOTATION — A naming style where a variable name starts with a short lower-case prefix showing its data type, e.g. strName, intAge, fltPrice, blnPassed. Word 2 of: Hungarian ________
10CASE — Word 2 of the term in 2 Down: __________
Down
1DOCSTRING — A triple-quoted string on the first line of a function or class body. It documents what the code does, its parameters and its return value. help() displays it.
2SNAKE — A naming convention that writes every letter in lower ______ and joins words with underscores, e.g. student_first_name. Python uses it for variables and functions. Word 1 of: __________
4NAMING — Word 1 of the term in 3 Across: ______ __________
5BECAUSE — A comment that explains what a variable, array, record or algorithm is for and why it was chosen, rather than just repeating what the code does. Word 3 of: # array used _______ ____ is fixed
7PASS — A Python statement that does nothing. It fills a stub's empty body, often beside a # TODO comment, so the program still runs while the real code is written later.