Reference no: EM132181320

Mathematics Assessment - Geometry based programming project

Learning Outcomes -

• On successful completion of this module, learners are able to understand and apply trigonometry and core trigonometric identities in game development situations.
• On successful completion of this module, learners are able to examine and apply vector mathematics to situations found in game programming.
• 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 -

Open up the file 'MAT101_Assessment_4_Attachment_1_T1_2018_071117.pdf', which is attached.

Create the required source code for the document and develop tests to verify the functions that you implement.

Keep in mind the following criteria when you complete this assessment:

Build Quality: The source code is required to display the following features:

Free of:

• Build warnings at Warning Level 3 for all build targets.
• Build errors at Warning Level 3 for all build targets.
• 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.

• Name the source code folder as: GeometryProjectSource - Student Name
• 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.

Runtime Quality: The source code is required to display the following features:

Free of:

• Memory leaks.
• Bugs.
• Crashes.

Instructions:

1. Files to be created : main.cpp, geometry.h, geomtery.cpp, test.h, test.cpp

2. Write your test cases such that code keeps track of how many test scenarios were run (by keeping the count of it) and OUTPUT it. Do not rename or change the header file.

Attachment:- Assignment Files.rar