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?
Confirm component requirements within game context
|
|
Identify definition and purpose of 3-D components with examples Completed |
Evidence:
|
Identify context of component design within game design document Completed |
Evidence:
|
Create list of required components Completed |
Evidence:
|
Identify component integration methods within game architecture
|
|
Discuss component format, file extensions and the ramifications of choice Completed |
Evidence:
|
Establish methods of component loading and usage Completed |
Evidence:
|
Establish content creation pipeline
|
|
Finalise required component list Completed |
Evidence:
|
Discuss hardware and software required for the creation of 3-D components and assets Completed |
Evidence:
|
Discuss methods of file archiving and naming of components and assets Completed |
Evidence:
|
Establish deadlines for component creation Completed |
Evidence:
|
Integrate components for testing and analysis
|
|
Identify evaluation methods for quality assurance Completed |
Evidence:
|
Ensure that produced components meet the established quality requirements Completed |
Evidence:
|
Make changes to components as required by testing and evaluation Completed |
Evidence:
|
Submit finalised assets with archiving format outlined in assignment brief Completed |
Evidence:
|