NTISthis.com

Evidence Guide: ICTTEN814 - Manage development and application of testing artefacts

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

 

ICTTEN814 - Manage development and application of testing artefacts

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

Plan the test effort and develop test strategy for software testing

  1. Critically analyse functionalities of an application software from the system design document and create a test strategy for a new telecommunications product line
  2. Produce steps in developing test strategy and attributes of each step, according to enterprise policy
  3. Produce a test strategy to evaluate suitability of application software for integration into the telecommunications network
  4. Assess a range of tests required to evaluate performance and functionality of application software and determine tests required to suit the test regime
  5. Evaluate features of testing tool and debuggers, and select an appropriate tool to test the software application and detect faults
  6. Produce a test plan based on requirements of the project specifications, and identify testing artefacts required for model-based software testing
Critically analyse functionalities of an application software from the system design document and create a test strategy for a new telecommunications product line

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce steps in developing test strategy and attributes of each step, according to enterprise policy

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce a test strategy to evaluate suitability of application software for integration into the telecommunications network

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assess a range of tests required to evaluate performance and functionality of application software and determine tests required to suit the test regime

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Evaluate features of testing tool and debuggers, and select an appropriate tool to test the software application and detect faults

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce a test plan based on requirements of the project specifications, and identify testing artefacts required for model-based software testing

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Plan the development of testing artefacts

  1. Develop software testing strategies for uncovering evidence of defects in software systems as part of the quality assurance process
  2. Produce a test dependency model of the relationship between the test regime and test levels in software testing for referencing and validation
  3. Critically analyse software testing requirements to determine domain testing and application testing artefacts requirements to validate the software product
Develop software testing strategies for uncovering evidence of defects in software systems as part of the quality assurance process

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce a test dependency model of the relationship between the test regime and test levels in software testing for referencing and validation

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Critically analyse software testing requirements to determine domain testing and application testing artefacts requirements to validate the software product

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Develop and manage testing artefacts

  1. Create reusable domain artefacts to detect early defects in domain testing
  2. Modify domain test artefacts by binding variability to create application test artefacts to detect defects in product line applications
  3. Produce test reporting associated with test cycle phases within the test plan
  4. Critically analyse test reports and evaluate the impact of the test plan with testing artefacts on the testing environment
  5. Manage progress of the test plan to minimise risks associated with testing and ensure the test complies with test requirements
  6. Report detected defects to product evaluation personnel and prepare a strategy to manage defects
  7. Critically analyse testing metrics produced by the test tool to manage tracking of defects, and use metrics to plan process improvements
  8. Produce an evaluation report from the traceability matrix to manage defects or failures from the test plan
Create reusable domain artefacts to detect early defects in domain testing

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Modify domain test artefacts by binding variability to create application test artefacts to detect defects in product line applications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce test reporting associated with test cycle phases within the test plan

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Critically analyse test reports and evaluate the impact of the test plan with testing artefacts on the testing environment

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Manage progress of the test plan to minimise risks associated with testing and ensure the test complies with test requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Report detected defects to product evaluation personnel and prepare a strategy to manage defects

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Critically analyse testing metrics produced by the test tool to manage tracking of defects, and use metrics to plan process improvements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce an evaluation report from the traceability matrix to manage defects or failures from the test plan

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. Plan the test effort and develop test strategy for software testing

1.1 Critically analyse functionalities of an application software from the system design document and create a test strategy for a new telecommunications product line

1.2 Produce steps in developing test strategy and attributes of each step, according to enterprise policy

1.3 Produce a test strategy to evaluate suitability of application software for integration into the telecommunications network

1.4 Assess a range of tests required to evaluate performance and functionality of application software and determine tests required to suit the test regime

1.5 Evaluate features of testing tool and debuggers, and select an appropriate tool to test the software application and detect faults

1.6 Produce a test plan based on requirements of the project specifications, and identify testing artefacts required for model-based software testing

2. Plan the development of testing artefacts

2.1 Develop software testing strategies for uncovering evidence of defects in software systems as part of the quality assurance process

2.2 Produce a test dependency model of the relationship between the test regime and test levels in software testing for referencing and validation

2.3 Critically analyse software testing requirements to determine domain testing and application testing artefacts requirements to validate the software product

3. Develop and manage testing artefacts

3.1 Create reusable domain artefacts to detect early defects in domain testing

3.2 Modify domain test artefacts by binding variability to create application test artefacts to detect defects in product line applications

3.3 Produce test reporting associated with test cycle phases within the test plan

3.4 Critically analyse test reports and evaluate the impact of the test plan with testing artefacts on the testing environment

3.5 Manage progress of the test plan to minimise risks associated with testing and ensure the test complies with test requirements

3.6 Report detected defects to product evaluation personnel and prepare a strategy to manage defects

3.7 Critically analyse testing metrics produced by the test tool to manage tracking of defects, and use metrics to plan process improvements

3.8 Produce an evaluation report from the traceability matrix to manage defects or failures from the test plan

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. Plan the test effort and develop test strategy for software testing

1.1 Critically analyse functionalities of an application software from the system design document and create a test strategy for a new telecommunications product line

1.2 Produce steps in developing test strategy and attributes of each step, according to enterprise policy

1.3 Produce a test strategy to evaluate suitability of application software for integration into the telecommunications network

1.4 Assess a range of tests required to evaluate performance and functionality of application software and determine tests required to suit the test regime

1.5 Evaluate features of testing tool and debuggers, and select an appropriate tool to test the software application and detect faults

1.6 Produce a test plan based on requirements of the project specifications, and identify testing artefacts required for model-based software testing

2. Plan the development of testing artefacts

2.1 Develop software testing strategies for uncovering evidence of defects in software systems as part of the quality assurance process

2.2 Produce a test dependency model of the relationship between the test regime and test levels in software testing for referencing and validation

2.3 Critically analyse software testing requirements to determine domain testing and application testing artefacts requirements to validate the software product

3. Develop and manage testing artefacts

3.1 Create reusable domain artefacts to detect early defects in domain testing

3.2 Modify domain test artefacts by binding variability to create application test artefacts to detect defects in product line applications

3.3 Produce test reporting associated with test cycle phases within the test plan

3.4 Critically analyse test reports and evaluate the impact of the test plan with testing artefacts on the testing environment

3.5 Manage progress of the test plan to minimise risks associated with testing and ensure the test complies with test requirements

3.6 Report detected defects to product evaluation personnel and prepare a strategy to manage defects

3.7 Critically analyse testing metrics produced by the test tool to manage tracking of defects, and use metrics to plan process improvements

3.8 Produce an evaluation report from the traceability matrix to manage defects or failures from the test plan

Evidence of ability to:

produce steps in developing test strategy

produce a test strategy to evaluate suitability of application software

develop software testing strategies for uncovering evidence of defects in software systems

create reusable domain artefacts to detect early defects in domain testing

produce test reporting associated with phases of a test cycle within the test plan

produce an evaluation report from the traceability matrix.

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:

outline applications’ software features and functionalities

specify the configuration of software testing tools

define software artefact and explain the process for testing artefacts

summarise creation of the traceability matrix

summarise steps in developing the test strategy and specify various tests that may be applied

outline domain and application testing

explain essential elements of test plans

evaluate features of testing tools and debuggers

explain the identification of types of risks

outline the management of:

software defects

test traceability

explain phases of test cycles

summarise production of test reviews

outline steps in developing a test strategy

explain testing procedures.