Unit of competency Outline
Date retreived
24/07/2026 1:02 AM AWST
24/07/2026 1:02 AM AWST
Whilst all efforts are made to provide accurate and timely information from the relevant source/documentation, please be aware that the information supplied may not be the most current version. The accuracy of the detail has not been confirmed by the Department and therefore should not be relied upon without first confirming the contents.
Build a database to support a computer game
Build a database to support a computer game
Unit of competency
National Code
ICAGAM419A
ICAGAM419A
State Code
D7806
D7806
TGA Status
Replaced
Replaced
DTWD Status
Replaced
Replaced
State Implementation and Classification
Approved Date
04/11/2011
Field of Education
020303 - Database Management
Original Release Date
04/11/2011
Nominal Hours
30
Description
This unit describes the performance outcomes, skills and knowledge required to build a database to support a computer game.
Notes
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
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.
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.
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.
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.
Replaced By
| State Code | National Code | Title | Type |
|---|---|---|---|
| AUT77 | ICTGAM419 | Build a database to support a computer game | Unit of competency |
| State Code | National Code | Title | Type |
|---|---|---|---|
| D568 | ICA50211 | Diploma of Digital and Interactive Games | Qualification |