Assessor Resource

ICAGAM419A
Build a database to support a computer game

Assessment tool

Version 1.0
Issue Date: April 2024


This unit applies to game programmers or junior analyst programmers responsible for the development and implementation of a database to support state management for a computer game.

This unit relates to the specific requirements for designing and implementing a relational database required for the management of persisted state of a computer game. The game may be an online or networked game or a stand-alone game where player actions are preserved or persisted between sessions.

This unit does not address specialist programming skills required for games programming which are detailed in other units of competency.

This unit describes the performance outcomes, skills and knowledge required to build a database to support a computer game.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)

Prerequisites

Not applicable.

Employability Skills

This unit contains employability skills.



Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

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 object-oriented 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 non-English speaking background may need additional support.

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

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

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 game-play rules and the game design requirements

communication skills to:

identify and discuss game-play 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 game-play 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 game-play 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 object-oriented database management system

plan an effective implementation to a relational or object-oriented database management system

problem-solving 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 object-oriented 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 object-oriented 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

object-oriented database management systems

relational database management systems:

IBM DB2

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:

1:1

1:M

M:N

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 ADO.Net

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 Crow’s Foot models

relationship between game-play rules and the modelling of the database structure.

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.

Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Verify that game architecture and system implementation requirements have been addressed by the proposed database architecture 
Correlate data model entities and their attributes with the game artefacts and game design requirements 
Verify that entity relationships defined in the data model implement game design and game-play rules 
Verify estimates of amounts of data storage required and data types defined by the data model 
Document design inconsistencies 
Review database model and address and correct inconsistencies 
Define database test data 
Implement conceptual data model design as a physical database design 
Determine default database file size according to the data model storage estimates 
Determine game data input and output workload estimates 
Determine reliability and performance requirements 
Define minimum hardware requirements to support input and output workload and reliability or performance requirements 
Configure the database management system to use minimum hardware requirements 
Refine and confirm database test data 
Write structured query language (SQL) scripts to create physical database files according to design requirements 
Write SQL scripts to create database tables 
Implement primary key constraints 
Implement foreign key constraints 
Define and script stored procedures for selecting, inserting, updating and deleting data 
Define and script Insert statements for test data 
Execute SQL scripts and database, including test data 
Document entity integrity tests and results 
Document referential integrity tests and results 
Document input and output performance tests and results 
Document stored procedures tests and results 
Review test result deficiencies 
Define, evaluate and test deficiencies and ensure corrective measures are implemented 
Implement corrections to database 

Forms

Assessment Cover Sheet

ICAGAM419A - Build a database to support a computer game
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICAGAM419A - Build a database to support a computer game

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: