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 ICTPRG501, 'Apply advanced object-oriented language skills'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Reference books for 'Apply advanced object-oriented language skills' 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
Elements describe the essential outcomes.
Performance criteria describe the performance needed to demonstrate achievement of the element.
1. Develop client-server application
1.1 Build and test object-oriented applications
1.2 Make use of features of language that enable inter-process communication through at least one mechanism
1.3 Make use of features of language that enable remote procedure calls (RPCs) using class based on multiple inheritances
1.4 Build programs using classes based on nested classes
2. Develop graphical user interface (GUI)
2.1 Code to implement drag and drop
2.2 Develop GUI help files
2.3 Code using 2-D graphics
3. Build applications
3.1 Code within existing architectural framework
3.2 Ensure code follows standards for object-oriented language
3.3 Develop application that includes data transfer between client and server
3.4 Review concept of design patterns used by architectural framework
4. Debug code
4.1 Use stand-alone debugging tools or tools provided by integrated development environment to examine running code
4.2 Detect logical and coding errors using debugger
4.3 Detect and correct errors by tracing code and examining variable content
5. Test application
5.1 Design and document tests to be performed
5.2 Undertake limited testing of produced code to ensure it complies with program specification
5.3 Document test results
6. Document system
6.1 Demonstrate adherence to guidelines for developing maintainable code and company or institutional coding standards
6.2 Create code using supplied design documents
6.3 Create and maintain program documentation
6.4 Ensure that user documentation in form of online help is built into applications