NTISthis.com

Evidence Guide: ICTGAM511 - Manage testing of games and interactive media

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTGAM511 - Manage testing of games and interactive media

What evidence can you provide to prove your understanding of each of the following citeria?

Determine the quality requirements statement that will enable product release

  1. Review the picture of the product in the market place to determine high-level requirements provided by the product, for expected clients, considering all types of requirements
  2. Define a releasable product in terms of outstanding bugs, to enable a limited release and a complete product release
  3. Summarise findings into a product release, enabling quality requirements statement
  4. Confirm that the client requirements and development specifications are in agreement for product release, to enable the preparation of a quality requirements statement
Review the picture of the product in the market place to determine high-level requirements provided by the product, for expected clients, considering all types of requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define a releasable product in terms of outstanding bugs, to enable a limited release and a complete product release

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Summarise findings into a product release, enabling quality requirements statement

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm that the client requirements and development specifications are in agreement for product release, to enable the preparation of a quality requirements statement

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define test plan that enables testing of required quality as defined by quality requirements statement

  1. Determine expected test cycles during the software development life cycle, considering the development methodology in use and the quality requirements for the product’s release
  2. Determine the types of testing to be performed during the test cycles, to enable the efficiency of processes, and the confirmation of the quality requirements statement
  3. Determine the testing methods to be used to implement the testing types defined for the identified test cycles
  4. Determine the testing technique to be used to determine test cases, and analyse results
  5. Perform the test cycle until a combination is found that provides an acceptable balance of cost, quality and risk, and on which upper management and development team can agree
  6. Select test-support software to enable efficiency in testing and testing management
  7. Define implementation details for agreed testing and the team responsible for testing management
  8. Define reporting details for testing throughout the product life cycle to enable ongoing management of the testing process
  9. Confirm test plan completeness using available completeness techniques
  10. Confirm the test plan with development team and management
Determine expected test cycles during the software development life cycle, considering the development methodology in use and the quality requirements for the product’s release

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the types of testing to be performed during the test cycles, to enable the efficiency of processes, and the confirmation of the quality requirements statement

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the testing methods to be used to implement the testing types defined for the identified test cycles

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the testing technique to be used to determine test cases, and analyse results

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Perform the test cycle until a combination is found that provides an acceptable balance of cost, quality and risk, and on which upper management and development team can agree

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Select test-support software to enable efficiency in testing and testing management

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define implementation details for agreed testing and the team responsible for testing management

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define reporting details for testing throughout the product life cycle to enable ongoing management of the testing process

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm test plan completeness using available completeness techniques

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm the test plan with development team and management

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Install and configure test plan defined test support software

  1. Install and configure the bug tracking process, and define bug description fields to maximise efficiency, and minimise possibilities of bouncing bugs
  2. Install and configure test case management software
  3. Install and configure test cycle management and reporting software
  4. Install and configure automated test tools
Install and configure the bug tracking process, and define bug description fields to maximise efficiency, and minimise possibilities of bouncing bugs

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Install and configure test case management software

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Install and configure test cycle management and reporting software

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Install and configure automated test tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage testing process to enable defined quality requirements

  1. Manage and report on the development of test cases
  2. Manage and report on test cycle status
  3. Manage and report on outstanding bug status
  4. Manage and report on the status of product testing related to product release, enabling a quality requirements statement
  5. Update the test plan and schedule to deal with changing development conditions, and to ensure that management is informed
  6. Manage bugs to ensure efficient bug handling and resolution
  7. Manage the test environment, including setup, receipt of test builds and clean-up
Manage and report on the development of test cases

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage and report on test cycle status

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage and report on outstanding bug status

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage and report on the status of product testing related to product release, enabling a quality requirements statement

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Update the test plan and schedule to deal with changing development conditions, and to ensure that management is informed

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage bugs to ensure efficient bug handling and resolution

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage the test environment, including setup, receipt of test builds and clean-up

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Finalise testing for release

  1. Produce testing results for management review prior to release
  2. Manage test product freeze for final release and final test run
  3. Confirm the product, release enabling, and ensure that quality requirements have been met
Produce testing results for management review prior to release

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage test product freeze for final release and final test run

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm the product, release enabling, and ensure that quality requirements have been met

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the quality requirements statement that will enable product release

1.1 Review the picture of the product in the market place to determine high-level requirements provided by the product, for expected clients, considering all types of requirements

1.2 Define a releasable product in terms of outstanding bugs, to enable a limited release and a complete product release

1.3 Summarise findings into a product release, enabling quality requirements statement

1.4 Confirm that the client requirements and development specifications are in agreement for product release, to enable the preparation of a quality requirements statement

