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 ICAA5146B, 'Develop website information architecture'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Develop website information architecture' 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. Identify content needs | 1.1. Identify strategic intent of website from business requirements and client expectations 1.2. Develop information requirements based on the website intent, intended audiences, types of client interactions, and long- and short-term goals for the site 1.3. Identify required information and group into business schemes related to the business structure 1.4. Determine content requirements for each process |
2. Plan content structure | 2.1. Cluster and document information in related topics 2.2. Develop a hierarchy of information and check data to confirm sequence of hierarchy 2.3. Ensure that labels are clear, consistent, coherent and relatively intuitive for client to access |
3. Develop navigation system | 3.1. Build navigation system for overall website based on business requirements 3.2. Ensure ease of navigation on the site and provide different ways of searching, while providing feedback to client. 3.3. Ensure the navigation system gives users the flexibility to find the information and products they want 3.4. Develop a consistent and logical labelling system, taking into account client demographics |
4. Test and sign off | 4.1. Construct prototype of information architecture design 4.2. Arrange for a subset of the client to test the prototype for usability to determine if architecture meets client expectations 4.3. Ensure site content will format correctly in the business and client technical environment 4.4. Adjust architecture based on client feedback 4.5. Sign off prototype to confirm current and future business requirements are met |