CSCE 4813 - Homework 2
Due Date - 02/23/2012 at 11:59 PM

1. Problem Statement:

This programming project is a continuation of your first project where you created a simple building model. This time your task is to create an interactive program to let the user "click, drag and drop" to define the 2D line segments representing walls. Once the user has drawn a set of walls, they can go into "3D view mode" to translate and rotate the building model to see what it looks like. They should also be allowed to go back into "2D drawing mode" to add more lines. Your program does NOT need to have an interface to delete or edit lines -- save that feature for people getting paid to implement drawing packages.

Once you have the basic features above working, extend your program so the user can to read/write building models from/to ascii files. You need to invent a format that is easy for both humans and computers to understand. To test this format, you may want to use the building model from the first assignment and verify that you get roughly the same output image.

2. Design:

There are a number of design decisions you need to make. First of all, what keyboard commands will you use for different operations? How will you use the mouse operations to define line segments? What internal representation are you going to use to store your collection of line segments? Finally, what ascii file format are you going to use to store your building models? In your documentation, describe each of your decisions above, and provide a small users manual for your program.

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.

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 (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 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.