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 ICTPRG414, 'Apply introductory 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 introductory 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 |
Elements describe the essential outcomes. | Performance criteria describe the performance needed to demonstrate achievement of the element. |
1. Apply basic language syntax and layout | 1.1 Apply basic language syntax rules 1.2 Use language data types, operators and expressions to create clear and concise code 1.3 Use appropriate language syntax for sequence, selection and iteration constructs |
2. Code using data structures | 2.1 Use data structures 2.2 Write code to create and manipulate arrays 2.3 Design, define and use data structures |
3. Code using standard algorithms | 3.1 Create sequential search, binary search, insertion and deletion algorithms to operate on arrays 3.2 Code standard sequential access algorithms and random access algorithms |
4. Debug code | 4.1 Use stand-alone debugging tools or tools provided by integrated development environment (IDE) to debug code 4.2 Use a debugger to trace code execution and examine variable contents to detect and correct errors |
5. Document activities | 5.1 Follow organisational guidelines for developing maintainable code and adhere to provided coding standard when documenting activities 5.2 Apply internal documentation, suitable for use by peers, to all code created and use documentation tools available in target language when documenting activities |
6. Test code | 6.1 Design and document tests 6.2 Capture and record test results |