NTISthis.com

Evidence Guide: ICAPRG410A - Build a user interface

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

 

ICAPRG410A - Build a user interface

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

Build a prototype user interface

  1. Gather requirements for the user interface
  2. Determine the application development language for writing the user interface
  3. Build a prototype using prototyping tools available in the determined language
  4. Review UI prototype with client and edit as required
Gather requirements for the user interface

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the application development language for writing the user interface

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Build a prototype using prototyping tools available in the determined language

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review UI prototype with client and edit as required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design UI

  1. Formulate application content flow
  2. Design UI components
  3. Define UI actions
  4. Itemise UI events
Formulate application content flow

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design UI components

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define UI actions

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Itemise UI events

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Build UI

  1. Determine the appropriate language
  2. Build UI with the required functionality
Determine the appropriate language

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Build UI with the required functionality

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test UI

  1. Test UI for overall functionality according to requirements
  2. Iterate UI design or build until test results meet requirements
Test UI for overall functionality according to requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Iterate UI design or build until test results meet requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document UI and obtain client sign-off

  1. Document user requirements
  2. Document UI
  3. Obtain client sign-off to completed UI
Document user requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document UI

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Obtain client sign-off to completed UI

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 a fully functional UI in consultation with the user using the determined language

create a prototype UI

review the prototype with the user

build the UI

test that created UI is complete, consistent and functional.

Context of and specific resources for assessment

Assessment must ensure access to:

internet in order to use online tools available for prototyping and UI design

integrated development environment (IDE) for the determined language

specific tools and licenses are available depending on particular platform, such as Windows, Linux, Unix, Mac and Google Chrome

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:

UI prototype

completed UI

review of candidate’s UI documentation

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

UI components

prototyping methodology.

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 provide advice and guidance to others

literacy skills to read basic technical data

numeracy skills to make basic calculations for specifying the layout of the UI

research skills to keep up-to-date with UI technologies and tools

technical skills to:

create applications using basic programming techniques

create web pages using hypertext markup language (HTML) and cascading style sheet (CSS)

debug applications using basic debugging techniques

test applications using basic testing techniques.

Required knowledge

maths at a basic level

object-oriented programming

open-source development tools

small-size application development.

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.

Gather requirements may include:

interviews

observation

questionnaires.

Development language may include:

object-oriented language, such as:

ASP.NET

C++

Java

JavaScript

JSP

NET (VB, C#)

Python

XHTML, DHTML and CSS.

Prototyping tools may include:

commercial applications, such as:

Adobe FireWorks CS4

Adobe Flash Catalyst

Axure

Balsamiq Mockups

Microsoft Expression Blend

MockupScreens

open-source tools, such as:

FluidIA

Napkin Look & Feel

Pencil Sketching

web-based tool, such as:

Hot Gloo

Mockingbird.

UI components may include:

common and basic controls, such as button, label, textbox, checkbox and combo box

container controls

data controls

dialogs

menus and toolbars controls

printing controls.

UI actions may include:

keyboard actions along with the key modifiers

keyboard actions, such as key press, key release and key action

mouse actions include moves, button presses, button releases and dragging

use of emerging interactive surface technologies and the NUI.