1. Dynamic Website Design for Temple Beth-El of Ithaca, NY CS 501 Project – Final Presentation May 4, 2006 Presented By: Peter Babinski, Christopher Benedict, Benjamin Darfler, Eugene Kim, Muir Manders, Vivek Shah, and Michael Veilleux

2. Second Presentation Summary Project Scope: Build a dynamic webpage that, from the web browsers point of view, is easier to browse and more up to date with current webpage design. From the webpage manager’s point of view, the page contents must be easy and secure to manage from a remote location. Second Iteration Evaluation: All but one task was on schedule. That task, system and acceptance testing, was listed as a top priority for the final iteration. Third-Iteration Tasks: System and acceptance testing, change system as necessary during user testing, and implement more add- ons (i.e. Google search bar, visitor tracking, counter, help documentation, and Hebrew text editing) Still Feasible? Yes!

3. 3 rd Milestone Goal: Iteration #3 Requirements Design Implementation Evaluation FINAL IMPLEMENTATION BY MAY 11 Reference: Iterative Procedure Diagram from Dr. William Arms, http://www.cs.cornell.edu/courses/cs501/2006sp/slides/lecture1.htmlhttp://www.cs.cornell.edu/courses/cs501/2006sp/slides/lecture1.html

4. Final Iteration Network Diagram Third Iteration Work Breakdown

5. Project Requirements  Optimize “Browseability”: 1)New layout should resemble old layout; client must be involved in choosing final layout 2)Increase ease of browsing: menu, search toolbar 3)Upcoming services posted at bottom of main menu  Increased “Manageability”: 1)Counter 2)Database design 3)Visitor tracking 4)Secure login for site managers 5)Posting events on: events page, main menu, any site page 6)Help documentation 7)Text and graphics editing 8)Page creation/deletion, updating hierarchy of pages, menu link updates

6. Browseability: Main Page Layout Requirement: New layout should resemble old layout; client must be involved in choosing final layout Old Website Layout New Layout Design Implemented Layout (accepted by our client) Dem o

7. Browseability: Menu and Site Search Requirement: Increased ease of browsing – menu and search toolbar Google Search Toolbar: Searches TBE site or web, integrates within title header, convenient portal for TBE community Menu provides for easy browsing between TBE- Ithaca webpages Dem o

8. Additional Menu Features Browseability Requirement: Posting of upcoming services within menu Manageability Requirement: Site visitor counter List of services, including date, time, and description (more about manageability of events later…) Visitor counter

9. Project Requirements  Optimize “Browseability”: 1)New layout should resemble old layout; client must be involved in choosing final layout 2)Increase ease of browsing: menu, search toolbar 3)Upcoming services posted at bottom of main menu  Increased “Manageability”: 1)Counter 2)Database design 3)Visitor tracking 4)Secure login for site managers 5)Posting events on: events page, main menu, any site page 6)Help documentation 7)Text and graphics editing 8)Page creation/deletion, updating hierarchy of pages, menu link updates

10. Manageability: Requires Design Implied Requirement: Creating a more manageable site required database design diagrams in order to clearly communicate our realization of the requirements back to the client 1) State Transition Diagram (Updated)

11. Manageability: Requires Design Implied Requirement: Creating a more manageable site required database design diagrams in order to clearly communicate our realization of the requirements back to the client 2) ER Diagrams (Updated)

12. Implied Requirement: Creating a more manageable site required database design diagrams in order to clearly communicate our realization of the requirements back to the client 3) UML Classes Manageability: Requires Design

13. Project Requirements  Optimize “Browseability”: 1)New layout should resemble old layout; client must be involved in choosing final layout 2)Increase ease of browsing: menu, search toolbar 3)Upcoming services posted at bottom of main menu  Increased “Manageability”: 1)Counter 2)Database design 3)Visitor tracking 4)Secure login for site managers 5)Posting events on: events page, main menu, any site page 6)Help documentation 7)Text and graphics editing 8)Page creation/deletion, updating hierarchy of pages, menu link updates

14. Manageability: Secure Login  Login module allows any page to offer login/logout option  Dynamic menu bar changes to reflect login status  Stores login status as session variable to keep out of reach of user Regular User Login Create User Modify User Delete Users Database Admin Logout Forgot Password Login successful Requirement: Site management should be easy and secure Dem o

15. Administering Users  Once logged in, admin can: Create a new user Delete an existing user Modify an existing user (change password or email address) Logout Requirement: Site management should be easy and secure

16. Secure Login Error Handling  Performs basic username/password check  On creation of new user checks that username is unique  Does not allow user to delete himself  When specifying new password must specify twice as a safeguard Requirement: Site management should be easy and secure

17. Password Reminder  Password reminder feature if user forgets password  Queries database for a given username (assumes user remembers username)  Dispatches automated password reminder to the email address on file for the user Requirement: Site management should be easy and secure

18. Project Requirements  Optimize “Browseability”: 1)New layout should resemble old layout; client must be involved in choosing final layout 2)Increase ease of browsing: menu, search toolbar 3)Upcoming services posted at bottom of main menu  Increased “Manageability”: 1)Counter 2)Database design 3)Visitor tracking 4)Secure login for site managers 5)Posting events on: events page, main menu, any site page 6)Help documentation 7)Text and graphics editing 8)Page creation/deletion, updating hierarchy of pages, menu link updates

19. Manageability: Calendar/Events  Many Changes Many more fields now marked optional Names of fields changed to be more understandable Better formatting Graceful error checking added Associated With field implemented so that events will be also shown on pages that they pertain to Changed date format to Rabbi’s preference  Upcoming Events page implemented Requirement: Calendar/Events listing Dem o

20. Manageability: Help Documents  Red help link near the title of all backend pages  Help system will pop-up if the link is clicked  Help system details: Page Description Page Fields How To Submit Requirement: Help documentation to assist the page manager Dem o

21. Project Requirements  Optimize “Browseability”: 1)New layout should resemble old layout; client must be involved in choosing final layout 2)Increase ease of browsing: menu, search toolbar 3)Upcoming services posted at bottom of main menu  Increased “Manageability”: 1)Counter 2)Database design 3)Visitor tracking 4)Secure login for site managers 5)Posting events on: events page, main menu, any site page 6)Help documentation 7)Text and graphics editing 8)Page creation/deletion, updating hierarchy of pages, menu link updates

22. Manageability: Text Editing Requirement: Must be able to edit main page text and graphics on all pages Cleaned up the FCK menu bar Reduced the font size Added a checkbox for displaying page sensitive events Dem o

23. Manageability: Text Editing Requirement: Hebrew text

24. System and User Testing  Unit and system tests have been run continuously throughout  Aspects of user and acceptance testing completed: Web layout design (feedback from client and Rabbi) Calendar/events formatting Overall system has been tested through sit- downs and email communication with the client as she uses the system

25. Project Evaluation  All tasks, except migration, are complete.  Our client has expressed that she is pleased with the new system design.

26. Handoff Requirements  Finish migration  Final report  Previous documentation: feasibility report, milestone reports, and all presentations  Continued support

27. Acknowledgements  Our Client, Jane Griffith  The Rabbi and all other senior members at TBE, for their input during the design process  Professor Arms and our T.A., Theresa Velden