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?
Plan process
|
|
Produce a plan to analyse the specified requirements and design and build valid extensible mark-up language documentation allowing for iterative development Completed |
Evidence:
|
Analyse specified requirements
|
|
Determine and document the purpose, expectations and functionality of the XML document Completed |
Evidence:
|
Determine the hardware and software and tools needed to design the document Completed |
Evidence:
|
Determine the requirements for the document Completed |
Evidence:
|
Determine appropriate design methodologies, such as utilising software engineering life-cycle Completed |
Evidence:
|
Design and develop document
|
|
Decide on document type definition (DTD), if required Completed |
Evidence:
|
Define the required entities, elements and their attributes Completed |
Evidence:
|
Produce the document, declaring the DTD, the required entities, elements and their attributes, including associated graphics or sounds, following appropriate standards Completed |
Evidence:
|
Test document
|
|
Test document off-line against specifications and confirm the document's validity Completed |
Evidence:
|
Test, where appropriate, the document on-line against specifications and with a representative audience Completed |
Evidence:
|