VCE Vault

VCE Applied Computing: Software Development past exams 2023–2025

Every question from the last three VCE Applied Computing: Software Development exams, matched to the lesson that teaches it, with class averages from the examiners' reports and worked solutions. VCE Applied Computing: Software Development (Year 12) lessons.

2025 Exam

  • MC 1 (1 mark, class average 83%): Name the data structure shown as a row of indexed decimal values. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 2 (1 mark, class average 78%): Which naming convention a lower-case variable name with words joined by `_` uses. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 3 (1 mark, class average 69%): Most likely cause of a syntax error reported by the compiler. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • MC 4 (1 mark, class average 71%): Control structure used by a set of IF and ELSEIF branches. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 5 (1 mark, class average 55%): Compare cash bonuses for different numbers of referrals by tracing the bonus pseudocode. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables, Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 6 (1 mark, class average 55%): UX characteristic most in need of improvement in a tax calculator mock-up. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • MC 7 (1 mark, class average 80%): Choose the IPO chart that matches the tax calculator. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • MC 8 (1 mark, class average 95%): Factor most relevant to a constraint about devices with little processing power. Lesson: The Problem-Solving Methodology for Software Development
  • MC 9 (1 mark, class average 52%): Pick the missing use cases and includes/extends relationships for a parking app. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • MC 10 (1 mark, class average 69%): Who the unlabelled actor in the parking use case diagram is. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • MC 11 (1 mark, class average 79%): Access modifier that keeps an attribute visible only inside its own class. Lesson: Object-Oriented Programming — Classes, Objects, Encapsulation, Generalisation and Inheritance
  • MC 12 (1 mark, class average 98%): Benefit of commenting out code while debugging. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • MC 13 (1 mark, class average 85%): Best way to record and deal with a delay to a task on the critical path. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • MC 14 (1 mark, class average 76%): Long-term impact of unmanaged scope creep on a large software project. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • MC 15 (1 mark, class average 42%): Which statement about a constant, a global variable and a local variable is wrong. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 16 (1 mark, class average 86%): Pick the example of an insider threat to a development environment. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 17 (1 mark, class average 75%): Most important security control for sensitive visitor data stored on one device. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 18 (1 mark, class average 71%): Which action would breach the Copyright Act 1968 when updating third-party software. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development
  • MC 19 (1 mark, class average 84%): Which option is one of the Essential Eight strategies. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 20 (1 mark, class average 65%): Why using AI to write the first code for every new package is an ethical issue. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development
  • B1a (1 mark, class average 63%): How tasks are put in order on a Gantt chart. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • B1b (2 marks, class average 55%): One milestone in Sayid's project and why it helps monitor progress. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • B1c (2 marks, class average 40%): How Sayid can use a Gantt chart to monitor and document progress. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • B2 (2 marks, class average 40%): A strategy to improve secure development practices among new developers. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B3 (4 marks, class average 40%): Two risks of updating live business software in a combined environment. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B4 (4 marks, class average 90%): Match four error descriptions to error types. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • B5a (1 mark, class average 79%): Best data structure for the game's 5 × 5 board. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • B5b (2 marks, class average 25%): Best data type for a player's symbol, with a reason. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • B5c (2 marks, class average 30%): Two benefits of sending each move as XML. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • C1 (3 marks, class average 60%): Three reasons the head office might start a software development project. Lesson: The Problem-Solving Methodology for Software Development
  • C2 (4 marks, class average 30%): Justify building the web application in-house rather than outsourcing it. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C3 (4 marks, class average 53%): Best data collection method for property managers and for the leadership team. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • C4a (4 marks, class average 78%): Fill in the two entities and two data flows missing from the Level 1 DFD. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • C4b (2 marks, class average 20%): Find and explain the error in the Level 1 DFD. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • C5 (3 marks, class average 80%): Classify three statements as functional or non-functional requirements. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams, The Problem-Solving Methodology for Software Development
  • C6 (4 marks, class average 50%): Complete a mind map for the prospective landlord component. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • C7a (2 marks, class average 40%): One benefit of inheritance, with an example from the case study. Lesson: Object-Oriented Programming — Classes, Objects, Encapsulation, Generalisation and Inheritance
  • C7b (2 marks, class average 40%): Name sections A and B of the object description. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles, Object-Oriented Programming — Classes, Objects, Encapsulation, Generalisation and Inheritance
  • C7c (4 marks, class average 48%): Fill in the two missing attributes of RentalProperty and their data types. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles, Programming Fundamentals — Data Types, Data Structures and Control Structures
  • C8 (4 marks, class average 18%): For each dashboard sketch, justify a UX characteristic it shows better than the other. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • C9 (3 marks, class average 17%): How user-centred design can make the application efficient and effective. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles, The Problem-Solving Methodology for Software Development
  • C10a (4 marks, class average 30%): How identity and access management and version control protect development. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C10b (1 mark, class average 17%): A threat modelling principle that follows defining security requirements. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C11a (1 mark, class average 68%): Validation technique used on line 2 of the rental application pseudocode. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C11b (2 marks, class average 55%): One more validation check the rental application code needs, and why. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C11c (6 marks, class average 60%): Complete a test table for the rental application check, with rent of 2000 per month. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C12a (1 mark, class average 56%): Which user group should beta test retrieving an inspection report. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C12b (3 marks, class average 17%): Describe a beta testing strategy using property owners. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C13 (3 marks, class average 33%): An issue with how the project log records changes, and two ways to improve it. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral

