NTISthis.com

Evidence Guide: ICAPRG416A - Manage a software component reuse library

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

 

ICAPRG416A - Manage a software component reuse library

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

Specify components for reuse library

  1. Determine component suitability for reuse by checking its quality and uses
  2. Review the size and complexity of reuse components for generalisation and remove project-specific refinements
  3. Evaluate components, including patterns, clusters and frameworks, and break down into smaller components for greater flexibility or use
  4. Review components for duplication and remove duplicates
Determine component suitability for reuse by checking its quality and uses

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the size and complexity of reuse components for generalisation and remove project-specific refinements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate components, including patterns, clusters and frameworks, and break down into smaller components for greater flexibility or use

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review components for duplication and remove duplicates

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document reuse library

  1. Document components internally and externally to ensure efficient retrieval
  2. Document public constants, data structures, component interfaces and limitations
  3. Document possible relationships between data structures or objects
  4. Provide example code, demonstrating the use of components within the documentation
  5. Document development environment configuration
  6. Provide simple test programs to prove the functionality of the library
Document components internally and externally to ensure efficient retrieval

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document public constants, data structures, component interfaces and limitations

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document possible relationships between data structures or objects

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Provide example code, demonstrating the use of components within the documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document development environment configuration

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Provide simple test programs to prove the functionality of the library

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Set up library structure

  1. Classify data structures or objects in a consistent and logical manner
  2. Ensure that library has a logical structure so that the user is aware of library contents and can understand the logic of how the functionality may be used by another developer
  3. Develop the structure in a manner that avoids redundancy within the library
  4. Configure development environment to automate build of reuse components and library
  5. Take action to ensure interfaces to library components are consistent and abstracted
  6. Add, update and remove reuse components as development is undertaken
Classify data structures or objects in a consistent and logical manner

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ensure that library has a logical structure so that the user is aware of library contents and can understand the logic of how the functionality may be used by another developer

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop the structure in a manner that avoids redundancy within the library

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Configure development environment to automate build of reuse components and library

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure interfaces to library components are consistent and abstracted

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Add, update and remove reuse components as development is undertaken

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:

reuse libraries and manage components within the library structure

store, document and improve the quality of reuse components for efficient retrieval and use

organise and communicate library contents.

Context of and specific resources for assessment

Assessment must ensure access to:

software development environment

technical requirements

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 design paradigms

review of the candidate’s library structure

evaluation of the library components added.

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:

classify data structures

determine the quality of reuse components for efficient retrieval and use

evaluate components to allow for greater flexibility or use

communication skills to liaise with users

literacy skills to provide technical documents

planning and organisational skills to:

manage own work priorities

produce a logical library structure

technical skills to:

provide example code to demonstrate functionality

use simple test programs to prove the functionality of the library.

Required knowledge

abstraction of code module interfaces

component libraries

design paradigms

patterns, frameworks and idioms

reuse components and metrics

reuse libraries content and structure.

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.

Component may include:

classes

code

design

documents

metadata

methods

modules

test cases.

Reuse components may include:

code

design patterns

metadata

requirements

specifications.

Project may include:

business improvement process

business involved in a total organisational change

ebusiness solution involving the total organisation or part of the organisation

systems-only change.

Development environment may include:

computer language used

development methodology

development tools

operating systems

target environments

version control systems.

User may include:

department within the organisation

person within a department

third party.