Dynamic Website Design for Temple Beth-El of Ithaca, NY CS 501 Project - Milestone #2

1. Dynamic Website Design for Temple Beth-El of Ithaca, NY CS 501 Project - Milestone #2 April 6, 2006 Presented By: Peter Babinski, Christopher Benedict, Benjamin Darfler, Eugene Kim, Muir Manders, Vivek Shah, and Michael Veilleux

2. Presentation Outline • Updated Feasibility After First Iteration • Evaluation of First Iteration • Current Status: Completed Second Iteration • Updated Requirements • Higher Level Design and Implementation • Database Specification • Calendar/Events • Page Creation/Deletion & Dynamic Menu • Text Editor Implementation • Site Managers’ Secure Login • Evaluation and Tasks for Final Iteration

3. Updated Feasibility – March 10 Client: Jane Griffith, the Administrative Assistant at Temple Beth-El of Ithaca 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 Requirements: Implement and test many of the dynamic webpage features – automatically updated menu bar, page creation/deletion, events database, secure login for site managers, text editor implementation Still Feasible? Yes!

4. First Iteration Evaluation • Self-Evaluation: • Overall progress is as planned – behind schedule with page creation/deletion tasks; ahead of schedule with site layout implementation • Client Evaluation: • Pleased with the progress, communication, and achieving the preliminary requirements • Stressed the importance of requirements that must be met during the second and third iterations: • Implement Davka – Jewish calendar software • Track site visitors – client is willing to pay for software • Google search bar, weather icon • Use a fixed webpage width • Test the layout of a webpage when printed

5. 2nd Milestone Goal: Iteration #2 Requirements Evaluation TODAY’S PRESENTATION Implementation Design Reference: Iterative Procedure Diagram from Dr. William Arms, http://www.cs.cornell.edu/courses/cs501/2006sp/slides/lecture1.html

6. Work Breakdown Structure Second Iteration Work Breakdown

7. Second Iteration Requirements • Update design documents – state transition and entity relation diagrams for database design • Allow for creation and display of time sensitive data on: • An events/calendar page • The bottom of the main menu bar • Implement easier and secure site manageability tools: • Secure login for site managers • Simple page creation/deletion with automatic updates of the website hierarchy, and… • Automatic updates of the main menu • Text and graphics editor (FCK Editor)

8. Presentation Outline • Updated Feasibility After First Iteration • Evaluation of First Iteration • Current Status: Completed Second Iteration • Updated Requirements • Higher Level Design and Implementation • Database Specification • Calendar/Events • Page Creation/Deletion & Dynamic Menu • Text Editor Implementation • Site Managers’ Secure Login • Evaluation and Tasks for Final Iteration

9. Requirements Specification Updated State Transition Diagram

10. Database Specification Updated ER Diagram: Users

11. Database Specification Updated ER Diagram: Page Content

12. Database Specification Updated ER Diagram: Events

13. Calendar/Events Implementation • Cannot integrate with Davka, so Calendar Eliminated • Event functionality completed • Can create new events and delete / modify existing events • Services displayed on main bar • Menus still need better formatting • Demo! • http://205.232.75.214/eventmain.php

14. Presentation Outline • Updated Feasibility After First Iteration • Evaluation of First Iteration • Current Status: Completed Second Iteration • Updated Requirements • Higher Level Design and Implementation • Database Specification • Calendar/Events • Page Creation/Deletion & Dynamic Menu • Text Editor Implementation • Site Managers’ Secure Login • Evaluation and Tasks for Final Iteration

15. Text Editor Implementation • Integrated with page creation/edit page • Turned on spell checking with IE

16. Page Creation & Deletion • Page file (pageID.php) created on the fly • Page entered into the database for use in menu propagation • Demo: • http://205.232.75.214/editor.php

17. Dynamic Site Map • Hierarchy in menu is set/changed on the page creation/edit page • Menu automatically created based on input

18. Menu Design & Implementation • Enforces Dynamic Representation of Content • Also holds Events, Services, and Login/Logoff • Adds privileged links if administrator • Edit events/services • Create/Edit pages – Link to FCKEditor • Also displays upcoming services • Blends Login/Logoff script seamlessly • Order of user created pages can be modified

19. Presentation Outline • Updated Feasibility After First Iteration • Evaluation of First Iteration • Current Status: Completed Second Iteration • Updated Requirements • Higher Level Design and Implementation • Database Specification • Calendar/Events • Page Creation/Deletion & Dynamic Menu • Text Editor Implementation • Site Managers’ Secure Login • Evaluation and Tasks for Final Iteration

20. Site Managers’ Secure Login • Login module allows any page to offer login option • Add user, modify user, delete user all available • After successful login redirects you to original page • Remembers you are logged in until you end session • Can log out after you have logged in Database Regular User Login Logout Admin Create User Modify User Delete Users

21. Second Iteration Evaluation • Overall, progress is as expected • Slightly behind schedule for: • User Testing 2) Unit Testing • Ahead of schedule for: 1) Visitor tracking software

22. Next Milestone: Final Iteration Requirements Evaluation FINAL IMPLEMENTATION IN EARLY MAY Implementation Design Reference: Iterative Procedure Diagram from Dr. William Arms, http://www.cs.cornell.edu/courses/cs501/2006sp/slides/lecture1.html

23. Final Iteration Network Diagram Third Iteration Work Breakdown

24. Third Iteration Requirements • Ask client for any new requirements • Update design documents as necessary • Add site traffic counter and tracking software • Attach Google search bar and weather icon • Create a help file for site management tools • Site layout testing, and management tool testing • Production-level installation and testing • Successful handover to client and site managers