Introduction

You have been hired as an intern by a really big company to help develop the next great operating system. You have just been assigned to the group working on next generation graphics application programming interfaces (API), a part of the larger application framework group.

By listening to customers about their usage of the currently existing graphics API, this group has managed to come up with a small prototype graphics API that they think could help alleviate the two major concerns of current users: ease-of-use, and lack of object oriented-ness. The group wants you and a partner to develop something cool to show that in fact they've been able to meet these goals. The framework is available.

Partners

The group is highly team-driven, and highly encourages you to partner up with one (and only one) other person for this particular project. However, they do understand that you may not wish to work with a partner, and so it is permissable to do this project alone. Note that you must notify your immediate supervisor (your TA) as soon as possible as to whether or not you'll be partnering up, and with whom. While it is preferable for your partner to also have the same supervisor, so long as your TA agrees, you may partner up with another person with a different TA.

Graphical API

The graphical API is available as a zip file and as a self extracting executable. The system can be compiled and run. A sample world file is provided which instantiates various draggable objects.

More information about the graphical API is available in Word 97 format , rich text format (rtf) and in Acrobat format (pdf file), or by simply clicking here.

Deliverables

Your team is required to make at least 2 classes that perform interesting activities. At least one of the classes must be interactable with the user, and at least one of the classes must interact in some interesting way with other objects in the world.

Tuesday, March 9, In Section

1. You will be required to hand in a chart during section that shows the relationship between classes in the Object hierarchy, in terms of super/sub-classing. You need to also state on the chart which classes require what methods to be overriden by subclasses (as opposed to optionally overriden). Also, place the classes that you are building in the chart.
2. You will be required to hand in a paper documenting what classes you have chosen to design and what kind of behavior they will be exhibiting.

Friday, March 12, 1999, 6 pm

Electronic turnin is due. You will need to meet with your supervisor to show first-hand the progress you have made on this project. Sign-up sheets will be made available next week. You may turn in your paper copy to your TA at that time.

Submitting Your Program for Grading

When you have finished, go back to the main homework 5 page and follow the directions for turning in your homework.

Fine print

• Working in groups
  • You are encouraged to work in groups of two on this assignment.
  • You may do the assignment alone.
  • You may not work in groups larger than two.
  • We would prefer you to work with a partner who has the same TA as you have (but this is not a requirement).