SeattleTestbed / attic

ARCHIVAL: Full mirror of SeattleTestbed's SVN in early 2014. We use GitHub since!
MIT License
0 stars 1 forks source link

MapReduce assignment documentation #263

Closed choksi81 closed 10 years ago

choksi81 commented 10 years ago

The Lisping strike force produced the code and a report on a Seattle MapReduce implementation. An important next step is to create the appropriate documentation that will enable a student in a distributed systems course to recreate a map-reduce implementation by following the assigned steps.

This assignment should be composed of, at a minimum, of 3 steps. Each one should clearly state the goals/deliverables, define the appropriate interfaces, and outline how achieve those goals.

choksi81 commented 10 years ago

Author: alpers This was done here and added to the assignments page about a week ago.

choksi81 commented 10 years ago

Author: ivan At the moment the page is a rough description of a project that provides no details on how to actually get it done.

This page needs to be an assignment in that the students have an easy to follow set of step-by-step instructions that describe not only what the big picture is, but also specify the interfaces (API) to their code, the functional parts/modules of their code, the protocols they should implement, etc

An example of this type of writeup can be found here: http://www.cs.brown.edu/courses/csci1380/projects/chord.pdf

choksi81 commented 10 years ago

Author: justinc Milestone Map Reduce v1 deleted

choksi81 commented 10 years ago

Author: justinc We're abandoning this implementation. As a result, this work would likely need to be redone...