Reference no: EM132365741

Learning Outcomes

e) On successful completion of this module learners are able to understand and apply trigonometry and core trigonometric identities in game development situations.

f) On successful completion of this module learners are able to examine and apply vector mathematics to situations found in game programming.

g) On successful completion of this module learners are able to examine and apply analytic geometry in common game development situations.

Assessment Overview:

This assessment requires you to be able to apply to apply vector mathematics and geometry in a software program.

Instructions:

• Create a new C++ Visual Studio project
• Add the file ‘geometry.h' to the project. This is found in the Assessment 4 folder in the assessment section of Blackboard.
• Create the required source code for the document and develop tests to verify the functions that you implement.
o Files to be created/implemented : main.cpp, geometry.h, geomtery.cpp, test.h, test.cpp
o Write your test cases such that code keeps track of how many test scenarios were
• run (by keeping the count of it) and OUTPUT the count and the test result to the console.

• Do not rename or change the header file.
o Note - with the exception of template code provided by Torrens University or your facilitator, all code must be written by you the student. Anything less will be considered plagiarism. If you are unsure, please contact your facilitator for clarification.

Build Quality:

The source code is required to display the following features:

Free of:

o Build warnings at Warning Level 3 for all build targets.
o Build errors at Warning Level 3 for all build targets.
o All intermediate files, (.obj, .pdb, .ilk, ..., files etc).

An electronic copy of the source code (.h, .cpp), solution file (.sln) and project file (.vcxproj) are required to be submitted.
o Name the source code folder as: GeometryProjectSource - Student Name
o Name the solution as: GeometryProject.sln

Coding Standards:
The source code is required to display the following features:

• The template header.
• Standardised naming convention for variables.
• Discrete Functions that perform the task reflected in their name.
• Appropriate use of commenting; especially, in complex areas of the code.
• Appropriate use of whitespace and indentation.
• Appropriate function headers as specified below:

/***********************

* name of the function: the task of the function

* @author: who is the author of the function

* @parameter: info about the parameters of the function

* @return: the return value of the function

********************/