NTISthis.com

Evidence Guide: ICAPRG510A - Maintain custom software

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

 

ICAPRG510A - Maintain custom software

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

Determine software fault to be corrected

  1. Collect and review software fault details from sources
  2. Obtain technical data to assist in identifying problem
  3. Clarify nature of the problem with appropriate person where necessary
Collect and review software fault details from sources

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Obtain technical data to assist in identifying problem

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Clarify nature of the problem with appropriate person where necessary

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify and isolate fault

  1. Review program documentation for specific modules in order to pinpoint problem areas
  2. Review source code for logic errors
  3. 2.3 Read manuals, help files and 'read me files' to determine if there is a known fix
  4. Undertake additional testing to identify or duplicate fault
  5. Escalate difficult faults that cannot be identified
Review program documentation for specific modules in order to pinpoint problem areas

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Review source code for logic errors

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

2.3 Read manuals, help files and 'read me files' to determine if there is a known fix

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Undertake additional testing to identify or duplicate fault

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Escalate difficult faults that cannot be identified

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Design fix for fault

  1. Ensure requirements to fix the fault are understood by client
  2. Consider alternative options and choose the most effective solution
  3. Consider the possible impact of the fix on other parts of the system
  4. Document changes according to organisational guidelines
Ensure requirements to fix the fault are understood by client

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Consider alternative options and choose the most effective solution

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Consider the possible impact of the fix on other parts of the system

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document changes according to organisational guidelines

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Carry out fix to software

  1. Identify and obtain access to appropriate software development tools, source code and libraries
  2. Construct appropriate code to correct the fault according to organisational and programming standards
  3. Compile or regenerate code for changed programs and associated modules
  4. Correct and resubmit code until error free
  5. Document changes according to organisational and programming standards
Identify and obtain access to appropriate software development tools, source code and libraries

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Construct appropriate code to correct the fault according to organisational and programming standards

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Compile or regenerate code for changed programs and associated modules

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Correct and resubmit code until error free

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document changes according to organisational and programming standards

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test fix and associated system areas

  1. Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere
  2. Request users to perform acceptance testing and record outcomes
Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Request users to perform acceptance testing and record outcomes

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Hand over to systems operations area

  1. Update documentation to reflect all changes made
  2. Confirm acceptance by systems operations and arrange for sign-off according to procedures
Update documentation to reflect all changes made

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm acceptance by systems operations and arrange for sign-off according to procedures

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:

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.

Required Skills and Knowledge

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.

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.

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.