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?
Develop algorithms to represent solutions to a given problem
|
|
Consult with client and key stakeholders to identify the problem and associated script requirements Completed |
Evidence:
|
Employ abbreviated software development cycle to script creation Completed |
Evidence:
|
Develop an algorithm to solve the problem and meet client requirements Completed |
Evidence:
|
Develop an algorithm which takes account of expected possible situations Completed |
Evidence:
|
Develop an algorithm which is guaranteed to end Completed |
Evidence:
|
Use structure, sequence, selection and iteration Completed |
Evidence:
|
Create code
|
|
Select appropriate scripting language Completed |
Evidence:
|
Demonstrate understanding and application of basic language syntax rules and best practices Completed |
Evidence:
|
Select and use language data types, operators and expressions to create clear and concise code Completed |
Evidence:
|
Use techniques of selection, iteration and sequence to control script execution flow Completed |
Evidence:
|
Use techniques for sequential file input and output to retrieve and store information Completed |
Evidence:
|
Obtain and use user input to affect the operation of the script Completed |
Evidence:
|
Apply internal document principles to created code Completed |
Evidence:
|
Follow organisational guidelines for developing maintainable code when creating scripts Completed |
Evidence:
|
Adhere to coding standards when creating scripts Completed |
Evidence:
|
Use operating system tools
|
|
Use searching and sorting tools to select information from the logging output of operating system (OS) Completed |
Evidence:
|
Implement controls to ensure that where significant events occur, script creates and maintains a log of operations via operating system logging mechanism Completed |
Evidence:
|
Register and run scripts with OS scheduling facility Completed |
Evidence:
|
Test and debug code
|
|
Engineer, document and conduct simple tests to confirm code meets design specification Completed |
Evidence:
|
Identify areas that are not covered or are covered incorrectly in the script Completed |
Evidence:
|
Take action to ensure that code complies with security policy Completed |
Evidence:
|
Take action to ensure that code operates with proper permissions Completed |
Evidence:
|
Use script debugging techniques suitable for use with scripting language to detect and resolve errors of syntactical, logical and design origin Completed |
Evidence:
|
Document script
|
|
Create technical-level documentation Completed |
Evidence:
|
Create user-level documentation Completed |
Evidence:
|