Unit 10DEVELOPING COMPUTER GAMES

K/601/7324 LO4 - Be able to test and document computer games

P5 - Follow a test strategy to test and debug a computer gameM4 - Gain user feedback to a computer game to suggest improvementsD2 - Act on user feedback to improve aspects of the computer gameP6 - Produce user documentation for a computer gameP7 - Produce technical documentation for a computer game Learners could evidence this criterion by producing and using a test

plan/table using multiple tests throughout the game, thoroughly testing the game that has been produced against the specification and then showing the debugging of their game.

For merit criterion M4 learners should gain feedback from users and suggest possible improvements to the game based on these suggestions. This could be evidenced in the form or a report summarising the feedback received and an explanation of the format chosen for feedback and why this was appropriate. The learner should also identify any improvements that have been suggested and why they may or may not be used.

Assessment Criteria P5, M4, D2, P6 and P7

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

For distinction criterion D2 learners should use the feedback gained in the Merit Criteria and the improvements they have identified could be used and improve aspects of the computer game – this can be evidenced through screen captures showing the game prior to improvements and after giving detailed evidence of the improvements that are being made and including a justification why these changes were made.

Learners will evidence these criterions with the production of all the documentation required for the working game. The documentation will need to be clear and include graphics to illustrate areas that are being explained. The learners’ will need to produce a user guide for P6 and the technical documentation for P7.

Assessment Criteria P5, M4, D2, P6 and P7

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

Learners will be shown how to develop and use a test plan and how to gain feedback from test users – this will include the way feedback can be gathered and the sort of areas that could be tested or checked by the test user (learners should look at different types of questioning techniques to draw out information from test users). The learner should create a test plan to test their developed games and perhaps those of others to identify the stages of testing and the details of the tests they will need to record. Learners will also identify that they are testing and correcting errors throughout the development process and these should also be recorded for future reference.

The learners should be encouraged to review each others games and provide feedback over a number of identified criteria. The group feedback should then be reviewed by each learner to identify any changes, problems or improvements that have been suggested and to act on the appropriate feedback to improve the game.

When the computer game has been developed and tested, the learner should understand the importance of technical and user documentation. They should review a number of user guides from a range of computer games and identify whether they are detailed and comprehensive enough for users.

Learners should also look at technical documentation to gain an understanding of what is included in these documents and the differences between this and the user documentations. Learners may bring in documents from their own games in order to analyse these.

Be able to test and document computer games

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

Now the game is complete and in your eyes it is wonderful. But you do not want to put it out on the market without making sure that others feel the same and you do not want it to be seen as bugged. Bug crashes can cause a reputation for a company, it can cause product withdrawal, enforced delays, complaints from the users and suppliers etc. It is necessary to soak test the product now that it has been tweaked and tested during operation.

You will need to test a range of areas now that it complete, these need to be on multiple screens and levels to ensure consistency. This could include such things as the User Interface, Success of Support, Navigation system, scoring, level difficulty, Collision prevention, quality of graphics and appropriateness of multimedia content. Anything that does not reach a standard should be repaired and evidenced.

P5.2 – Task 01 - Create a test strategy to test for a range of post production tests and evidence debugging the game.

LO4 Be able to test and document computer games – Post Testing

What Am I Testing

What Should Happen What Did Happen Steps To Correct

Evidence

I am testing that the scoring of the levels transfers to

the next level

When the user moves from one level to the next, the

scoring of the game should be redisplayed at the bottom of the screen.

When the user moved from one level to the next,

the scoring of the game redisplayed at the bottom

of the screen.

None See printscreen

1 and 2

I am testing that the scoring of the levels resets itself at the start of each

level.

When the user moves from one level to the next, the

scoring of the game should be redisplayed at the

bottom of the screen as a zero score.

When the user moved from one level to the next,

the scoring of the game did not redisplay at the bottom of the screen as

zero.

I will need to edit the

program code to force the

scoreboard to reset to zero

See Printscreen 3, 4, 5 and

6.

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

P5.2 - Task 03 - Conduct and collect Peer feedback for you game with a view to improvements being made.

Construct a questionnaire or survey with a mixture of open and closed questions to get feedback from a peer.

Ensure you cover a range of elements. Ensure your evaluators refer to specific areas of your game. This could be typed up or written (don’t lose the originals!)

