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 mark-up and scripting options
|
|
Obtain production and technical specifications Completed |
Evidence:
|
Identify areas where mark-up and scripting languages may be required Completed |
Evidence:
|
Locate script/mark-up libraries for pre-written scripts or programming Completed |
Evidence:
|
Brief programmer on customised scripts/mark-up languages Completed |
Evidence:
|
Determine applicability of mark-up to product functionality Completed |
Evidence:
|
Present and discuss scripting options with relevant personnel to ensure compliance with technical specifications Completed |
Evidence:
|
Select mark-up language and scripting options Completed |
Evidence:
|
Integrate mark-up and scripting language
|
|
Apply and integrate mark-up and scripting language into authoring process Completed |
Evidence:
|
Ensure scripted elements comply with all navigation and graphic design interface considerations Completed |
Evidence:
|
Eliminate or merge redundant scripting and mark-up elements Completed |
Evidence:
|
Apply principles of visual, instructional and interactive design in selecting the best approach Completed |
Evidence:
|
Select a systematic approach that will meet the creative, production and technical requirements specified in the brief outcome Completed |
Evidence:
|
Test mark-up and scripting language
|
|
Test routines to verify script (programming) elements fulfil requirements Completed |
Evidence:
|
Test that mark-up and language elements run true to requirements Completed |
Evidence:
|
Conduct tests to ensure that elements conform to required technical specifications Completed |
Evidence:
|
Test for faults and document findings Completed |
Evidence:
|
Use standard techniques to remove any faults Completed |
Evidence:
|
Develop the storyboard/s in accordance with the needs of the job and the development team Completed |
Evidence:
|
Ensure the design is consistent with the project brief Completed |
Evidence:
|
Identify deliverables and agree on milestones Completed |
Evidence:
|
Evaluate mark-up and scripting language
|
|
Liaise with relevant personnel to evaluate process and record all decisions Completed |
Evidence:
|
Archive suitable and relevant scripts for future use Completed |
Evidence:
|
Review the design to ensure it meets the technical requirements of the brief Completed |
Evidence:
|
Adjust the design as necessary after discussions with relevant personnel Completed |
Evidence:
|
Clarify any legislative or ownership issues to comply with production and/or organisational requirements Completed |
Evidence:
|
Confirm acceptance of the design including deliverables, milestones and timeline Completed |
Evidence:
|