CSCE 4813 - Homework 5
Due Date - 04/19/2011 at 11:59 PM

1. Problem Statement:

In order to create our "Monopoly Town" program we must complete three tasks: 1) we must create buildings and position them on the surface, 2) we must calculate the surface normals for the surface and buildings, and 3) we must display the surface and buildings using smooth shading.

Your last assignment focused on the creation of a surface and placing random houses on this surface. The goal of this assignment is to make your "Monopoly Town" look nicer. To to this, you must create surface normals for your surface (and your houses) and use OpenGL smooth shading commands to specify material and light properties.

2. Design:

Your first task is to create and store the surface normals for your surface. This can be done using cross products of tangents on your surface. This is not too difficult, but there are special cases on the border of the surface that can be tricky to work out.

Your next task is to specify the lights and material properties in your scene. There are several programs in the src directory that you are welcome to look at for ideas and sample code. To make thinks interesting, try to use two or more different colored lights.

Finally, you have to modify your surface and house display functions to provide (x,y,z) coordinate of polygons, and the surface normals at these points. Again, there are several programs in the src directory to look at to help you with this task.

If you borrow sample code to rotate the viewpoint of your scene, you should be able to get several screen shots to show off your final product.

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 functions and classes, and test theses functions using a simple main program that calls each method. When this is working, you can create the main program that uses these functions 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 functions to pretend to solve the problem. Then add in the code for these functions 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.

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 screen shots and/or testing output in text files for submission on the program due date.

5. Documentation:

When you have completed your program, write a short report (less than one page 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 document 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" or "upload" your documentation, 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 instructor in your next class or put it his mailbox in the department office. Please print and include a copy of the programming project evaluation form as the title page of your report.