In this assignment, you will complete the code for a very simple game engine called uEngine. This will increase your practical understanding of:
The uEngine provides a framework for the implementation of very simple 2D games. While the engine provides functions associated with advanced engines such as physics simulation, sound, an graphical rendering, these features are provided in a very simple way only. Specifically, the features of uEngine are:
This class diagram shows the structure of uEngine.
uEngine was programmed in Java using the Eclipse IDE. You can download your own copy of Eclipse, or use it in the CASLab. I have tested the sample code using Eclipse Mars Release (4.5.0).
To get your own copy of uEngine:
You will find that this project has errors and will not compile. Your first task in this assignment is to fix these errors.
The version of uEngine that I have given you has critical lines removed, or critical parts of lines not provided. Read through the code for uEngine to find and repair these problems. I recommend that you carefully read through all of the code and study the class diagram to understand how uEngine works before you undertake these changes.
I have provided two test programs that you can use to help determine whether you have correctly repaired uEngine. Note, though, that successfully running the test programs is not proof that all issues have been correctly fixed.
Provide brief answers to the following questions. Your answers should be concise, but should provide sufficient detail to fully answer the question.
Using OnQ, provide a handin consisting of two parts: (1) Your modified code for uEngine, and (2) a report answering the questions from part 2.
Your modified code should be a zip file containing a folder called uEngine-yourLastName. That folder should contain your full running solution to part 1. If your project doesn't work, include a description in your report specifying what does and does not work.
Your report for part 2 should be in PDF format. It should include your name and a title (e.g., Assignment 1, Part 2 Report). Use 11 pt type with at least 1" margins. UML diagrams should be integrated into the report, not submitted separately as raw UMLet files.
The assignment will be graded with the rubric provided in OnQ. Please review this rubric while completing the assignment.