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 ICTDBS502, 'Design a database'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Design a database' 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 |
Elements describe the essential outcomes. | Performance criteria describe the performance needed to demonstrate achievement of the element. |
1. Determine database requirements | 1.1 Meet with the client, and conduct a user-needs analysis, to determine database functionality 1.2 Analyse the results of a user-needs analysis to identify technical requirements 1.3 Develop a conceptual model of the database 1.4 Submit the conceptual model to the client for review 1.5 Evaluate client feedback and make changes as required |
2. Develop a logical data model | 2.1 Identify the attributes and determine the data types 2.2 Undertake the normalisation of attributes 2.3 Develop an entity-relationship (ER) diagram in order to clarify the cardinality of relationships 2.4 Document attributes, normalised data, and the ER diagram 2.5 Forward documentation to the client for confirmation |
3. Design the data structures | 3.1 Confirm primary and foreign keys for tables 3.2 Review client business rules 3.3 Identify the referential integrity constraints 3.4 Establish database management system constraints and incorporate into database design 3.5 Develop the validation rules for data 3.6 Design indexes and develop the data dictionary 3.7 Document the database design |
4. Design queries, screens and reports | 4.1 Design the user interface for database, including menus, input screens and outputs 4.2 Design queries, based on requirements 4.3 Design output reports, based on requirements 4.4 Compare the physical design with the conceptual model, or user-needs analysis 4.5 Incorporate changes as required |
5. Design access and security systems | 5.1 Review the business security plan as a basis for commencing the access and security design 5.2 Design the password and access system for the database 5.3 Identify multiple-user requirements 5.4 Develop client access profiles using the client business model |
6. Confirm the database design | 6.1 Identify the database backup and recovery requirements 6.2 Develop and document the database backup and restore procedures 6.3 Submit the database, and documentation, to the client for final approval |