Baseline Programming Process Script

To guide a programmer in the collection of basic process measures (in as unobtrusive manner as possible) that can serve as a baseline for future improvement efforts.

A Unix development environment with an installation of BlueJ ver 2.5.3 with the Compile Logger extension.
An Archive folder exists as a subdirectory of .bluej.
A Solutions folder exists as a subdirectory of CSC301.
Before you launch BlueJ, delete the bluej-compilelog.txt file.
A printed copy of the Baseline Time Log.
The requirements for the programming assignment.

Enter your name in the header of the Time Log form.
Enter the program identifier, name, and the date you begin work in the first three fields.
Enter the start time.
Read the assignment requirements and create a solution.
Implement the solution in Java using the BlueJ IDE.
Test your solution using a driver, JUnit, or Web-CAT as specified in the assignment.
When your solution is complete, exit BlueJ (in order to save the compile log).
Print the source code, test data and output. Place these in your binder along with any other artifacts you produced.
Record stop time in the data form.
Save the form in your binder in front of the source code and other listings.
Copy only the java source code file into your Solutions directory. Rename it programXX.java where XX is the program identifier.
Move bluej-compilelog.txt to your Archive directory. Rename it bluej-compilelogXX.txt where XX is the program identifier.
Login to vogon.csc.calpoly.edu using the Linux Terminal (or Secure Shell for Windows).
If you are not in the CSL, upload your source code file and compile log file.
On vogon, use the handin commands shown below. Spell your file names exactly as shown, where XX is the program identifier.

handin graderjd XX

programXX.java

handin graderjd XX bluej-compilelog

XX.txt

Version 1.2 4/6/2010