CSCE 4813 - Homework 1
Due Date - 02/22/2011 at 11:59 PM

1. Problem Statement:

The goal of this programming project is to give students exposure to the OpenGL library for rendering images, and also some experience building geometric models of every day objects. Students should start with the sample program "office.c" which contains functions for drawing 3D blocks, and tables and book cases using these blocks.

Your first task is to design geometric models for other TWO additional office items out of 3D blocks (eg. desks, chairs, file cabinets, office partitions). Then write functions to display your office items at specific (x,y,z) positions, with one or more size parameters. Use the "table" and "book_case" functions as examples.

Your second task is to modify the "display" function to create an office with 5-6 objects in different locations in the room, by calling the functions above. This may be a little tricky because we have not spoken about rotating objects into different orientations. Just do the best you can given the default orientations.

2. Design:

The primary design task for this assignment is in object modeling and in office modeling. You may want to work with 2D front/side/top view diagrams of your objects to figure out the relative sizes and positions of the blocks in your object. The office design will probably need some trial and error work to get things looking like you want.

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.