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 ICTICT449, 'Use version control systems in development environments'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Use version control systems in development environments' 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. Prepare to use version control systems (VCS) | 1.1 Research and choose version control system (VCS) according to organisational requirements 1.2 Identify required subversion and VCS pre-installation factors 1.3 Determine and communicate installation disruption to required personnel according to organisational policies and procedures 1.4 Install VCS and create personal account and push changes from branch according to VCS service provider and organisational requirements 1.5 Configure tools and user interface of VCS according to organisational requirements |
2. Build files in VCS | 2.1 Create local repository according to service provider procedures 2.2 Create required directory according to service provider procedures and organisational requirements 2.3 Create and access required staging environment structures and branches 2.4 Create and access files in the repository according to service provider procedures |
3. Test VCS | 3.1 Add and commit files to staging environment 3.2 Commit required files to local depository 3.3 Locate track of initial version change and confirm new status according to service provider procedures 3.4 Respond to remote pull requests according to service provider procedures 3.5 Retrieve remote commits and locally merge according to service provider procedures |
4. Finalise use of VCS | 4.1 Document VCS test outcomes according to organisational requirements 4.2 Submit documented outcomes to required personnel 4.3 Respond to feedback on documented outcomes from required personnel 4.4 Obtain final task sign off from required personnel |