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 ICAPRG418A, 'Apply intermediate 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 intermediate 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
1. Code using user defined data structures | 1.1 Design, define and use data structures that are an aggregate of other data types 1.2 Code using an array of user-defined data types 1.3 Use the facilities in the language to create, manipulate and destroy dynamic variables, such as arrays |
2. Code using standard algorithms | 2.1 When coding, use a modular programming approach, including pass-by-reference parameter passing 2.2 Write code to create and manipulate a 2-D array 2.3 Create and maintain a sorted array and use language-provided facilities for sorting an array of ordered elements 2.4 Code a simple binary search technique for use with an array of sorted data 2.5 Code binary file-handling solutions using random access algorithms |
3. Debug code | 3.1 Use stand-alone debugging tools or tools provided by integrated development environment to debug code 3.2 Use a debugger to trace code execution and examine variable contents to detect and correct errors |
4. Document activities | 4.1 Follow organisational guidelines for developing maintainable code and adhere to the provided coding standard when documenting activities 4.2 Apply internal documentation suitable for use by peers to all code created 4.3 Use documentation tools available in the target language when documenting activities |
5. Test code | 5.1 Design and document tests 5.2 Undertake limited testing of produced code to ensure compliance with program specification 5.3 Capture and record test results |
6. Create an application | 6.1 Build an application in response to a user requirement 6.2 Access multiple source code files 6.3 Employ integrated development environment project maintenance facilities or make files to automate program building 6.4 Develop a program specification solution when provided with a basic design document 6.5 Design the algorithm, and document, construct and test applications in response to a problem description using the language 6.6 Document the completed application |