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 ICTSAS402, 'Implement configuration management strategies'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Implement configuration management strategies' 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. Identify and clarify configuration management requirements | 1.1 Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders 1.2 Identify software configuration tools and procedures for the required level of integration into the programming environment 1.3 Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes 1.4 Take action to ensure that stakeholders are aware of their roles 1.5 Identify point at which items are subjected to configuration control with stakeholders |
2. Employ appropriate control mechanisms | 2.1 Identify and document method for identification and recording of change requests in line with organisational requirements, and ensure this is maintained during development process 2.2 Take action to ensure evaluation criteria and process for approval of change requests are employed according to organisational requirements 2.3 Take action to ensure other management, security and access control criteria are employed according to organisational requirements 2.4 Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development |
3. Implement monitoring mechanisms | 3.1 Implement controls to ensure mechanisms to identify software status throughout the software development life cycle are continuously maintained 3.2 Document development and maintenance of records and status reports required to show the history of baselines and their links to backups 3.3 Take action to ensure level of detail required in status reports, and identification of target audiences, meet the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements 3.4 Integrate configuration management into general project management processes for monitoring and control purposes and document |
4. Manage release of product | 4.1 Take action to ensure physical and functional completeness of items for release to all stakeholders 4.2 Identify and implement requirements for formal control of software products 4.3 Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines |