|
In class on Tuesday, we discussed a high level
architecture for the final project application,
and broke it up into several high-level tasks:
- Hardware: Andrew and Dan
- Network health: Nikita and Shi-Hua
- Escape paths: Manan and Xin (and Neil?)
- Tools: Slava and William
- Scripting/language support: Kaisen
If I incorrectly remembered who signed up for what,
let me know as soon as possible, please.
Assignment
As a group, write up a short proposal of (1-2 pages of text)
how you are going to approach your part
of the project. The document should have five parts:
Problem Statement: You should clearly, in one
paragraph, state what the purpose of your part of the
project is. What are its requirements? What is the
problem you are trying to solve? Mention the tradeoffs,
such as traffic vs. rate, and how you will approach them.
Design: Give a high-level design of how you
are going to meet the requirements you stated in the
previous section. For example, describe a high-level
algorithm for a protocol, or include a concept picture
of what a GUI will look like.
Dependencies: Are you going to depend on other
groups for your part to work? How so? What do you expect
others to provide? Think about this carefully, so it doesn't
turn out that two groups both expected the other to
be responsible for a critical part of the system
functionality.
Goals: Specify a minimum set of requirements
that your part of the system must meet for it to
be considered operational. Include several ways in which
it could be improved from this bare-bones version. Although
it's unlikely that you'll be able to achieve all of them,
you should be able to achieve some of them.
Questions: If thinking about your part of
the problem has raised questions which affect other groups
(and should be discussed in class), include them here.
Handing in
Email your proposal to Phil.
|