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 record and system requirements
|
|
Comprehensive specifications are prepared based on requirements of potential users Completed |
Evidence:
|
Conflicting requirements are identified and solutions are negotiated prior to and during development process Completed |
Evidence:
|
Objectives are defined and specifications documented to establish the expected inputs, outputs and means of delivery Completed |
Evidence:
|
System and record requirements are prioritised according to importance and urgency of user needs Completed |
Evidence:
|
Security requirements to maintain system integrity are identified and incorporated into the system design Completed |
Evidence:
|
Features of existing system (if any) and records are reviewed to establish their suitability and usability Completed |
Evidence:
|
Recording processes are established according to accepted practice and in accordance with legislation and codes of practice Completed |
Evidence:
|
Evaluate alternative systems
|
|
Features of various systems are compared and measured against user requirements to enable identification of alternative systems and solutions Completed |
Evidence:
|
Cost-benefit analysis on alternative systems and solutions is carried out and subsequent recommendations are documented Completed |
Evidence:
|
Acceptance test system
|
|
System is tested in an operational environment to ensure compliance with user requirements, system specifications and with relevant legislation or industry codes of practice Completed |
Evidence:
|
Formal confirmation from all users is obtained on acceptability of new system/system changes against all criteria and system specifications Completed |
Evidence:
|
Prepare system documentation
|
|
System documentation is prepared thoroughly and accurately using clear and simple language and in a clear format to enable system implementation and training Completed |
Evidence:
|
Users are consulted to ensure clarity, accuracy, thoroughness and usability of system documentation Completed |
Evidence:
|
System documentation is made easily accessible and is constantly reviewed and updated to ensure currency and accuracy Completed |
Evidence:
|
Implement reporting systems and records
|
|
Implementation is carried out in accordance with specified guidelines and timelines Completed |
Evidence:
|
Contingency plans are established to deal with potential delays or problems Completed |
Evidence:
|
Effective training schedules and programs are established to support implementation Completed |
Evidence:
|
All data is transferred from existing to new/modified system and records without error or loss Completed |
Evidence:
|
Systems and records are updated regularly to identify ongoing benefits and threats to the organisation Completed |
Evidence:
|
Files are maintained within organisational and statutory requirements and discrepancies identified and remedied Completed |
Evidence:
|
Integrity of systems and records complies with organisational and statutory requirements Completed |
Evidence:
|
Transactions are monitored to identify taxation and other liabilities Completed |
Evidence:
|
Monitor reporting systems
|
|
Transactions are analysed and accounted for completely and are correctly related to accounting period Completed |
Evidence:
|
Processes for recording and classifying transactions are communicated and promoted to support internal verification of records Completed |
Evidence:
|
Sources of input data and documentation are standardised in structured formats to minimise errors Completed |
Evidence:
|
Back-ups are maintained in accessible location to safeguard data in accordance with organisational and audit requirements Completed |
Evidence:
|
Review reporting procedures
|
|
Sources of input data and documentation records are systematically checked for accuracy and reliability Completed |
Evidence:
|
Reporting requirements are established and analysed regularly to identify variations and compliance with established processes for recording and classifying transactions Completed |
Evidence:
|
Written reports, explanatory notes and financial results are maintained to support source documentation Completed |
Evidence:
|