Project 1
Spring 2004
Due: Feb 6 @ 5 PM
6 points
Design and implement the Person class. Persons have a name and social security number.
For storing information about undergraduate students, use inheritance to derive the UStudent class from the Person class. Undergraduate students have majors and grade-point averages.
Similarly, for storing information about graduate students, derive the GStudent class from the UStudent class. Graduate students have undergraduate degrees (e.g., BA, BS). Should they also have graduate majors and graduate GPAs, or should they inherit major and GPA from the UStudent class?
For each of these classes implement the necessary virtual and non-virtual methods. For example, Person::getSSN should be a non-virtual method, whereas the print() method should be virtual. There are other interesting design questions, such as whether GStudent::gpa should be different from or should override UStudent::gpa. These are issues we should discuss in class.
Design and implement the Students class, which uses a C++ vector to store information about persons (i.e., undergraduate and graduate students). Implement methods to read students from a file, print students in the vector, and compute the average GPA of those students.
Design a file format for a class, which stores information about students enrolled in a hypothetical class. Fabricate data for three undergraduate and three graduate students.
In the main function, write a simple driver program that reads students from a data file, prints the students to the console, and prints the average GPA for the students.
Use stepwise refinement and incremental development. For example, implement the Person class and test it thoroughly before implementing the UStudent class.
You must provide a working UNIX Makefile with your submission. Start with this Makefile, which compiles a project consisting of main and person.
All class definitions and class methods must be documented with Doc comments. Doc comments for class definitions must include @author and @version tags. Doc comments for methods must include @param and @return tags, where appropriate.
Instructions for Electronic Submission: At the top of the file main.cc (or the file containing the main function), place the following header comment, with the appropriate modifications:
// // COSC 072 Project 1 // Name: <your name> // ID: <GoCard ID> // E-mail: <e-mail address> // Instructor: Maloof // TA: <TA's name> // // In accordance with the class policies and Georgetown's Honor Code, // I certify that, with the exceptions of the class resources and those // items noted below, I have neither given nor received any assistance // on this project. //
Although you may use any C++ compiler to develop your program, it must run under UNIX and must compile using GNU g++. You must also provide a working UNIX Makefile for your project.
Place all of your code in a subdirectory named p1. To create this subdirectory, type
gusun% mkdir p1To descend into the directory, type
gusun% cd p1All of the files for your project should be in this directory.
If you need to include a message to your TA about your submission, then place the message in a file named README. Place the README file in the project's directory.
Before submitting, to reduce the size of the zip file, type 'make clean'.
To move up from the p1 directory, type
gusun% cd ..(Additional UNIX commands at the bottom of this page: HOWTO Compile under UNIX)
When you're ready to submit, change the name of the directory to your netid. For example, if your netid is maloofm, then rename the directory p1 by typing
gusun% mv p1 maloofmCreate a zip file of the directory and its contents by typing
gusun% zip -r p1.zip maloofm/*This command creates a zip file named p1.zip by recursively (-r) copying all of the files (*) from the directory maloofm/.
To submit the zip file type
gusun% submit -a p1 -f p1.zipp1 is the name of the assignment (-a) and p1.zip is the file (-f) to be submitted for that assignment.
If the program submits the file successfully, you will receive a receipt by e-mail at the address <netid>@georgetown.edu.
Submit your project only once.
Once you've submitted your project, it is important to keep an electronic copy on a university machine (e.g., gusun or cssun) that preserves the modification date and time. If we lose your project or the submission system breaks, then we will need to look at the modification date and time of your project to ensure that you submitted it before it was due.
You can also change the directory's name back to the original name. For example,
gusun% mv maloofm p1Note that changing the name of the directory does not change the dates of the files in the directory. You can also remove the zip file from your directory:
gusun% rm p1.zip
The TAs who will be grading your projects this semester are listed on the main page. You must submit your project before 5 PM on the due date.
If you're running submit correctly and you see an error message labeled as SEVERE, then execute Plan B by using pine to submit your project as an attachment to an e-mail.
To accomplish this, at the gusun prompt, type 'pine'. When the menu appears, select the menu item for composing messages (C). In the To field, type the e-mail address cosc072maloof@cs. Attach your zip file. Control-T (symbolized ^T) will give you a list of files. Select the file to attach. The subject should be your netid followed by the extension .zip. For example, if your netid is maloofm, then the subject of the e-mail should be maloofm.zip. There's no need to include anything in the MESSAGE TEXT screen.
Once you've entered this information, the screen should look something like the following:
Finally, type ^X (Ctrl-X) to send the e-mail to the course account.