1. EZReg Jun Ma Xu Nathan Plesnicher Jerin Schneider Chris Kennewick Sharon Lin Brian Watanabe

2. Introduction Our product is:  a web-based application which will allow UW students have greater control over their general registration experience using search options and an interactive visual schedule

3. Introduction Users can: Search the catalog and return a course list Mouse over preview with ghosting Add a course in the visual scheduler Add a course that conflicts with an existing course and handle that case by providing a list of overlapping courses register via our web app

4. Introduction Our product will NOT:  deal with the various issues that can arise while registering, such as: A class becoming full while using our tool Entry code violations Etc…

5. Architecture

6. Execution Plan  We split into two groups: frontend and backend development teams Frontend: Javascript, CSS, HTML Backend: PHP, MySQL  Each team meets more than twice a week  Big team meets once a week

7. Execution Plan – Team Structure TitleMain responsibilities Back end developer (3) Manipulation of the Database, Back end PHP support for front end Javascript Front end developer (4) Integration of AJAX framework into the project Front end Javascript interaction with the PHP back end Search pane Front end Javascript effects Program manager (1) Oversee the project and coordinate between subgroups Dev/Test (1) Automation for testing/managing bugtracking

8. Execution Plan  April 29 th : each team finish their own parts  April 29 th – May 10 th : integrating, testing, usability testing  May 10 th : beta release  May 10 th – May 20 th : feedback Integrated into product, fixing bugs  May 20 th : a possible Beta refresh  May 20 th -May30 th : Final release feature complete Test and clean up of bugs  May 30 th : Final Product Release

9. Execution Plan - Risks  UW database too unwieldy to use effectively  Refreshing front page may be too slow due to either database or javascript limitations  AJAX integration proves more difficult than anticipated

10. Testing Plan  Unit Test Strategy  System Test Strategy  Usability Test Strategy  Adequacy of Test Strategy  Bug Tracking Mechanism and Plan of Use

11. Documentation Plan  A walkthrough of a typical search, find, and register process  Tips on how to resolve conflicts in the schedule  Tips on how to most effectively search for classes  Detailed descriptions on the search criteria that we offer  Description of the relationship between the manipulation of the search option and the visual schedule

12. Questions?