2. Define test plan that enables testing of required quality as defined by quality requirements statement

2.1 Determine expected test cycles during the software development life cycle, considering the development methodology in use and the quality requirements for the product’s release

2.2 Determine the types of testing to be performed during the test cycles, to enable the efficiency of processes, and the confirmation of the quality requirements statement

2.3 Determine the testing methods to be used to implement the testing types defined for the identified test cycles

2.4 Determine the testing technique to be used to determine test cases, and analyse results

2.5 Perform the test cycle until a combination is found that provides an acceptable balance of cost, quality and risk, and on which upper management and development team can agree

2.6 Select test-support software to enable efficiency in testing and testing management

2.7 Define implementation details for agreed testing and the team responsible for testing management

2.8 Define reporting details for testing throughout the product life cycle to enable ongoing management of the testing process

2.9 Confirm test plan completeness using available completeness techniques

2.10 Confirm the test plan with development team and management

3. Install and configure test plan defined test support software

3.1 Install and configure the bug tracking process, and define bug description fields to maximise efficiency, and minimise possibilities of bouncing bugs

3.2 Install and configure test case management software

3.3 Install and configure test cycle management and reporting software

3.4 Install and configure automated test tools

4. Manage testing process to enable defined quality requirements

4.1 Manage and report on the development of test cases

4.2 Manage and report on test cycle status

4.3 Manage and report on outstanding bug status

4.4 Manage and report on the status of product testing related to product release, enabling a quality requirements statement

4.5 Update the test plan and schedule to deal with changing development conditions, and to ensure that management is informed

4.6 Manage bugs to ensure efficient bug handling and resolution

4.7 Manage the test environment, including setup, receipt of test builds and clean-up

5. Finalise testing for release

5.1 Produce testing results for management review prior to release

5.2 Manage test product freeze for final release and final test run

5.3 Confirm the product, release enabling, and ensure that quality requirements have been met

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the quality requirements statement that will enable product release

1.1 Review the picture of the product in the market place to determine high-level requirements provided by the product, for expected clients, considering all types of requirements

1.2 Define a releasable product in terms of outstanding bugs, to enable a limited release and a complete product release

1.3 Summarise findings into a product release, enabling quality requirements statement

1.4 Confirm that the client requirements and development specifications are in agreement for product release, to enable the preparation of a quality requirements statement

2. Define test plan that enables testing of required quality as defined by quality requirements statement

2.1 Determine expected test cycles during the software development life cycle, considering the development methodology in use and the quality requirements for the product’s release

2.2 Determine the types of testing to be performed during the test cycles, to enable the efficiency of processes, and the confirmation of the quality requirements statement

2.3 Determine the testing methods to be used to implement the testing types defined for the identified test cycles

2.4 Determine the testing technique to be used to determine test cases, and analyse results

2.5 Perform the test cycle until a combination is found that provides an acceptable balance of cost, quality and risk, and on which upper management and development team can agree

2.6 Select test-support software to enable efficiency in testing and testing management

2.7 Define implementation details for agreed testing and the team responsible for testing management

2.8 Define reporting details for testing throughout the product life cycle to enable ongoing management of the testing process

2.9 Confirm test plan completeness using available completeness techniques

2.10 Confirm the test plan with development team and management

3. Install and configure test plan defined test support software

3.1 Install and configure the bug tracking process, and define bug description fields to maximise efficiency, and minimise possibilities of bouncing bugs

3.2 Install and configure test case management software

3.3 Install and configure test cycle management and reporting software

3.4 Install and configure automated test tools

4. Manage testing process to enable defined quality requirements

4.1 Manage and report on the development of test cases

4.2 Manage and report on test cycle status

4.3 Manage and report on outstanding bug status

4.4 Manage and report on the status of product testing related to product release, enabling a quality requirements statement

4.5 Update the test plan and schedule to deal with changing development conditions, and to ensure that management is informed

4.6 Manage bugs to ensure efficient bug handling and resolution

4.7 Manage the test environment, including setup, receipt of test builds and clean-up

5. Finalise testing for release

5.1 Produce testing results for management review prior to release

5.2 Manage test product freeze for final release and final test run

5.3 Confirm the product, release enabling, and ensure that quality requirements have been met

Evidence of the ability to:

define quality requirements and an associated test plan for software

install and configure testing support software

manage the testing process

identify bugs or issues, accurately and concisely

finalise the software testing process to enable the product release.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

provide a detailed summary of client requirements for platforms, hardware and software

provide a detailed explanation of client system requirements, both functional and non-functional

outline the procedures for bug or issue management and identification

summarise test reporting requirements

explain testing techniques, methods, test types and system dissection.