Modification History
|
Release |
Comments |
|
Release 1 |
This Unit first released with ICA11 Information and Communications Technology Training Package version 1.0 |
Unit Descriptor
This unit describes the performance outcomes, skills and knowledge required to build a database to support a computer game.
Application of the Unit
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.
Licensing/Regulatory Information
No licensing, legislative, regulatory or certification requirements apply to this unit at the time of endorsement but users should confirm requirements with the relevant federal, state or territory authority.
Pre-Requisites
Not applicable.
Employability Skills Information
This unit contains employability skills.
Elements and Performance Criteria Pre-Content
|
Element |
Performance Criteria |
|
Elements describe the essential outcomes of a unit of competency. |
Performance criteria describe the performance needed to demonstrate achievement of the element. Where bold italicised text is used, further information is detailed in the required skills and knowledge section and the range statement. Assessment of performance is to be consistent with the evidence guide. |
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 |
Required Skills and Knowledge
This section describes the skills and knowledge required for this unit.
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.
Evidence Guide
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:
|
|
Context of and specific resources for assessment |
Assessment must ensure access to:
|
|
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:
|
|
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. |
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: |
|
|
System implementation requirements may include: |
|
|
Database architecture may include: |
|
|
Data model may include: |
|
|
Game artefacts may include: |
|
|
Game-design requirements may include: |
|
|
Entity relationships may include: |
|
|
Input and output workload may include estimates of: |
|
Unit Sector(s)
Game development
