VCE Software Development - Chapter 1 Vocabulary

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/22

flashcard set

Earn XP

Description and Tags

Vocabulary flashcards focusing on exam command terms, data types, data structures, constraints, requirements, and design tools from Chapter 1.

Last updated 1:59 AM on 9/1/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

23 Terms

1
New cards

Identify (Command Term)

State the correct concept or answer.

2
New cards

Explain (Command Term)

Show how or why something occurs, not merely what it is.

3
New cards

Justify (Command Term)

Give a reason that connects your choice to the scenario.

4
New cards

Compare (Command Term)

Identify a relevant similarity and/or difference between alternatives.

5
New cards

Evaluate (Command Term)

Make a judgement using relevant strengths, weaknesses or evidence.

6
New cards

String Data Type

A data type used when a value is an identifier rather than a quantity, which preserves leading zeros.

7
New cards

Floating Point Data Type

A data type appropriate for storing numerical values that can contain decimal places.

8
New cards

Record Data Structure

A data structure used when several related fields describe one entity and may use different data types.

9
New cards

Two-Dimensional Array

A data structure representing a grid where row and column indices identify individual items.

10
New cards

Functional Requirement

A requirement that specifies a required behaviour or action the system must perform.

11
New cards

Non-Functional Requirement

A requirement that specifies system qualities or operational attributes, such as usability or robustness.

12
New cards

Technical Constraint

A technical limitation (such as low network speeds) that impacts how an application or interface is designed.

13
New cards

Economic Constraint

A budget or cost restriction that limits project capabilities and affects scope.

14
New cards

Data Dictionary

A design tool that records data elements and characteristics such as variable name, data type, purpose, format, and validation rules.

15
New cards

Interface Mock-Up

A visual design tool that represents the appearance of a system screen rather than algorithmic logic.

16
New cards

Pseudocode

A text-based design tool used to represent calculation steps and algorithmic logic.

17
New cards

IPO Chart

A design tool that supports an overview of system inputs, processing, and outputs.

18
New cards

CSV (Comma-Separated Values)

A simple file format suitable for small, simple, tabular datasets and spreadsheet-style exports.

19
New cards

XML (Extensible Markup Language)

A cross-platform, self-describing file format that supports structured and hierarchical data transfer between applications.

20
New cards

Internal Documentation

Comments embedded in code that explain complex logic, document inputs/outputs, and assist with safe maintenance.

21
New cards

Camel Case

A naming convention (e.g., customerName) applied consistently to improve code readability and maintainability.

22
New cards

Recommendation

An answer component that explicitly names the choice or tool being selected.

23
New cards

Justification

An answer component that explains why a selected choice fits the specific scenario provided.