Unit of competency Outline
Date retreived
22/07/2026 5:54 PM AWST
22/07/2026 5: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
ICTPRG540
ICTPRG540
State Code
OBT02
OBT02
TGA Status
Current
Current
DTWD Status
Approved
Approved
State Implementation and Classification
Approved Date
15/01/2021
Field of Education
020103 - Programming
Original Release Date
15/01/2021
Nominal Hours
35
Description
This unit describes the skills and knowledge required to maintain software to client user requirements.It applies to individuals who may work as software developers who are required to maintain existing software.No licensing, legislative or certification requirements apply to this unit at the time of publication.
Notes
Elements and Performance Criteria
1. Determine software fault
- 1.1 Determine details of software faults
- 1.2 Identify and document technical data required to troubleshoot determined fault
- 1.3 Submit documentation to required personnel and seek and respond to feedback
2. Identify and isolate fault
- 2.1 Review program documentation and identify specific modules according to task requirements
- 2.2 Review the source code and identify logic errors according to technical data
- 2.3 Read manuals, help files and ‘read me files,’ and determine if there is a known fix
- 2.4 Conduct required testing and identify and document fault
- 2.5 Escalate faults that cannot be identified to required personnel according to organisational procedures
3. Design fix for fault
- 3.1 Determine and document faults and initial fix suggestions according to organisational requirements
- 3.2 Determine and document alternative options and choose required solution
- 3.3 Determine and document impact of fix on other parts of system
- 3.4 Document required changes according to organisational guideline
- 3.5 Submit documents to required personnel and seek and respond to feedback
4. Implement fix to software
- 4.1 Identify and obtain access to required software development tools, source code, and libraries
- 4.2 Construct required fault correction code according to organisational and programming standards
- 4.3 Compile code for changed programs and associated modules
- 4.4 Correct, and resubmit required 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 and determine it works with test data, corrects original fault, and does not cause problems elsewhere
- 5.2 Request users to perform acceptance testing and document outcomes
- 5.3 Submit documentation to required personnel and seek and respond to feedback
- 5.4 Confirm acceptance by systems operations and arrange for sign-off, according to procedures
No information
No information
Replaces
| State Code | National Code | Title | Type |
|---|---|---|---|
| AUV74 | ICTPRG510 | Maintain custom software | Unit of competency |
| State Code | National Code | Title | Type |
|---|---|---|---|
| BFG0 | ICT50120 | Diploma of Information Technology | Qualification |
| BGJ4 | ICT50220 | Diploma of Information Technology | Qualification |