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
What evidence can you provide to prove your understanding of each of the following citeria?
Investigate scripting options
|
|
Assess design specifications to identify areas where scripting languages may be required Completed |
Evidence:
|
Locate script libraries for pre-written scripts Completed |
Evidence:
|
Identify areas where customised or new scripts may be necessary Completed |
Evidence:
|
Present and discuss scripting options with relevant personnel, and confirm compliance with design specifications Completed |
Evidence:
|
Write scripts
|
|
Scope control structures and algorithms using pseudo-code and flow charts Completed |
Evidence:
|
Check objects and assets are in place and identified by appropriate labels Completed |
Evidence:
|
Identify and recommend event handlers Completed |
Evidence:
|
Write code using correct syntax to meet functional requirements Completed |
Evidence:
|
Write comments to document coding where necessary Completed |
Evidence:
|
Use authoring environment, where appropriate, to check code and syntax Completed |
Evidence:
|
Save code in appropriate format Completed |
Evidence:
|
Adopt safe ergonomic practices when using screens and keyboards for extended periods of time Completed |
Evidence:
|
Integrate scripting language
|
|
Source and integrate scripts into authoring environment Completed |
Evidence:
|
Confirm scripted elements comply with all navigation and graphic design interface considerations Completed |
Evidence:
|
Eliminate or merge redundant code to ensure code is clean Completed |
Evidence:
|
Test scripting language
|
|
Test routines to verify script fulfils requirements Completed |
Evidence:
|
Conduct tests to ensure scripted elements conform to required technical specifications Completed |
Evidence:
|
Test for faults, and document findings Completed |
Evidence:
|
Use standard de-bugging techniques to remove fault Completed |
Evidence:
|
Evaluate scripting language
|
|
Liaise with relevant personnel to evaluate process, and record decisions Completed |
Evidence:
|
Archive suitable and relevant scripts for future use Completed |
Evidence:
|