Unit of competency Outline
Date retreived
22/07/2026 9:54 PM AWST
22/07/2026 9:54 PM AWST
Whilst all efforts are made to provide accurate and timely information from the relevant source/documentation, please be aware that the information supplied may not be the most current version. The accuracy of the detail has not been confirmed by the Department and therefore should not be relied upon without first confirming the contents.
Maintain custom software
Maintain custom software
Unit of competency
National Code
ICAPRG510A
ICAPRG510A
State Code
D8025
D8025
TGA Status
Replaced
Replaced
DTWD Status
Replaced
Replaced
State Implementation and Classification
Approved Date
04/11/2011
Field of Education
020103 - Programming
Original Release Date
04/11/2011
Nominal Hours
35
Description
This unit describes the performance outcomes, skills and knowledge required to maintain software so that it continues to meet client user requirements.
Notes
Elements and Performance Criteria
1. Determine software fault to be corrected
- 1.1 Collect and review software fault details from sources
- 1.2 Obtain technical data to assist in identifying problem
- 1.3 Clarify nature of the problem with appropriate person where necessary
2. Identify and isolate fault
- 2.1 Review program documentation for specific modules in order to pinpoint problem areas
- 2.2 Review source code for logic errors
- 2.3 Read manuals, help files and 'read me files' to determine if there is a known fix
- 2.4 Undertake additional testing to identify or duplicate fault
- 2.5 Escalate difficult faults that cannot be identified
3. Design fix for fault
- 3.1 Ensure requirements to fix the fault are understood by client
- 3.2 Consider alternative options and choose the most effective solution
- 3.3 Consider the possible impact of the fix on other parts of the system
- 3.4 Document changes according to organisational guidelines
4. Carry out fix to software
- 4.1 Identify and obtain access to appropriate software development tools, source code and libraries
- 4.2 Construct appropriate code to correct the fault according to organisational and programming standards
- 4.3 Compile or regenerate code for changed programs and associated modules
- 4.4 Correct and resubmit code until error free
- 4.5 Document changes according to organisational and programming standards
5. Test fix and associated system areas
- 5.1 Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere
- 5.2 Request users to perform acceptance testing and record outcomes
6. Hand over to systems operations area
- 6.1 Update documentation to reflect all changes made
- 6.2 Confirm acceptance by systems operations and arrange for sign-off according to procedures
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.
Technical data may be obtained from:
error messages
memory dumps
software traces
other information.
Appropriate person may include:
authorised business representative
client
supervisor.
Documentation may follow:
audit trails
International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) standards
maintaining equipment inventory, client training and satisfaction reports
naming standards
project-management templates and report writing
version control.
Technical data may be obtained from:
error messages
memory dumps
software traces
other information.
Appropriate person may include:
authorised business representative
client
supervisor.
Documentation may follow:
audit trails
International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) standards
maintaining equipment inventory, client training and satisfaction reports
naming standards
project-management templates and report writing
version control.
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:
effectively maintain custom software
apply a fix that works
deploy a possible range of solutions to produce the same results.
Context of and specific resources for assessment
Assessment must ensure access to:
fault logs and help-desk reports
software development tools, documentation and environment
source code and libraries
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 candidate’s updated program documentation
verbal or written questioning to determine candidate’s understanding of:
impact of changes on applications and systems
programming standards.
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 non-English speaking background may need additional support.
In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.
Overview of assessment
Critical aspects for assessment and evidence required to demonstrate competency in this unit
Evidence of the ability to:
effectively maintain custom software
apply a fix that works
deploy a possible range of solutions to produce the same results.
Context of and specific resources for assessment
Assessment must ensure access to:
fault logs and help-desk reports
software development tools, documentation and environment
source code and libraries
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 candidate’s updated program documentation
verbal or written questioning to determine candidate’s understanding of:
impact of changes on applications and systems
programming standards.
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 non-English speaking background may need additional support.
In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.
Replaces
| State Code | National Code | Title | Type |
|---|---|---|---|
| D0087 | ICAB5230B | Maintain custom software | Unit of competency |
Replaced By
| State Code | National Code | Title | Type |
|---|---|---|---|
| AUV74 | ICTPRG510 | Maintain custom software | Unit of competency |
| State Code | National Code | Title | Type |
|---|---|---|---|
| D567 | ICA50111 | Diploma of Information Technology | Qualification |
| D573 | ICA50711 | Diploma of Software Development | Qualification |