Maintain open-source code programs

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 ICAPRG401A, '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

1. Investigate open-source paradigm

1.1 Examine the open-source paradigm and demonstrate an understanding of the differences from the traditional software development models

1.2 Investigate and demonstrate understanding of the types of online resources

1.3 Investigate and demonstrate understanding of the types of project documentation

1.4 Recognise and demonstrate understanding of the role of an online community and international collaboration

1.5 Examine and demonstrate understanding of motivational factors for contributors to open-source code

1.6 Analyse and demonstrate understanding of open-source licensing models

2. Familiarise with target project

2.1 Examine online resources associated with the target project

2.2 Download pre-built executable binaries to install and run project

2.3 Download, read and demonstrate understanding of 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 latest source code and supporting documentation

3.3 Build and execute snapshot where appropriate

4. Maintain code

4.1 Access the project bug database and select bugs to be resolved or features to be added

4.2 Make changes to local copy of code to resolve selected bugs

4.3 Test resulting code to ensure it performs appropriately

4.4 Prepare code patch for submission

4.5 Submit code patch to project

4.6 Use appropriate software-development tools and environment

5. Maintain documentation

5.1 Access project documentation

5.2 Prepare and contribute new information or updates to existing documentation

5.3 Prepare and submit documentation changes to 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 exchanges are socially acceptable

6.3 Submit code and documentation code patches for inclusion

6.4 Access online project resources frequently to keep up-to-date with project and community developments

6.5 Take action to ensure community-participation standards are observed and maintained