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 ICTNWK409, 'Create scripts for networking'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Reference books for 'Create scripts for networking' 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
Elements describe the essential outcomes.
Performance criteria describe the performance needed to demonstrate achievement of the element.
1. Develop algorithms to represent solutions to a given problem
1.1 Consult with client and key stakeholders to identify the problem and associated script requirements
1.2 Employ abbreviated software development cycle to script creation
1.3 Develop an algorithm to solve the problem and meet client requirements
1.4 Develop an algorithm which takes account of expected possible situations
1.5 Develop an algorithm which is guaranteed to end
1.6 Use structure, sequence, selection and iteration
2. Create code
2.1 Select appropriate scripting language
2.2 Demonstrate understanding and application of basic language syntax rules and best practices
2.3 Select and use language data types, operators and expressions to create clear and concise code
2.4 Use techniques of selection, iteration and sequence to control script execution flow
2.5 Use techniques for sequential file input and output to retrieve and store information
2.6 Obtain and use user input to affect the operation of the script
2.7 Apply internal document principles to created code
2.8 Follow organisational guidelines for developing maintainable code when creating scripts
2.9 Adhere to coding standards when creating scripts
3. Use operating system tools
3.1 Use searching and sorting tools to select information from the logging output of operating system (OS)
3.2 Implement controls to ensure that where significant events occur, script creates and maintains a log of operations via operating system logging mechanism
3.3 Register and run scripts with OS scheduling facility
4. Test and debug code
4.1 Engineer, document and conduct simple tests to confirm code meets design specification
4.2 Identify areas that are not covered or are covered incorrectly in the script
4.3 Take action to ensure that code complies with security policy
4.4 Take action to ensure that code operates with proper permissions
4.5 Use script debugging techniques suitable for use with scripting language to detect and resolve errors of syntactical, logical and design origin
5. Document script
5.1 Create technical-level documentation
5.2 Create user-level documentation