Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

  1. Verify database model
  2. Create physical database design
  3. Implement physical database prototype
  4. Test the database and document results
  5. Review, evaluate and correct database performance

Required Skills

Required skills

analytical skills to

analyse and assess quantitative requirements for data storage and data throughput

analyse game architecture and game system implementation requirements in the context of the proposed database architecture

assess how well the implementation of the data model maps to the game artefacts the gameplay rules and the game design requirements

communication skills to

identify and discuss gameplay rules with game designers

define and describe data throughput requirements and discuss these with game designers

negotiate with project managers to determine database implementation resource requirements project timeframes and deliverables

propose data structures to implement gameplay functionality and system requirements

initiative and enterprise skills to

assess proposed database architectures within the context of existing enterprise technologies infrastructure and industry standards

recommend solutions to problems or deficiencies associated with the implementation of the database

learning skills to

acquire the skills and knowledge required to overcome current limitations in data throughput and query execution times

stay at the cutting edge of industry developments industry standards and innovative applications of relational database management systems to problems of persisting state in computer games

literacy skills to

document physical design inconsistencies

interpret documentation describing game design requirements and gameplay rules

interpret related game industry standards and associated database management system standards and query language standards

write requirement specifications for physical database implementation

planning and organising skills to

organise resources documentation and infrastructure elements required for the implementation of a relational or objectoriented database management system

plan an effective implementation to a relational or objectoriented database management system

problemsolving skills to

debug query scripts identify script errors and resolve all query scripting issues

identify and implement solutions to problems with the initial conceptual database model

identify problems with physical model and implement solutions

research skills to

enhance knowledge of industry standards and industry trends related to computer game state management techniques and relational or objectoriented database management systems

identify and locate sources of information that provide solutions to technical problems

identify sources of information and documentation required to build a database to support a computer game

technical skills to

execute data and query analysis tools and evaluate data input and output performance statistics

redefine data structures to improve the efficiency of data throughput

use an integrated development environment to build modify and manipulate relational or objectoriented data structures

write code to implement a physical database design

Required knowledge

computer hardware specifications and hardware performance expectations

creation use and testing of stored procedures

defining input parameters

defining output parameters

database stress testing and stress testing software

database testing methodologies

objectoriented database management systems

relational database management systems

IBM DB

Microsoft Access

Microsoft SQL MS SQL server

MySQL

Oracle

Postgre Structured Query Language Postgre SQL

relational database modelling building blocks and theory

attributes

entity relationship modelling

normalisation of database tables

relationship cardinality and connectivity

M

MN

SQL such as

data definition language

data manipulation language

evolution of relational database management systems and their relationship to the flat file hierarchical and network data storage legacy of games

important functions of a relational database management system within the context of a computer game such as

controlling data access for multiple users

interpreting data access languages such as SQL and LINQ

interpreting data application programming interfaces APIs such as ADONet

managing data integrity

managing disaster recovery and backups

managing the data dictionary

managing the data storage

managing the security requirements of the data

transforming and presenting data

importance of data models

different types of data models such as Chen and Crows Foot models

relationship between gameplay rules and the modelling of the database structure

Evidence Required

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria required skills and knowledge range statement and the Assessment Guidelines for the Training Package

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to

interpret a conceptual database model and create a physical database design from the conceptual model

create a database that allows for the persistence of state data for a computer game

evaluate and improve the performance of a database built to support a computer game

Context of and specific resources for assessment

Assessment must ensure access to

computer aided software engineering and modelling tools

relational or objectoriented database management system

performance testing and analysis software for the selected database management system

game architecture specifications

game design and requirements documentation

client or server hardware and networking infrastructure sufficient to simulate the game architecture specifications

appropriate learning and assessment support when required

modified equipment for people with special needs

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge The following examples are appropriate for this unit

written or verbal evaluation of knowledge of data modelling techniques

written or verbal evaluation of knowledge of scripting languages such as SQL and LINQ

evaluation of the implementation of a conceptual model as a physical model

review of a database created to support a computer game

review of a database performance measurement process and evaluation techniques

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector workplace and job role is recommended where appropriate

Assessment processes and techniques must be culturally appropriate and suitable to the communication skill level language literacy and numeracy capacity of the candidate and the work being performed

Indigenous people and other people from a nonEnglish speaking background may need additional support

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge


Range Statement

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

Game architecture may include:

networked, persistent games, including massively multi-player online (MMO) games, such as:

World of Warcraft

Second Life implemented in a client (PC), server architecture using web-based protocols

networked proprietary console game architectures implemented on hardware, such as:

PlayStation

Xbox

Wii

Nintendo

iPod Touch

Zone 40

where game state is persisted between sessions

non-networked persistent games.

System implementation requirements may include:

games that persist current game state and consequently must manage an authoritative store of state data using a client-server architecture

non-networked stand-alone games that persist game state between sessions.

Database architecture may include:

client-server based architectures that use:

relational database management systems

object-oriented database management systems.

Data model may include:

Chen Entity relationship diagrams

Crow’s Foot entity relationship diagrams

data dictionaries

object data models

relational data models.

Game artefacts may include:

characters

maps

objects, weaponry, machinery and prizes

players

regions, geographical locations and game servers.

Game-design requirements may include:

design rules and limitations

level customisations and game level design

level definitions

level progression requirements

play rules.

Entity relationships may include:

assessed and implemented cardinality requirements

assessed and implemented connectivity requirements

consideration of degree of normalisation of tables and referential integrity constraints

consideration of entity integrity constraints.

Input and output workload may include estimates of:

index read, modify and rebuild rates

number of database transaction log entries generated

number of random disk read writes

number of sequential disk read writes.