2024 Exam

  • MC 1 (1 mark, class average 91%): What a type check makes sure of. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • MC 2 (1 mark, class average 47%): Stage of the problem-solving methodology in which usability testing happens. Lesson: The Problem-Solving Methodology for Software Development, Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 3 (1 mark, class average 64%): Contents of an array after one pass of selection sort. Lesson: Searching and Sorting — Linear and Binary Search, Selection Sort and Quick Sort
  • MC 4 (1 mark, class average 65%): Which pseudocode correctly swaps the first two values of an array. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures, Searching and Sorting — Linear and Binary Search, Selection Sort and Quick Sort
  • MC 5 (1 mark, class average 38%): Which factor relates to the scope of a new solution. Lesson: The Problem-Solving Methodology for Software Development, Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • MC 6 (1 mark, class average 58%): Number of binary search iterations needed to find a value in a sorted array. Lesson: Searching and Sorting — Linear and Binary Search, Selection Sort and Quick Sort
  • MC 7 (1 mark, class average 91%): Best protection against an organisation losing its data. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 8 (1 mark, class average 87%): A key consideration for organisations when they develop software. Lesson: The Problem-Solving Methodology for Software Development
  • MC 9 (1 mark, class average 68%): Effect of a two-day delay to one task on later tasks in a Gantt chart. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • MC 10 (1 mark, class average 61%): Best name for a drop-down list for choosing a state. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures, Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • MC 11 (1 mark, class average 76%): SRS feature most relevant to deciding which pool lane a lesson uses. Lesson: The Problem-Solving Methodology for Software Development, Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • MC 12 (1 mark, class average 70%): Data collection technique that would measure the efficiency of an existing app. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams, The Problem-Solving Methodology for Software Development
  • MC 13 (1 mark, class average 61%): Which option isn't a technique for managing files effectively. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 14 (1 mark, class average 73%): Output of a short WHILE loop that updates two variables. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables, Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 15 (1 mark, class average 95%): Defining feature of a man-in-the-middle attack. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 16 (1 mark, class average 70%): Which technique isn't part of a risk management strategy for development. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 17 (1 mark, class average 96%): Good way to manage the risks of third-party software. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 18 (1 mark, class average 55%): A criterion for judging how effective development security strategies are. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 19 (1 mark, class average 64%): Which statement about a five-second credit card validation is most likely true. Lesson: The Problem-Solving Methodology for Software Development
  • MC 20 (1 mark, class average 42%): Missing line that makes nested discount IF statements work. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables, Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • B1 (3 marks, class average 97%): Choose a data type for each of three variables in a data dictionary. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures, Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • B2a (1 mark, class average 67%): First advantage of giving customers regular software updates. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B2b (1 mark, class average 53%): A second, different advantage of regular software updates. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B3a (1 mark, class average 71%): A tool that shows which tasks are on the critical path. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • B3b (3 marks, class average 40%): How tracking the critical path and progress could have avoided running out of time. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • B4 (4 marks, class average 73%): Sort four statements into goals and objectives for an organisation and an information system. Lesson: The Problem-Solving Methodology for Software Development
  • B5a (1 mark, class average 73%): One functional requirement of a satellite image zoom app. Lesson: The Problem-Solving Methodology for Software Development, Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • B5b (2 marks, class average 25%): Pick the magnification tool with better affordance and give a reason. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • B6a (1 mark, class average 40%): Describe cross-site scripting. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B6b (1 mark, class average 30%): One technique to protect a website against cross-site scripting. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B6c (2 marks, class average 20%): How cross-site scripting affects the integrity of user data and the site owner. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C1a (1 mark, class average 21%): Why the reliability of the rewards app matters. Lesson: The Problem-Solving Methodology for Software Development
  • C1b (1 mark, class average 48%): Why the number of failures matters when judging reliability. Lesson: The Problem-Solving Methodology for Software Development
  • C1c (1 mark, class average 10%): When to evaluate the reliability of the rewards app. Lesson: The Problem-Solving Methodology for Software Development
  • C2 (2 marks, class average 90%): Classify two constraints as usability or technical. Lesson: The Problem-Solving Methodology for Software Development, Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • C3a (3 marks, class average 63%): Fill in the actor and two relationship labels in a partial use case diagram. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • C3b (1 mark, class average 31%): Draw the association for the Use points use case. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • C4a (2 marks, class average 35%): Fill in the missing entity and data flow in the points balance DFD. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • C4b (2 marks, class average 35%): Say whether the diagram is a level 0 or level 1 DFD, with one reason. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • C5 (3 marks, class average 37%): Justify a record over a 1D array or an associative array for customer data. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • C6 (3 marks, class average 33%): Justify a linear or binary search for finding a customer by phone number. Lesson: Searching and Sorting — Linear and Binary Search, Selection Sort and Quick Sort
  • C7 (2 marks, class average 55%): Two reasons locking a cancelled customer out beats deleting all their data. Lesson: The Problem-Solving Methodology for Software Development, Legal Obligations, Ethics and Emerging Trends in Software Development
  • C8a (1 mark, class average 46%): Write a third criterion for judging the accessibility of the login designs. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles, The Problem-Solving Methodology for Software Development
  • C8b (1 mark, class average 99%): Choose the better login design. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • C8c (2 marks, class average 70%): Justify the choice of login design using the evaluation criteria. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • C9 (2 marks, class average 35%): One benefit each of CSV and XML for storing and updating points balances. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • C10 (3 marks, class average 47%): Justify staying with agile or switching to waterfall when the client changes requirements. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • C11 (2 marks, class average 25%): Another data integrity characteristic a reusable discount code would damage. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C12a (2 marks, class average 75%): Complete a test table for the CheckPoints function with a purchase of 5000 points. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C12b (1 mark, class average 58%): Identify the line of CheckPoints that causes the error. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C12c (1 mark, class average 54%): Rewrite the faulty line so it gives the right result. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C13 (3 marks, class average 30%): Write pseudocode to update the points balance after paying by points or by cash. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles, Programming Fundamentals — Data Types, Data Structures and Control Structures
  • C14a (2 marks, class average 50%): Two purposes of a software audit. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C14b (2 marks, class average 30%): How a software audit supports linking the app to the phone's built-in payment feature. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C15a (2 marks, class average 55%): The ethical issue with family sharing and its impact on Café SD. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development
  • C15b (2 marks, class average 50%): Two design changes so family sharing avoids the ethical issue. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development, Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • C16 (3 marks, class average 50%): Impact of using an outdated code library on the login page, and how to fix it. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C17a (1 mark, class average 63%): Why every registration field needs an existence check. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C17b (1 mark, class average 61%): How to apply an existence check to the Name field. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C18a (2 marks, class average 55%): Two advantages of eye tracking over an observer in a usability test. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C18b (2 marks, class average 40%): Two advantages of an observation-based usability test over eye tracking. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C19a (1 mark, class average 69%): Legislation breached when an ex-employee takes usability test data to a competitor. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development
  • C19b (1 mark, class average 62%): How the identified legislation was breached. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development
  • C19c (2 marks, class average 60%): Two steps SoDeBiz should have taken to prevent the data leaving with the employee. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing, Legal Obligations, Ethics and Emerging Trends in Software Development

