Extend your previous program to keep track of different users and events. You do not need to worry about authentication. That is, simply accept user names, not passwords. The event information screen should show all current events, and let users confirm on any of the current events. When a user enters an event information, the user must supply a user name, which is then shown beside the event information. When a user confirms for an event, the user must also supply a user name. A user cannot confirm on his or her own event. Once a user name is given in the session, that user name must stay the same throughout the session. That is, the user cannot change a user name once given.

Details:

• You will need to use both the session object and the context object.
• In this assignment, the event information screen should be created from a JSP, not a servlet.
• You should still include a "restart" ability.

Hint: If you open up two different browsers on your computer, they will each have a separate session. This might help test your program.

You can format the screens as you wish as long as you follow the usability guidelines from class. You can also add additional functionality. Get creative and have fun!

As before, you can work with a partner or alone. You can work with the same partner as the previous assignment, or a different partner. Be sure to alert me to any conflicts that could endanger your grade.

Within the above constraints, feel free to format the output web page any way you like and include extra functionality if you like. Your program will be graded on correctness, and also on the readability and maintainability of the Java and the HTML that it produces (for example, be sure to add carriage returns!).

You will deploy your program on the swe432 application server, as detailed in the instructions.

Submission

Put your name and "SWE 432 - Assignment 10" on all screens. If you work with a partner, put both names on the screens. Submit your program by

• Deploying your JSP, servlet, and other Java classes on the server.
• Placing a link to the initial JSP on your website. Partners' websites should both link to the same web page.
• Posting all your source files on Blackboard. Do not post source files on your website.

Making your web page available to me is your responsibility. If I cannot access your file then you will not get credit. Be sure to test access to your file before the due date.

Prepare to present your invitation system at the end of the semester.

Grading Rubric

The grading for this assignment will be as follows:
[Total: 20 points]

• (2 points) — Correctly keeping track of multiple events
• (2 points) — Correctly keeping track of multiple users
• (2 points) — Preventing a user from confirming on his or her own events
• (2 points) — Preventing user from changing his or her user name during a session
• (1 point) — Screen that shows all current events
• (2 points) — Having the events and confirmation persist across sessions
• (5 points) — Adherence to all usability concepts discussed in class
• (2 points) — Adherence to directions and submission instructions
• (2 points) — JSP, Java, HTML, and JavaScript readability, style, and maintainability

Special Helper Extra Points

[Purpose: promote collaboration]
[Total: 10 points]

If you got help from your classmates (excluding your partner), when you submit your assignment on Blackboard, please

• Clearly specify the name(s) of your special helper(s)
• Clearly and briefly describe what and how you were helped

© Based on documents by Dr. Jeff Offutt (the original author) and Dr. Kinga Dobolyi, use with permission of the author. This document is made available for use by GMU students of SWE 432. Copying, distribution or other use of this document without express permission of the author is forbidden. You may create links to pages in this web site, but may not copy all or part of the text without permission of the original author.