From: Janet Davis (jlnd_at_cs.washington.edu)
Date: Thu Jan 15 2004 - 14:03:35 PST
On Thu, 15 Jan 2004, Eileen Hash wrote:
> So I'm just curious what kind of information we should put in the design
> decision writeup. Specifically, how much information do you want about
> the decisions we put in? Do you want a basic list of decisions? Detailed
> information about all the alternatives and an explanation for why we
> didn't pick them? Something in between?
>
> I initially interpreted it as a basic list of design decisions without
> any explanation for why, and then used #5 in the writeup to examine one
> in detail. I'd appreciate being corrected if necessary :)
The main thing I want to see here is the list of design decisions you
made, and for each, why you chose the alternative you did.
The fact that you had to make a decision implies there is more than one
alternative. There's no need to explain all the alternatives in detail,
unless you feel it's necessary to justify the alternative you picked.
For instance, if there is a tradeoff between two alternatives, you should
explain what the tradeoff is.
For a guideline, I was able to jot down a design document in about half a
page.
In contrast to the design document, question #5 lets you think about
alternatives beyond the scope of the assignment, such as adding new fields
to the Packet class, adding a new protocol, changing the rules of the
protocols we have specified, changing the interaction between Fishnet and
your code, and so on. You can also go into greater detail about something
within the scope of the assignment.
By the way, at least one person has asked if we expect one writeup per
person or one per group. We want one per group.
Cheers,
Janet
-- Janet Davis jlnd_at_cs.washington.edu http://www.cs.washington.edu/homes/jlnd/ _______________________________________________ Cse461 mailing list Cse461_at_cs.washington.edu http://mailman.cs.washington.edu/mailman/listinfo/cse461
This archive was generated by hypermail 2.1.6 : Thu Jan 15 2004 - 14:03:38 PST