CSCI 5895:
Assignment 3: Wireless Markup Language
Due Monday, June 11
Introduction
You are to develop a simple mobile “registration
system” using Wireless Markup Language.
Students will use it to “register” for a summer course offered by the CSIS department. These include:
Entire 12 weeks:
|
Code |
Number |
Title |
|
0605 |
1590 |
Survey of Computer Science and Information |
|
0610 |
2610 |
Programming & Problem Solving |
|
0623 |
3782 |
|
First 6 weeks:
|
Code |
Number |
Title |
|
0600 |
1514 |
Business Computer Systems |
|
0620 |
3720 |
System
Configuration and Maintenance |
|
0621 |
3722 |
Development of Databases |
|
0622 |
3723 |
Networking Concepts & Administration |
|
0660 |
5895 |
Mobile Web Programming |
Second 6 weeks
|
Code |
Number |
Title |
|
0650 |
4895 |
Web Server Programming |
Note that you may as an alternative create a mobile site for something other than this (such as another organization or your own personal site). However, it should be at least as functional as the pages described below. Please contact me if you have any questions.
“Login” Card
The first card in your deck must prompt the user for a student ID. As with the previous assignment, the student ID should be restricted to be an 8-digit value starting with two zeros.
“Course Selection”
Cards
The user should then be taken to a card where they are provide with a list of “terms”:
o Entire 12 weeks
o First 6 weeks
o Second 6 weeks
When the user makes a selection, they should then be taken to another card with a list of courses offered that term (see above). They should then be allowed to either select one of those courses, or to return to the list of terms.
“Course Submission” Card
Once the user has selected a course, they should be taken to a card that displays the number and title of the course they have chosen. That page should also contain a button/softkey/etc. to send the request to the server (since we don’t actually have a server, you can use a fake address for now).
The following information must be posted to the server when this occurs:
o The student ID.
o The course code of the course they have added.
“Quit” Option
Each card in your deck must provide a way for the user to “quit” the process, and return to your main CSIS page.
However, before quitting, the user must be asked to confirm this decision. This is to be done with an additional “confirmation” card which either takes the user to your main CSIS page if they choose to quit, or back to the previous card if they do not.
You are also to use a timer
to return them to the previous page automatically
if they do not make a choice within 10 seconds.
Usability
o There are many ways that users can navigate between cards, including softkeys, pseudolinks, buttons, list selection, and timers, not all of which work on all devices. Give the user alternative ways to navigate where appropriate.
o When possible, use templates to avoid duplication of code.
o Think carefully about the type of list most appropriate for each stage in your deck.
Testing
You are to test your site on the Openwave emulator and at least one other emulator.
If possible, also test it on your own phone (and for that matter, phones of other people that you know). Of course this will require you to post it on a server (I know that a number of you have accounts within the department or elsewhere).
What to Turn In
Please turn in a CD or diskette with all files (including images and other media) necessary to run your site.