The Registration Alert System LCA Overview

Overview The Registration Alert System (RAS) is web-based software package that allows University of Washington students to sign up to be sent automated alerts when space opens up in classes they are trying to register for.

Use Case Scenario: Billy Billy needs to get into a class Doesn’t have the time to check the UW site Goes to the RAS site, creates a new account Signs up for an and text message alert when an opening shows up When opening appears, he gets a text message on his phone Billy heads to the nearest PC to register for the space

User Interaction Log-in / create new account Sign up for new alerts View current alerts Modify current alerts Cancel alerts

Administrator Interaction Special login View statistics (number of users, number of alerts, etc.) Options to modify system variables to balance load issues

System Design

Software Architecture

Web UI Developed in C# with Visual Studio.net Responsible for providing the interface for all system functionality Web forms to: create new accounts, log into existing accounts, create new alert requests, etc…

Database Wrapper Responsible for presenting a clean interface to the database to the rest of the system Supports methods for storing, modifying, and accessing information All other software components will not have to worry about database specifics

Scheduler Responsible for making sure events happen when they are supposed to; the “conductor” of the system Addresses load and performance issues Makes calls to the page fetch system, and to the mailer at the appropriate times

Parser/Page Fetcher Responsible for fetching pages off the UW site and parsing them to extract the relevant information Has the potential to be a large point of failure for the system Must be able to ensure robustness

Mailer Responsible for providing a simple interface for notifying users Supports text messaging and ing

Task Assignments Makara: Parser/Page Fetcher Jim: Database Wrapper Garron: Scheduler Peng: Web UI Kelvin (Zhu):Mailer Mark : Project Manager

Schedule 4/28 First team meeting 5/3 Class interfaces complete Team meeting to begin development 5/10In progress check-in, resolve development issues 5/17 Beta release Meet to discuss fixes and new features to be added 6/2Final release