1 / 11

Pizzlet Information System “When Spam just isn’t good enough…” Troy Lamberte Blake Norrish

The Pizzlet Information System (PIS) gathers and distributes "Free Stuff" details via email parsing to users' cell phones. Designed for University of Washington students seeking campus freebies, it streamlines information delivery effectively. Deployable components include email connection, parsing, database integration, client communication, and the Pizzlet Midlet for mobile display. The system simplifies access to useful updates like free food alerts and campus event notifications. Practical and adaptable, it offers convenience and ease to users, aiding in maximizing freebie exploration on campus.

scullum
Télécharger la présentation

Pizzlet Information System “When Spam just isn’t good enough…” Troy Lamberte Blake Norrish

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Pizzlet Information System“When Spam just isn’t good enough…” Troy Lamberte Blake Norrish

  2. Operational Concepts(Overview) The Pizzlet Information System (PIS) facilitates the gathering and distribution of “Free Stuff” information. A server application receives and parses e-mails from an e-mail address, and sends relevant “free stuff” information to a list users running the Pizzlet Midlet on their cell phones. This is aimed at University of Washington students and the free food that is regularly distributed around campus.

  3. System RequirementsWhat DOES it do for us? User Scenario 1 (setup) 1)      Bob hears about Pizzlet from a CS friend 2)      Bob logs onto the World Wide Web 3)      Bob navigates to the URL homepage of the Pizzlet Server. 4)      Bob enters his username, cell phone number, and preferences about what kind of information he would like to receive. 5)      Bob downloads the Midlet portion of Pizzlet to his cell phone. Bob leaves • User Scenario 2 (use) • 1)    Bob is sitting on campus like he always does • 2)      Bob is hungry like he always is • 3)      Bob uses his cell phone to check the latest information from Pizzlet. • 4)      Bob sees that there is some sort of Engineering kickoff meeting tonight in the HUB, and they have free pizza • 5) Bob goes, and eats free pizza

  4. System Requirements (2)What it looks like: (Web part)

  5. System and Software Architecture The Components • E-Mail Component; Responsible for e-mail connection and e-mail retrieval • Parsing Object; Responsible for looking at e-mail and determining if its “free stuff” • Database Connection Object; Needed to get list of user’s cell phone numbers for info distribution • Client Communication Object; Responsible for ending data to client’s cell phone • Pizzlet Midlet; On Cell phone, responsible for displaying info received from Pizzlet Server

  6. Components (visual)

  7. The Hard Parts: Email retrieval and Parsing E-mail: Use JavaMail API and JavaBeans Activation Framework to get mail. Use e-mail forwarding to internet POP server to bypass need for SSL or TLS (JavaMail does not support) It works… we already did it. Parsing: Search on predefined keywords/phrases in e-mail subject/body Assign e-mail “confidence” depending on number/type of keywords found High “Confidence” means free stuff, send info to cell phones Also use “filter” word to weed out junk, porn, etc.

  8. Lifecycle Plan Who wants it? I do, you do, we do, Bob does. And who will support it? Little support needed. E-mail configuration needed (about) quarterly to keep Pizzlet’s E-mail address on lots of distribution lists. Tech Support: BYOTS (and RTFM?)

  9. Conclusions: • No known technical impossibilities • E-mail retreival solved • Parsing reasonable • Good Product /Work ratio • Isn’t a huge project (small work), but could be an interesting solution (Nice Product) • Known user base • Me • You • Bob • But….

  10. … Some things that could go wrong • Our system is dependent on a web-based free e-mail server. • Policy change (no free POP acocunts) • Out of business • JackA**’s • People who know about system could easily compromise it, send false e-mails, etc

  11. FINAL Conclusion Build it.

More Related