NTISthis.com

Evidence Guide: ICTGAM419 - Build a database to support a computer game

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTGAM419 - Build a database to support a computer game

What evidence can you provide to prove your understanding of each of the following citeria?

Verify the database model

  1. Verify that the game architecture and system implementation requirements have been addressed by the proposed database architecture
  2. Correlate data model entities and their attributes with the game artefacts, and the game design requirements
  3. Verify that the entity relationships defined in the data model implement the game-design and game-play rules
  4. Verify the estimates of the amounts of data storage required, and the data types defined by the data model
  5. Document design inconsistencies
  6. Review the database model and address, and correct any inconsistencies
  7. Define the database test data
Verify that the game architecture and system implementation requirements have been addressed by the proposed database architecture

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Correlate data model entities and their attributes with the game artefacts, and the game design requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Verify that the entity relationships defined in the data model implement the game-design and game-play rules

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Verify the estimates of the amounts of data storage required, and the data types defined by the data model

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document design inconsistencies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the database model and address, and correct any inconsistencies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define the database test data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create the physical database design

  1. Implement the conceptual data model design as a physical database design
  2. Determine the default database file size, according to the data model storage estimates
  3. Determine game data input and output workload estimates
  4. Determine the reliability and performance requirements
  5. Define the minimum hardware requirements to support the input and output workload and reliability or performance requirements
  6. Configure the database management system in order to use minimum hardware requirements
  7. Refine and confirm the database test data
Implement the conceptual data model design as a physical database design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the default database file size, according to the data model storage estimates

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine game data input and output workload estimates

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the reliability and performance requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define the minimum hardware requirements to support the input and output workload and reliability or performance requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Configure the database management system in order to use minimum hardware requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Refine and confirm the database test data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Implement the physical database prototype

  1. Write structured query language (SQL) scripts to create physical database files according to the design requirements
  2. Write SQL scripts to create database tables
  3. Implement the primary key constraints
  4. Implement the foreign key constraints
  5. Define, and script, stored procedures for selecting, inserting, updating and deleting data
  6. Define and script insert statements for test data
  7. Execute SQL scripts and database, including test data
Write structured query language (SQL) scripts to create physical database files according to the design requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Write SQL scripts to create database tables

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Implement the primary key constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Implement the foreign key constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define, and script, stored procedures for selecting, inserting, updating and deleting data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define and script insert statements for test data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Execute SQL scripts and database, including test data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test the database and document results

  1. Document the entity integrity tests, and results
  2. Document the referential integrity tests, and results
  3. Document the input and output performance tests, and results
  4. Document the stored procedures tests, and results
Document the entity integrity tests, and results

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the referential integrity tests, and results

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the input and output performance tests, and results

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the stored procedures tests, and results

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review, evaluate and correct database performance

  1. Review the test result deficiencies
  2. Define, evaluate and test the deficiencies, and ensure that corrective measures are implemented
  3. Implement corrections to the database
Review the test result deficiencies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define, evaluate and test the deficiencies, and ensure that corrective measures are implemented

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Implement corrections to the database

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Verify the database model

1.1 Verify that the 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 the game design requirements

1.3 Verify that the entity relationships defined in the data model implement the game-design and game-play rules

1.4 Verify the estimates of the amounts of data storage required, and the data types defined by the data model

1.5 Document design inconsistencies

1.6 Review the database model and address, and correct any inconsistencies

1.7 Define the database test data

2. Create the physical database design

2.1 Implement the conceptual data model design as a physical database design

2.2 Determine the default database file size, according to the data model storage estimates

2.3 Determine game data input and output workload estimates

2.4 Determine the reliability and performance requirements

2.5 Define the minimum hardware requirements to support the input and output workload and reliability or performance requirements

2.6 Configure the database management system in order to use minimum hardware requirements

2.7 Refine and confirm the database test data

3. Implement the physical database prototype

3.1 Write structured query language (SQL) scripts to create physical database files according to the design requirements

3.2 Write SQL scripts to create database tables

3.3 Implement the primary key constraints

3.4 Implement the 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 the entity integrity tests, and results

4.2 Document the referential integrity tests, and results

4.3 Document the input and output performance tests, and results

4.4 Document the stored procedures tests, and results

5. Review, evaluate and correct database performance

5.1 Review the test result deficiencies

5.2 Define, evaluate and test the deficiencies, and ensure that corrective measures are implemented

5.3 Implement corrections to the database

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Verify the database model

1.1 Verify that the 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 the game design requirements

1.3 Verify that the entity relationships defined in the data model implement the game-design and game-play rules

1.4 Verify the estimates of the amounts of data storage required, and the data types defined by the data model

1.5 Document design inconsistencies

1.6 Review the database model and address, and correct any inconsistencies

1.7 Define the database test data

2. Create the physical database design

2.1 Implement the conceptual data model design as a physical database design

2.2 Determine the default database file size, according to the data model storage estimates

2.3 Determine game data input and output workload estimates

2.4 Determine the reliability and performance requirements

2.5 Define the minimum hardware requirements to support the input and output workload and reliability or performance requirements

2.6 Configure the database management system in order to use minimum hardware requirements

2.7 Refine and confirm the database test data

3. Implement the physical database prototype

3.1 Write structured query language (SQL) scripts to create physical database files according to the design requirements

3.2 Write SQL scripts to create database tables

3.3 Implement the primary key constraints

3.4 Implement the 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 the entity integrity tests, and results

4.2 Document the referential integrity tests, and results

4.3 Document the input and output performance tests, and results

4.4 Document the stored procedures tests, and results

5. Review, evaluate and correct database performance

5.1 Review the test result deficiencies

5.2 Define, evaluate and test the deficiencies, and ensure that corrective measures are implemented

5.3 Implement corrections to the database

Evidence of the ability to:

interpret a conceptual database model

create a database from a conceptual model, 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.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

identify computer hardware specifications and performance required to support database development

discuss the creation, use and testing of stored procedures

explain why input and output parameters are required

explain database stress testing and stress testing software

discuss the principles of database testing methodologies

describe object-oriented database management systems

discuss the similarities and difference between relational database management systems:

IBM DB2

Microsoft Access

Microsoft SQL (MS SQL) server

MySQL

Oracle

Postgre Structured Query Language (Postgre SQL)

discuss relational database modelling building blocks and theory, including attributes, entity relationship modelling and normalisation of database tables

discuss relationship cardinality and connectivity:

1:1

1:M

M:N

outline the features, and functions, of structured query language (SQL), including data definition language and data manipulation language

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

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

interpret data access languages, such as SQL and language-integrated query (LINQ)

interpret data application programming interfaces (APIs) including:

ADO.Net

data integrity

disaster recovery and backups

data dictionary

data storage

security requirements of the data

transforming and presenting the data

discuss the importance of data models

describe the different types of data models, including Chen and Crow’s Foot models

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