Corning Community College
CSCS2650 Computer Organization
PROJECT: Make Pong Go (MPG0)
OBJECTIVE
Read through pertinent technical specifications and guides for Vircon32, and build a functioning pong game that can be played in the emulator.
EDIT
You will want to go here to edit and fill in the various sections of the document:
MPG0
References
Game Mechanics
Game loop
Sprites
Bounds checking
Handling motion
Score Display
SUBMISSION
To be successful in this project, the following criteria (or their equivalent) must be met:
Project must be submit on time, by the deadline.
Executed programs must display in a manner similar to provided output
Processing must be correct based on input given and output requested
Output, if applicable, must be correct based on values input
Code must be nicely and consistently indented
Code must be consistently written, to strive for readability from having a consistent style throughout
Code must be commented
No global variables (without instructor approval), no goto statements, no calling of main()!
Track/version the source code in your lab46 semester repository
Submit a copy of your source code to me using the submit tool by the deadline.
Let's say you have completed work on the project, and are ready to
submit, you would do the following:
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
You should get some sort of confirmation indicating successful submission
if all went according to plan. If not, check for typos and or locational
mismatches.
RUBRIC
I'll be evaluating the project based on the following criteria:
26:mpg0:final tally of results (26/26)
*:mpg0:input via gamepad interface [7/7]
*:mpg0:proper bounds checking [7/7]
*:mpg0:display of ball and paddles [6/6]
*:mpg0:some other enhancement [6/6]
Pertaining to the collaborative authoring of project documentation
Additionally
Solutions not abiding by spirit of project will be subject to a 50% overall deduction
Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction