Assessor Resource

ICAPRG526A
Maintain functionality of legacy code programs

Assessment tool

Version 1.0
Issue Date: April 2024


This unit applies to individuals working in software development who are required to maintain legacy programs, updating them as required.

This unit describes the performance outcomes, skills and knowledge required to maintain the functionality of legacy code programs.

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

Prerequisites

Not applicable.

Employability Skills

This unit contains employability skills.



Evidence Required

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:

read legacy language

identify and isolate the required change

implement the change via the chosen technique.

Context of and specific resources for assessment

Assessment must ensure access to:

documents detailing organisational standards for software development

existing legacy code

appropriate compilers

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 candidate’s completed change in legacy code

review of candidate’s documentation that reflects modification in legacy programs

verbal or written questioning to determine candidate’s knowledge of:

key design alternatives

change-management process.

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.

Submission Requirements

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)

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 determine functional changes and impacts these changes will have on the system

communication skills to liaise with user and operational personnel

literacy skills to interpret and write technical documentation

planning and organisational skills to determine change-management process

technical skills to:

code in legacy language

test new code

use change-management system.

Required knowledge

operational procedures on the required operating system

organisational standards for software development

security and viruses

privacy legislation and copyright with regard to legacy code, the particular system involved and its data

technical terminology related to reading help files and manuals

types of software.

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.

User may include:

department within the organisation

person within a department

third party.

Technical documentation may include:

brochures

help references

online help

project specifications

reports

technical manuals

training materials and self-paced tutorials

user guides.

Change approach may include:

implementing a new layer or replacing an existing layer to the architecture of the system

implementing the changes in the legacy language

implementing wrappers to the legacy code.

Hardware may include:

modems and other connectivity devices, such as asymmetric digital subscriber line (ADSL) modems

networks

personal computers

remote sites

servers

workstations.

Software may include:

commercial applications

customised

in-house

organisation-specific

packaged.

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
Consult user to determine and document the functional change required 
Clarify impact of changes with operational personnel 
Identify the basic structures of the legacy language 
Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling 
Review the basic algorithms of the legacy language 
Review the technical documentation for the system to determine modules to change 
Review source code to determine program logic and flow 
Update the technical documentation to reflect current state of program 
Determine the change approach to be used to implement the change 
Ascertain and detail the risks for each approach 
Determine the personnel who will make the changes 
Develop the changes required, considering the impact of the changes on other parts of the system 
Document the changes according to change-management standards 
Identify and obtain appropriate hardware and software for the change 
Write code according to programming standards 
Compile and unit test the changes 
Document the changes according to programming standards 
System test the changes and record outcomes 
Perform user acceptance testing and record outcomes 
Sign off change request 
Create new version of software according to configuration management standards 
Archive the development system, including source code, compilers and test data 

Forms

Assessment Cover Sheet

ICAPRG526A - Maintain functionality of legacy code programs
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

ICAPRG526A - Maintain functionality of legacy code programs

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: