Professional Documents
Culture Documents
CAIE AS Level Computer Science 9618 Practical v1 Z-Notes
CAIE AS Level Computer Science 9618 Practical v1 Z-Notes
ORG
CAIE AS LEVEL
COMPUTER
SCIENCE (9618)
SUMMARIZED NOTES ON THE PRACTICAL SYLLABUS
CAIE AS LEVEL COMPUTER SCIENCE (9618)
WWW.ZNOTES.ORG
CAIE AS LEVEL COMPUTER SCIENCE (9618)
Takes up a single unit of storage (usually a byte). 1-Dimensional (1D) Array: declared using a single index,
can be represented as a list
String:
Boolean:
Date:
Array:
File:
2.4. Arrays
WWW.ZNOTES.ORG
CAIE AS LEVEL COMPUTER SCIENCE (9618)
Python:
WWW.ZNOTES.ORG
CAIE AS LEVEL COMPUTER SCIENCE (9618)
WWW.ZNOTES.ORG
CAIE AS LEVEL COMPUTER SCIENCE (9618)
Coding:
The IDE executes the code & initial error detection carried
out by
compiler/interpreter doing the following:
Syntax/Logic Error: before program is run, an error
message
warns the user about this
Runtime Error: run of the program ends in an error
Debugging:
Example:
Single stepping: traces through each
line of code and
steps into procedures. Allows you to view the
effect of
each statement on variables
WWW.ZNOTES.ORG
CAIE AS LEVEL COMPUTER SCIENCE (9618)
When source code does not obey rules of the language 4.7. Testing Strategies
Compiler generates error messages
Black box testing:
Examples:
Misspell identifier when calling it Use test data for which results already calculated &
Missing punctuation – colon after if compare result
from program with expected results
Incorrectly using a built-in function Testing only considers input and output and the code is
Argument being made does not match data type
viewed as
being in a ‘black box’
Run-time errors: White box testing:
Source code compiles to machine code but fails upon Examine each line of code for correct logic and accuracy.
execution (red
lines show up in Python) May record value of variables after each line of code
When the program keeps running and you have to kill it Every possible condition must be tested
manually
Examples: Stub testing:
Division by 0
Infinite loop – will not produce error message, Stubs are computer programs that act as temporary
program will
just not stop until forced to replacement for a
called module and give the same
output as the actual product or
software.
Logic errors: Important when code is not completed however must be
tested so
modules are replaced by stubs
Program works but gives incorrect output
Examples: Dry run testing:
Out By One – when ‘>’ is used instead of ‘>=’
Misuse of logic operators A process where code is manually traced, without any
software used
The value of a variable is manually followed to check
4.5. Corrective Maintenance whether it is used and updated as expected
Used to identify logic errors, but not execution errors
Corrective Maintenance is correcting identified errors
White-Box testing: making sample data and running it Walkthrough testing:
through a
trace table
Trace table: technique used to test algorithms; make sure A test where the code is reviewed carefully by the
that
no logical errors occur e.g. developer’s peers, managers, team members, etc.
It is used to gather useful feedback to further develop the
code.
Integration testing:
WWW.ZNOTES.ORG
CAIE AS LEVEL COMPUTER SCIENCE (9618)
This method allows all the code snippets to integrate with the developer.
each other, making the program work. Basically another term for ‘second round of testing’
This is the testing done on software ‘in-house’, meaning it A test carried out by the intended users of the system:
is done by the developers the people who requested the software.
Basically another term for ‘first round of testing’ The purpose is to check that the software performs
exactly as required.
Beta testing: The acceptance criteria should completely be satisfied for
the program to be released.
This is the testing done on the software by beta users,
who use the program and report any problems back to
WWW.ZNOTES.ORG
CAIE AS LEVEL
Computer Science (9618)