Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.
Required skills
communication skills to liaise with internal and external personnel on technical, operational and business-related matters
literacy skills to:
interpret technical documentation
write reports in required formats
numeracy skills to take test measurements, and interpret and evaluate results
planning and organisational skills to:
coordinate the test process in liaison with others
plan, prioritise and monitor own work
problem-solving and contingency-management skills to develop strategic review results of earlier unit testing and identify critical issues
research skills to identify, analyse and evaluate broad features of system testing and best practice in system testing
technical skills to:
analyse data related to analysis and evaluation
use programming skills in programming languages relevant to project.
Required knowledge
at least two programming languages, with detailed knowledge of programming languages required by system
automated test tools, with detailed knowledge of features and processes in some areas
input and output requirements
organisational practice and standards relating to integration testing
system or application being tested
testing techniques, with detailed knowledge of features and processes
underlying test data.
The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.
Test environment may include: | data network or communications and other equipment operating system other support software program libraries. |
Test and acceptance criteria may relate to: | type of test: cohesion efficiency functional. |
Test tools may include: | applications testing: Cyrano Suite DataShark Datatect preVue-C/S code, unit and class testing: AssertMate BoundsChecker C-Cover CodeReview CodeWizard DeepCover FailSafe Hindsight Insure++ JavaPureCheck JCAST Logiscope stress load testing: Astra SiteManager Astra SiteTest automated test facilities AutoTester Web e-Load e-MONITO E-TEST Suite JavaLoad LoadRunner. |
Software life cycle may include: | AS/NZS15271:1999 Guide for AS/NZS ISO/IEC 12207 Information technology - Software life cycle processes AS/NZS ISO/IEC12207:1997 Information technology - Software life cycle processes. |
Quality benchmarks may include: | relevant quality standards: AS 3925.1-1994 Software quality assurance - Plans AS 4042-1992 Software configuration management plans AS 4043-1992 Software configuration management AS/NZS 14102:1998 Information technology - Guideline for evaluation and selection of CASE tools AS/NZS 4258:1994 Software user documentation process AS/NZS ISO/IEC 12207:1997 Information technology - Software life cycle processes standards for software review, mainly developed by: Institute of Electrical and Electronics Engineers (IEEE) International Organization for Standardization (ISO) Software Engineering Institute (SEI) US Department of Defence (DoD) standards. Note: International and Australian standards are updated and changed on a regular basis. It is therefore important to check the Standards Australia website on a regular basis for new standards. |
Documentation and reporting may include: | ISO, International Electrotechnical Commission (IEC) and Australian Standards (AS) standards templates for information gathering processes various organisational approaches to: audit trails naming standards project-management templates report writing version control. |
Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.
Observation Checklist