Unit of competency Outline

Date retreived
22/07/2026 10:55 AM 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
ICTPRG510
State Code
AUV74
TGA Status
Replaced
DTWD Status
Replaced
Current Release Number
1.00
Current Release Date
25/03/2015
View on TGA
State Implementation and Classification
Approved Date
16/09/2015
Field of Education
020103 - Programming
Original Release Date
16/09/2015
Nominal Hours
35
Description
This unit describes the skills and knowledge required to maintain software so that it continues to meet client user requirements.It applies to individuals who may work as programmers 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 the software fault to be corrected
  • 1.1 Collect and review the software fault details from sources
  • 1.2 Obtain technical data to assist in identifying the problem
  • 1.3 Clarify nature of the problem with appropriate person where necessary
2. Identify and isolate the fault
  • 2.1 Review program documentation for specific modules in order to pinpoint problem areas
  • 2.2 Review the 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 the difficult faults that cannot be identified
3. Design a fix for the fault
  • 3.1 Ensure that the requirements needed to fix the fault are understood by the 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 the changes according to the organisational guidelines
4. Carry out the fix to the software
  • 4.1 Identify, and obtain, access to the appropriate software development tools, source code, and libraries
  • 4.2 Construct the appropriate code to correct the fault, according to organisational and programming standards
  • 4.3 Compile, or regenerate, the code for changed programs and the associated modules
  • 4.4 Correct, and resubmit, the code until error free
  • 4.5 Document the changes, according to organisational and programming standards
5. Test the 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 the documentation to reflect all the changes made
  • 6.2 Confirm acceptance by systems operations and arrange for sign-off, according to procedures
No information
No information
Replaces
State Code National Code Title Type
D8025 ICAPRG510A Maintain custom software Unit of competency
Replaced By
State Code National Code Title Type
OBT02 ICTPRG540 Maintain custom software Unit of competency