Project 3 Design
Due Date
- 11:59pm, Sunday, Nov 16, 2003
- No late designs accepted
Objective
The objective of this assignment is to make sure that you begin thinking
about your project in a serious way early. This will not only give you
experience doing design work, but will help you anticipate the number of
hours that you'll need to set aside to be able to complete the project.
The Assignment
Your design assignment is broken down into three parts.
- Class definitions.
In this section you will design each of the classes necessary for your
project -- the BankAcct, SavingsAcct, CheckingAcct and Check classes.
You will decide on the private and protected data for each class and each method that
the classes will provide. Basically you are writing your .h file for each
class.
- Function prototypes for functions which are not part of any class.
Any function used by main() that is not part of class (ie PrintAllAccts())
should be specified here.
- A list of tests you plan to perform to verify that your program works properly.
A template for your design document, p4design.txt,
is provided in Mr. Frey's public directory. Copy that file
<![CDATA[
/afs/umbc.edu/users/d/e/dennis/pub/CMSC202/p4/p4design.txt
]]>
to your local directory and fill in the necessary information.
Submit your modified p3design.txt file to complete this assignment.
Grading
You p4design.txt file will count as 10% of your Project 3 grade
(part of the Correctness). If this file is not submitted by its due date,
or if you submit a new version
after its due date, you will lose all 10 points.
Your p4design.txt file will be compared to the header file or files that you
submit when Project 3 is due. Minor changes to the design are allowed. A
minor change might be the addition of another parameter to a function's
parameter list, or the addition of another function or two.
If there are major changes between the design document and the header files
that are part of the final project, you will lose 5 points. This would
indicate that you didn't give sufficient thought to your design before
beginning the implementation.
If there are insufficient test cases, you will also lose 5 points.