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?
Create scripts
|
|
Employ abbreviated software development cycle to script creation Completed |
Evidence:
|
Select appropriate scripting language Completed |
Evidence:
|
Apply internal document principles to all 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:
|
Execute example scripts and record outcomes Completed |
Evidence:
|
Create code
|
|
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:
|
Use operating system tools
|
|
Use searching and sorting tools to select information from the logging output of operating system 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 operating system scheduling facility Completed |
Evidence:
|
Debug code
|
|
Use script debugging techniques suitable for use with scripting language to detect and resolve errors of syntactical, logical and design origin Completed |
Evidence:
|
Test code
|
|
Engineer, document and conduct simple tests to confirm code meets design specification 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:
|
Create small utilities
|
|
Design, document, construct and test a small single purpose operating system utility application in response to a problem description Completed |
Evidence:
|
Validate and record script results Completed |
Evidence:
|