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. Identify and clarify configuration management requirements
  2. Employ appropriate control mechanisms
  3. Implement monitoring mechanisms
  4. Manage release of product

Required Skills

Required skills

communication skills to

gain consensus on concepts

liaise with stakeholders

transfer and collect information

literacy skills to develop technical and business reports

numeracy skills to manage a budget

planning and organisational skills to estimate use across a range of predictable project contexts related to either varied or highly specific functions

problemsolving skills to

identify configuration control with developers and team members

scope and prepare time lines budget and risk manage process

research skills to analyse and evaluate

broad features of a particular business domain

best practice in software development methodologies

technical skills to use a range of software configuration tools and software applications

Required knowledge

projectplanning methodologies and tools

benchmarking methodologies when implementing monitoring mechanisms

how to formulate software size models and size estimates when employing control mechanisms

quality assurance and quality processes when implementing monitoring mechanisms

software development methodologies when identifying and clarifying configuration management requirements

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

use quality processes audit trails and version control to implement administrative and technical procedures throughout the software development and documentation life cycle

implement and maintain reliable and valid configuration management procedures for technical and administrative procedures for use during the software life cycle

Context of and specific resources for assessment

Assessment must ensure access to

configuration tools

evaluation criteria

process for approval of change requests

templates for status reports

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

software development

benchmarking methodologies

audit requirements

parallel development

review of candidates documentation with particular reference to

code identification in line with organisational requirements

change control

backup management

version control

release mechanisms

direct observation of candidate briefing stakeholders

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 applications

in-house or customised

organisation-specific

packaged.

Documentation may follow:

audit trails

ISO, IEC and AS standards

naming standards

project management templates

report writing principles

version control.

Stakeholders may include:

development team

management

project team

sponsor

testers

user.

Software configuration tools may include:

Baseline +Plus

ClearCase

Continuus/CM

CVS

PVCS Configuration Builder

PVCS Version Manager

PVCS Version Manager PLUS

RCS

SCCS

Source Integrity

TeamWare

Version +Plus

Version Stamper.

Organisational requirements may include:

how and what the organisation wants in regard to work environment

preventative maintenance and diagnostic policy, roles and technical responsibilities in the IT department

problem-solution processes

vendor and product service level support agreements.

Requirements may relate to:

business

network

people in the organisation

system.

Organisational guidelines may include:

communication methods

content of emails

dispute resolution

document procedures and templates

downloading information and accessing particular websites

financial control mechanisms

opening mail with attachments

personal use of emails and internet access

virus risk.