SWE 437 Homework 2
Spring 2008
Web Enabling a Legacy Application : Due 2/25


You can't only do what's possible, you must change what's possible.
- Eliot Feld, Ballet director

This next homework continues using the stutter example by turning it into a simple web application. This is currently a very common maintenance task in the software industry and sometimes has surprising complexity. We will keep it simple, however.

More than half of the class has taken SWE 432, which introduces web application development. Thus we will divide the class into teams of two, where each team has one person who took SWE 432. The configuration for our deployment platform is the same as last semester, except we will use the virtual server apps-swe437.ite.gmu.edu
(http://apps-swe437.ite.gmu.edu:8080/swe437/servlet/).

The deployment instructions for servlets are still posted. Remember that you need to establish a VPN connection if you are working from off-campus.

Your program should accept plain text in a "textarea" box and report all repeated words.

Submit, as hard copy in class, a very short report. The report should include the URL to your stutter servlet and short answers to the following questions:

  1. In what ways would you suggest changing the user interface to be more convenient?
  2. What was the hardest part about this assignment?
  3. How did you change your original code to accodomate being deployed on the server?

You may start with the Java program from either partner, or use the sample solution that will be posted on the website. The grading will be based on the successful execution of your web app as well as thoughtful, concise, answers to the questions.