Web Design and Implementation

409 - 737 * Winter 2011-12 * Prof. Jeff Sonstein

• 
• | Syllabus
• | Outline
• | Projects
• | Details

• Group Midterm

Group Midterm Web Project

Background

The design of the Web "site" for this class has not been reworked for several years, and could be better. The task for your teams is to design (and then implement for the final group project) a new site for this class, and one which works equally well on "big screen" and mobile devices.

Details

The WebMonkey Online Specifications should be used for the design document. The design document should be completely online, and should not just say what you want to do. The design document should also clearly show why you have chosen whatever approach and content and etc which you choose to use.

You may choose to use either XHTML (Strict) or HTML5, but you need to say why you chose one over the other.

Site Design Document

Your group will create a Site Design Document with page mock-ups using the WebMonkey Online Specifications. Note that there are 5 lessons on the site each one dealing with multiple sections of the document. Your group needs to create a document that explicitly deals with each and every lesson.

Developing and presenting this sort of document is not a trivial task, and this sort of work makes a lot of consulting firms a lot of money. Web-aware companies know having a good design document will save them money and heartache in actually getting a website up and running smoothly.

The Point of the Design Document

Organizing information for presentation on the Web is not the same as organizing information for presentation on paper. One of the points of giving you this material to work with is that the structure of the data is clear and already in place. It is pure HTML, and it has a table of contents and an organization for information chunks already in place. Your basic task is to communicate how this cookbook can most effectively be re-organized for Web navigation and presentation.

Main Tasks

• Goals
• User Experience
  • Audience
  • Scenarios
  • Competative Analysis
• Content
  • Content Grouping and Labeling
  • Functional Requirements
  • Content Inventory
• Site Structure
  • Site Structure Listing (or Summary)
  • Architectural Blueprints
  • Global and Local Navigation Systems
• Visual Design
  • Layout Grids
  • Design Sketches
  • Page Mock-ups
  • Web-based Prototype

For Group Leaders

I will expect group leaders to post a series of progress notes to your group project Web page, at least one per week. These notes should detail the progress of your group towards meeting the requirements of the project that week, and what each and every member of your group is going to accomplish the following week.

In other words, group leaders are expected to post on the group webpage each and every week at least one note about what concrete and measurable objectives:

• your team as a whole has completed in the previous week and will complete by the time you post again the following week.
• each and every member of your team individually has completed in the previous week and will complete by the time you post again the following week.

Due Date & Time

Due Wednesday of week 6, not later than 2400 hours (20 percent).

(That is 2400 hours, New York time, on the Planet Earth... the one in the Milky Way)

---

Group Website Project Teams

Coming Soon! :)

---