Upload
aron-bruce
View
218
Download
0
Tags:
Embed Size (px)
Citation preview
EZReg
Jun MaXu XuNathan PlesnicherJerin SchneiderChris KennewickSharon LinBrian Watanabe
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
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
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…
Architecture
PHP
UW Course Database
Web browser Web server
Linux file system
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
Execution Plan – Team Structure
Title Main 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 ba
ck 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
Execution Plan
April 29th: each team finish their own parts April 29th – May 10th: integrating, testing, usability testing May 10th: beta release May 10th – May 20th: feedback Integrated into product,
fixing bugs May 20th: a possible Beta refresh May 20th-May30th:
Final release feature complete Test and clean up of bugs
May 30th: Final Product Release
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
Testing Plan
Unit Test Strategy System Test Strategy Usability Test Strategy Adequacy of Test Strategy Bug Tracking Mechanism and Plan of
Use
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
Questions?