Design Document Grading
Team: Jestre
Grade: (100 out of 100)
The following is a breakdown of the grading.
Document presentation (5 out of 5)
Important points:
- Organization: OK
- Document author: OK
- use of English: OK
Comments: Excellent job!
Project Description of Target System (5 out of 5)
Link to other documents? yes
Comments:
High-level architecture (30 out of 30)
- static description (box-and-line type diagram, or suitable
substitute): good
- dynamic description (Can I tell how the system executes over
time?): yes
- use of standard or understandable notations: not great, but OK
- completeness: OK
Comments:
Design specification (30 out of 30)
- module/class definitions (identified, interfaces provided)
- following a prescribed method (mainly for OO people) yes, well
done! Whoever taught you how to do such brilliant object-oriented
design? :)
- use of standard or understandable notations: yes
- completeness: pretty good
Comments: Now, how straightforward is it going to be to go from this
to the Java code?
User Interface (30 out of 30)
- where relevant, is the human interface well-defined? yes, and it
looks good.
- evidence of UI design (screens, drawings, etc.) OK
Comments:
If you wish to have your Design Document regraded, revise it
within one week of receiving comments. Be sure to maintain a link to
the original version of the Design Document in your notebook for
comparison purposes. To get a regrade, you must send e-mail to the
instructor requesting the regrade.