Richard G Baldwin (512) 223-4758, NRG Room 4238,,

ITSE2317 Java Programming (Intermediate)

This material applies to classroom sections and Distance Learning sections including APT sections taught by Professor Baldwin.

Instructions for Downloading and Submitting Assignments

Spring 2014

Revised: 01/11/14

The official web page for this course is ITSE2317.htm


This document may be modified as the semester progresses in order to incorporate new instructions or clarify existing instructions. Therefore, you should review the instructions periodically and then immediately before submitting each assignment to confirm that you are in compliance.

Failure to comply with the instructions usually results in a failing grade for the assignment, often zero.

The assignments for this course are take-home assignments. You may use any reference material that you have available. However, you are instructed not to obtain assistance from anyone.

The procedure for submitting assignments in the JSP portion of the course is significantly different from the procedure for submitting assignments in the Generics and Event Handling portions of the course. Therefore, this document has one major section for Generics and Event Handling (Asg01 through Asg08) and a separate major section for JSP (Asg09 through Asg12). Make certain that you understand and adhere to the instructions for the specific assignment that you are submitting.

Generics and Event Handling Assignments

This section contains instructions for the Generics and Event Handling portions of the course (Asg01 through Asg08).

Downloading Assignment Files

Assignments are posted in Blackboard. There is a zip file associated with each assignment that you can download from Blackboard. The zip files have names like, ...

Format of Downloadable Zip File

Each of the zip files contains the following material as a minimum:

Each assignment requires that you write one program. Open the ProjXX.htm file in your browser to view the programming specifications for the assignment.

Don't use NetBeans, Eclipse, or other high-level IDEs for Generics and Event Handling Assignments

NetBeans, Eclipse, and other high-level IDEs are excellent productivity tools for programmers in the workplace who are working on large projects, who know exactly what they are doing, and who have a need to become more productive in their programming efforts.

However, with the exception of the JSP assignments, in order to write the simple programs required for this course, you should need nothing more sophisticated than a text editor (preferably with Java syntax color coding) and the Oracle Java Development Kit (JDK). You shouldn't need a high-level IDE to serve as a crutch to help you write these simple programs. The use of a high-level IDE to write the programs required for this course is overkill, can lead to problems, and is not recommended.

(As you will see later, NetBeans is the recommended tool for writing the JSP assignments.)

Special Instructions Regarding the Submission of Assignments

You may submit each assignment up to two times before the deadline explained in the syllabus. Your highest score among the two scores for each assignment will be used to compute your final grade.

Each assignment requires you to write one Java program.

Your name

Your name is required one or more times in the output for every program and the program specifications will indicate where your name must appear. If there is any confusion as to where your name must appear, please discuss this with me at least one week prior to the assignment deadline. (If your name does not appear, I will assume that the material that you submitted does not constitute your own work and you will not get credit for the assignment.)

Separate class and interface definitions

Every class definition (including the driver class that I provide) and every interface definition must be contained in a separate source code file with an extension of .java. Give the file the same name as the class or interface that the file contains.

Each such file must include any required import declarations.

None of the files may include a package declaration.

Submit source code files only

You must submit only your Java source code files encapsulated in a zip file. Do not submit class files. If you do submit them, they will simply be overwritten when I compile and execute your programs.

Your name in the zip file

Include your name in the name of the zip file that you submit to help me avoid getting your zip file mixed up with another student's zip file when I retrieve them from Blackboard. A suitable example file name is:

Do not submit my driver class files

Do not submit files named,,, ... I already have them. I don't need them, I don't want them, and allowing them to be included in the zip file has caused major problems for some students who failed to separate their class and interface definitions into separate files.

Code compatibility

