NTISthis.com

Evidence Guide: ICAPRG512A - Prepare for the build phase of an IT system

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

 

ICAPRG512A - Prepare for the build phase of an IT system

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

Identify best development platform for project

  1. Identify requirements of the development platform using the detailed technical specifications
  2. Match the technical specification of the development platform with the technical specification of the project and quality standards
Identify requirements of the development platform using the detailed technical specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Match the technical specification of the development platform with the technical specification of the project and quality standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify best development tools for project

  1. Identify functional requirements for development tools using the detailed technical specifications and other program documentation
  2. Evaluate development tools for match with requirements and document evaluation outcomes
  3. Select appropriate development tools
Identify functional requirements for development tools using the detailed technical specifications and other program documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate development tools for match with requirements and document evaluation outcomes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Select appropriate development tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare development environment

  1. Obtain components for development platform, development tools and required hardware
  2. Install, configure and test development platform and tools
  3. Document the configuration of the development platform
Obtain components for development platform, development tools and required hardware

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Install, configure and test development platform and tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the configuration of the development platform

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:

meet technical requirements by successfully preparing the development environment.

Context of and specific resources for assessment

Assessment must ensure access to:

design specification

software requirement specifications

system requirements

technical specifications

version control standards

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 candidate’s completed development environment

review of candidate’s documented configuration

verbal or written questioning to assess candidate’s knowledge of software development environments.

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 identify, analyse and evaluate a range of solutions

literacy skills to:

read and correctly interpret technical design documentation

write quality-related software documentation

planning and organisational skills to complete the preparation tasks according to project timescales

research skills to identify best development tools for project

technical skills to install, configure and test a variety of development tools and platforms.

Required knowledge

client business domain

current industry-accepted coding methods and standards in a recognised language and database management system (DBMS) modelling techniques

processes and techniques related to software and database design, architectures and their technical requirements

quality assurance practices.

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.

Development platform may include:

computer language used

development methodology

development tools

operating systems

target environments

version control systems.

Technical specification may include:

system functionality

technical requirements

user problem statement.

Quality standards include:

AS3925.1-1994 Software quality assurance - plans

AS4042-1992 Software configuration management plans

AS4043-1992 Software configuration management

AS/NZS 14102:1998 Information technology - guideline for evaluation and selection of CASE tools

AS/NZS4258:1994 Software user documentation process

AS/NZS ISO/IEC 12207:1997 Information technology - Software life cycle processes

Note: International and Australian standards are updated and changed on a regular basis. It is therefore important to check the Standards Australia website on a regular basis for new standards.

Program documentation may include:

architecture documentation

code comments

design documents

in-code documentation

internal module documentation

release documents

requirement documents

test documents

user manuals.

Development tools may include:

computer-aided software engineering (CASE) tools

fourth-generation language

program generator

screen generator.

Components may include:

CD and DVD drives

central processing unit (CPU)

complementary metal oxide semiconductor (CMOS) battery

CPU upgrades

drives

fax or modem cards

interface cards

motherboards

random access memory (RAM) upgrades.

Hardware may include:

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

networks

personal computers

remote sites

servers

workstations.