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 ICAGAM419A, 'Build a database to support a computer game'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Build a database to support a computer game' 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. Verify database model | 1.1 Verify that game architecture and system implementation requirements have been addressed by the proposed database architecture 1.2 Correlate data model entities and their attributes with the game artefacts and game design requirements 1.3 Verify that entity relationships defined in the data model implement game design and game-play rules 1.4 Verify estimates of amounts of data storage required and data types defined by the data model 1.5 Document design inconsistencies 1.6 Review database model and address and correct inconsistencies 1.7 Define database test data |
2. Create physical database design | 2.1 Implement conceptual data model design as a physical database design 2.2 Determine default database file size according to the data model storage estimates 2.3 Determine game data input and output workload estimates 2.4 Determine reliability and performance requirements 2.5 Define minimum hardware requirements to support input and output workload and reliability or performance requirements 2.6 Configure the database management system to use minimum hardware requirements 2.7 Refine and confirm database test data |
3. Implement physical database prototype | 3.1 Write structured query language (SQL) scripts to create physical database files according to design requirements 3.2 Write SQL scripts to create database tables 3.3 Implement primary key constraints 3.4 Implement foreign key constraints 3.5 Define and script stored procedures for selecting, inserting, updating and deleting data 3.6 Define and script Insert statements for test data 3.7 Execute SQL scripts and database, including test data |
4. Test the database and document results | 4.1 Document entity integrity tests and results 4.2 Document referential integrity tests and results 4.3 Document input and output performance tests and results 4.4 Document stored procedures tests and results |
5. Review, evaluate and correct database performance | 5.1 Review test result deficiencies 5.2 Define, evaluate and test deficiencies and ensure corrective measures are implemented 5.3 Implement corrections to database |