NTISthis.com

Evidence Guide: ICAPRG526A - Maintain functionality of legacy code programs

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICAPRG526A - Maintain functionality of legacy code programs

What evidence can you provide to prove your understanding of each of the following citeria?

Determine functional changes required

  1. Consult user to determine and document the functional change required
  2. Clarify impact of changes with operational personnel
Consult user to determine and document the functional change required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Clarify impact of changes with operational personnel

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review legacy language

  1. Identify the basic structures of the legacy language
  2. Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling
  3. Review the basic algorithms of the legacy language
Identify the basic structures of the legacy language

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the basic algorithms of the legacy language

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and isolate change

  1. Review the technical documentation for the system to determine modules to change
  2. Review source code to determine program logic and flow
  3. Update the technical documentation to reflect current state of program
Review the technical documentation for the system to determine modules to change

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review source code to determine program logic and flow

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Update the technical documentation to reflect current state of program

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine framework for change

  1. Determine the change approach to be used to implement the change
  2. Ascertain and detail the risks for each approach
  3. Determine the personnel who will make the changes
Determine the change approach to be used to implement the change

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ascertain and detail the risks for each approach

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the personnel who will make the changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design change

  1. Develop the changes required, considering the impact of the changes on other parts of the system
  2. Document the changes according to change-management standards
Develop the changes required, considering the impact of the changes on other parts of the system

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the changes according to change-management standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Code change

  1. Identify and obtain appropriate hardware and software for the change
  2. Write code according to programming standards
  3. Compile and unit test the changes
  4. Document the changes according to programming standards
Identify and obtain appropriate hardware and software for the change

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Write code according to programming standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compile and unit test the changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the changes according to programming standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test change

  1. System test the changes and record outcomes
  2. Perform user acceptance testing and record outcomes
  3. Sign off change request
System test the changes and record outcomes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Perform user acceptance testing and record outcomes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Sign off change request

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Archive system

  1. Create new version of software according to configuration management standards
  2. Archive the development system, including source code, compilers and test data
Create new version of software according to configuration management standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Archive the development system, including source code, compilers and test data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

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.

Required Skills and Knowledge

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.

Range Statement

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.