(copy to editor, edit, hand in to appropriate asgns directory with
filename AUTHOR_by_REVIEWER.txt)

Specifications Author: Dominic Latty
Project Title: Book Locator
Reviewer: Colin Stebbins Gordon

Evaluate the elements below on a scale from 1-5.  Add comments after
each as needed.  Copy in any text from the specification to make
appropriate comments.  Address comments to the author of the
specification.

	1) description of the project (from requirements);
	4
	Gives a good description of the project's purpose.  I don't like that
	the administrative interface is optional.  Short of that, there's no
	clear way to update the system as books move due to new acquisitions.
	Without an easy way to update maps, librarians likely will not update
	them, and the system's usefulness will degrade greatly over a (probably
	reasonably long) period of time.

	2) system model diagram;
	4
	The find-by-call-number tool seems superfluous, and why is it not
	directly related to the GUI?  Are the purposes really that different?
	The 'Locator' module is also vague - does the same component handle book
	queries, location queries, and path generation?

	3) annotations describing each component of the system model;
	0
	Absent.

	4) user interface diagrams and descriptions;
	4
	Good way to demonstrate initial appearance of GUI.  I suppose a
	description of most parts of the interface is not needed since it's
	based very closely on Josiah.

	5) written description of the above;
	3
	Honestly, the wording of your description is awkward in such a way as to
	make it unclear to me what exactly happens when you click the directions
	button.  Does AJAX pop up a map?  Does it go to a new page?

	6) non-functional requirements (performance, testing,
		reliability, ease of use, portability, documentation,
		dependencies on other systems);
	4
	What about testing the *main* system?  You only mention testing the
	admin tool, which according to earlier sections is optional.

	7) updated requirements (with priorities, etc.);
	4
	Reasonably complete functional requirements, but really, I feel like
	some sort of usable administrative interface, even if it's just a
	configuration file and a script, should be a mandatory requirement,
	because otherwise, it's half as useful.

	8) any risky parts.
	5
	Good assessment of the problems with the admin GUI.  Reasonable
	solution, which wouldn't be terrible to implement.

Other comments:

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

Additional comments/changes after presentation: