Maintain functionality of legacy code programs

Formats and tools

Unit Description
Reconstruct the unit from the xml and display it as an HTML page.
Assessment Tool
an assessor resource that builds a framework for writing an assessment tool
Assessment Template
generate a spreadsheet for marking this unit in a classroom environment. Put student names in the top row and check them off as they demonstrate competenece for each of the unit's elements and performance criteria.
Assessment Matrix
a slightly different format than the assessment template. A spreadsheet with unit names, elements and performance criteria in separate columns. Put assessment names in column headings to track which performance criteria each one covers. Good for ensuring that you've covered every one of the performance criteria with your assessment instrument (all assessement tools together).
Wiki Markup
mark up the unit in a wiki markup codes, ready to copy and paste into a wiki page. The output will work in most wikis but is designed to work particularly well as a Wikiversity learning project.
Evidence Guide
create an evidence guide for workplace assessment and RPL applicants
Competency Mapping Template
Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners. A template for developing assessments for a unit, which will help you to create valid, fair and reliable assessments for the unit, ready to give to trainers and students
Observation Checklist
create an observation checklist for workplace assessment and RPL applicants. This is similar to the evidence guide above, but a little shorter and friendlier on your printer. You will also need to create a seperate Assessor Marking Guide for guidelines on gathering evidence and a list of key points for each activity observed using the unit's range statement, required skills and evidence required (see the unit's html page for details)

Self Assessment Survey
A form for students to assess thier current skill levels against each of the unit's performance criteria. Cut and paste into a web document or print and distribute in hard copy.
Moodle Outcomes
Create a csv file of the unit's performance criteria to import into a moodle course as outcomes, ready to associate with each of your assignments. Here's a quick 'how to' for importing these into moodle 2.x
Registered Training Organisations
Trying to find someone to train or assess you? This link lists all the RTOs that are currently registered to deliver ICAPRG526A, 'Maintain functionality of legacy code programs'.
Google Links
links to google searches, with filtering in place to maximise the usefulness of the returned results
Reference books for 'Maintain functionality of legacy code programs' on This online store has a huge range of books, pretty reasonable prices, free delivery in Australia *and* they give a small commission to for every purchase, so go nuts :)

Elements and Performance Criteria

1. Determine functional changes required

1.1 Consult user to determine and document the functional change required

1.2 Clarify impact of changes with operational personnel

2. Review legacy language

2.1 Identify the basic structures of the legacy language

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

2.3 Review the basic algorithms of the legacy language

3. Identify and isolate change

3.1 Review the technical documentation for the system to determine modules to change

3.2 Review source code to determine program logic and flow

3.3 Update the technical documentation to reflect current state of program

4. Determine framework for change

4.1 Determine the change approach to be used to implement the change

4.2 Ascertain and detail the risks for each approach

4.3 Determine the personnel who will make the changes

5. Design change

5.1 Develop the changes required, considering the impact of the changes on other parts of the system

5.2 Document the changes according to change-management standards

6. Code change

6.1 Identify and obtain appropriate hardware and software for the change

6.2 Write code according to programming standards

6.3 Compile and unit test the changes

6.4 Document the changes according to programming standards

7. Test change

7.1 System test the changes and record outcomes

7.2 Perform user acceptance testing and record outcomes

7.3 Sign off change request

8. Archive system

8.1 Create new version of software according to configuration management standards

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