Second Design Document
A modified design document specifying the current design of toonces
is due on Wednesday, October 30, at the beginning of class. This
document should include a set of requirements, what you will
require toonces to do. Ideally this would have been written
before the fact, not after the project is underway. In the requirements
section you should specify what toonces is required to deliver
in terms of functionality.
The design should represent class relationships as they exist in your
current toonces framework and as you expect them to evolve.
You should include complete descriptions of your member functions and
classes. Ideally this will be done using the java.doc
facility of generating HTML documents directly from Java source (see the
Nuthsell book and online Java resources).
C++ versions of toonces
Each group must submit a C++ version of toonces. This program should be
able to read a file of appointments and print either an ASCII or HTML
calendar based on the appointments in at least monthly and yearly
formats.
The C++ program will account for 20% of the toonces grade.
Due Dates
Toonces programs will be demo'd in class on November 4. The demo should
be an advanced prototype. Programs may be demo'd again on Nov 8, but
will be due on November 11 with supporting documentation and user
manual/man pages.