NTISthis.com

Evidence Guide: ICAPRG509A - Build using rapid application development

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

 

ICAPRG509A - Build using rapid application development

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

Construct application using RAD

  1. Capture and record business rules using a methodology well-suited for the chosen RAD and RAD techniques
  2. Design application with focus on modularity and future extension
  3. Develop code by other RAD tools
  4. Build and demonstrate completed transaction to user for revision within the agreed terms of reference
  5. Take action to ensure that design caters for continuous change by involving user in iteration process
  6. Provide quality assurance (QA) testing throughout the phase and provide feedback to appropriate person
  7. Demonstrate use of code optimisers and performance tools
Capture and record business rules using a methodology well-suited for the chosen RAD and RAD techniques

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design application with focus on modularity and future extension

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop code by other RAD tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Build and demonstrate completed transaction to user for revision within the agreed terms of reference

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure that design caters for continuous change by involving user in iteration process

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Provide quality assurance (QA) testing throughout the phase and provide feedback to appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Demonstrate use of code optimisers and performance tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare handover stage

  1. Track implemented modules and follow up where necessary with appropriate person
  2. Review user and builds for each module in the deliverables as preparation for handover
  3. Compare specifications and implementation schedules for each module and confirm the functional requirements according to specifications
  4. Document the completed work
Track implemented modules and follow up where necessary with appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review user and builds for each module in the deliverables as preparation for handover

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare specifications and implementation schedules for each module and confirm the functional requirements according to specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the completed work

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:

design application and develop high quality code according to client specifications

provide QA testing and monitoring

demonstrate use of code optimisers using RAD techniques

document completed work.

Context of and specific resources for assessment

Assessment must ensure access to:

CASE repository to facilitate the re-use of templates and components

CASE tools

code generator

detailed user requirements

prototyping software

requirements document, including model and scope

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 completed code

review of documentation

verbal or written questioning to assess knowledge of prototyping and RAD process.

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 users while managing iterative changes in design by involving end users in the development process

literacy skills to write technical documents and present written material for review

planning and organisational skills to keep accurate technical records

problem-solving skills to solve problems with design

technical skills to identify, analyse and evaluate a range of solutions using prototyping tools.

Required knowledge

broad knowledge of industry-accepted prototyping tools

overview knowledge of:

quality assurance practices

client business domain

role of stakeholders and the degree of stakeholder involvement

three or more current industry development methodologies

three or more programming languages.

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.

RAD techniques may include:

computer-aided software engineering (CASE) tools

iterative life cycles

prototyping

re-use of applications, templates and code

SWAT teams

timebox-development methodology

workshops.

Application may include:

commercial software applications

organisation-specific software:

communication packages

database

graphic

presentation functionalities

spreadsheet

word-processing.

RAD tools may include:

CASE tools

code generators.

User may include:

department within the organisation

person within a department

third party.

Appropriate person may include:

authorised business representative

client

supervisor.

Specifications may include:

current system functionality

metrics

project plan

software requirements

technical requirements

user problem statement.