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 ICAICT411A, 'Select and employ software and hardware testing tools'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Select and employ software and hardware testing tools' 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
1. Establish process operational requirements | 1.1 Identify process requirements ensuring they are accurate, complete, prioritised, and have functionality, and reference appropriate method or media types 1.2 Identify conflicting or overlapping requirements 1.3 Document and validate functional requirements of the client 1.4 Identify and validate available resources and budget |
2. Select hardware and software for processing function | 2.1 Identify and evaluate relevant hardware and software tools with reference to functional requirements 2.2 Identify and analyse relevant products and equipment interdependencies with reference to functional requirements and system architecture 2.3 Identify and document appropriate tools, including their limitations for the required use and industry standards 2.4 Select and acquire tools according to purchasing policies |
3. Configure and test hardware and software | 3.1 Install and configure appropriate hardware and software tools according to vendor guidelines with reference to system architecture and client functionality requirements 3.2 Configure system architecture for optimal usage 3.3 Prepare, schedule and execute tests and record outcomes 3.4 Track errors, and interpret and correct them 3.5 Make changes to the tested hardware or software based on test results 3.6 Document the hardware and software configuration according to requirements |
4. Use and validate software and hardware | 4.1 Provide appropriate training of client with reference to guides, instructions and vendor materials 4.2 Use hardware and software according to vendor guidelines 4.3 Validate hardware and software performance with reference to client functional requirements |