paper 2 theory Flashcards

1
Q

what does an identifier table contain

A
  • list of variable names
  • explanation of what that variable does
  • datatype of the variable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

algorithm

A
  • sequence of instructions
  • to implement a task/solution to a problem
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

features to make a program easier to read/understand

A
  • indentation
  • sensible variable names
  • comments
  • prettyprint
  • capitalization of keywords
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

source code

A

represents a solution algorithm expressed in high level language

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

object code

A
  • produced by the compiler during translation stage
  • the object code is produced by translating the source code
  • not produced by interpreter
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

pseudocode

A

a way of using keywords and identifiers to describe an algorithm without following the syntax of a particular programming language

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

flowchart

A

graphical representation of an algorithm

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

verification

A
  • checking that data has not been changed during transfer to a computer
  • double entry
  • parity check
  • checksum
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

validation

A
  • checking that data meets certain criteria
  • range check
  • presence check
  • length check
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

integrated development environment (IDE)

A

software application that combines all the features and tools needed by a software developer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

features of an IDE

A
  • pretty print
  • automatic indentation
  • syntax checking
  • highlights any undeclared variable
  • dynamic syntax checking
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

methods to find errors in IDE

A
  • dry run, trace table
  • breakpoint: run code to set point to find error
  • variable watch: checks the content of variable at specific points
  • stepping: execute the code line by line
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

program development cycle

A
  • amazing: analysis
  • doctors: design
  • can: coding
  • treat: test
  • men: maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

corrective maintenance

A
  • occurs when testing reveals a fault in the program and this is corrected
  • used to amend the algorithm to eliminate errors
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

adaptive maintenance

A
  • a term used for changes that are made to a program in response to a specification change
  • a result of changes to requirements or available technology
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

perfective maintenance

A
  • mainly deals with implementing new or changed user req
  • involves making functional enhancement
  • includes enhancing both the function and efficiency of the code and changing the functionalities as per the user’s changing needs
17
Q

preventive maintenance

A

performing activities to prevent the occurrence of error

18
Q

syntax error

A

small grammatical mistakes, sometimes limited to a single char

19
Q

logic error

A
  • program does not perform as expected
  • errors in the logic of a program
20
Q

run-time error

A
  • program executes an invalid instruction
  • attempts to divide by 0
  • program crashes
21
Q

black box testing

A
  • match expected to actual ans
  • person does not need to know the structure of the code
  • person chooses normal or boundary data
22
Q

white box testing

A
  • test every possible ‘logic path’ thru the code
  • trace table is often used during the program testing
23
Q

alpha testing

A
  • in house testing
  • testing is done by devs in-house rather than the one that developed the software
24
Q

beta testing

A
  • out of house testing
  • performed by a group of people assigned to find errors in the code
25
Q

stub testing

A
  • simple/dummy model written to stimulate the model
  • test carried out on all modules that have been written
26
Q

integration testing

A

the testing of any separately written modules to ensure that they work together

27
Q

acceptance testing

A
  • used for the completed program to prove to the client that it works as required
  • end-user testing
28
Q

stepwise refinement

A
  • breaking down of an algorithm
  • to a level of sufficient detail into smaller parts
  • from which it can be programmed
29
Q

use of subroutine in a program

A
  • to perform frequently used operations within a program
  • can be called when needed
  • can be reused by another program
30
Q

why use modules to construct programs

A
  • to find a more manageable solution
  • subroutine may be independently tested
  • program easier to maintain
31
Q

advantages of a subroutine

A
  • allows to be called into multiple places
  • may be tested independently
  • if tasks changes, changes only need to be made once
  • reduces unnecessary duplications
32
Q

procedure

A
  • a sequence of steps that is given an identifier and can be called to perform a sub-task
  • does not return a value
33
Q

function

A
  • a sequence of steps that is given an identifier and can be called to perform a sub-task
  • returns a value