Final steps! Modify your program in following ways:

1. Keep track of events and confirmation across multiple sessions. That is, you need to persist the confirmation on permanent storage. Save the data into an XML file. Refer to the servlet lectures for how to write a file on our swe432 application server, and make sure your XML file name includes your GMU user ID (to ensure uniqueness). Read and write the data each time a user adds an event or confirms.
2. Sort the events based on the highest number of "attend" confirmation.
3. Last time you added user names. Now add a password and allow a user to login and delete his or her own events. Do not allow a user to delete other users' events. Do not allow a user to confirm on his or her own events. Save the user name and password into the XML data file.

NOTE: the use of XML is a required element; no databases, cloud storage, or other types of files.

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.

Within the above constraints, feel free to format the web pages 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 11" on all screens. If you work with a partner, put both names on the screens. Submit your program by

• Deploying your program components on the server.
• Placing a link to the program on your website. Partners' websites should both link to the same web page.
• Posting all your source and XML 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) — Keeping events across multiple sessions
• (2 points) — Sorting events based on the highest number of "attend" confirmation
• (2 points) — Password authentication
• (2 points) — Allowing a user to delete his or her own events
• (1 point) — Preventing a user from deleting others' events
• (1 point) — Preventing a user from confirming on his or her own events
• (2 points) — Using valid XML files
• (4 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.