NTISthis.com

Evidence Guide: CUADIG404 - Apply scripting language in authoring

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

 

CUADIG404 - Apply scripting language in authoring

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

Investigate scripting options

  1. Assess design specifications to identify areas where scripting languages may be required
  2. Locate script libraries for pre-written scripts
  3. Identify areas where customised or new scripts may be necessary
  4. Present and discuss scripting options with relevant personnel, and confirm compliance with design specifications
Assess design specifications to identify areas where scripting languages may be required

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Locate script libraries for pre-written scripts

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify areas where customised or new scripts may be necessary

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Present and discuss scripting options with relevant personnel, and confirm compliance with design specifications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Write scripts

  1. Scope control structures and algorithms using pseudo-code and flow charts
  2. Check objects and assets are in place and identified by appropriate labels
  3. Identify and recommend event handlers
  4. Write code using correct syntax to meet functional requirements
  5. Write comments to document coding where necessary
  6. Use authoring environment, where appropriate, to check code and syntax
  7. Save code in appropriate format
  8. Adopt safe ergonomic practices when using screens and keyboards for extended periods of time
Scope control structures and algorithms using pseudo-code and flow charts

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Check objects and assets are in place and identified by appropriate labels

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify and recommend event handlers

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Write code using correct syntax to meet functional requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Write comments to document coding where necessary

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Use authoring environment, where appropriate, to check code and syntax

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Save code in appropriate format

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Adopt safe ergonomic practices when using screens and keyboards for extended periods of time

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Integrate scripting language

  1. Source and integrate scripts into authoring environment
  2. Confirm scripted elements comply with all navigation and graphic design interface considerations
  3. Eliminate or merge redundant code to ensure code is clean
Source and integrate scripts into authoring environment

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm scripted elements comply with all navigation and graphic design interface considerations

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Eliminate or merge redundant code to ensure code is clean

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test scripting language

  1. Test routines to verify script fulfils requirements
  2. Conduct tests to ensure scripted elements conform to required technical specifications
  3. Test for faults, and document findings
  4. Use standard de-bugging techniques to remove fault
Test routines to verify script fulfils requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Conduct tests to ensure scripted elements conform to required technical specifications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Test for faults, and document findings

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Use standard de-bugging techniques to remove fault

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Evaluate scripting language

  1. Liaise with relevant personnel to evaluate process, and record decisions
  2. Archive suitable and relevant scripts for future use
Liaise with relevant personnel to evaluate process, and record decisions

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Archive suitable and relevant scripts for future use

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Investigate scripting options

1.1 Assess design specifications to identify areas where scripting languages may be required

1.2 Locate script libraries for pre-written scripts

1.3 Identify areas where customised or new scripts may be necessary

1.4 Present and discuss scripting options with relevant personnel, and confirm compliance with design specifications

2. Write scripts

2.1 Scope control structures and algorithms using pseudo-code and flow charts

2.2 Check objects and assets are in place and identified by appropriate labels

2.3 Identify and recommend event handlers

2.4 Write code using correct syntax to meet functional requirements

2.5 Write comments to document coding where necessary

2.6 Use authoring environment, where appropriate, to check code and syntax

2.7 Save code in appropriate format

2.8 Adopt safe ergonomic practices when using screens and keyboards for extended periods of time

3. Integrate scripting language

3.1 Source and integrate scripts into authoring environment

3.2 Confirm scripted elements comply with all navigation and graphic design interface considerations

3.3 Eliminate or merge redundant code to ensure code is clean

4. Test scripting language

4.1 Test routines to verify script fulfils requirements

4.2 Conduct tests to ensure scripted elements conform to required technical specifications

4.3 Test for faults, and document findings

4.4 Use standard de-bugging techniques to remove fault

5. Evaluate scripting language

5.1 Liaise with relevant personnel to evaluate process, and record decisions

5.2 Archive suitable and relevant scripts for future use

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Investigate scripting options

1.1 Assess design specifications to identify areas where scripting languages may be required

1.2 Locate script libraries for pre-written scripts

1.3 Identify areas where customised or new scripts may be necessary

1.4 Present and discuss scripting options with relevant personnel, and confirm compliance with design specifications

2. Write scripts

2.1 Scope control structures and algorithms using pseudo-code and flow charts

2.2 Check objects and assets are in place and identified by appropriate labels

2.3 Identify and recommend event handlers

2.4 Write code using correct syntax to meet functional requirements

2.5 Write comments to document coding where necessary

2.6 Use authoring environment, where appropriate, to check code and syntax

2.7 Save code in appropriate format

2.8 Adopt safe ergonomic practices when using screens and keyboards for extended periods of time

3. Integrate scripting language

3.1 Source and integrate scripts into authoring environment

3.2 Confirm scripted elements comply with all navigation and graphic design interface considerations

3.3 Eliminate or merge redundant code to ensure code is clean

4. Test scripting language

4.1 Test routines to verify script fulfils requirements

4.2 Conduct tests to ensure scripted elements conform to required technical specifications

4.3 Test for faults, and document findings

4.4 Use standard de-bugging techniques to remove fault

5. Evaluate scripting language

5.1 Liaise with relevant personnel to evaluate process, and record decisions

5.2 Archive suitable and relevant scripts for future use

Evidence of the ability to:

use design specifications and discussion with relevant personnel, to identify scripting requirements

create pseudo-code and flowcharts to structure functional logic prior to coding

write scripting language code to meet functional requirements for interactive media products

produce clean, logical and well-documented code

test code and de-bug as required to ensure interactive functions work without fault.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

outline typical challenges when writing scripts for interactive products and how to handle these

describe a range of authoring software, scripting languages and scripted elements

explain different structures used in scripting languages for authoring multimedia products, including Document Object Model (DOM) and Object Oriented Programming (OOP)

identify basic health and safety requirements when working on computers and keyboards.