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 ICAB5227B, 'Apply advanced programming skills in another language'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Apply advanced programming skills in another language' 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. Code using advanced data structures | 1.1. Design, implement and use dynamic data structures, including double linked lists and binary trees for coding |
2. Code using advanced algorithms | 2.1. Code using hashing techniques 2.2. Consider and record the advantages and disadvantages of at least three sorting algorithms 2.3. Code at least one sorting algorithm 2.4. Code advanced searching techniques for use with complex data structures |
3. Write simple multi-process application | 3.1. Demonstrate use of the features of the language that enable inter-process communication through at least one mechanism 3.2. Demonstrate use of features of the language that allow for operating system 'signals' to be captured and responded to |
4. Use third party libraries | 4.1. Use a third-party library in the construction of an application 4.2. Reference third-party documentation 4.3. Use procedural techniques to write an application to work within a GUI environment |
5. Debug code | 5.1. Use an integrated developmentenvironment debugging facilities or a standalone debugger 5.2. Use program debugging techniques to detect and resolve errors of syntactical, logical and design origin |
6. Document activities | 6.1. Demonstrate use of source code version control 6.2. Demonstrate adherence to guidelines for developing maintainable code and to a set of provided codingstandards 6.3. Apply internal documentation suitable for consumption by peers to all code created and utilising documentation tools available in the target language |
7. Test code | 7.1. Design and document tests to be undertaken 7.2. Undertake limited testing of produced code to ensure program specification is complied with 7.3. Capture test results |
8. Create an application | 8.1. Develop a solution from a program specification design document 8.2. Design the algorithm, construct and test applications in response to a problem description and language |