CSCE 5013 - Homework 1
Due Date - September 8, 2011 at 11:59 PM

1. Problem Statement:

The goal of this programming assignment is to develop a program to locate and identify circles and rectangles in a black and white JPEG image and calculate geometric properties of these objects. Your program should print out the center and radius of each circle, and the minimum and maximum (x,y) coordinates of all rectangles.

2. Design:

Input images will be synthetically generated such that the circles and rectangles do not overlap each other, but they may overlap the boundaries of the image. If this happens, a circle will appear to be chopped off whereas a rectangle will just look like a smaller rectangle touching the boundary.

Students are expected to use the "libim" and "libjpeg" libraries provided in the class website under the "Source Code" link. If you copy the src.tar file to any Linux machine, you can compile the libraries and the example.cpp program as follows:

tar xvf src.tar
cd src/jpeg
make all
cd ../libim
make all
cd ..
make example

Running the example program will create three random test images. One with only circles, one with only rectangles, and one with both circles and rectangles. Students should write their program to look for one of these geometric shapes in an image, and test the program with the corresponding input images. Once this is working, students can add code to locate and identify the other shape and test the program with all three input images.

3. Implementation:

You can implement this program using either a bottom-up approach or a top-down approach. If you go for a bottom-up approach, start by creating basic methods and classes, and test theses methods using a simple main program that calls each method. When this is working, you can create the main program that uses these methods to solve the problem above.

If you go for a top-down approach, start by creating your main program that reads user input, and calls empty methods to pretend to solve the problem. Then add in the code for these methods one at a time. This way, you will get an idea of how the whole program will work before you dive into the details of implementing each method and class.

Regardless of which technique you choose to use, you should develop your code incrementally adding code, compiling, debugging, a little bit at a time. This way, you always have a program that "does something" even if it is not complete.

When you think you are about 1/2 way through the program, upload a copy of your source code and your program output at that point. Be sure to hand in something that compiles even if it does not do much when it runs.

4. Testing:

Test your program to check that it operates correctly for all of the requirements listed above. Also check for the error handling capabilities of the code. Try your program on 2-3 input documents, and save your testing output in text files for submission on the program due date.

5. Documentation:

When you have completed your C++ program, write a short report (1-2 pages long) describing what the objectives were, what you did, and the status of the program. Does it work properly for all test cases? Are there any known problems? Save this report in a separate text file to be submitted electronically.

6. Project Submission:

In this class, we will be using electronic project submission to make sure that all students hand their programming projects and labs on time, and to perform automatic analysis of all programs that are submitted. When you have completed the tasks above go to the class web site to "submit" your documentation, C++ program, and testing files.

The dates on your electronic submission will be used to verify that you met the due date above. All late projects will receive reduced credit (50% off if less than 24 hours late, no credit if more than 24 hours late), so hand in your best effort on the due date.

You should also PRINT a copy of these files and hand them into your teaching assistant in your next lab. Include a title page which has your name and uaid, and attach your hand written design notes from above.