CMSC 202H — Fall 2011

Projects

Project Descriptions

• Project 1 — Sieve of Eratosthenes
• Project 2 — You've Got Mail! (Part 1)
• Project 3 — You've Got Mail, Round 2!
• Project 4 — You've Got Mail, Round 2.5!
• Project 5 — You've Got Mail: The Real Thing

(This page was updated, on Oct. 13, to better align with the other 202 sections. However, if you liked the old instructions better (the instructions on how to download, compile, etc. were slightly different), you can still access them here.)

Project Development References

• Transferring files to the GL system
• Compiling and executing on the GL system
• Submitting your project for grading
• Policy on late project submission
• Working on your project remotely
• Coding and commenting standards
• How your project will be graded

The Eclipse Development Environment

Projects in this course will be developed using the Eclipse Integrated Development Environment (IDE). Eclipse is designed to assist you when writing Java applications. Eclipse is available on the PCs located in the OIT labs. If you prefer to work on your own PC, use the “Eclipse IDE for Java Developers” (NOT “Eclipse IDE for Java EE Developers”). The Eclipse IDE requires the installation of a Java Runtime Environment (JRE) or Java Development Kit (JDK) in order to run. Both Eclipse and the JavaSE JDK can be downloaded and installed free of charge — see the Downloads section of the Resources page for download links.

We will spend some time in one of the labs gettting acquainted with Eclipse, but you would do well to spend time using Eclipse on your own.

The UMBC GL Development Environment

The UMBC UNIX system runs several different versions of UNIX. The systems known as linuxl.gl.umbc.edu, linux2.gl.umbc.edu, & linux3.gl.umbc.edu all run a version of UNIX called Linux. The systems known as solaris.gl.umbc.edu and irix.gl.umbc.edu run other versions of UNIX called Solaris and Irix.

The project graders will use either linux1, linux2, or linux3 to compile and test your program. Therefore, ALL PROJECTS must compile and execute on linux1, linux2, or linux3.

If you have been developing your code on some other machine (most likely a personal laptop/desktop), you must first get your files onto the campus network file system. This will then make them directly accessible from almost any of the university's machines (the lab machines, the GL servers, etc.) You will also need some way to work on one of the GL servers. The easiest way is to go to one of the labs; however, you can also do this remotely (see the Working Remotely link above).

Project Policies

Each project description will designate the project as OPEN or CLOSED as defined below.

OPEN Projects

1. You should try as much as possible to complete the project by yourself.
2. You may get assistance from anyone — TAs, instructors, fellow students, relatives, friends, etc.
3. You must document all outside help you get as part of your file header comment.

This DOES NOT mean

1. That you may copy anyone else's code,
2. Have someone else write your code for you, or
3. Submit someone else's code as your own.

CLOSED Projects

1. You should try as much as possible to complete the project by yourself.
2. You may get assistance only from the TAs, CS Help Center staff, or instructors.
3. You must document all outside help you get as part of your file header comment.

You MAY NOT

1. Copy anyone else's code,
2. Have someone else write your code for you,
3. Submit someone else's code as your own,
4. Look at someone else's code, or
5. Have someone else's code in your possession at any time.