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 ICAGAM511A, 'Manage testing of games and interactive media'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Manage testing of games and interactive media' 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. Determine quality requirements statement which will enable product release | 1.1 Review picture of product in market place to determine high-level requirements provided by product, for expected clients, considering all types of requirements 1.2 Define a releasable product in terms of outstanding bugs, to enable a limited release and a complete product release 1.3 Summarise findings into a product release enabling quality requirements statement 1.4 Confirm client and development, agreement on product release enabling quality requirements statement |
2. Define test plan to enable testing of required quality as defined by agreed quality requirements statement | 2.1 Determine expected test cycles, during the software development life cycle, considering what development methodology is in use and what the quality requirements are for product release 2.2 Determine what types of testing will be performed during the test cycles to enable efficiency of processes and confirmation of quality requirements statement 2.3 Determine what testing methods will be used to implement testing types defined for defined test cycles 2.4 Determine testing technique to be used to determine test cases and analyse results 2.5 Perform test cycle until a combination is found that provides an acceptable balance of cost, quality and risk, for upper management and development to agree to 2.6 Selection test-support software to enable efficiency in testing and testing management 2.7 Define implementation details for agreed testing and team responsible for testing management 2.8 Define reporting details for testing throughout product life cycle to enable ongoing management of testing process 2.9 Confirm test plan completeness using available completeness techniques 2.10 Confirm test plan with development and management |
3. Install and configure test plan defined test support software | 3.1 Install and configure bug tracking process and define bug description fields to maximise efficiency and minimise possibilities of bouncing bugs 3.2 Install and configure test case management software 3.3 Install and configure test cycle management and reporting software 3.4 Install and configure automated test tools |
4. Manage testing process to enable defined quality requirements | 4.1 Manage and report on development of test cases 4.2 Manage and report on test cycle status 4.3 Manage and report on outstanding bug status 4.4 Manage and report on status of product testing related to product release enabling quality requirements statement 4.5 Update test plan and schedule to deal with changing development conditions, and ensure management are informed 4.6 Manage bugs to ensure efficient bug handling and resolution 4.7 Manage test environment, including setup, receipt of test builds and clean-up |
5. Finalise testing for release | 5.1 Produce testing results for management review prior to release 5.2 Manage test product freeze for final release and final test run 5.3 Confirm product, release enabling, and quality requirements have been met |