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 ICAT5083B, 'Develop and conduct client acceptance test'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Reference books for 'Develop and conduct client acceptance test' 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. Identify acceptance criteria and develop test plan
1.1. Review system requirements documentation and project plans to identify mandatory system objectives and optional criteria/conditions for acceptance of system
1.2. Develop test plan based on system requirements
1.3. Review and validate the test plan based on mandatory criteria/conditions, and system objectives and requirements
1.4. Clearly communicate the test plan to the client and prepare the client for the acceptance test
1.5. Notify appropriate person of the scheduled acceptance test
2. Perform functional testing on software modules
2.1. Prepare the test environment for client use
2.2. Perform the testing according to the test plan and documentation
2.3. Execute each test cycle
2.4. Document errors, difficulties or communicated problems
3. Validate test results against expected results
3.1. Record and investigate discrepancies and corrections according to project procedures and timeframe
3.2. Brief the client on outcomes to ensure the client understands test results
3.3. Monitor system performance as required
3.4. Reschedule required code changes or modifications
4. Obtain signoff and acceptance
4.1. Confirm with the client the results of the test
4.2. Identify and document client concerns over system operation, identify possible solutions, and if necessary notify appropriate development staff
4.3. Obtain client acceptance and sign-off by the client of that acceptance
4.4. Seek and formalise the agreement of involved parties regarding the rescheduling of further required maintenance