NTISthis.com

Evidence Guide: ICAICT420A - Develop client 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

 

ICAICT420A - Develop client user interface

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

Prepare design for interface

  1. Review requirements and other documentation to determine user needs
  2. Investigate system environment to determine the impact of user interface design
  3. Review organisational goals to ensure consistency with organisational styles
  4. Define data query and report formats for the user interface design where appropriate
  5. Document needs and findings and obtain approval for the proposed interface from the appropriate person
Review requirements and other documentation to determine user needs

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Investigate system environment to determine the impact of user interface design

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Review organisational goals to ensure consistency with organisational styles

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Define data query and report formats for the user interface design where appropriate

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document needs and findings and obtain approval for the proposed interface from the appropriate person

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Design and document user interface

  1. Design menu structures according to requirements and acceptance criteria and following design principles
  2. Design screen dialogues according to requirements and acceptance criteria and following design principles
  3. Design batch procedures where appropriate to technical specifications and acceptance criteria
  4. Design online help and tutorials for the prototype following design principles
  5. Document prototype according to organisational goals
  6. Submit prototype to appropriate person for sign-off
Design menu structures according to requirements and acceptance criteria and following design principles

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Design screen dialogues according to requirements and acceptance criteria and following design principles

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Design batch procedures where appropriate to technical specifications and acceptance criteria

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Design online help and tutorials for the prototype following design principles

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document prototype according to organisational goals

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Submit prototype to appropriate person for sign-off

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:

determine impact of user interface design in the system environment and identify appropriate data query and report formats

design menu structures according to design principles

design screen dialogues in line with requirements and acceptance criteria

design batch procedures

develop online help and tutorials for prototype.

Context of and specific resources for assessment

Assessment must ensure access to:

design specifications

organisational standards for documentation and version control

project management process and hierarchy

usability test plan

agreed usability metrics

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:

direct observation of candidate defining data query and report formats for the user interface design based on analysis of requirements

verbal or written questioning to assess candidate’s knowledge of requirements for designing online help and tutorials

review of candidate’s user interface prototype.

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 and negotiate with clients and staff

present information

literacy skills to:

analyse and evaluate information

develop online help and tutorials

write business reports

technical skills to:

design and document user interface, including screen dialogues and batch procedures

prepare and review technical documentation.

Required knowledge

client business area

current industry design principles

current industry-accepted hardware and software products, including broad knowledge of general features and capabilities

current industry-accepted user interfaces, including broad knowledge of general features and capabilities

front-end systems

web design principles.

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 refer to:

business

network

people in the organisation

system.

Documentation may involve:

business performance data

business policies customer feedback

business strategic plans

change-management plans

current systems design plans

project management plans.

User may include:

department within the organisation

person within a department

third party.

System environment may include:

business

computers

financial system

information system

management system

network

software.

Organisational goals may include:

preventative maintenance and diagnostic policy

problem solution processes

roles and technical responsibilities in the IT department

vendor and product service level support agreements

work environment.

Appropriate person may include:

authorised business representative

client

supervisor.

Acceptance criteria may include:

cost implications

logistical considerations

technical

timeframe.

Design principles may include:

consistency

ease of learning

familiarity

flexibility

invisible technology

product compatibility

protection

responsiveness

robustness

simplicity

task compatibility

user compatibility

workflow compatibility.