Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

  1. Construct application using RAD
  2. Prepare handover stage

Required Skills

Required skills

communication skills to liaise with users while managing iterative changes in design by involving end users in the development process

literacy skills to write technical documents and present written material for review

planning and organisational skills to keep accurate technical records

problemsolving skills to solve problems with design

technical skills to identify analyse and evaluate a range of solutions using prototyping tools

Required knowledge

broad knowledge of industryaccepted prototyping tools

overview knowledge of

quality assurance practices

client business domain

role of stakeholders and the degree of stakeholder involvement

three or more current industry development methodologies

three or more programming languages

Evidence Required

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria required skills and knowledge range statement and the Assessment Guidelines for the Training Package

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to

design application and develop high quality code according to client specifications

provide QA testing and monitoring

demonstrate use of code optimisers using RAD techniques

document completed work

Context of and specific resources for assessment

Assessment must ensure access to

CASE repository to facilitate the reuse of templates and components

CASE tools

code generator

detailed user requirements

prototyping software

requirements document including model and scope

appropriate learning and assessment support when required

modified equipment for people with special needs

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge The following examples are appropriate for this unit

evaluation of completed code

review of documentation

verbal or written questioning to assess knowledge of prototyping and RAD process

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector workplace and job role is recommended where appropriate

Assessment processes and techniques must be culturally appropriate and suitable to the communication skill level language literacy and numeracy capacity of the candidate and the work being performed

Indigenous people and other people from a nonEnglish speaking background may need additional support

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge


Range Statement

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.

RAD techniques may include:

computer-aided software engineering (CASE) tools

iterative life cycles

prototyping

re-use of applications, templates and code

SWAT teams

timebox-development methodology

workshops.

Application may include:

commercial software applications

organisation-specific software:

communication packages

database

graphic

presentation functionalities

spreadsheet

word-processing.

RAD tools may include:

CASE tools

code generators.

User may include:

department within the organisation

person within a department

third party.

Appropriate person may include:

authorised business representative

client

supervisor.

Specifications may include:

current system functionality

metrics

project plan

software requirements

technical requirements

user problem statement.