IT 432 Web Architecture for Non-Programmers
Winter 2011
Final Team Project
Due Sunday March 13
Overview
This team project consists of the final work on the selected
design for a web application.
Minimal Requirements
For the web application, the minimal requirements are the same as
those for the individual design requirements, namely:
- Data models. The website should have a minimum of
three data models (corresponding to three database table). One table
should consist of users and be used for authentication.
- Authentication. User authentication should
involve at least two levels of authorization (e.g. regular user and
administrator; anonymous user and logged in user). Alternatively,
some pages should be restricted to certain users.
- Data creation and display. The website should
support appropriate user operations for creating, displaying, updating
and deleting content. While the final project does not need to fully
match the original design, it should successfully provide the main
operations needed to support the design idea.
Summary Document
Prepare a document (3-4 pages) that summarizes your application and
the work your team has done. Summarize the development process
including any revisions based on user-centered feedback
(e.g. usability testing). Include individual contributions.
Submission
The summary document should use a common presentation format,
ideally PDF. Using a Zip application, package both the summary
document and your rails folder containing all of the code into one Zip
file. Submit the zip file using the D2L submission site.
Grading
This project is worth 30 points and will be reviewed using the
following criteria:
- Clarity. The summary document should concisely and
efficiently present the project's accomplishments.
- Accomplishment. The project accomplishments should surpass
the project requirements.
- Soundness. The web application works without errors.
Up to 10 points will be awarded to each of the three criteria using the following rubric:
- 10 -- the project clearly surpasses all requirements and represents an outstanding achievement without any deficiencies.
- 9 -- the project meets all requirements and represents a solid
achievement with perhaps a minor deficiency.
- 8 -- the project nearly meets all requirements and represents
a substantive achievement with a few minor deficiencies or a major
deficiency.
- 7 -- the project meets most requirements and represents a marginal
achievement with several major deficiencies.
For the extremely rare case that a project does not meet any of the
descriptions above, fewer points may be assigned in proportion to the
amount of work achieved. Ideally, all team members will receive the
same score. However, for exceptional cases where team members
contributed little, these members will receive credit in proportion to
their contribution.