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?
Prepare to develop control programs for microcomputer equipped devices.
|
|
OHS processes and procedures for a given work area are identified, obtained and understood. Completed |
Evidence:
|
Established OHS risk control measures and procedures are followed in preparation for the work. Completed |
Evidence:
|
The extent of development work is determined from design brief and in consultation with relevant persons. Completed |
Evidence:
|
Development work is planned to meet scheduled timelines in consultation with others involved on the work site. Completed |
Evidence:
|
Appropriate development tools and software are selected based on specified requirements and performance standards. Completed |
Evidence:
|
Materials and devices/components required for the work are selected on compatibility of specifications with control requirements and project budget constraints. Completed |
Evidence:
|
Strategies are implemented to ensure development work is carried out efficiently. Completed |
Evidence:
|
Develop control programs.
|
|
OHS risk control measures and procedures for carrying out the work are followed. Completed |
Evidence:
|
Knowledge of computer-equipped devices and systems and compliance standards are applied to the design. Completed |
Evidence:
|
Alternative arrangements for the development are considered based on the requirements outlined in the design brief. Completed |
Evidence:
|
Safety, functional and budget considerations are incorporated in the design. Completed |
Evidence:
|
Prototype devices and circuits are constructed and tested for compliance with the design brief and regulatory requirements. Completed |
Evidence:
|
Knowledge of programming language code, functions and features in current use are applied to developing control programs. Completed |
Evidence:
|
Prototype malfunctions are rectified and re-tested to ensure effective operation of design. Completed |
Evidence:
|
Program development is documented for submission to appropriate person(s) for approval Completed |
Evidence:
|
Approaches to issues/problems are analysed to provide most effective solutions. Completed |
Evidence:
|
Quality of work is monitored against personal performance agreement and/or established organisational or professional standards. Completed |
Evidence:
|
Test, evaluate, implement and document control programs.
|
|
Testing and procedures are developed to evaluate control program. Completed |
Evidence:
|
Problems and bugs in program are identified and rectified to ensure specifications are met. Completed |
Evidence:
|
Intermediate and final work reports are written in accordance with professional standards and presented to appropriate person(s). Completed |
Evidence:
|