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?
Identify the required game assets in a team environment
|
|
Obtain the project brief and other relevant documents Completed |
Evidence:
|
Identify the game production assets required to meet the creative and production requirements, and technical specifications Completed |
Evidence:
|
Discuss the formats of assets, and issues of asset integration, with the appropriate personnel Completed |
Evidence:
|
Determine the sequence for the development of a beta-version prototype for testing game play Completed |
Evidence:
|
Create a schedule for production and testing Completed |
Evidence:
|
Determine strategies for monitoring production progress against the schedule Completed |
Evidence:
|
Identify the capability of game-engine software and tools and make a selection in a team environment
|
|
Identify and review the range of industry-standard game-engine software and development tools available Completed |
Evidence:
|
Assess the software and tools related to the specified game concept and play requirements Completed |
Evidence:
|
Discuss considerations for the selection of game-engine software with the relevant personnel, to ensure that the selection will meet the specified outcomes Completed |
Evidence:
|
Select the game-engine software and development tools Completed |
Evidence:
|
Create or acquire the required assets for a game in a team environment
|
|
Establish an environment for a project that supports sharing of project assets produced by team members Completed |
Evidence:
|
Review the attributes of the assets required in a game project related to the chosen game engine Completed |
Evidence:
|
Create or acquire the visual assets for a games project Completed |
Evidence:
|
Customise asset attributes to suit the game design, and chosen game engine Completed |
Evidence:
|
Use game-engine software and development tools in a team environment
|
|
Collaborate in the use of tools, and features, of software relevant to the game-production process Completed |
Evidence:
|
Create, modify or access scripts or code to combine assets, and achieve agreed project goals Completed |
Evidence:
|
Create and check game-play elements, according to the creative and technical requirements Completed |
Evidence:
|
Test and run the game prototype as a presentation, to ensure that sequences meet the creative, production and technical requirements Completed |
Evidence:
|
Evaluate the game prototype in a team environment
|
|
Demonstrate the initial prototype to the relevant personnel Completed |
Evidence:
|
Evaluate against criteria, including the achievement of a creative and user-friendly product Completed |
Evidence:
|
Discuss and agree on required changes Completed |
Evidence:
|
Assist, if required, in tests and user trials Completed |
Evidence:
|
Evaluate the feedback from user trials Completed |
Evidence:
|
Confirm the endorsement from relevant personnel to develop the prototype into a complete product Completed |
Evidence:
|
Transform the prototype into final publication
|
|
Make the necessary changes, as indicated by user trials Completed |
Evidence:
|
Integrate all game elements, as required by the specifications Completed |
Evidence:
|
Make final checks to ensure that all sequences conform to the navigation design Completed |
Evidence:
|
Assemble a final publication for distribution Completed |
Evidence:
|