Assignment#3
Due Date: Friday, March 18 (at start of class)
In this assignment you are (teams of 5) to write an X page long (I am not
going to specify a number as it will depend on the number classes, ...etc,
of your system) Object Design Document (ODD) for the assignment submission system. Download
the following template (Object
Design Document). Use this template as a guideline for the tasks that
need to be done for this assignment. And as always, the format (fonts,
etc) of this template is not consistent, so make sure the format of your
final document is consistent.
Start by meeting with your group members and distributing the work. Each
person's work should be reviewed by at least one other person
in the group, and be prepared to merge and check your work with other group members. At
the end, the document must be consistent in
terms of formatting and, more importantly, concepts used throughout the
document. On March 18 (at start of class), hand in your
document (printed version and the rest of the packages on disk), ALONG
WITH the REVISED Requirements Analysis Document and System Design
Document, enclosed in a binder.
Marking Scheme: you will be marked out of 50 according to the
following scheme:
- 3 marks: spelling (use a spell checker)
- 4 marks: aimed at the correct audience and understandable by them
- 3 marks: concentration on object design and implementation details
- 4 marks: precise description of the object design goals and
trade-offs. Make sure they are clearly stated
- 4 marks: coding conventions
- 6 marks: final class diagram(s)[show associations and multiplicities]
- 5 marks: package diagram
- 12 marks: description of packages, classes, methods, ...etc. This
information should be generated by javadoc (classes, methods, etc must have full detailed
description using javadoc)
- 2 marks: consistent terms throughout the document. Make sure all
terms used by different team members are
consistent. If javadoc comments are being written by more than one person
(and that is going to be the case), make sure the terms used
are consistent. Consider adding new terms to the Glossary of Assignment#2
and moving that Glossary to the end of this document. Make
sure you hand in the revised Requirements Analysis Document AND
System Design Document.
- 3 marks: changes AND description of changes made to the Requirements
Analysis Document in the appropriate place (e.g. revision
history)
- 4 marks: changes AND description of changes made to the System Design
Document in the appropriate place (e.g. revision history)
If you have any questions, please see me during my office hours or send me
an email (allow 2 days for a reply).
© Qusay H. Mahmoud