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?
Establish configuration management requirements
|
|
Establish identification standards for naming and version control of system, network, software and documentation to align with organisational needs Completed |
Evidence:
|
Establish tools and procedures for the required level of integration into the programming, system or network environment Completed |
Evidence:
|
Determine responsibilities for configuration management within the project and for ongoing support, including approval of changes Completed |
Evidence:
|
Determine the appropriate points for configuration of particular items Completed |
Evidence:
|
Establish control mechanisms
|
|
Establish methods for identification and recording of change requests in line with organisational guidelines Completed |
Evidence:
|
Establish acceptance criteria, test and acceptance processes and processes for approval of change requests in line with organisational guidelines Completed |
Evidence:
|
Establish security, access and management control criteria and quality benchmarks Completed |
Evidence:
|
Determine necessary audit trails and alerts for variations or non-conformance Completed |
Evidence:
|
Establish monitoring mechanisms
|
|
Establish mechanisms to identify software status throughout the software life cycle, or the status of the system or network during upgrading or reconfiguration Completed |
Evidence:
|
Determine management of records and status reports, including the history of baselines and their links to backups Completed |
Evidence:
|
Define target audiences and determine the level of detail required in the status reports Completed |
Evidence:
|
Integrate configuration management into general project management processes for monitoring and control purposes Completed |
Evidence:
|
Document control and monitoring mechanisms Completed |
Evidence:
|
Manage the release of the product to clients
|
|
Determine physical and functional completeness of items prior to release Completed |
Evidence:
|
Determine requirements for formal control of software products and documentation Completed |
Evidence:
|
Determine policies for retention of baseline and master copies in line with safety, security and legislative requirements and organisational guidelines Completed |
Evidence:
|