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 AURAKA2001, 'Use information technology systems'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Use information technology systems' 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
ELEMENT | PERFORMANCE CRITERIA |
1. Use enterprise information technology systems | 1.1. Knowledge of enterprise information technology systems is accurately demonstrated and conveyed to other staff members 1.2. Hardware is accurately identified and operated according to manufacturer/component supplier instructions and enterprise procedures 1.3. Software, including databases, menus and electronic data interchange (EDI), is accurately identified and used according to manufacturer/component supplier instructions and enterprise procedures 1.4. Application and uses of available software is accurately identified and used according to enterprise procedures 1.5. Data is transmitted according to EDI procedures 1.6. Keyboard skills are used accurately to enter information according to enterprise policies 1.7. Back-up procedures are regularly performed according to enterprise procedures |
2. Edit/update information | 2.1. Information to be edited/updated is correctly identified according to enterprise procedures 2.2. Information on system is accurately edited/updated according to enterprise procedures |
3. Solve problems | 3.1. Equipment/hardware/software faults are identified and rectified where possible or expert assistance sought without delay 3.2. Maintenance programs for hardware and software systems are monitored and implemented according to manufacturer/component supplier specifications and enterprise procedures 3.3. Routine problems are handled using appropriate problem-solving techniques and referred to appropriate persons 3.4. Assistance is positively and actively provided to staff as problems arise |