Programming
Project:
Teams
of Two (2) People; no more, no less. In the event of an odd number of students, one group of
three will be permitted. Do not assume you can form a group of three if there is an odd number of students in the class! A group of three
will only be permitted after all groups of two have registered with the
instructor. Single person teams are not permitted under any circumstance. It is
up to you to form your own team. It is STRONGLY encouraged that you form your
team and start thinking about your project as soon as possible.
Design
a game and implement it in Assembly Language. You may use C++ or another
high-level language to create a more robust user interface, but you must write
the majority of your program in Assembly.
All
Projects must receive prior
approval. Your professor will not
provide example projects, but will be happy to help you refine your own ideas.
ONLY ONE PROJECT OF ANY GIVEN TYPE WILL BE PERMITTED. In other words, if two
teams want to do Halo 5, then the first team that submits their request will be
permitted to do Halo 5 and any other teams who had wanted to do Halo 5 will
have to find another project like Quake 5 or GTA5.
You
will submit a one-page project proposal on 28 January 2013. This proposal
should include your group members, the name of your game, a rough idea of how
it is played, and a rough idea of how you plan to implement this game.
You
will give a PDR (Preliminary Design Review) of your Project to the class on 4
February 2013. A Power Point Presentation is essential. As a class, we will
evaluate the complexity and feasibility of the proposed Project and make
suggestions and offer positive constructive criticisms. A CDR (Critical Design
Review) will take place on 20 February 2013. At the CDR, you should show
exactly how you plan to solve your game’s problems and should provide a
flowchart and a division of labor plan. You should have a good idea of the
modularity of your project and perhaps even some example code. One person programming and the other person
documenting is NOT ACCEPTABLE. All components of the project should be shared by both team members. You may be
asked to explain what is going on with any part of your project. "That's
not my part." is not an acceptable answer!
This
project is due on 22 April 2012. Grading will be done both by the class and by
the instructor. Your group will also give a presentation and demonstration of
your Project at this time. You are expected to BOTH copiously comment and
document your program. The part of your project that is turned in should be a
written report that includes an introduction, some background, your code and
documentation, problems you encountered and your solutions, future work, and
your conclusions. You should also include a user manual with your project. A
draft of the written portion of your project is also due 1 April 2013. You may
earn bonus credit by presenting your project at the Spring 2013 Undergraduate
Research Conference: http://ius.edu/AcadAffairs/studentconference/index.cfm
on 13 April 2013.
The
written portion of your project will be evaluated by your professor and
returned to you with comments.
The
written portion of your project will be graded using these guidelines:
Your
instructor is fluent in C/C++, Assembly, Java, Pascal, Fortran, and Basic. Your
instructor is familiar with DOS, Windows, Mac OS, and UNIX operating
systems/environments. You do not have to choose any of these languages/OSes,
but I’m probably going to be better able to help you with your code if you do
select something I already know.
Please
contact your instructor if you have any questions!
This
project is worth 15% of the final grade. Of the 15%, 1% is the proposal, 2% is
the PDR, 3% is the CDR, 4% is the Final Presentation, 2% is the first report
submission and 3% is the last report submission.