This unit applies to programmers who are required to maintain existing software.

Organisations may use either software that has been developed in-house or off-the-shelf packages. Some customisation generally occurs with off-the-shelf packages. It is important that all changes made to standard software products are documented. Changes may be made in response to user requests or organisational requirements.

This unit describes the performance outcomes, skills and knowledge required to maintain software so that it continues to meet client user requirements.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)

Not applicable.

This unit contains employability skills.

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

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.

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

Required skills

analytical skills to review software fault details and interpret complex technical data

communication skills to liaise with clients

literacy skills to interpret and write technical documents

planning and organisational skills to ensure adherence to standards and procedures in programming

problem-solving skills to consider alternative options and possible impacts

technical skills to use, customise and adapt software packages.

Required knowledge

detailed knowledge of:

concepts relating to system performance

concepts relating to testing of software systems

current industry-accepted hardware and software products, and their general features and capabilities

system's current functionality.

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.

Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice	Yes	No	Comments/feedback
Collect and review software fault details from sources
Obtain technical data to assist in identifying problem
Clarify nature of the problem with appropriate person where necessary
Review program documentation for specific modules in order to pinpoint problem areas
Review source code for logic errors
2.3 Read manuals, help files and 'read me files' to determine if there is a known fix
Undertake additional testing to identify or duplicate fault
Escalate difficult faults that cannot be identified
Ensure requirements to fix the fault are understood by client
Consider alternative options and choose the most effective solution
Consider the possible impact of the fix on other parts of the system
Document changes according to organisational guidelines
Identify and obtain access to appropriate software development tools, source code and libraries
Construct appropriate code to correct the fault according to organisational and programming standards
Compile or regenerate code for changed programs and associated modules
Correct and resubmit code until error free
Document changes according to organisational and programming standards
Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere
Request users to perform acceptance testing and record outcomes
Update documentation to reflect all changes made
Confirm acceptance by systems operations and arrange for sign-off according to procedures

Assessment Cover Sheet

ICAPRG510A - Maintain custom software

Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICAPRG510A - Maintain custom software

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: