Part 3 Sdd

PART 3 – Documentation List of Objectives 1) 2) 3) 4) 5)

Create relevance to the 3 – 5 year old age bracket Take into account social and ethical issues Contain relevant help Development of games to reach out to its target market Games to contain both entertainment and educational value

IPO Chart of the intended solutions Math’s Game I Answer (Integer)

P Add two integers together Calculate if the inputted number is correct

O Correct or incorrect

Snakes and Ladders Game I Roll Dice (1, 2, 3, 4, 5, 6)

P Generate a random number

O

Move players according to this random number Place player score as sum of random numbers Calculate when a player finishes

Move player to cell

P Determine whether this is the first image chosen Determine whether this is the second image chosen Check whether the two images match

O Display image

Display Score Display result

Memory Game I Selection of first image Selection of second image

Display image Display result

Snakes and Ladders Game I Select Choice (Scissors, Paper or Rock)

P Generate random case

Select a random case

O

Check whether the player wins or loses according to choice Hierarchy of the intended program

Display result

Splash Screen

Main Menu

Snakes and Ladders Math’s Game

Memory Game

How to Play How to Play

How to Play

Scissors, Paper, Rock

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 Screen

Menu

Snakes Ladders Screen

and

Memory Screen

Math’s Game Screen

Game

Scissors, Paper, Rock Game Screen