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?
Apply basic language syntax and layout
|
|
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 the appropriate language syntax for sequence, selection and iteration constructs Completed |
Evidence:
|
Use a modular programming approach within member or function logic Completed |
Evidence:
|
Apply arrays, including arrays of objects to introductory programming tasks Completed |
Evidence:
|
Use standard-array processing algorithms Completed |
Evidence:
|
Use the facilities of the language to read and write data from and to text files and record outcomes Completed |
Evidence:
|
Apply basic object-oriented principles in the target language
|
|
Implement a class that contains primitive member or instance variables Completed |
Evidence:
|
Implement a class that contains multiple options for object construction Completed |
Evidence:
|
Implement a class that uses user-defined aggregation (object instance or member variables) Completed |
Evidence:
|
Use the facilities provided in the language to implement inheritance to at least two levels of depth Completed |
Evidence:
|
Use polymorphism at a simple level through inheritance to enable easy extension of code Completed |
Evidence:
|
Debug code
|
|
Use an integrated development environment, in particular the language debugging facilities, to debug code Completed |
Evidence:
|
Interpret compiler or interpreter messages to resolve syntax errors and use debugging techniques to resolve logic errors Completed |
Evidence:
|
Document activities
|
|
Follow organisational guidelines for developing maintainable code and adhere to the provided coding standards when documenting activities Completed |
Evidence:
|
Apply internal documentation to all code created and use documentation tools available in the target language when documenting activities Completed |
Evidence:
|
Test code
|
|
Create and conduct simple tests to confirm code meets design specification Completed |
Evidence:
|
Document the tests performed and results achieved Completed |
Evidence:
|
Create an application
|
|
Develop a solution when provided with a basic object-oriented design document Completed |
Evidence:
|
Refer to appropriate documentation for the language Completed |
Evidence:
|