Project #0 CMSC 131
Due:  Thursday Feb. 7 at 11:00 pm Object-Oriented Programming I
Type of project: Open Spring 2013

Exercising the Submit Server

Objective(s)

The primary purpose of this project is to ensure that you can:

  1. Check Out a Project from your CVS Repository
  2. Modify its contents.
  3. Use the Internet (or other sources) to answer some basic questions about computing and history.
  4. Submit your work.
  5. See the results of your submission in the Submit server.


Preliminary Research

Before doing anything, use the Internet (or some other resource of your choosing) to answer the following questions:

  1. In what year did the World Wide Web go public on the alt.hypertext newsgroup?
  2. What is the word used to describe the physical components of a computer system?
  3. How many bits are there in a byte?
  4. What is the cryptographic technique of hiding a message in plain site (whose name comes from steganos and graphein)?


Getting Started

Assuming that you know these answers, "check out" the project from your CVS repository. This was demonstrated in class, and is also described in the Eclipse Tutorial. The basic steps are:

  1. Start Eclipse and open the CVS perspective. (If you have not set up this perspective, consult the documentation under the Resources link, or ask a TA).
  2. Click on the little triangle next to the Respository entry, which should result in a few subitems opening under the Respository; click the item named "Head" and several files should open directly under it.
  3. Right click on the project named "Spring2013-Proj0" and choose "Check Out."
  4. Go back to the Java perspective.
Once you are back in the Java perspective, you should see the project folder on the left, and you should be able to begin working on the project.
  1. Open the Java project by clicking on the triangle next to it. Click next on the triangle marked src; continue by clicking on the triangle next to default package. Finally, open the file named History.java by double-clicking on it. Its contents (source code) should appear in the Editor window to the right.
  2. Edit that file by replacing the missing fields with the information you obtained from your research.

If you write the project from scratch, without checking out the "Spring2013" files from your CVS repository, you will not be able to submit your work easily, and you will receive NO CREDIT.


Submitting Your Work

Submit your project from Eclipse (within Java perspective) by right-clicking the project folder and selecting "submit" . When it asks for your ID and password, be sure to use your University of Maryland "Directory ID" and the corresponding password, and NOT your class account and password. You may submit as many times as you want -- we will always grade the submission that scores the highest on our automated testing (taking into account the late penalty for any submissions that were after the deadline, but not more than 24 hours late. The penalty for late submissions is 20%.)   After you have submitted your project, you should visit the submit server.  There you can obtain limited feedback about how well your project is performing.  The number of times you can run our tests on your project (before the due date) is limited.  The earlier you begin working on the project, the more opportunities you will have to see how your project performs on our tests before the due date!


Public and PrivateTests

In general, your code will be subjected to Public as well as Private tests. Sometimes, you will be given the code for the Public tests, although you will not be given code for Private tests. Your grade is determined by your performance on both these tests.


Grading

Your grade is determined by how well your code performed on both Public and Private tests. If you pass all of these tests, you obtain 100%.

Note that as we engage in more sophisticated projects, these tests will become more complex, and you will also be limited to three submissions during a twenty-four hour window. This is to discourage "jamming" the Submit Server with a constant stream of partially-working code in the hopes of obtaining clues from test results.



Web Accessibility