2023 Exam

  • MC 1 (1 mark, class average 73%): Name the search algorithm shown in the pseudocode. Lesson: Searching and Sorting — Linear and Binary Search, Selection Sort and Quick Sort
  • MC 2 (1 mark, class average 43%): Which list of numbers could have produced the given binary search trace. Lesson: Searching and Sorting — Linear and Binary Search, Selection Sort and Quick Sort, Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • MC 3 (1 mark, class average 56%): Control structure that the Else in the search pseudocode belongs to. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 4 (1 mark, class average 96%): How a programming language tells comments apart from code. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures, Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • MC 5 (1 mark, class average 62%): Best data structure for lines that pair a label with a word. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 6 (1 mark, class average 78%): Stage of the problem-solving methodology where requirements data is collected. Lesson: The Problem-Solving Methodology for Software Development, Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • MC 7 (1 mark, class average 47%): Data collection technique used when reviewing satisfaction logs from the old system. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • MC 8 (1 mark, class average 91%): Type of constraint created by catering for users from diverse cultural backgrounds. Lesson: The Problem-Solving Methodology for Software Development, Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • MC 9 (1 mark, class average 91%): What a task that delays the whole project must be. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • MC 10 (1 mark, class average 66%): Something the Privacy Act 1988 requires organisations to do. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development
  • MC 11 (1 mark, class average 70%): Which upgrade would most speed up uploading large files to the cloud. Lesson: The Problem-Solving Methodology for Software Development
  • MC 12 (1 mark, class average 47%): Pick a suitable objective for an order tracking system. Lesson: The Problem-Solving Methodology for Software Development
  • MC 13 (1 mark, class average 65%): Stage in which a strategy is developed to judge whether requirements were met. Lesson: The Problem-Solving Methodology for Software Development
  • MC 14 (1 mark, class average 76%): Name a reusable block of code that takes coordinates and returns a Boolean. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 15 (1 mark, class average 70%): Data structure for values of one type found by whole-number indexes. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • MC 16 (1 mark, class average 66%): Which option is a characteristic of an effective solution. Lesson: The Problem-Solving Methodology for Software Development
  • MC 17 (1 mark, class average 61%): What an invoice whose bank details changed on the way suggests. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 18 (1 mark, class average 79%): Data integrity characteristic most affected by anonymous product reviews. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • MC 19 (1 mark, class average 76%): What use case diagrams show. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • MC 20 (1 mark, class average 53%): Where the Health Records Act 2001 applies. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development
  • B1 (2 marks, class average 50%): One characteristic of a well-constructed software requirements specification. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • B2 (2 marks, class average 50%): Why some numbers should be stored as strings, with an example. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • B3a (1 mark, class average 67%): Name the design tool used for the two app screens. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • B3b (3 marks, class average 37%): How object descriptions and pseudocode show different parts of a design from mock-ups. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • B4a (2 marks, class average 65%): Who should take part in usability testing of the workflow tool, and why. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B4b (3 marks, class average 20%): Choose between video recording and direct observation for usability tests. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B5a (1 mark, class average 9%): Why risk management should be part of software development practices. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B5b (3 marks, class average 7%): Propose a risk management strategy as a technique, a responsibility and a timing. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B5c (1 mark, class average 7%): One benefit of the technique proposed in part b. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • B6 (2 marks, class average 60%): Compare version control with backing up a file. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C1a (1 mark, class average 46%): Name the development model Ness's team is using. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • C1b (3 marks, class average 33%): Draw and label the development model Ness has chosen. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • C2 (3 marks, class average 30%): Three criteria for evaluating Ness's secure development practices. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing, The Problem-Solving Methodology for Software Development
  • C3 (2 marks, class average 65%): A characteristic the team's naming convention should have, with an example. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures, Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • C4a (2 marks, class average 40%): A technique for recording progress that shows changes to the project plan. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • C4b (2 marks, class average 45%): Effect on the milestone if equipment set-up takes six days instead of two. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • C5 (3 marks, class average 57%): Name the entity and two data flows missing from the authentication DFD. Lesson: Analysis — The Software Requirements Specification, Context Diagrams, DFDs and Use Case Diagrams
  • C6 (1 mark, class average 54%): A user interface feature for entering the state efficiently and effectively. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • C7a (2 marks, class average 50%): Two consequences of the choice between cutting staff and cheaper test data. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development
  • C7b (3 marks, class average 7%): A way to resolve one consequence, with an advantage and a disadvantage. Lesson: Legal Obligations, Ethics and Emerging Trends in Software Development
  • C8a (1 mark, class average 45%): Type of risk shown by a crafted string typed into the username field. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C8b (2 marks, class average 30%): Two reasons an attacker might use this risk on the platform. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C8c (1 mark, class average 24%): One way to mitigate the risk. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C9 (3 marks, class average 53%): Use three criteria to choose between two transcription screen designs. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles
  • C10a (2 marks, class average 65%): Tests for valid and invalid file types at upload. Lesson: Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C10b (2 marks, class average 65%): How an error message makes the upload screen more effective. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles, Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C11a (3 marks, class average 27%): Justify using a function rather than a method for the transcription code. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures, Object-Oriented Programming — Classes, Objects, Encapsulation, Generalisation and Inheritance
  • C11b (2 marks, class average 15%): How a class could be used in the transcription module. Lesson: Object-Oriented Programming — Classes, Objects, Encapsulation, Generalisation and Inheritance
  • C12 (6 marks, class average 42%): Complete the data dictionary for the transcription checking algorithm. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles, Programming Fundamentals — Data Types, Data Structures and Control Structures, Validation, Testing and Debugging — Error Types, Test Tables and Trace Tables
  • C13 (3 marks, class average 20%): How to manage three risks of plugging in a third-party AI translation service. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing, Legal Obligations, Ethics and Emerging Trends in Software Development
  • C14a (3 marks, class average 23%): Justify XML over CSV for passing paragraphs to the translation API. Lesson: Programming Fundamentals — Data Types, Data Structures and Control Structures
  • C14b (1 mark, class average 66%): Circle the factor that would influence choosing XML. Lesson: Designing Solutions — Pseudocode, Data Dictionaries, Object Descriptions, Mock-ups and Design Principles, Programming Fundamentals — Data Types, Data Structures and Control Structures
  • C15 (3 marks, class average 47%): A suitable backup procedure for Ness while working on the project. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing
  • C16 (2 marks, class average 40%): Two areas to investigate when reviewing maintainability, security and legal compliance. Lesson: Software Security — Threat Modelling, Vulnerabilities, Secure Coding and Alpha and Beta Testing, Legal Obligations, Ethics and Emerging Trends in Software Development
  • C17a (2 marks, class average 20%): How Ness could assess how effective her project plan was. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral
  • C17b (2 marks, class average 40%): Why Ness should assess how well the plan helped her monitor progress. Lesson: Development Models and Project Management — Waterfall, Agile and Spiral