Here are my thoughts on the group projects for this class. I've divided them into two chunks, stuff that applies to all the groups and then a set of group-specific items. We'll talk about the projects in class on Monday March 22nd.
Make sure that you are covering the roles of scribe, toolsmith, and architect. For each project the details of a particular role will vary, this is to be expected. Each project does have a significant component of documentation, code/configurations/tools, and overall design.
Through-out the second half of the semester your project log should be available and up-to-date. I'll add links to them on this page when they are available. A text file in a location that's visable to a web server is as complex as the log needs to be. The important issue is using it as a tool to guide your work. As soon as you have published your log (and possibly other documents as well) send me the URL so I can add it here.
The highest grade possible is an A, the lowest an F. Printed copies of the documents will be due in class on the days listed above unless we agree to change a particular item as a group. Software will be turned-in via a pointer to a place where I can view/run it. Each day a particular item is late will cost about 1/2 a grade.
Your grade will consist of equal parts documentation, code or environment, and project log. Based on the log component I plan to have the ability to give each member of the group a grade rather than the same grade for each group member.
Route, filter, and choke inserted into design and build a network. Tested via this environment.
Design and build a network simulating mapping and monitoring's proposal for access to off-campus facilities.
Others?