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.
The goal of this assignment is to create buildings of different sizes and randomly position them on the surface so they do not intersect each other. The following assignment will complete the final two tasks to create "Monopoly Town" program.
Your first task is to create a "building" function that displays a simple building at a specified (x,y,z) position and with a known size in the (x,y,z) dimensions. This task is similar creating new office furniture. It would be nice if your building had a pitched roof of some sort, and perhaps some doors and windows (which can be implemented using different colored polygons).
Once you have a building function, you need to call this function N times to put buildings at random locations on top of your surface. The odds are high that two or more buildings will intersect each other. To prevent this from happening, you need to store the locations of buildings as they are placed, and check this data structure before you add each new building.
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.
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.
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.
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.