Formats and tools
- Unit Description
- Reconstruct the unit from the xml and display it as an HTML page.
- Assessment Tool
- an assessor resource that builds a framework for writing an assessment tool
- Assessment Template
- generate a spreadsheet for marking this unit in a classroom environment. Put student names in the top row and check them off as they demonstrate competenece for each of the unit's elements and performance criteria.
- Assessment Matrix
- a slightly different format than the assessment template. A spreadsheet with unit names, elements and performance criteria in separate columns. Put assessment names in column headings to track which performance criteria each one covers. Good for ensuring that you've covered every one of the performance criteria with your assessment instrument (all assessement tools together).
- Wiki Markup
- mark up the unit in a wiki markup codes, ready to copy and paste into a wiki page. The output will work in most wikis but is designed to work particularly well as a Wikiversity learning project.
- Evidence Guide
- create an evidence guide for workplace assessment and RPL applicants
- Competency Mapping Template
- Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners. A template for developing assessments for a unit, which will help you to create valid, fair and reliable assessments for the unit, ready to give to trainers and students
- Observation Checklist
- create an observation checklist for workplace assessment and RPL applicants. This is similar to the evidence guide above, but a little shorter and friendlier on your printer. You will also need to create a seperate Assessor Marking Guide for guidelines on gathering evidence and a list of key points for each activity observed using the unit's range statement, required skills and evidence required (see the unit's html page for details)
- Self Assessment Survey
- A form for students to assess thier current skill levels against each of the unit's performance criteria. Cut and paste into a web document or print and distribute in hard copy.
- Moodle Outcomes
- Create a csv file of the unit's performance criteria to import into a moodle course as outcomes, ready to associate with each of your assignments. Here's a quick 'how to' for importing these into moodle 2.x
- Registered Training Organisations
- Trying to find someone to train or assess you? This link lists all the RTOs that are currently registered to deliver ICTDBS401, 'Identify physical database requirements'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Reference books for 'Identify physical database requirements' on fishpond.com.au. This online store has a huge range of books, pretty reasonable prices, free delivery in Australia *and* they give a small commission to ntisthis.com for every purchase, so go nuts :)
Elements and Performance Criteria
Elements describe the essential outcomes.
Performance criteria describe the performance needed to demonstrate achievement of the element.
1. Identify the database scope
1.1 Review the requirements of the user, and the current systemâ€™s architecture
1.2 Determine database size from the requirements and the technical specifications
1.3 Document the database design, and scope, of the project
1.4 Evaluate several database management systems against the requirements, and make the appropriate selection
2. Identify the database requirements
2.1 Review the technical specifications for the database
2.2 Identify the database tables and relationships
2.3 Identify the database data dictionary, table attributes and keys
2.4 Determine the database reports based on the acceptance criteria and requirements
3.Identify the security requirements
3.1 Review the system security plan
3.2 Clarify and confirm that the database management system, and user security, aligns with the system security plan
3.3 Identify, evaluate and record database performance, recovery and audit trail needs
4. Seek client feedback and approval
4.1 Present database scope, technical requirements and security documentation to the user for feedback
4.2 Review user feedback and adjust the database documentation, as required
4.3 Present database documentation to the user for final approval