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?
Gather and confirm architecture requirements
|
|
Gather information regarding architectural requirements Completed |
Evidence:
|
Establish and document architectural requirements Completed |
Evidence:
|
Design layered architecture
|
|
Separate the areas of concern into logical layers Completed |
Evidence:
|
Determine the cross-cutting concerns Completed |
Evidence:
|
Define the system into components Completed |
Evidence:
|
Identify the responsibilities of each component Completed |
Evidence:
|
Identify interconnections between components Completed |
Evidence:
|
Plan a strategy to re-use components
|
|
Determine an appropriate strategy for communicating with external systems Completed |
Evidence:
|
Interact with existing legacy components Completed |
Evidence:
|
Design for globalisation and localisation
|
|
Determine culture-specific information Completed |
Evidence:
|
Consider database design features Completed |
Evidence:
|
Select appropriate user interface Completed |
Evidence:
|
Develop software product for worldwide distribution Completed |
Evidence:
|
Develop software product for specific country Completed |
Evidence:
|