Professional Documents
Culture Documents
List of Objectives
Math’s Game
I P O
Answer (Integer) Add two integers together
Calculate if the inputted number Correct or incorrect
is correct
I P O
Roll Dice (1, 2, 3, 4, Generate a random number
5, 6)
Move players according to this Move player to cell
random number
Place player score as sum of Display Score
random numbers
Calculate when a player finishes Display result
Memory Game
I P O
Selection of first Determine whether this is the first Display image
image image chosen
Selection of second Determine whether this is the Display image
image second image chosen
Check whether the two images Display result
match
I P O
Select Choice Generate random case
(Scissors, Paper or
Rock)
Select a random case
Check whether the player wins or Display result
loses according to choice
Hierarchy of the intended program
Splash Screen
Main Menu
In order to test the solution of the software the developer can use a variety of
testing and checking processes such as desk-checking, documentation
(walkthroughs, syntax diagrams).
Testing and checking of software solutions can also be done by a process called
‘path coverage testing’. This requires a unique test data to be tested for each
possible path in the algorithm. Each binary statement creates two possible paths,
two binary selections make four, ect. As this may require a large number of test
data, CASE tools assist in testing and checking code.
User documentation is used to teach users about the processes and operation of the
software solution. This documentation may include guides, manuals, and tutorials.
Internal documentation is used to make programming code readable and more
understandable.
Splash Screen
Main Menu
Screen
Snakes and
Ladders Screen
Memory Game
Screen
Math’s
Game
Screen
Scissors, Paper, Rock Game Screen