1. OmnėMail Nicholas Allen Effie Goenawan Annie Liu

2. Scenario… Marty wants to check his emails He’s at Suzzallo Library He has 5 different accounts What will he do….? “If only I could do this all with one click…”

3. Introducing… OmnėMail!!!  Check all your emails at once anywhere  Accessible via Internet connection  Features: Aggregates all email accounts in one convenient place Online application Address book User profile Built-in instant messenger (optional)

4. Interface Design Write a mail View all mails Sent mails UW Account CSE Account Gmail Hotmail Yahoo Add a new account… Manage my account Edit my address book □ □ Pizza in the lounge!Jan 8, 1:39pm □ More pizza in the lounge!Jan 8, 2:18pm □ FREE FOOD (TOP PRIORITY)Jan 8, 5:18pm □ Mail from president Emmert about over-eatingJan 7, 1:28am □ Pizza in the lounge!Jan 8, 1:39pm □ You long abandoned hotmailJan 8, 1:39pm □ Pizza in the lounge!Jan 8, 1:39pm □ I don’t know what to say nowJan 8, 1:39pm □ Expedia Special travel dealJan 8, 1:39pm □ More news on yahoo newsJan 8, 1:39pm □ Orkut inviteJan 8, 1:39pm □ I just want to write something that’s really longJan 8, 1:39pm □ Pizza in the lounge!Jan 8, 1:39pm DeleteSelect AllTo FolderFolders

5. Architecture ASP.net web pages C# core implementation XML module communication IMAP, IPOP3 protocols Sockets mail server networking SQL-Server database

6. Architecture (cont.) Access Options Data Access User Data Network with Email Accounts Options Filter Profile Filter Email Filter OmniMail Server Email Servers YahooUW Pine GmailUW CSE Options Display Profile Display Email Display ASP.net C# modules XML Comunication SQL Sockets IMAP POP3 Access Options Data Access User Data Network with Email Accounts Options Filter Profile Filter Email Filter OmniMail Server Email Servers YahooUW Pine GmailUW CSE Options Display Profile Display Email Display ASP.net C# modules XML Comunication SQL Sockets IMAP POP3 Data flow from server to clientData flow from client to server

7. Lifecycle Model Staged Delivery Software Concept Requirements Analysis Architectural Design Stage 1: Detailed design, code, debug, test, and delivery Stage 2: Detailed design, code, debug, test, and delivery Stage 3: Detailed design, code, debug, test, and delivery Stage 4: Detailed design, code, debug, test, and delivery Basic Multiple Email Checking Feature UI Improved Address Book Integration Instant Messenger

8. The Workers Project Manager (1 person) Make sure the project is on schedule Understand overall design and architecture well Mediator between other team members Code on a smaller piece of the project Developer (± 6 people) Design, code, and debug his/her own part Tester (± 6 people) Each developer tests somebody else’s code

9. Developer’s Skills Database Email protocols C# Web programming UI design Computer networks

10. Feasibility Rationale Most technologies are taught here Software required is provided in the labs Help and references are available Possible risks: Personal issues Unavoidable technical issues

11. Assumptions Emails are accessible Work email  security control problem The system is reasonably fast Users trust us Learning curve for new technologies is not too big

12. Thank You Any questions?