Final Project

Purpose

The purpose of this project is to practice web service design and development skills by creating an application that makes meaningful use of web services.

The Problem

You should work in a group of 2-3 people. Each group will choose your own topic. It is essential that you act as self starters. If you need to find group partners, send an email to lqiu@oswego.edu

The application developed by a two-person group should consume at least two web service. The application developed by a three-person group should consume at least three different web services.

Here are some examples of web services that you might use. WS Finder has a collection of web services and open APIs.

Project proposal

By 3/9/2006, send an email to lqiu@oswego.edu with "CSC535 Final project proposal - your group member last names" as the subject.

In the email, indicate your group members and describe your topic. You should explain which web services that you are going to use and how you plan to use them. You are encouraged to submit your topic well before the deadline to receive feedback regarding the appropriateness of your topic.

Proposal presentation

3/28, 3/30, in class.

Your presentation needs to address the following questions:
  • Why do you want to develop your program? What is cool about your program?
  • What are the similar programs or webpages out there?
  • What is the intended design of your program?
  • What is current status of your project? Show toy programs that work with each web service in your project.
  • What are the team member roles and responsibilities?
    • Document the answers to the above questions on a webpage.

    Midpoint demo

    4/18, 4/20 individual group meeting to demo project progress.

    Final presentation

    5/9, 5/11, presentation of the final project to class. It has to include:
  • An overview of your project
  • A demo of your program that addresses the following questions:
  • What can your program do?
  • How does your program work?
  • What are the interesting features?
  • Why you think your program is cool?
  • Three course-related lessons that your would learned in the project. For each lesson, describe:
  • What is the problem?
  • What did you try and how did you solve it?
  • What is the code to solve the problem?
  • What did you learn from the problem? What is the take-home message for the class?
    • Document the above (including the overview, status, and discussion of issues) on a webpage.

    Submission

    Submit a zip file with your project name as the file name. Include the following in the zip file:
  • a directory called "program" containing the source code and compiled code of your program, and a readme file for how to run your program.
  • a directory called "webpage" containing the webpages describing your project, including:
  • an index.html file as the homepage for your project
  • a demo showing how to use your program. Follow this example.
  • webpages for the project proposal
  • webpages for the final presentation
    • Email your zip file to lqiu@cs.oswego.edu. This file is due on or before 5/14.

    Grading rubrics

    Total: 100
  • final presentation: 20%
  • Good: clear demo of the user interface, meaningful lessons with good discussion
  • OK: ok demo with ok lessons
  • Weak: demo does not go well (e.g., set up problems, runtime bugs, etc.), lessons are not important or poorly described
  • webpage documentation: 20%
  • program functionality and implementation: 60%