View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007

The Dream Team M9

REQUIREMENTS
M9 THE TWIST

the big reveal - actually kind of anti-climactic after the hints and announced lecture on web design, but here it is:
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

-Create a site map, a flow chart of the required functionality, and a wireframe of the UI. See lecture notes for details.
-Display a welcome screen and allow launching (creation) of a CCS.
-Your CCS should autoload a saved configuration with some POS and Suppliers already created.
-After launch, display a list of all POS already in the system.
-Allow the user to use a text box to input a POS name. If the POS exists, display a screen with the POS details. If the POS does not exist, notify the user and redisplay the list of POS.
-Allow the user to create a new POS, and then display the POS list and show that it was in fact added.
-Any additional functionality (editing POS details, creating/displaying Suppliers) would be extra credit for M9, UNLESS that functinality is needed to demo the basic requirements above.

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 ............................................. 10
-POS existence check and error message for not found .............................. 10
-POS List Screen and required input form ..................................................... 15
-Create POS showing web interface actually talking to smalltalk app................ 15

Coding Style and comments (5)

We were able to successfully get our web front-end working for our project. However, the .st file is loaded on another computer, so we will try to upload screenshots if time permits. This took a lot of time to do, not b/c it was hard, but b/c it was meticulous. There is a lot of smalltalk-to-html converting that you have to do, especially if you don't know html well. We would definitely suggest starting the twist as soon as it's mentioned, as early as M8 is handed out. Have a couple people do M8, and then divide up M9 with whatever you have left to do in the project.

Link to this Page