Past questions: 2023

[Question 21] Criteria | Marks • Demonstrates a sound understanding of the use of prototyping | 2 • Demonstrates some understanding of prototyping | 1

Sample answer: A prototype can be used to show screen design and navigation, to clarify understanding of the system and get client feedback.

[Question 22] Criteria | Marks • Explains the importance of communication over different stages in the software development cycle • Provides ONE benefit of communication, with reference to a stage in the software development cycle OR • Provides some benefits of communication • Demonstrates some understanding of the need for communication in software development

Sample answer: Without a clear understanding of client needs and without ongoing communication during the defining and planning stages, there is a risk that the final product does not meet their needs or that it becomes increasingly expensive to make necessary changes. Communication with the client during the testing stage is important in the development of relevant test data and for thorough evaluation of the software.

[Question 23 (a)] Criteria | Marks • Provides TWO reasons for the importance of security of this database | 2 • Demonstrates some understanding of the importance of data security | 1 Criteria | Marks • Provides a substantially correct system flowchart for the authentication process, using appropriate symbols • Provides a partially correct system flowchart | 2 • Provides a diagram that shows some understanding of the process | 1

Sample answer: Unintentional/malicious changes to the data may cause harm to the patients. Privacy of the patient may be compromised if the data is made public.

[Question 23 (b)] Sample answer:

[Question 26 (a)] Criteria | Marks • Demonstrates a sound understanding of why both Read statements are needed • Demonstrates some understanding of a read statement | 1 Criteria | Marks • Provides TWO reasons why the code is easy to maintain • Includes examples from the code • Provides ONE reason why the code is easy to maintain, using an example from the code OR • Provides TWO reasons why the code is easy to maintain • Demonstrates some understanding of code maintenance | 1 Criteria | Marks • Provides a thorough explanation of the need for both module and system testing in this scenario • Demonstrates a sound understanding of the need for module and system testing • Demonstrates some understanding of module and/or system testing | 2 • Demonstrates some understanding of testing | 1

Sample answer: Line 9 provides a priming read from the file and thus enables the EOF condition in line 10 to be tested, allowing for an empty file. Line 14 provides subsequent records for processing and provides the terminating condition when there are no more records.

[Question 26 (b)] Sample answer: The use of meaningful variable and module names, such as UserID and CheckPasswordCorrect, assists maintenance programmers to quickly understand the purpose of the code. Including calls to subroutines in lines 5 and 12 enables maintenance programmers to easily locate the detailed logic that may need to change.

[Question 26 (c)] Sample answer: Module testing will confirm that the module works, including the logic of the called modules with parameters being passed appropriately, for example when calling CheckPasswordCorrect with its three parameters. During system testing, live data will provide expected volumes of data which may show potential issues with performance and response times when accessing both files. Live data also ensures that unexpected combinations of data are well handled compared to the minimal conditions when using selected test data. It also tests for missing files or inappropriate file types or record formats.

[Question 27 (a)] Criteria | Marks • Produces a well-designed interface which uses appropriate screen design elements • Produces an interface with some appropriate elements | 2 • Provides a diagram that demonstrates some understanding of the system Criteria | Marks • Produces a substantially correct structure chart that represents the system • Produces a structure chart that represents most components of the system • Produces a chart with some relevant components | 2 • Provides a diagram that demonstrates some understanding of the system Criteria | Marks • Describes how the system can be evaluated with reference to TWO appropriate quality assurance criteria • Shows some understanding of quality assurance | 2 • Provides some relevant information | 1

Sample answer:

[Question 27 (b)] Sample answer:

[Question 27 (c)] Sample answer: The functionality of the system could be evaluated by viewing samples of transactions and checking that the correct fees were charged, based on the recorded entry and exit times. The ease of use of the system could be evaluated by presenting a sample of users with a survey requiring them to comment on their experiences of the process and analysing the responses.

[Question 28 (a)] Criteria | Marks • Provides a substantially correct desk check | 3 • Provides a partially correct desk check | 2 • Demonstrates some understanding of the algorithm | 1 Criteria | Marks • Identifies TWO errors and suggests ways to correct them | 3 • Identifies ONE error and suggests a way to correct it OR | 2 • Identifies TWO errors • Identifies an error | 1

Sample answer: OK | ProductCode | Len | Extracted | Count | Display character F | p3 | 2 T | p F | Not uppercase p | 1 F | 3 | 2 | Not all lowercase Invalid code F | Pad | P T | P | 1 | Not all lowercase F | a | 2 Invalid code T | Q Note: X is not considered

[Question 28 (b)] Sample answer: At line 110 the FOR/NEXT loop counter should start at 2. The value of Len is not being updated for the next ProductCode. Move line 40 to line 55.

[Question 30] Criteria | Marks • Provides a substantially correct algorithm that addresses the following features: – Display menu screen – Get a non-zero ButtonClick – Perform correct subroutine – Loop until Quit (9) is selected • Provides an algorithm that attempts to address some of the features | 2 • Demonstrates some understanding of the problem | 1

Sample answer: BEGIN Menu REPEAT Display MenuScreen REPEAT Get ButtonClick UNTIL ButtonClick <> 0 CASEWHERE ButtonClick is 1 | : Screen1 2 | : Screen2 3 | : Screen3 4 | : Screen4 Otherwise : | Quit ENDCASE UNTIL ButtonClick = 9 END Menu

[Question 32 (a)] Criteria | Marks • Provides THREE items of test data for different aspects of the algorithm, with corresponding reasons for inclusion • Provides TWO items of test data for different aspects of the algorithm, with some justification • Demonstrates some understanding of test data relevant to this algorithm | 1 Criteria | Marks • Provides a substantially correct algorithm that addresses the following features: – Validates the inputted date – Uses appropriate data structures and library routines – Outputs the correct long date – Provides meaningful error messages • Provides a substantially correct algorithm that addresses most of the features • Provides an algorithm that addresses some of the features | 3 • Provides an algorithm that attempts to address one of the features | 2 • Demonstrates some understanding of the problem | 1

Sample answer: Test data | Reason for inclusion 01/15/2022 | Check that the month is valid (1−12) 31/06/2023 | Check correct number of days in month 19/04/2022 | Verify that correct long date is produced

[Question 32 (b)] Sample answer: BEGIN date_conversion Get InDate MM = Extract(InDate, 4, 2) Month = Value (MM) DD = Extract(InDate, 1, 2) Days = Value (DD) YYYY = Extract(InDate, 7, 4) validmonth = CheckMonth(Month) IF validmonth THEN validday = CheckDays(Month, Days) IF validday THEN Display DD + “ ” + MonthName(Month) + “ ” + YYYY ELSE Display “Your days” + DD “are not valid for your entered month”; MM ENDIF ELSE Display “Your entered month must be a valid number between 1 and 12” ENDIF END date_conversion BEGIN CheckMonth(MM) flag = 1 IF MM < 1 OR MM > 12 THEN flag = 0 ENDIF RETURN flag END CheckMonth BEGIN CheckDays(Month, Days) flag = 1 IF Days > DaysinMonth(Month) OR Days < 1 THEN flag = 0 END IF RETURN flag END CheckDays