NTISthis.com

Evidence Guide: CUFDIG502A - Design web environments

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

 

CUFDIG502A - Design web environments

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

Determine project requirements

  1. Analyse project brief to identify purpose of, and target audience for, web environments
  2. Consult with clients to clarify project requirements
  3. Identify target audience characteristics and determine how these influence all aspects of design
  4. Identify content to be incorporated and generated and how this content is to be accessed, searched or delivered
Analyse project brief to identify purpose of, and target audience for, web environments

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Consult with clients to clarify project requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify target audience characteristics and determine how these influence all aspects of design

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify content to be incorporated and generated and how this content is to be accessed, searched or delivered

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Research and select web environments

  1. Research web environments and analyse their potential
  2. Analyse how these web environments meet audience and content requirements
  3. Identify issues relating to delivery platform and standards, and determine how these may affect web environment options
  4. Consult relevant personnel to ensure that all possible web environment options are considered
  5. Select web environments that will meet creative, production and technical requirements
Research web environments and analyse their potential

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Analyse how these web environments meet audience and content requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify issues relating to delivery platform and standards, and determine how these may affect web environment options

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Consult relevant personnel to ensure that all possible web environment options are considered

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Select web environments that will meet creative, production and technical requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Draft design specifications

  1. Design the architecture of web environments to show interrelationship between environment components
  2. Identify each web environment and specify its individual interactive features, functionality and navigation and its relationship to design as a whole
  3. Identify content components and specify how these will be logically structured and integrated into and/or generated by web environments
  4. Specify levels of access permissions to web environments as required
  5. Specify media assets as required
  6. Specify user interfaces of web environments
  7. Specify production requirements, including appropriate testing strategies
  8. Write draft design specifications to include all relevant advice to design and development teams
  9. Discuss draft design specifications with client to ensure designs are consistent with project briefs
Design the architecture of web environments to show interrelationship between environment components

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify each web environment and specify its individual interactive features, functionality and navigation and its relationship to design as a whole

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify content components and specify how these will be logically structured and integrated into and/or generated by web environments

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Specify levels of access permissions to web environments as required

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Specify media assets as required

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Specify user interfaces of web environments

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Specify production requirements, including appropriate testing strategies

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Write draft design specifications to include all relevant advice to design and development teams

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Discuss draft design specifications with client to ensure designs are consistent with project briefs

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Review and confirm design specifications

  1. Review designs against required project outcomes, as well as client and audience needs
  2. Review designs to ensure they meet creative and technical requirements
  3. Adjust designs as necessary after discussions with relevant personnel
  4. Clarify legislative or ownership issues to comply with production and organisational requirements
  5. Confirm with client acceptance of design specifications, including deliverables, milestones and timelines
Review designs against required project outcomes, as well as client and audience needs

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Review designs to ensure they meet creative and technical requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Adjust designs as necessary after discussions with relevant personnel

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Clarify legislative or ownership issues to comply with production and organisational requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm with client acceptance of design specifications, including deliverables, milestones and timelines

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 following is essential:

design specifications for web environments that:

are well documented and clearly presented

meet client and audience requirements

are technically feasible

ability to work effectively as a member of a production team.

Context of and specific resources for assessment

Assessment must ensure:

practical demonstration of skills through the design of web environments for at least two projects

access to project briefs on which designs can be based

access to appropriate learning and assessment support when required

use of culturally appropriate processes and techniques appropriate to the language and literacy capacity of learners and the work being performed.

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 questioning combined with review of portfolios of evidence and third-party workplace reports of on-the-job performance

evaluation of designs for web environments documented by the candidate and of their effectiveness in terms of meeting project requirements

observation of a candidate presenting his/her design for web environments to team members and explaining how it meets requirements

written or oral questioning to test knowledge as listed in the required skills and knowledge section of this unit.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, for example:

CUFDIG505A Design information architecture

CUFPPM404A Create storyboards.

Required Skills and Knowledge

Required skills

communication, teamwork and literacy skills sufficient to:

interpret and clarify written proposals and creative briefs

work collaboratively in a team environment

present ideas for the design of web environments for discussion and feedback from team members

clearly and concisely document specifications for the design of web environments

initiative, enterprise and creativity in the context of:

generating ideas for the design of web environments

thinking laterally when developing concepts

undertaking background research into web environments

maintaining design integrity

finding solutions to problems encountered when designing web environments

finding ways to minimise the effect of technical constraints

ensuring there is an intuitive and logical flow to the navigation of web environments

technical skills sufficient to create storyboards, maps and other diagrams to specify the architecture and navigation of web environments

self-management skills sufficient to:

meet deadlines

provide appropriate and timely documentation

Required knowledge

industry knowledge, including:

roles and responsibilities of project team members, e.g. designers, content creators, information architects, programmers and coders

sequence and interrelationship of stages in the process of developing web environments

broad range of web applications and technologies

web design and its relationship to web optimisation strategies

web standards, including SCORM, usability, W3C Accessibility and interoperability

issues and challenges that arise in designing and developing web environments

typical formats and techniques for documenting the design of web environments

OHS standards as they relate to working for periods of time on computers

intellectual property rights and copyright clearance procedures

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.

Purpose may include:

business and corporate

community

education

entertainment

government

information and news

knowledge management

personal

promotion

training.

Project requirements may include:

access to facilities and resources

budget

deliverables

milestones

personnel, including:

number

availability

expertise prototyping

technical issues, including:

delivery platform

disk space

bandwidth

testing plan

timelines.

Audience characteristics may include:

computer literacy

demographics, such as:

age

gender

education

occupation

location

cultural background

hobbies

interests

internet literacy

language, literacy and numeracy

personas

specific needs - physical or psychological.

Web environments may include one or combinations of:

audio streaming

blog

chat

conferencing tool

content learning management system (CLMS)

content management system (CMS)

database repository

discussion forum

dynamic website

electronic newsletter

interactive calendar

interactive form

learning management system (LMS)

podcast

RSS feed

static website

TiVo

video streaming

other online collaboration and social network tools.

Delivery platform may include:

digital television set

internet

mobile phone

other wireless/mobile devices

personal digital assistant (PDA).

Standards may include:

interoperability

SCORM

usability

W3C Accessibility.

Relevant personnel may include:

art director

client

educator

graphic designer

head of department

information architect

instructional designer

programmer

technical director

technical staff

other specialist creative and administrative staff.

Media assets may include:

animation

audio

audio/visual files, such as PowerPoint

graphics

images

text

text documents, such as PDF and Word

video.

Production requirements may include:

levels of expertise

production deadlines

production schedules

production team

production values

testing strategies.

Testing strategies may include:

alpha

beta

completion

continuous

milestone

prototype

staged.

Design specifications may include:

content inventory

diagrams

flow charts

maps

navigation charts

plans

storyboards

technical specifications

user interface mock-ups

wire frames.

Legislative or ownership issues may be:

access and equity

clearances

confidentiality

copyright

intellectual property rights

non-disclosure agreements

open source licensing

ownership of assets

product licensing.