(copy to editor, edit, hand in to appropriate asgns directory with
filename AUTHOR_by_REVIEWER.txt).  Comments should be constructive and 
addressed to the author.

Requirements Author: Dominic Latty
Project Title: BookFinder ??
Reviewer: Colin Stebbins Gordon

Evaluate the following criteria on a scale from 1-5.  Add comments after each

OVERALL EVALUATION (1-5):
USEFUL TO OTHERS: 4
I'm not actually convinced it's *that* hard to find a book in the Rock or SciLi
- usually when it's become difficult, it's as the result of misshelved books.
HAS SPECIFIC USERS: 5
All patrons of the Rock.
CAN BE SCALED UP TO PC-SCOPE PRODUCT: 3
Iffy.  It can certainly be extended to be flexible enough for other libraries,
but the amount of work that would be required to adjust it to a new library
would be significant.  Certainly more than most library administrators would
want to do, so it would probably need to be attached to some sort of
setup/update service to be a reasonable commercial product.
DIVISIBLE: 5
Database, filling the database, pathfinding, GUI, Josiah integration.  Seems
reasonable.
WELL DEFINED ENOUGH TO IMPLEMENT: 4
Well defined enough to implement *something,* but most of the details of both
user and update UIs are left unspecified.  Particularly updates to the stack
list.
IN C++ ON LINUX: 3
This seems betters suited for a more traditional webapp language (Perl, PHP,
Python, Ruby), except for the path finding algorithm if it turns out to be too
slow for those languages.  I suspect that it would be fine to do pathfinding not
in C++, though, because the floors of the Rock aren't actually that big.

are sources clear for requirements?
The librarians.

is are there good criteria for testing?
Other than looking up some books and checking directions, I'm not sure.

Other comments:
Books will shift between adjacent stacks fairly frequently as new books are
added - so the update interface has to be very usable, at the very least for
this task.

================================================================

Additional comments/changes after presentation: