String Output Assignment

Program Instructions

1.      Learn by doing: An assignment is the equivalent of an open book test, work of art, or written paper. It is your individual, unique solution to a problem. In order for you to learn as much as possible, each assignment must be done 100% by yourself.

2.      Collaboration: Working together with other students is NOT permitted. If you have questions or get stuck, ask your instructor or TA for advice, not your fellow students.

3.      Penalties for plagiarism, copying, or working together: If you are seen or heard working together with other students on your assignment, or if the algorithm or text of one or more lines of your program’s code, comments, or delimiters match with another student, instructor, textbook, Internet, or any other programs, all students will earn a zero (0) for the assignment, and documentation of the event will be placed in the student's ICS department file.  If this happens twice, the student will earn an F for the course, documentation of the event will be placed in the student's department file, and the Dean of Students will be notified, which may result in possible suspension or expulsion.

4.      Problem: Write a Java program that prints out a 5 line limerick, a 3 line haiku, or a 4 line poem.

Submission Instructions

1.      E-Mail Your Assignment to the TA: Use your University of Hawaii e-mail account to submit your assignment. Only submit the LastNameFirstName1.javafile.  Do not submit the *.class file.

2.      Top of your assignment:
/**
 * Short description of program.
 * @author        Last Name, First Name
 * @assignment    ICS 111 Assignment X 
 * @date          Today’s Date

 * @link          For applets, include the link to your HTML page that displays your applet
 * @bugs          Short description of bugs in program
 */

3.      Filename of your assignment:
LastnameFirstnameX.java.
(Note: For example, SuzukiBubba1.java would be submitted for the first assignment if Bubba Suzuki were submitting it.)

4.      "To" field of e-mail:
The TA's e-mail address: ztomasze at Hawaii DOT EDU (DO NOT send your assignment to the instructor.)

5.      "Cc" field of e-mail:
Your UH UNIX e-mail address (That way, if the TA doesn't get your email for some reason, you have proof that it was sent.)

6.      Subject of email:
Assignment X (Albritton)
(Note: Substitute the 'X' for the assignment number)

7.      Body of email:
Copy and paste the latest version of your program. That way, we have your program even if you forgot to attach it.

8.      Attachments:
Attach your LastnameFirstnameX.java file. (DO NOT submit the LastnameFirstnameX.class file or a zip file.)

9.      After you send your e-mail: Be sure to double-check your assignment submission by opening the e-mail that you sent to the TA, downloading the attached program, and compiling and running the program to make sure it works, and that it is the program that you intended to submit. YOU ARE RESPONSIBLE FOR SENDING THE CORRECT PROGRAM.  No excuses will be accepted.

10.  Multiple submissions: You may submit an assignment more than one time. Only the most recent assignment submitted before the deadline will be graded. If you cannot make the deadline, then turn in what you have before the deadline for partial credit.

Grading Guidelines

1.      (-10 points) Miscellaneous mistakes/problems.

2.      (-10 points) Assignment not submitted according to specifications. For example, your name is missing, incorrect email subject, hardcopy not turned in, etc.

3.      (-10 points) Bad interface. For example, output is not displayed for long enough for the user to read it, user has to guess what the input is, etc.

4.      (-10 points) The program doesn't work as expected for some values.

5.      (-20 points) Program crashes with bad user input. We will test boundary conditions and bad conditions when testing your programs.  For instance, if your program asks for a number between 1-10, we will try inputting things like: -3, abc, 11, and 99999 to see if your program handles it, and asks for input again.

6.      (-20 points) The program doesn't compile or crashes (has runtime errors), because of a small syntax error. 

7.      (-30 points) The program doesn't work as expected for any values.

8.      (-30 points) Code not commented. Comments should be IN YOUR OWN WORDS. You should comment at every 3-5 lines of code.

9.      (-30 points) Not following the ICS 111 Java Coding Standard.

10.  (-40 points) The program doesn't compile or crashes (has runtime errors), because of numerous syntax errors.

 

© 2007 William Albritton