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 ICTTEN7226A, 'Manage development and application of testing artefacts'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Manage development and application of testing artefacts' 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 |
1. Plan the test effort and develop test strategy for software testing | 1.1. Analyse the functionalities of an application software from the system design document and create a test strategy for a new telecommunications product line 1.2. Produce the steps in developing the test strategy and the attributes of each step according to enterprise policy 1.3. Produce a test strategy to evaluate the suitability of the application software for integration into the telecommunications network 1.4. Assess a range of tests required to evaluate the performance and functionality of the application software and determine the tests required to suit the test regime 1.5. Evaluate features of testing tool and debuggers and select an appropriate tool to test the software application and detect faults 1.6. Produce a test plan based on the requirements of the project specifications and identify testing artefacts required for model based software testing |
2. Plan the development of testing artefacts | 2.1. Develop software testing strategies for uncovering evidence of defects in software systems as part of the quality assurance process 2.2. Produce a test dependency model of the relationship between the test regime and the test levels in software testing for referencing and validation 2.3. Analyse the software testing requirements to determine the domain testing and application testing artefacts requirements to validate the software product |
3. Develop and manage testing artefacts | 3.1. Create reusable domain artefacts to detect early defects in domain testing 3.2. Modify domain test artefacts by binding the variability to create application test artefacts to detect defects in product line applications 3.3. Produce test reporting associated with phases of a test cycle within test plan 3.4. Analyse test reports and evaluate the impact of test plan with the testing artefacts on the testing environment 3.5. Manage the progress of test plan to minimise the risks associated with testing and ensure test complies with test requirements 3.6. Report detected defects to product evaluation personnel and prepare a strategy manage the defects 3.7. Analyse the testing metrics produced by the test tool to manage the tracking of defects and use metrics to plan process improvements 3.8. Produce an evaluation report from the traceability matrix to manage the defects or failures from the test plan |