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. Investigate open-source paradigm
  2. Familiarise with target project
  3. Prepare for maintenance activities
  4. Maintain code
  5. Maintain documentation
  6. Participate in community

Required Skills

Required skills

analytical skills to

apply some of the latest information technology tools and techniques

evaluate and compare a range of opensource tools and components to use in software development and maintenance

communication skills to

discuss issues with global peers

participate effectively in discussions on a number of information technology issues

participate in volatile communities of interest

initiative and enterprise skills to

apply information technology knowledge and skills in a multidisciplinary environment

participate in opensource projects

literacy skills to

read and interpret complex technical and nontechnical information from a range of sources

write a clearly structured document or update existing documentation

problemsolving skills to choose the best solution for a particular context

research skills to identify and locate possible sources of required information for a target project

technical skills to

build existing software projects from source

create and maintain code

use basic language syntax and layout data structures arrays and standard algorithms

test and debug code at a high level

Required knowledge

detailed knowledge of

debugging and testing techniques

documentation techniques including internal documentation user guides and technical documentation

opensource development methodology

overview knowledge of online project communities

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

provide significant contribution to an opensource project in the form of

program source code changes andor additions

documentation changes or additions

online participation in the project direction

local proof of building of snapshots code modifications and testing

Context of and specific resources for assessment

Assessment must ensure access to

software development environment

internet

technical requirements

databases

information repositories

programming languages

groupfacilitation software

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

verbal or written questioning to assess candidates knowledge of opensource practices opensource software and opensource issues such as distribution compatibility and security

evaluation of candidates

participation

application code test and documentation

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.

Software may include:

commercial software applications

customised software

in-house software

organisation-specific software

packaged software.

Online resources may include:

community sites

CVS trees

FTP sites

gopher sites

news groups

online communities

websites.

Documentation may follow:

audit trails

International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), and Australian Standards (AS) standards

naming standards

project management templates

report writing principles

version control.

Online community may include:

local communities

online virtual communities of interest

organisational communities

main tools for online communities:

mailing lists

newsgroups

web conferencing.

Licensing models may include:

Apache licences

Berkeley Software Distribution (BSD)

General Public License (GPL)

Lesser General Public License (LGPL)

Mozilla.

Software-development tools may include:

computer language

development methodology

development tools

operating systems

target environments

version control systems.

Socially acceptable should be:

designed and sent with regard to recipient's:

culture

ethnicity

location

race

social sensitivities.

Online project may include:

commercial hosting facility hosting community code

CVS site

FTP site

other type of group repository

private website.

Community-participation standards may include:

informal or formal rules and regulations used by groups to manage their online projects

procedures or guidelines

verbal or written policies.