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 ICAB4169B, 'Use development software and IT tools to build a basic website'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Use development software and IT tools to build a basic website' 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. Select and analyse website structure and development tools | 1.1. Analyse business specification and select appropriate software 1.2. Identify technical needs for the website and select appropriate software tools 1.3. Identify site structure and navigation flow and demonstrate understanding of functionality 1.4. Review design documentation and integrate design work with site structure and navigation, in accordance with webdevelopmentstandards |
2. Begin site construction | 2.1. Take action to ensure user input during website construction 2.2. Validate existing information and basic content when incorporating data on website 2.3. Apply consistent design specifications to all aspects of the website 2.4. Gather feedback from user on web design, content, accessibility and structure, using appropriate feedback mechanism |
3. Complete and validate website construction and content | 3.1. Undertake an evaluation of the website against technical requirements and design specification 3.2. Test each function and process of the website 3.3. Conduct navigation tests and HTML compliance with website standards 3.4. Stress test the website to meet design criteria and user load 3.5. Record testing results to ensure website meets user requirements 3.6. Obtain sign-off/approval of user |