CSE 113 Final Project
Due:
May 10, 2018 11:59 PM (plus you get a 24 hour grace period)
Some assignment segments have earlier dates
Objective:
Learn to take an ending objective to guide your problem solving and project planning. You will
use the tools you already know, plus ones you will continue to acquire and be encouraged to
learn new ones along the way.
Problem context: You will be designing and implementing a game in processing that can be
played. You will take on the role of a game designer in industry through the demonstration of the
development process with the “Game Plan Sheet”, creation of a proper flow chart to be used as
your guide to help with implementation, development of a working game, and finally a written
report.
As with many applications testing is specific to the application, this is managed with test
conditions. For your grading rubric you will be providing the conditions to allow the criteria that
are required to be appropriately graded against your unique program. You will also be evaluated
on how much the game matches the game you were supposed to implement, and a report to
present on your implementation process and outcome.
Reminder of Academic Integrity:
For this project, it is likely you will go to other resources for support that were not provided to
you. You must cite them in your code by including the link, and you will need to do a formal
citation in the report. Citing your entire program, meaning you just put together a bunch of work
that is not yours, this is a violation of academic integrity. If you work with a partner, that partner
is exempt from the collaboration rules for you. Collaboration with any other students is still not
allowed. Using work that is not yours, is still not allowed. All the other rules are still in place too.
Partner Selection (50 Points):
Determine if you want to work alone or select a partner. Once you make this decision, it is final.
If you work with a partner, they must be in the same lab section. Your partner must also select
you in return. If there is no mutual selection or you are not in the same section, you will forfeit
these points and have to work alone.
In both cases you are required to submit text on UBLearns of your decision. Here are the
templates for your submissions (fill in as appropriate). You just put the appropriate response into
the comments field when you go to submit.
“I am working alone”
“I am in Section _ and will be working with ___”
Your submission is due on March 29th at 11:59pm (close out 24 hours later).
If you are working with a partner, there will be 1 submission per group made for all future
assignments. We will still allow multiple submissions, grading only the final submission. So
partners, make sure that the last submission from either of you is the one you want graded.
Prelab (50 Points):
Determine what game you are planning to implement and fill out the “Game Plan” sheet. The
initial submission of this is due on April 12th at 11:59pm (close out 24 hours later).
Flow Chart (100 Points): During week one of the recitations assigned to this lab, you are
expected to complete a flow chart demonstrating an approach to the implementation of your
game. At this point you may not have all the knowledge to implement the game but you should
be able to break down the tasks in a visual manner. This flow chart must be shown to the TA
during this lab session for a sign off to achieve full credit. Once it is signed off, upload the PDF.
You will need to save this to include in your final report at well.
Due April 12th at 11:59pm (close out 24 hours later).
Once you have completed this task in recitation, please start working on your project right away.
Time will go by faster than you expect.
Functionality of Concepts (200 Points):
To test the functionality in the labs you were given rubrics to follow. For this project, you will be
developing those test statements so that we can accurately test your program for the required
concepts. This part of the project is broken down into three parts: the test statements, game
requirements, and game implementation. All components for this part of the final project will be
submitted to the lab assignment “Functionality” by the due date.
Due May 10, 2018 11:59 PM (plus you get a 24 hour grace period).
Test Statements (30 Points):
While we will be testing game play, it is important to grade on the concepts you are supposed to
implement that demonstrate important ideas you have learned across the semester. To grade
fairly across the different game possibilities (and implementation approaches), the rubric
provided outlines each requirement and you will submit a 1-2 sentence explanation how we are
going to test that requirement. Here are some examples of test statements:
● In lab 2 task you made a fish with 3 air bubbles, the test statement would be “when the
program is running the display will output a triangle primitive located to the right of the
ellipse primitive and it will resemble a fish”.
● Or when you had to add comments to the code it can be “look at line 25 of the sketch file
test.pde to verify”.
Your test cases must make sense. Following is a bad example of test statement:
● If you were asked for how to test to see if the ball was moving across the screen in Lab 2
Task 1 and said “read the comment on line 43 to verify the ball moves” you will not get
points for the statement or the criteria since it does not make logical sense due to a
comment shows no movement of a ball; the correct statement would be “run the program
and look at the middle of the display to see the ball move”.
You will get points for each test statement, as well as the implementation requirement being
satisfied. Use the provided template to declare your test statements and submit it as a pdf with
your code, and game plan.
Game Plan (75 Points):
At the start of the project you created a game plan sheet. You will submit either the original plan
or if you change games, the updated one with a TA sign off (25 Points). This will be used to
verify your game implementation is representing the game you were supposed to implement.
This is the check to make sure you implemented the correct game functionality. The functionality
must follow the specifications below and also the ones you define on the game plan sheet and
is worth 50 points.
Game Requirements (70 Points):
For your game there are many concepts that are non-negotiable and must be incorporated in
your project. It is up to you on how to do so while completing the aspects of the chosen game.
If there is not a test statement, you can not earn implementation points. If your test statement is
not correct or inappropriate, you can only earn half the possible implementation points for that
criteria and none of the test statement points.
● Global variable
● Local variable
● Event variable
● Event function
● Create and use a splash screen
● Change the background color
● Use non-default display size
● Use an image
● Use text on the display
● Use an object
● Use something that involves push/pop (matrix manipulation)
● Use an array
● Use a conditional
● Use a loop
● Allow for continuous play (when a game finishes, it allows you to start over again)
You are not allowed to create any classes, you will be instructed on basic ones that you can use
in your program if you want. If a proper header is not included in your program, you will get a 10
point penalty on your requirements.
Game Implementation (25 Points):
In this document, the list of the approved games have specifications to ensure that your game
matches the general objective. Your game will be compared against the overall implementation
rules for the game for 25 Points.
Project Report: (100 Points)
The report is to be typed in a professional manner that will present the design process, your
game and make future recommendations for improvement. The following sections must be
included. Make sure that you address all the content requirements for each section.
● Title Page (5 Points)
● Introduction (5 Points)
● Planning Section
○ Game Plan Explanation- With reference to the appendix where your game plan
from the prelab is actually located (10 Points)
○ Flow chart explanation- Flow chart should be embedded in this section (10
Points)
■ If you change games, you still need this section, so you will need to make
a new flow chart for your game. No new sign off is required.
○ Game development process- Discuss the process of developing your game, if
you worked with a partner, make sure to describe who did what and how the
collaboration worked. If you did not have a partner, do you think one would have
been beneficial, and why? If you used any resources that were not provided to
you, this is where you would talk about them. All of these resources must have a
traditional citation (MLA, IEEE, APA, etc. you pick) in the report, in addition to
their link in the program. (10 Points)
● Implementation
○ Game implementation success- Discuss how the game turned out, did it meet all
the objectives in the game plan? If it didn’t, why? Did you make any changes
from the game plan, and if so why? Make sure to include screenshots of the
game. (15 Points)
● Reflection
○ Game improvement- If you were to make a version 2.0, how would you improve
the game? (10 Points)
○ Reflection- Discuss briefly about your experience with this project, what you liked
and didn’t, what you think could be improved (10 Points)
● Appendix
○ Contains your both of the Game Plan documents (initial and final), and also all
your code (5 Points)
■ “All” game plans submitted should have a TA signature on it.
Additionally the following format and professionalism guidelines must be followed:
● Page numbers (5 Points)
● Appropriate font (5 Points)
● Correct grammar and spelling (5 Points)
● Readability (5 Points)
You will submit the single PDF of your report to the assignment called “Final Report”. Due May
10, 2018 11:59 PM (plus you get a 24 hour grace period).
Game Options:
Here are the games you may choose from and the explicit requirements of functionality for each
game beyond the general rules of the game. You may not choose any other games.
● Tic tac toe (also known as three in a row)
○ Three game play versions: human vs human, human vs AI easy, human vs AI
hard
○ This is a sample of how the game play works: https://youtu.be/5SdW0_wTX5c
● Memory (also known as matching or find the pair)
○ Three versions of difficulty
○ This is a sample of how the gameplay works: https://youtu.be/Lxe0gvPQtnE
● Asteroid
○ Must have a score and increase speed of the asteroids with time
○ This is what the game should be modeled after: https://youtu.be/WYSupJ5r2zo
● Solitaire
○ Two versions: One card at a time deal and three cards at a time deal
○ This is a sample of what the game should be modeled after:
https://youtu.be/iWq8He0Yqkc
● Breakout (also known as breaking bricks)
○ Each level of bricks must be a color that corresponds to that level, each level
takes a different number of hits to make it disappear. Speed should increase and
decrease
○ Here is a sample of what the game play looks like” https://youtu.be/Up-a5x3coC0