Strategy Document

You nailed it. Visually, you could bold the first point in each numbered text list. It would just improve easy readability a touch.

Function Requirement—

            When you numbered your sections—hardware, software, etc., the numbers jump from 1 to 4 to 6…..what happened to 2,3 and 5?

The way you break down the tasks is very comprehensive—Good job Michael!

Use Cases

Very comprehensive. No suggestions… OK, Joy just said what about a “new” user or a “visitor”—is that something your system would need to be flexible with?

Architectural Diagram

For the “results” multilayer page….should that be a multilayer file instead of page? (the dog-eared page?)

The 1C connect is a little unclear. If sign-in is successful, wouldn’t the arrow point directly to the dotted container?

**May need more specific references to the add, comment, edit (perhaps number them) to refer users to the next page. (this was Mike’s suggestion)

Our brains have melted….but in a good way J

Information Views

What about an area to comment/annotate for each bibliographic entry? Is this what the comments in your Arch. Diagram would do?

The numbers in your main headings skip around again. Is there a logical reason (I’m sure there is…)

Wireframe

Good. Nice colors. Easy to understand.

Database Design

            User chart—you should break the full name into first name, last name.

Comp

            Michael, the site itself is really your design concept, yes? It’s very nice and matches back to the wireframe.