Anne
Dawson: CSCI102A_FA_SP04.htm
First
created: Wednesday 24th March 2004, 12:14 PT, AHD
Last updated: Monday
29th March 2004, 10:06 PT, AHD
This document is subject to change without notice.
Please
report any errors or omissions in this document:
adawson@coquitlamcollege.com
Special instructions: For
this assignment you may work in teams of 2, or alone.
This lab is due at the start of the last class of the semester.
Final
Assignment Specification
------------------------------
You
will write a college management system (CMS.java). The system is based on the
classes of StudentNode.java and StudentNodeLinkedList.java. The StudentNode
class should be amended to include the following instance variables:
studentNumber
(a String of 8 characters length, e.g. "00123456"
courseCode
(a String of 8 characters length, e.g. "CSCI110A"
quiz1
(an integer in the range 0 - 100)
quiz2
(an integer in the range 0 - 100)
midtermExam
(an integer in the range 0 - 100)
finalExam
(an integer in the range 0 - 100)
(the
latter 4 instance variables replace the instance variable score in the original
class)
When
the CMS runs, a menu is displayed:
1. Add a new student
2. Delete a student
3. Display a student's details
4. Enter a score
(For bonus points)
5. Write all details of
all students to a text file
6. Quit
Notes:
For Option
1, students are added to the list in alphabetic order by last name of student.
For
Option 2, the user enters the student number of the student to be deleted.
Submission
instructions:
-----------------------
This
assignment is due at the start of the last class of the semester (Week 13 Class
2).
You
should save your source code files to your folder in CSCI102A\Week13\FA.
If you
are working in a team, both team members save the same files to their own
folder.
Marking
Scheme
--------------
The
following marking scheme applies:
Course
Code: CSCI102A
Semester: SP04
Assignment
Code: Final Assignment
Lab
Specification: CMS
Instructor
Name: Dr Anne Dawson
Student
1 Name:
Student
1 Number:
Student
2 Name:
Student
2 Number:
DESIGN
1. The program has appropriate modularity
i.e.
methods are used where it makes sense to
use them. /10
2. Appropriate data types are used. /10
3. Appropriate control structures are used
(i.e. loops and decisions). /10
4. The User Interface (output to the screen) is
clear and tidy. /10
MAINTAINABILITY
5. The program is commented appropriately -
including
date, filename and pre- and post-condition
comments. Comment for javadoc, and run
javadoc on
your .java files. /10
6. The program has meaningful identifiers. /10
7. The program is indented (spaced out)
correctly, to
aid the understanding of the code. /10
8. The code is easy to follow. /10
CORRECTNESS:
9. The program compiles with 0 errors and 0
warnings. /10
10. The
program runs as intended. /10
%
Complete:
Bonus:
Total: /100
Date: