1. Conference Calendar 1.Description 2.User’s World 3.Data Structures 4.Use Cases 5.Schedule

2. Description The Conference Calendar is a web application that allows registered users to post conference events and have them display on a calendar for anyone to see. Registered users can add and/or edit entries, including the date, location, title of event, description and presenter. There would be an administrator that makes sure that there are no vandalisms and reverts any changes if necessary. All changes are saved and backup, allowing the ability to revert changes. The Conference Calendar functions like a wiki, allowing anyone to see the calendar, but restricts editing to only registered members and administrators. User can search by date of conference, topic, location and/or speaker of a conference. Users can comment or review the conferences or the speaker and can comment on each other.

3. User’s World Conference –Title of event –Date of event –Location –Description –Conference Fees –External Links –Workshops

4. User’s World Users –Non-registered Users Not logged in, no privileges other than viewing and searching. –Registered-Users Logged in, able to add, edit and delete entry. Able to reset password –Admin Able to restore backup Report abuse of privileges.

5. userLogin and userSignup username password resetPassword username password confirmPassword email

6. Data Structures User Username userID Password Level email

7. Data Structures (cont.) Conference Event Title Event ID Date entry is added Location Event Date Description Links

8. Use Cases Scenario 1 User views Scenario 2 User searches for event Scenario 3 User wants to add/edit/delete entry Scenario 4 Undo vandalism

9. search searchByEventDate searchByEventTitle searchByLocation

10. addEntry and editEntry EventTitle eventDate eventLocation eventDescription Rating (not enabled until date has passed)

11. deleteEntry sessionTracking checkUserID (userID) delete(eventID)

12. restoreDatabase (admin user) eventID backupDate

13. callForPaper  Link  backupLastThreeMonths  date  email

14. listGenerator currentDate sortByDate(eventDate)//default display sortByTitle() sortByLocation()

15. Schedule Week 4 Inquire on additional features and functionalities in the web application. Password locking to reduce vandalism. Calendar page format Conference Fees The extent of user comments Design for Call for Papers. Inclusion of Map –Tasks Finalize database tables Use RSA tool. Expand the diagram to list functionality. Research on data reversion. Week 5 Establish a location to upload code for group editing and coding Possibly use SourceForge

16. Schedule (cont.) Week 6 Talk to customers again Make any changes if necessary. Week 7 Finish login function Finish signup function Finish user and admin distinctions Start working on add function Edit function Week 8 Basic functions completed Have users test web page. Finish reversion function

17. Schedule (cont.) Week 9 Continue coding Week 10 End of CS 337 Have a basic webpage with most functions working User login and User sign in should work Add entry works. Administrator should be able to revert changes. Users can edit entries. Archive past conferences and prevent editing. Review entries should still work for past conferences.