NTISthis.com

Evidence Guide: ICAPRG514A - Prepare for software development 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

 

ICAPRG514A - Prepare for software development using rapid application development

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

Determine RAD requirements

  1. Select and demonstrate use of the most suitable industry standard tool set
  2. Implement a prioritised plan using a series of recursive stages of build and review for delivery of the system
  3. Implement and incorporate a physical database
  4. Identify, document and schedule modules to be implemented by incremental development techniques
  5. Identify and formally allocate responsibilities to authorised user and suitably skilled builders for each module
  6. Plan for and document the endorsement of reviews, administration schedules and development milestones
Select and demonstrate use of the most suitable industry standard tool set

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Implement a prioritised plan using a series of recursive stages of build and review for delivery of the system

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Implement and incorporate a physical database

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify, document and schedule modules to be implemented by incremental development techniques

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify and formally allocate responsibilities to authorised user and suitably skilled builders for each module

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Plan for and document the endorsement of reviews, administration schedules and development milestones

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Determine work metrics

  1. Set development goals
  2. Seek and secure agreement on and adherence to single common notation
  3. Determine tools, features and techniques most appropriate to the development environment
  4. Facilitate, plan, develop and document version and change control methods
  5. Facilitate training and exposure to the user participants via RAD
Set development goals

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Seek and secure agreement on and adherence to single common notation

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Determine tools, features and techniques most appropriate to the development environment

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Facilitate, plan, develop and document version and change control methods

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Facilitate training and exposure to the user participants via RAD

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Implement administration method

  1. Determine and reach agreement of stakeholders on the specifics
  2. Confirm dates for milestones with stakeholders and secure with written agreement
  3. Inform production system parties and secure with written acknowledgment
  4. Administer and maintain relevant time recording and management methodologies
Determine and reach agreement of stakeholders on the specifics

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm dates for milestones with stakeholders and secure with written agreement

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Inform production system parties and secure with written acknowledgment

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Administer and maintain relevant time recording and management methodologies

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:

use RAD tools and prototyping methods in order to meet client requirements

document the outcomes of the RAD.

Context of and specific resources for assessment

Assessment must ensure access to:

computer-aided software engineering tools (CASE) repository to facilitate the re-use of templates and components

CASE tools

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:

observation of candidate participating in RAD

review of candidate’s documentation of RAD process

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

client business requirement

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 stakeholders and users, especially when seeking agreement from all parties

facilitate training

literacy skills to interpret and write technical documents

planning and organisational skills to manage risk when a prioritised plan is implemented, using a series of recursive stages of build and review for delivery of the system

problem-solving skills to determine RAD requirements.

Required knowledge

broad knowledge of industry-accepted prototyping tools

detailed knowledge of:

client business

two or more programming languages

overview knowledge of:

quality assurance practices

two or more current industry development methodologies.

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.

Tool set may include:

bug analyser

code beautifier

compiler

integrated development environment

test harness software.

System may include:

application service provider (ASP)

applications

databases

gateways

internet service provider (ISP)

operating system

servers.

Database may include:

commercial off-the-shelf (COTS) database packages

object-relational databases

proprietary databases

relational databases.

Documentation may follow:

audit trails

client training

International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), and Australian Standards (AS) standards

maintaining equipment inventory

naming standards

project management templates and report writing

satisfaction reports

version control.

Stakeholders may include:

development team

project team

sponsor

user.