February 9, 2017


February 23, 2017


March 23, 2017


April 6, 2017


April 20, 2017


May 1, 2017


Project Description

Project Policy:

This course will have six small programming projects, each of which will consist of various sections. The programming project descriptions will be available online through this site and will be discussed during the laboratory sections. Students are also encouraged to work on the problems after laboratory hours as these hours will probably be insufficient for completing the project. Laboratory hours are primarily meant for discussions related to the project and will be supervised by Teaching Assistants (TAs). The project is to be submitted on the due date disclosed on the announcements page.


Primer on the programming projects:  (Late submission will not be accepted.)

The programming projects given in this course will be tightly linked and will each build upon the previous one. The later project problems will reuse part of the code from earlier problems. Therefore make sure that your code works before submitting them.

Things to be handed in:

* The source code with the following details as comments: your name ,
  date, project title, and e-mail address. 
* Highlight any special features of your program that we should look out for.

The neatness and professionalism of your report does matter. Make it
clear and easy to read. 

When submitting your project, you do not need to submit the .class
files. You should also not submit the source code for any classes we
provide. Unless a project explicitly says so,
just submit the source code (.java files) that you have written.

Note that if your project doesn't compile, you get a zero for the
project! Make sure you hand in the proper files and have not made any
untried last minute changes.
Also, unless a project specifically asks you to do so, do not modify
any Java classes we provide. If you think there's something wrong with
code we provide and can only get your code to work by "fixing" our
classes, you're probably going to end with a very low score for the
project. If you really think there is a bug in the code, post a
description to the ece122-ta mailing list and a TA or instructor
will investigate.

Check out Appendix F of Lewis & Loftus for a discussion of coding and
documentation styles. We're not going to enforce any particular style,
such as always indenting four spaces, but you should use some
consistent style. Only 50% of your grade is based on the program doing
what we asked. The rest of the points are for doing the task clearly
and comprehensibly.