1 / 9

Whenever Messenger Project Overview

The University of Portland School of Engineering's project, Whenever Messenger, aims to allow users to send offline messages through a web-based application using AOL's instant messaging protocol. The team has made progress in meeting accomplishments, outlining plans, addressing concerns, and drawing conclusions. Despite encountering server setup issues and protocol changes, they remain on track to complete project milestones.

betsy
Download Presentation

Whenever Messenger Project Overview

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. Project SantiamWhenever Messenger Team Lisa Eberle Jason Favors Ben Foran • Advisor • Dr. Vegdahl, Dr. VanDeGrift • Industry Representative • Mr. Gentry, Mr. Baker • Harland Financial Solutions University of Portland School of Engineering

  2. Overview • Introduction • Accomplishments • Plans • Issues/Concerns • Conclusions University of Portland School of Engineering

  3. Introduction • Recap: Whenever Messenger allows users to send messages to users not currently online. • Web-based application utilizing AOL’s instant messaging protocol Avoid waiting aimlessly for a buddy to come online University of Portland School of Engineering

  4. Accomplishments • Met plans of previous month • [Submit version 0.95 of our Functional Specifications document.] - done • [Submit version 1.0 of our Functional Specifications document.] – done, per approval meeting with industry representatives and faculty advisors • [Continue to meet regularly to discuss and plan our project.] – set up weekly meeting times, both with our faculty advisors and our group individually University of Portland School of Engineering

  5. Accomplishments, continued • Determined tentative deliverables • Began research • Researched ways to implement AIM’s protocol • Researched how to make use of XML for passing information between website and back-end software • Improved meetings (scheduled weekly meetings, complete with agendas and minutes) University of Portland School of Engineering

  6. Plans • Submit Plans document revision 0.9, 0.95, and 1.0 • Set up server • Work on design • Website • Database • XML Schema University of Portland School of Engineering

  7. Concerns/Issues • Unexpected problems with setting up server • Dedicated box/IP/location • Solution: temporarily use alternative location, such as on a personal website • Ongoing: AOL modifying its protocol • Solution: construct a wrapper to make handling a new protocol quick and relatively simple to adjust to the changes University of Portland School of Engineering

  8. Conclusions • Completed the functional specifications • Started research and outlining the project deliverables • Plan on completing a timeline for the project and begin design University of Portland School of Engineering

  9. Questions • Any questions? University of Portland School of Engineering

More Related