The source code files that you submit must contain code that is compatible with the version of Oracle's JDK installed in the NRG laboratory on the due date of the assignment. Among other things, this means that your source code must be compatible with the 64-bit version of Oracle's JDK 7 ( or later.

Testing your programs

Don't rely on the DrJava IDE (or any other IDE) to test your programs. Test your source code for each program from the command line using Oracle's javac.exe and java.exe programs to confirm that your programs conform to the program specifications before submitting your assignments.

To avoid possible class file problems, delete all of the class files produced by one version of your program before testing the next version of your program or before testing your next program.

No partial credit

I will score your programs from the Windows command line. (In case you develop under a different OS, make certain that your programs are compatible with the version of Windows installed in the NRG computer labs.) Each program will be graded either right or wrong. Partial credit will not be given for source code that does not fully conform to these instructions and to the program specifications. If one of your programs doesn't conform, don't bother submitting it.

Grading criteria

Each program requires you to use (without modification) a controlling class and/or other code that I have provided (file named and to duplicate the screen output shown while meeting all other written specifications. Any modification of the code that I have provided will be grounds for disqualification. (The zip file that you will download from Blackboard contains a Java source code file named for the driver class for each program. Use it without modification.)

My grading procedure

After copying your source code files into a folder identified by YourName on my M-drive , I will test your program by executing a batch file containing code in that folder similar to the following:

copy ..\_Solution\

del *.class
java Proj01

What does this mean?

In case you don't understand what the code shown above means, (and you have aspirations of becoming a computer programmer), it is time for you to do the necessary research to learn what it means.

Briefly, it means that I will copy my version of into the folder identified by YourName, overwriting your file, if any, having the same name. Then I will attempt to compile and execute the program using the required version of Java.

Failure to follow instructions

If you modified the code in the file named or you failed to separate your class and interface definitions into their own separate files when you wrote your program, it is unlikely that your program will compile and execute successfully under the procedure given above.

Run my class files

In all cases I will provide you with the set of class files produced by my version of the program so that you can run my version to observe the output. I recommend that you run my version (from the command line) side-by-side with your version and compare the two.

You must match the specified screen output in every significant way for every program. Extraneous characters on the screen, extraneous images that are not shown in the assignment specification, extra blank lines, missing blank lines, different colors for output images, etc., are grounds for disqualification. In other words, your output must be an exact image of the specified output.

You must also match the visual and operational aspects of my version in every significant way such as: shape, size, color, shading, labels, interactivity, etc. If they don't match, your version is not correct.

Every semester there are one or two students who are surprised and saddened to learn that I really do mean that you must follow the instructions and meet the specifications exactly or you won't get credit for the program. Don't be one of those students.

Output Visual Format

Different versions of Windows or the same version of Windows with different appearance options produce slightly different visual output formats for the same program. The images shown in the files named ProjXX.htm correspond to only one version of Windows and one set of appearance options.

As of this writing, the ACC computer labs are running Windows 7. Many of you (and myself included) may still be running Windows XP or Windows Vista at home.

In any event, if you run my solution and your solution side-by-side, the same appearance options will be applied to both outputs, which may cause both outputs to look somewhat different from the images in the files named ProjXX.htm. As long as your output matches my output, it is okay if they both look somewhat different from those images.

Recommended Study Procedures

You should study all of the material in the following sections of my e-book titled Object-Oriented Programming (OOP) with Java.

(A collapsible index to all the modules in the e-book appears on the left side of the page.)

Note that some of the material in the above list contains links to other material at or elsewhere on the web. That other material is also included in the recommended study material.

Submitting Your Assignment

Submit your assignment using the Blackboard Assignment feature.

Although I am unable to see the student's view of the Blackboard interface, the following instructions should be approximately correct.

If I am unable to successfully unzip the file that you submitted, or if it contains the wrong material, you will not get credit for the assignment.

The assignments require you to write programs and to submit the resulting source code files. The completed programs must satisfy the requirements described earlier in this document and the individual specifications that apply to each program.

Extraneous Material

Do not allow your programs to display screen images that do not appear in the assignment specifications. If you do, you won't get credit for the programs that display extraneous images

Do not submit extra files such as readme.txt files and expect me to pay attention to them. I won't pay attention to them.

Don't expect me to pay attention to text that you may choose to enter into the Blackboard Comments field when you submit your assignment file. I am not interested in them, and I won't pay attention to them.

Do not put comments in your source code and expect me to pay attention to them. I am not interested in them, and I won't pay attention to them.

Do not submit javadoc documentation for your programs. It causes the zip file to be very large and I don't need it.

The required material

All I expect to receive from you when you submit your assignment is the set of required source code files. (In many cases, there will only be one source code file with a name like There is no reason that you will need to communicate any information about your assignment to me when you submit it. Any need to discuss the requirements of the assignment must be satisfied prior to your submission of the assignment.

Encapsulate an electronic copy of the required material in a zip file and submit it as a Blackboard assignment, not later than the deadline given in the syllabus. If you are running Windows, you don't need a special program to create the zip file. The Windows file compression utility is entirely adequate.

The zip file must be one that I can unzip using the Windows de-compression utility with no effort required on my part other than to open the file and extract the material contained therein. There must be no requirement for any sort of special decoding. If there is such a requirement, I will not accept the assignment.

JSP Assignments

You may submit each assignment up to two times before the deadline explained in the syllabus. Your highest score among the two scores for each assignment will be used to compute your final grade.

Each program will be graded either right or wrong. Partial credit will not be given for programs that do not fully conform to these instructions and to the program specifications. If one of your programs doesn't conform, don't bother submitting it.

For detailed instructions regarding the JSP assignments, do the following:

Failure to Meet the Submission Deadline

The submission deadline for each assignment is provided in the Syllabus each semester. In most cases, the assignment will expire and disappear from Blackboard when the deadline passes.

The penalty for failing to meet the submission deadline is simply that you won't get credit for the assignment.

Before you ask, let me tell you that a temporary Blackboard outage, business travel, problems at work, extreme work pressures, divorce, depression, receipt of a "Dear John letter", automobile repairs, flat tires, computer problems, power failures, total eclipses, extremely high outside temperatures, high pollen count, broken lawnmowers, the Super Bowl Schedule, and other assorted and interesting circumstances are not valid excuses for failing to meet the submission deadline. About the only excuse that I might be willing to accept would be something on the order of extended hospitalization or extended serious illness on the part of you or an immediate member of your family. If your excuse is not on that order of magnitude, I really don't want to hear it.


File: ITSE2317AsgInstructions.htm