M4.2 - Task 04 – Analyse the results of this feedback, catalogue and comment on suggested improvements which could benefit the purpose and function of the game.

Identify any improvements that have been suggested and why you may or may follow up on these improvements in line with the intended game purpose, age and understanding of the target audience or other consideration.

LO4 Be able to test and document computer games – Seeking Feedback

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

It is always good to get a review from a user who can see the faults you cannot or fail to see. Called a “Fresh Eye”, critical feedback is not a criticism of the work produced but designed to make it even better. Evidence of these repairs should be made using screenshot evidence of before, during and after including the coding if possible. The game should be evidenced as tested after the improvement is made to verify this. For Distinction at least three improvements should be made to make the game more professional.

D2.1 - Task 05 – Using the feedback and from the user, improve the quality and operation of the game giving detailed evidence of the improvements that are being made, including a justification why these changes were made.

LO4 Be able to test and document computer games – Seeking Feedback

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

When games first came out the box they came in had almost as much detail as the user guide inside. How much instruction does the user need for Pacman. Games for the ZX Spectrum came on a tape with the instructions on the inside cover like a music CD.

With more modern games, the user guide has so much more, screenshot evidence of levels, instructions on control systems, what each object does, how to operate the menu system and a little section on strategy without giving the game away.

With some games the manual is very detailed including back story and aims. But more importantly they reflect the game, a front cover, character art, laid out in keeping with the style of the game. It is all part of the professionalism expected of a more expensive product.

Use the example provided to produce a guide that is appropriate for a professionally polished game release.

P6.1 - Task 06 – Create user documentation covering the purpose, navigation and operation of the game.

System Requirements (minimum and recommended) Provide a step by step section on how to install the game. Provide an introduction to the purpose, aim and ultimate goal of the game. Provide evidence of character and objects. Provide a step by step section on how to operate the controls of the game. A Strategy section on how to play the game better. A section of FAQs about the game. Include screenshots to help the user.

LO4 Be able to test and document computer games – User Guide

System Requirements Installing the Game

Characters and Objects Controlling the Game

Purpose and Aim Strategy Guide FAQ’s

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

Technical guides are there for problems, mostly unread by users unless there is a dire need such as problems installing, or if the game has been passed on to a second or third party developer to make it better or program a sequel.

With more modern games, the technical guide has to be produced for an alternative programmer in order to fix and manage the functions of the game in your absence, a third or second party developer. With some games the technical manual is very detailed including evidence of scripting and the functions of the scripts.

These can also include action charts demonstrating inputs and outputs so the transfer of coding to another platform can be repositioned for alternative control methods.

P7.1 - Task 07 – Create a technical guide covering data dictionary, user interface, data flow diagrams and action charts on how to manage the background functions of the game. Data Dictionary of terms used within the game and an explanation of those terms Algorithm design (including control methods) User interface method design (action charts/tables, input-output-process tables,

class and instance diagrams and dataflow diagrams) How to problem solve (screenshots) Troubleshooting section with answered responses

LO4 Be able to test and document computer games – User Guide

Data Dictionary Algorithm design

User interface How to problem solve Troubleshooting

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

LO4 Be able to test and document computer games – Algorithm Designs

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

LO4 Be able to test and document computer games – class and instance diagram

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7

P5.2 – Task 01 - Create a test strategy to test for a range of post production tests and evidence debugging the game.M4.1 - Task 02 - Explain the different considerations and methods of collecting feedback and how you are going to collect your data. Justify the reasons you have chosen to use this method.P5.2 - Task 03 - Conduct and collect Peer feedback for you game with a view to improvements being made.M4.2 - Task 04 – Analyse the results of this feedback, catalogue and comment on suggested improvements which could benefit the purpose and function of the game.D2.1 - Task 05 – Using the feedback and from the user, improve the quality and operation of the game giving detailed evidence of the improvements that are being made, including a justification why these changes were made.P6.1 - Task 06 – Create user documentation covering the purpose, navigation and operation of the game.P7.1 - Task 07 – Create a technical guide covering data dictionary, user interface, data flow diagrams and action charts on how to manage the background functions of the game.

Task List

Scenario Criteria Tasks Assessment1 2 3 4 5 6 7