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 ICAB5230B, 'Maintain custom software'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Maintain custom software' 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. Determine software fault to be corrected | 1.1. Collect and review software fault details from sources 1.2. Obtain technical data from software traces, memory dumps, error messages and other information to assist in identifying the problem 1.3. Clarify the nature of the problem with appropriateperson where necessary |
2. Identify and isolate fault | 2.1. Review program documentation for specific modules in order to pinpoint problem areas 2.2. Review source code for logic errors 2.3. Read manuals, help files, 'read me files' to determine if there is a known fix 2.4. Undertake additional testing to correctly identify or duplicate fault 2.5. Escalate difficult faults that cannot be identified |
3. Design fix for fault | 3.1. Ensure requirements to fix the fault are understood by client 3.2. Consider alternative options and choose the most effective solution 3.3. Consider the possible impact of the fix on other parts of the system 3.4. Document changes in line with organisational guidelines |
4. Carry out fix to software | 4.1. Identify and obtain access to appropriate software development tools, correct source code and libraries 4.2. Construct appropriate code to correct the fault in accordance with organisational and programming standards 4.3. Compile/regenerate code for changed programs and associated modules 4.4. Correct and resubmit code until error-free 4.5. Document all changes in accordance with organisational and programming standards |
5. Test fix and associated system areas | 5.1. Check logic to ensure that it works with test data, corrects original fault and does not cause problems elsewhere 5.2. Request users to perform acceptance testing and record outcomes |
6. Hand over to systems operations area | 6.1. Update documentation to reflect all changes made 6.2. Confirm acceptance by systems operations and arrange for sign-off in accordance with procedures |