Sample Design Documents
Here is a collection of Design Documents produced in earlier 3302
class taught by Dr. Abowd. These should help you get a feel for what makes
up a good design document for this class.
NOTE: These previous design documents did not have a
section entitled "Architecture rationale". This is a new wrinkle in
3302 this quarter. Unlike previous quarters, there is no requirement
to reproduce the project description in this document.
-
Spiderman
Overall good document. Clear architecture (though it could probably be
contained in a smaller space and still be legible).
-
Frozen Foto Gallery
Good high-level architecture, reasonable design specification, though
a bit low on detail.
-
Scooby2beDue
Very detailed design specification and thorough architecture
specification.
-
Jestre
Excellent example of following a development method (in this case, the
Coad/Nicola technique from CS 2390).
- ChoZen
Architecture could be improved by
including all of ZenPad, but they do handle the pieces specific to the
Preference Manager. All else is very good.
- CyberTalk
Excellent rationale. The
architecture is almost perfect, but it is a bit confusing because they
limited the dynamic description and the design specification is a
little hard to understand because it is slightly unorthodox.
Some not so good examples.
- Wok's Up...
Architecture is
sloppily described, especially the dynamic part.
- CyberFridge
didn't have enough description of
client-side architecture (Terminal Browser). Didn't show how link
with existing database of information (FoxPro) fits into the picture.
Architecture rationale looks OK.
Gregory D. Abowd <abowd@cc.gatech.edu>
Last modified: Fri Apr 24 10:58:22 EDT 1998