NTISthis.com

Evidence Guide: ICAPRG516A - Develop integration blueprint for IT systems

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

 

ICAPRG516A - Develop integration blueprint for IT systems

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

Review technical architecture documents

  1. Review technical architecture documents, supplemented with discussions where necessary
  2. Identify and evaluate technical considerations that cover the overall requirements and provide best technical fit against requirements
  3. Update the integration blueprint according to best-fit technical specifications
Review technical architecture documents, supplemented with discussions where necessary

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and evaluate technical considerations that cover the overall requirements and provide best technical fit against requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Update the integration blueprint according to best-fit technical specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Undertake compatibility tests

  1. Assemble components and component technologies according to design specifications
  2. Test components for functionality against design specifications
  3. Identify non-compliance against technical specifications
  4. Update the integration blueprint to reflect functionality and non-compliance changes
Assemble components and component technologies according to design specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test components for functionality against design specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify non-compliance against technical specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Update the integration blueprint to reflect functionality and non-compliance changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assess risk areas

  1. Identify the scope of modifications required from compatibility test
  2. Negotiate modifications required with the suppliers, based on outcomes of compatibility test
  3. Update the integration blueprint to reflect modifications to risk areas
Identify the scope of modifications required from compatibility test

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Negotiate modifications required with the suppliers, based on outcomes of compatibility test

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Update the integration blueprint to reflect modifications to risk areas

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assess readiness for stress testing

  1. Continue integration activities until platform is stable
  2. 4.2 Evaluate the platform's compliance against technical requirements
  3. Update the integration blueprint for stress testing
Continue integration activities until platform is stable

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

4.2 Evaluate the platform's compliance against technical requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Update the integration blueprint for stress testing

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:

identify and capture technical design changes important for future integration activities on a particular platform

avoid integration activities that have been previously performed.

Context of and specific resources for assessment

Assessment must ensure access to:

design specifications

high-level diagrammatic view of the main system components

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 systematic methods used to identify and select tests from component test suites to form integration test suites

review of reusable integration infrastructure to build an integration test platform to cope with integration of diversified components

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

system components

integration activities.

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 apply a range of test procedures

communication skills to liaise with clients and suppliers

literacy skills to review and write technical documents and keep accurate records

problem-solving skills to develop strategic initiatives and manage risk

technical skills to test components for functionality.

Required knowledge

sources of technology suppliers and components

overview knowledge of:

current industry development and design methodologies

current industry-accepted hardware and software products, features and capabilities

current industry-accepted testing procedures

stress load testing.

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.

Requirements may relate to:

business

database

network

people in the organisation

platform

system.

Specifications may include:

current system functionality

metrics

project plan

software requirements

technical requirements

user problem statement.

Components may include:

file system object in Windows operating systems

transactional processing component.

Component technologies may include:

ActiveX

component object model (COM)

common object request broker architecture (CORBA)

distributed component object model (DCOM)

JavaBeans

NET

OpenDoc.

Modifications may include:

board and chip revisions

custom-designed components

distribution release details

driver and firmware revisions

internal or external hardware model information

software patches and upgrades

software versions

telecommunications hardware and software version details.