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

System Goals

The system is designed to help users easily find an appropriate local
wedding venue.  It is a simple resource search  website (for examples,
see
kayak.com, urbanspoon.com). On the main page, the user  will  supply a
ZIP
code and distance from it.  She will enter other criteria and tags as
search
criteria. The system will locate all wedding venues that match the
specified
criteria within the specified radius and will allow her  to drill down
into
the results or refine the search criteria.
System engineering requirements

.       System will be written in the latest stable Rails release
(currently
1.2.3)
.       Pages will be valid XHTML, will use valid CSS and render
properly on
Firefox, IE, Safari and Opera.
.       Consistent layout and design throughout the site
.       The system will be delivered with unit tests
.       The system will be delivered with functional  tests
.       Will be amenable to SEO (use friendly urls)
.       The system shall use available plug-ins where available.

System Users & Tasks

General User

The main user of the site searches/browses for a wedding venue. They
most
likely found the site via a search engine. They may land on either the
main
search page or a particular venue's detail  page. In both cases it
must be
obvious to the user how to perform a new search.

Actions:
.       Search for a wedding  venue based on selected criteria
.       Browse through list of returned results
.       View a particular venue's detail page
.       Refine/modify search criteria
.       Add a review or comments to a wedding venue
.       Send comments to website administrator
.       If the user  is venue owner/manager, need to find workflow to
update
their information. This would include some verification via email that
they
indeed are the owners (perhaps email to the domain and back).

Administrator

The administrator manages and maintains the site and the associated
data. An
Administrator can add a wedding venue and update any of its
attributes. The
administrator will be myself and much of the data will in the database
will
be entered programmatically (outside of this project scope). The admin
pages
are primarily for maintenance  and need to be functional but not
necessarily
"pretty" - they are not customer facing
.       Login as administrator with password
.       Manage search criteria :  attributes(tags) and attribute
groups
.       Add new venue and its details page including images
.       modify existing venue
.       modify venue criteria and tags
.       Manage user comments (delete ; edit ; deal with spam)
.       The editing of detail pages will be off the public detail page
when
the administrator is authenticated.

Contact o...@stanfordalumni.org with proposals.