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 Website (Homepage) –A list of events from current date on (default 50) –Calendar gadget –Search section –Login/Signup section

4. User’s World Conference –A list of events including description and link to each event Title of event Date Location Description, including speaker –Call for papers feature –External Links –Workshops

5. User’s World Non-registered Users –View and Search events Registered-Users –View and Search events –Add event –Edit event –Delete event Admin –Update backup –IP ban user

6. userLogin and userSignup username password resetPassword username password confirmpassword email

7. resetPassword userName email

8. search searchByEventDate searchBySpeaker searchByEventTitle searchByLocation

9. addEntry and editEntry EventTitle eventDate eventLocation eventDescription eventSpeaker(fname, lname) Rating (not enabled until date has passed)

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

11. restoreDatabase (admin user) eventID backupDate

12. callForPaper  Link  backupLastThreeMonths  date  email

13. listGenerator currentDate sortByDate(eventDate)//default display sortBySpeaker(lname) sortByTitle() sortByLocation()

14. Data Structures User Username varchar(100) NOT NULL userID int(11) NOT NULL auto_increment password varchar(100) NOT NULL level enum(‘user’, ‘admin’) DEFAULT ‘user' NOT NULL email varchar(100) NOT NULL Primary Key [userID]

15. Data Structures (cont.) eventTable eventTitle varchar(100) NOT NULL eventID int(11) NOT NULL auto_increment addDate created TIMESTAMP DEFAULT NOW() location varchar(100) NOT NULL eventDate date NOT NULL description blob NOT NULL links varchar(100) NULL Primary Key [eventID] spfname varchar(100) NULL splname varchar(100) NULL

16. Data Structures (cont.) commentsTable commentID int(11) NOT NULL auto_increment eventTitle varchar(100) NOT NULL comment blob NULL eventID foreign key username varchar(100) NULL rating int(5) NOT NULL Primary Key [commentID]

17. Data Structures (cont.) backup backupID int(11) auto_increment NOT NULL eventID foreign key userID foreign key addDate created TIMESTAMP DEFAULT NOW() location varchar(100) NOT NULL eventDate date NOT NULL description blob NOT NULL links varchar(100) NULL Primary Key [backupID] Speaker varchar(100) NULL

18. Use Cases Scenario 1 Non-register user’s view. Scenario 2 User wants to add event, but is not logged in Scenario 3 User knows title of event, searches by title Scenario 4 User knows location of event, searches by location Scenario 5 User knows date of event, use calendar gadget to specify date

19. Use Cases (cont.) Scenario 6 User wants to browse calendar, uses calendar gadget. Scenario 7 User knows the speaker’s name, searches by speaker name. Scenario 8 User has call for paper link. User can add call for paper link and email Scenario 9 User wants to change date or location of event. Scenario 10 User wants to delete event. Delete method will delete the entry

20. Use Cases (cont.) Scenario 11 Event has passed, User wants to comment or rate the conference or the speaker. Scenario 12 Entry was vandalized, admin user wants to backup to previous edit.

21. 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

22. 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

23. 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.