NTISthis.com

Evidence Guide: ICASAS407A - Conduct pre-installation audit for software installation

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

 

ICASAS407A - Conduct pre-installation audit for software installation

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

Assess compatibility of existing software

  1. Confirm details of software loaded on client system from actual system and from existing system documentation
  2. Identify software prerequisites needed for new software
  3. Confirm customer requirements with technical specifications
  4. Confirm and assess compatibility issues against installation plan and cost constraints
  5. Document recommendations on variances, level and software consistency for consideration by appropriate person
Confirm details of software loaded on client system from actual system and from existing system documentation

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify software prerequisites needed for new software

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm customer requirements with technical specifications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm and assess compatibility issues against installation plan and cost constraints

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document recommendations on variances, level and software consistency for consideration by appropriate person

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm interoperability of software with environment

  1. Confirm that there are no conflicts between the new software and previously installed software and hardware
  2. Measure degree of interoperability between software
  3. Confirm interoperable functioning of all software involved
Confirm that there are no conflicts between the new software and previously installed software and hardware

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Measure degree of interoperability between software

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm interoperable functioning of all software involved

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assess system capacity to install ordered software

  1. Obtain details of current system memory, disk, available disk storage, and other specific hardware requirements from investigation of system and system documentation
  2. Confirm that the hardware prerequisites needed for new software are met, implications noted and minimum requirements identified
  3. Confirm and assess capacity issues against installation plan and cost constraints
  4. Document recommendations on variances in capacity for consideration by appropriate person
Obtain details of current system memory, disk, available disk storage, and other specific hardware requirements from investigation of system and system documentation

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm that the hardware prerequisites needed for new software are met, implications noted and minimum requirements identified

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm and assess capacity issues against installation plan and cost constraints

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document recommendations on variances in capacity for consideration by appropriate person

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Prepare and distribute audit report

  1. Document findings, recommendations and impact on project in a manner appropriate for target audience
  2. Present and distribute the audit analysis report according to organisational standards and procedures
Document findings, recommendations and impact on project in a manner appropriate for target audience

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Present and distribute the audit analysis report according to organisational standards and 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:

establish capability of hardware on which new system is to be installed

ensure that the nominated hardware has the capacity to run the installed system

ensure that new systems will operate cooperatively with existing systems

document variations from the above.

Context of and specific resources for assessment

Assessment must ensure access to:

documentation tools

operational system and system specifications

technical specifications of software to be installed

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:

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

system current functionality

system hardware and software requirements

review of audit analysis report.

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

communication skills to liaise with clients

initiative and enterprise skills to develop strategic initiatives

literacy skills to write technical reports and audit or analysis reports

numeracy skills to calculate hardware prerequisites

planning and organisational skills to:

prepare a risk management and contingency plan

scope, prepare time lines and cost out a project

technical skills to use system diagnostics and utilities.

Required knowledge

current industry-accepted hardware and software product

detailed knowledge of system's current functionality

overview knowledge of:

quality assurance practices

risk-management practices

client business domain

role of stakeholders and the degree of stakeholder involvement.

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.

Software may include:

commercial applications

customised

in-house

organisation-specific

packaged.

Client may be:

department within the organisation

third party.

System may include:

application service provider

applications

databases

gateways

internet service providers

networks

operating systems

servers

websites.

Constraints may include:

budget

hardware

legal constraints

policy

resource

software

time.

Appropriate person may include:

authorised business representative

client

supervisor.

Hardware may include:

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

networks

personal computers

remote sites

servers

workstations.