Threesuns

Email the Instructor

Contact

All Semesters

Semesters

All Courses

Courses

2011Fall

08.16.10 - 12.12.10

Rails II

CSYS2873

Wednesday
05:30 PM - 08:20 PM

Project Planning

Lab05

Objective: To develop a set of plans for completing the next programming assignment

pastdue

Submit Your Solution

Lab05

Request a Copy of your Solution

Lab05

Requirements

Complete actor list10 pts
Complete actions list10 pts
Complete Use Case list or diagram20 pts
Completed site map20 pts
Page wire frames20 pts
ERD20 pts
Total100 pts

Instructions

For this lab you will not be doing any coding, but will instead be developing a plan for the next project which you will later follow. The project will be to develop a flash card web application which will be made available for use by elementary school age children and their parents to practice spelling and/or math.

For this assignment you will create a plan for how you will make this web application. You plan should consist of the following:

  1. A list of actors - those people who will be using the application
  2. A list of traditional actions - list the things that the actors do when interacting with traditional flash cards
  3. Use cases - a list or diagram of situations and actions where the actors will be interacting with the application (see Use Cases on Wikipedia). This should be similar to the list of traditional actions except here you should take into account that the actors will not be using physical flashcards which should make some of the traditional actions unneeded and open up other new interactions that might not have previously been possible.
  4. Site Map - a diagram showing the relationship between the pages of the site
  5. Wire frames - Low fidelity mockups of the major page types
  6. ERD - create an entity relationship diagram based on what you've determined you'll need from the previous steps

Each of these items builds on the information gathered in the previous item.

Make sure to address usability issues, meaning that the use of the application should be as simple and understandable as possible from the users point of view. For example, look for actions that the user will do often and reduce those actions to the simplest set of steps possible. Scaffolding is great for developers but it is insufficient for most users.

If you have any questions about the requirements of the project address them to me as the "client" but remember that showing a "client" an ERD for example and saying "Is this correct?" is not something that a client could tell you.