IT 231

Spring 2018

Craig Miller

• Home
• Basic Information
• Grades and Policies
• Schedule

Weekly Notes

• Week 1
• Week 2
• Week 3
• Week 4
• Week 5
• Week 6
• Week 7
• Week 8
• Week 9
• Week 10

Assignments

• Assignment 1
• Assignment 2
• Assignment 3
• Assignment 4
• Assignment 5
• Assignment 6

Technical References

• Ruby on Rails Documentation
• Mozilla Technical Documents
• HTML Tag Reference
• CSS Property Reference
• JavaScript Guide

Assignment 5
Preliminary Final Project
Due Friday May 18 before 11:30pm

Overview

For this preliminary version of the final project, you will implement multiple data models and relationships between them. The final project will extend this work and include some aspect of authentication and authorization.

This project may be completed in teams of two or three. Teams are self forming on D2L.

Requirements

Continuing with a previous project, this assignment requires the following:

1. Data models based on at least two database tables.
2. Use relationships between data models.
3. Customized forms that support model relationships.

For relationships, you are encouraged to use a many-to-one relationship that allows users to submit reviews or comments that belong to the principal records of your application. However, you are free to consider other types of models and relationships.

In addition, your application should have well developed views with layouts. The web pages should have adequate links to allow users to navigate throughout your web application. The root path should take the user to a meaningful welcome page.

Summary Document

Prepare a one-page document that summarizes your application and the work you did to create it. The document should show evidence of your understanding of the application components by explaining how you developed them.

Here's a suggested organization for your summary document:

• A high-level description of your application and what it does. You might want to include a list of features or functions that your application supports.
• How your application is organized. Here you may want to summarize your models, controllers and views.
• Any details of how you developed the application, particularly non-trivial details. Naming actual commands and statements is discouraged---it's better to explain them than to quote them.
• Special instructions for running the application (if necessary).

Regardless of how you organize your summary document, it really helps to label the different sections with headers.

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 20 points and will be reviewed using the following criteria:

• Clarity and understanding (6 points). The summary document should concisely and efficiently present the project accomplishments.
• Accomplishment (7 points). The project accomplishments should surpass the project requirements.
• Soundness (7 points). Implementation should be technically correct. Views should be easy to navigate. User operations should be easy to understand and perform. Pages should have consistent layout and be aesthetically appealing.