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 ICTPRG401, 'Maintain open-source code programs'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Maintain open-source code programs' 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. Investigate the open-source paradigm | 1.1 Examine the open-source paradigm and analyse the differences with traditional software development models 1.2 Investigate the types of online resources 1.3 Investigate the types of project documentation 1.4 Recognise the role of an online community, and international collaboration 1.5 Examine motivational factors for contributors to open-source code 1.6 Analyse the open-source licensing models |
2. Familiarise with target project | 2.1 Examine the online resources associated with the target project 2.2 Download pre-built executable binaries to install, and run, the project 2.3 Download and analyse the supporting documentation |
3. Prepare for maintenance activities | 3.1 Select, and register with, a relevant online community open-source group 3.2 Download nightly snapshots of the latest source code and the supporting documentation 3.3 Build and execute a snapshot, where appropriate |
4. Maintain the code | 4.1 Access the project bug database, and select the bugs to be resolved or the features to be added 4.2 Make changes to the local copy of the code, in order to resolve selected bugs 4.3 Test the resulting code to ensure that it performs appropriately 4.4 Prepare the code patch for submission 4.5 Submit a code patch to the project 4.6 Use the appropriate software-development tools and environment |
5. Maintain the documentation | 5.1 Access the project documentation 5.2 Prepare and contribute new information, or updates, to the existing documentation 5.3 Prepare and submit documented changes to the project |
6. Participate in community | 6.1 Exchange messages with other project members and actively participate in community activities 6.2 Take action to ensure that exchanges are socially acceptable 6.3 Submit the code and documentation code patches for inclusion 6.4 Access online project resources frequently, to keep up-to-date with the project and with community developments 6.5 Take action to ensure that community-participation standards are observed and maintained |