NTISthis.com

Evidence Guide: ICAI5090B - Conduct pre-installation audit for software installation.doc

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

 

ICAI5090B - Conduct pre-installation audit for software installation.doc

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 minimum 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 appropriateperson
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 minimum 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 appropriateperson

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 the degree of interoperability between software
  3. Confirm the 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 the degree of interoperability between software

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm the 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, other specific hardware requirements from investigation of actual system and existing 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, other specific hardware requirements from investigation of actual system and existing 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 following is essential:

Assessment must confirm sufficient ability to guide clients about which specific components are required prior to commencement of installation. Clear recommendations and assignment of responsibility for missing components must be evident. Additionally, the person must be able to determine the impact and risks associated with either continuing or discontinuing implementation.

To demonstrate competency in this unit the person will require access to:

Operational system and system specifications

Technical specifications of software to be installed

Documentation tools

Context of and specific resources for assessment

Pre-installation planning and audit stages are important to the success of software installation and upgrade projects. Data collected and analyses undertaken through these processes inform the implementation plan by clearly establishing environmental and technical prerequisites and may assist in avoiding costly mistakes in software choice and lost revenue or productivity.

The breadth, depth and complexity covering planning and initiation of alternative approaches to skills or knowledge applications across a broad range of technical and/or management requirements, evaluation and coordination would be characteristic.

Assessment must ensure:

The demonstration of competency may also require self-directed application of knowledge and skills, with substantial depth in some areas where judgement is required in planning and selecting appropriate equipment, services and techniques for self and others.

Applications involve participation in development of strategic initiatives as well as personal responsibility and autonomy in performing complex technical operations or organising others. It may include participation in teams including teams concerned with planning and evaluation functions. Group or team coordination may also be involved.

Method of assessment

The purpose of this unit is to define the standard of performance to be achieved in the workplace. In undertaking training and assessment activities related to this unit, consideration should be given to the implementation of appropriate diversity and accessibility practices in order to accommodate people who may have special needs. Additional guidance on these and related matters is provided in ICA05 Section 1.

Competency in this unit should be assessed using summative assessment to ensure consistency of performance in a range of contexts. This unit can be assessed either in the workplace or in a simulated environment. However, simulated activities must closely reflect the workplace to enable full demonstration of competency.

Assessment will usually include observation of real or simulated work processes and procedures and/or performance in a project context as well as questioning on underpinning knowledge and skills. The questioning of team members, supervisors, subordinates, peers and clients where appropriate may provide valuable input to the assessment process. The interdependence of units for assessment purposes may vary with the particular project or scenario.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, for example:

ICAS5104B Determine maintenance strategy

ICAS5105B Coordinate change requests

ICAS5111B Review and manage delivery of maintenance services

ICAT5081B Perform systems test

An individual demonstrating this competency would be able to:

Demonstrate understanding of a broad knowledge base incorporating theoretical concepts, with substantial depth in some areas

Analyse and plan approaches to technical problems or management requirements

Transfer and apply theoretical concepts and/or technical or creative skills to a range of situations

Evaluate information, using it to forecast for planning or research purposes

Take responsibility for own outputs in relation to broad quantity and quality parameters

Take some responsibility for the achievement of group outcomes

Maintain knowledge of industry products and services

Required Skills and Knowledge

Required skills

Problem solving skills for a defined range of unpredictable problems involving participation in the development of strategic initiatives (e.g. when software prerequisites needed for new software are identified, implications noted, minimum requirements confirmed and customer requirements matched with technical specifications, and when capacity issues are confirmed and assessed against installation plan and cost constraints)

Teamwork skills involving the contribution to solutions

Report writing skills for business requiring depth in some areas, analysis and evaluation of information in a defined range of areas (e.g. when audit/analysis report is presented and distributed)

Facilitation and presentation skills in relation to transferring and collecting information and gaining consensus on concepts (e.g. when audit/analysis report is presented and distributed according to company and project procedure).

Use of system diagnostics and utilities (e.g. when details of current system memory, disk, available disk storage, other specific hardware requirements are obtained from investigation of actual system and existing system documentation)

Project planning skills in relation to scope, time, cost, quality, communications and risk management (e.g. determining the timeline for the installation of new software and presenting findings, recommendations and impact on project in a clear, concise and timely manner)

Required knowledge

Detailed knowledge of the system's current functionality (e.g. assessing compatibility of existing software when assessing system's capacity to install ordered software)

Current industry-accepted hardware and software products, with broad knowledge of general features and capabilities and detailed knowledge in some areas

Broad knowledge of the client business domain (e.g. assessing compatibility of existing software)

Broad knowledge of the role of stakeholders and the degree of stakeholder involvement (e.g. assessing possible effects on the client if the installation does not go according to plan)

Broad knowledge of quality assurance practices (e.g. when confirming interoperability of software with environment)

Broad knowledge of risk management (e.g. when preparing and distributing audit report or when testing the new software for compatibility with the old)

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.

Hardware may include but is not limited to:

workstations

personal computers

modems and other connectivity devices

networks

DSL modems

remote sites

servers

Client may be:

a department within the organisation

a third party, so the relationship and ease of access will vary

Appropriate person may include:

supervisor

teacher

authorised business representative

client

Constraints may include but is not limited to:

time

budget

resource

hardware

software

policy

legal constraints

Software may include but is not limited to:

commercial software applications; organisation-specific software, packaged software, in-house or customised software