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?
Determine database requirements
|
|
Meet with client and conduct a user needs analysis to determine database functionality Completed |
Evidence:
|
Analyse results of user needs analysis to identify technicalrequirements Completed |
Evidence:
|
Develop a conceptual model of the database Completed |
Evidence:
|
Submit conceptual model to client for review Completed |
Evidence:
|
Evaluate client feedback and make changes as required Completed |
Evidence:
|
Develop logical data model
|
|
Identify attributes and determine data types Completed |
Evidence:
|
Undertake normalisation of attributes Completed |
Evidence:
|
Develop entity relationship diagram to clarify cardinality of relationships Completed |
Evidence:
|
Document attributes, normalised data and entity relationship diagram Completed |
Evidence:
|
Forward documentation to client for confirmation Completed |
Evidence:
|
Design data structures
|
|
Confirm primary and foreign keys for tables Completed |
Evidence:
|
Review client business rules Completed |
Evidence:
|
Identify referential integrity constraints Completed |
Evidence:
|
Establish relevant database management system constraints and incorporate into database design Completed |
Evidence:
|
Develop validation rules for data Completed |
Evidence:
|
Design indexes and develop data dictionary Completed |
Evidence:
|
Document the database design Completed |
Evidence:
|
Design queries, screens and reports
|
|
Design user interface for database, including menus, input screens and outputs Completed |
Evidence:
|
Design queries based on requirements Completed |
Evidence:
|
Design output reports based on requirements Completed |
Evidence:
|
Compare physical design with conceptual model/user needs analysis Completed |
Evidence:
|
Incorporate changes as required Completed |
Evidence:
|
Design access and security systems
|
|
Review business security plan as basis for commencing access and security design Completed |
Evidence:
|
Design password and access system for database Completed |
Evidence:
|
Identify multiple-user requirements Completed |
Evidence:
|
Develop client access profiles using client business model Completed |
Evidence:
|
Confirm database design
|
|
Identify database back-up and recovery requirements Completed |
Evidence:
|
Develop and document the database back-up and recovery procedures Completed |
Evidence:
|
Submit database and documentation to client for final approval Completed |
Evidence:
|