Design Document Grading

Team: DNA

Grade: (99 out of 100)

High-level architecture (29 out of 30)

• static description (box-and-line type diagram, or suitable substitute): OK, good.
• dynamic description (Can I tell how the system executes over time?) Sixth bulleted item in this section says "A file that store the ..." Should be "stores".
• use of standard or understandable notations (If using a standard notation, cite the notation; otherwise use a key to help the reader decipher the diagram) OK

Architecture rationale (20 out of 20)

• Is every functional requirement listed and justified? If specific functional requirements are not justified, has the team argued for why that requirement has been ignored (lack of time; technically infeasible; shift in priorities) All accounted for.
• Is every non-functional requirement discussed in terms of how it is impacted by the architectural decisions? Yes, good rationale for the separation of fractal generation onto another machine. You might also want to add in that it was because of this separation that you had to use the procmail invocation method.

Design specification (30 out of 30)

• module/class definitions (identified, interfaces provided) You should show the format of the submit command in the HTML form. I cannot understand from your description what the color maps are used for. Also, do you mean that there are 9 color maps for EACH image or just 9 color maps in total (one for each image)? Not clear from your text.
• use of standard or understandable notations Lots of code templates/header files and plenty of explanatory text. Absolutely superb!
• completeness (Is every part of the architecture covered?) Very thorough.

User Interface (20 out of 20)

• where relevant, is the human interface well-defined? Yes
• evidence of UI design (screens, drawings, etc.) Yes, well done.