You are on page 1of 6

PART 3 – Documentation

List of Objectives

1) Create relevance to the 3 – 5 year old age bracket


2) Take into account social and ethical issues
3) Contain relevant help
4) Development of games to reach out to its target market
5) Games to contain both entertainment and educational value

IPO Chart of the intended solutions

Math’s Game

I P O
Answer (Integer) Add two integers together
Calculate if the inputted number Correct or incorrect
is correct

Snakes and Ladders Game

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

Snakes and Ladders Game

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

Snakes and Ladders Memory Game Scissors, Paper, Rock


Math’s Game

How to Play How to Play How to Play


How to Play

Syntax Diagrams – Railroad Diagrams

Checking Software Solutions

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).

Desk-Checking is a manual process whereby the developer runs through each


statement of the code or algorithm and the results are written in a table. In this
table, each identifier contains its own column used within the code or algorithm. As
the developer runs through the process, identifiers may change its values and in
turn, as this values changes, it is written under the old value. Therefore the full
record of changed values is recorded. Errors that are found are usually located
within one row. As desk-checking can be quite extensive, many simply desk-check
the first few iterations followed by the last few, as most errors occur in the middle
iterations.

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.

Draft Screen Designs

Splash Screen
Main Menu
Screen

Snakes and
Ladders Screen
Memory Game
Screen

Math’s
Game
Screen
Scissors, Paper, Rock Game Screen

You might also like