Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M9 Design Twist
Place a web front-end on your application.
Obviously, we are not requiring you to reimplement the entire application with a web front end. Instead, you will demonstrate the ability of your application to be adapted to a web application.
Your application must demonstrate the following features:
- Use of a style sheet (css) to standardize look and feel
- Use of query strings (?msg=111) to communicate information between the browser and web server
- Use of session variables to maintain state between server calls
- Static and Dynamic Web Pages
- Use of forms to transmit data to the web page
- Use of html include files for common data
- Embedded smalltalk code (.ssp)
You do NOT have to have any graphics output. Web pages can be all text. If your application does not demonstrate the above features after implementing the basic requirements below, then you must add additional features that will allow you to demonstrate those basic requirements if you want full credit.
Required Features
- Display a welcome screen and allow input of a leader name
- If name > 6 characters, allow the wagon to be configured as below, otherwise reprompt for leader name with error message
- Configure the wagon by setting the pace, ration, and chosing a profession.
- Display back a game status showing that your game has accepted the input parameters
- Any additional gameplay functionality (buying items etc) would be extra credit for M9.
Grading Criteria
Basic Requirements (30)
- use of style sheet ............... 5
- query strings ...................... 5
- session vars ....................... 5
- dynamic web page................ 5
- html forms........................... 5
- include files ........................ 5
Design (15)
- Basic Site Map .....................5
- Flowchart ...........................5
- Wireframe ...........................5
Specific Feature Requirements (50)
- Display welcome screen and display leader name form ............................................. 10
- Leader Name length check and error message for name too short .............................. 10
- Wagon Configuration Screen with form controls ..................................................... 15
- Game Status screen showing web interface actually talking to smalltalk app................ 15
Coding Style and comments (5)
What worked
- All the basic requirements were easy enough to accomplish on the site
- Simple style sheets were easy enough for anyone not familiar with css
- Hardest part was getting variable saving and checking correct from page to page using session variables and query strings
What didn't work
- Design requirements were harder to figure out than the actual scripting
What we did right
- All of the basic pages and the smalltalk code
- Forms and query strings
- Session variables!
What we didn't do right
What we could have fixed
- Flowchart to include logic flow from page to page
SSP Files
Complementary smalltalk code for the site
Link to this Page