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?
Code using user defined data structures
|
|
Design, define and use data structures that are an aggregate of other data types Completed |
Evidence:
|
Code using an array of user-defined datatypes Completed |
Evidence:
|
Use the facilities in the language to create, manipulate and destroy dynamic variables but limited to simple usage, such as an array of dynamic variables Completed |
Evidence:
|
Code using standard algorithms
|
|
Demonstrate use of a modular programming approach, including pass-by-reference parameter passing Completed |
Evidence:
|
Write code to create and manipulate a two-dimensional array Completed |
Evidence:
|
Create and maintain a sorted array and use language-provided facilities for sorting an array of ordered elements Completed |
Evidence:
|
Code a simple binary search technique for use with an array of sorted data Completed |
Evidence:
|
Code binary file handling solutions using random access algorithms Completed |
Evidence:
|
Debug code
|
|
Use standalone debugging tools or tools provided by integrated development environment to debug code Completed |
Evidence:
|
Use a debugger to trace code execution and examine variable contents to detect and correct errors Completed |
Evidence:
|
Document activities
|
|
Follow organisational guidelines for developing maintainable code and adhere to the provided codingstandard when documenting activities Completed |
Evidence:
|
Apply internal documentation suitable for use by peers to all code created and utilise documentation tools available in the target language when documenting activities Completed |
Evidence:
|
Testing
|
|
Design and document tests Completed |
Evidence:
|
Undertake limited testing of produced code to ensure compliance with program specification Completed |
Evidence:
|
Capture and record test results Completed |
Evidence:
|
Create an application
|
|
Build an application that requires access to multiple source code files Completed |
Evidence:
|
Employ integrated development environment project maintenance facilities or make files to automate program building Completed |
Evidence:
|
Develop a program specification solution when provided with a basic design document Completed |
Evidence:
|
Design the algorithm, and document, construct and test applications in response to a problem description using the language Completed |
Evidence:
|