Unified Distributed (UDub Mail) Life Cycle Objectives Sachin Pradhan Gabriel Maganis

Overview Operational Concept System Requirement System and Software Architecture Lifecycle Plan Feasibility Rationale

Operational Concept What is it? –A web based service that provides its users with the ability to manage their s from multiple accounts. User Community –Anyone using multiple accounts. Major Benefit –Save time –Simplify the task of checking s from multiple accounts –Provide organization Scope –Have an account for each user –Provide an intuitive UI –Provide some level of security –Not provide outgoing service –Not store for the user

System Requirements Client –Web browser –Incoming/Outgoing mail server –Incoming mail server protocol (IMAP) Server –Secure authentication of clients –Database to store the user settings –Functionality Check Composer and send Delete

System and Software Architecture Web Interface on the client side Database that stores the user information Web server that handles management Mail servers

System and Software Architecture (cont.)

Sample UI

Life Cycle Plan Stakeholders –Users –Developers –System administrators Why? –To provide a fast and secure access to s from multiple accounts in one interface. What? –Design the project architecture –Design and implement the UI and database schema –Operational prototype –Testing and Documentation –Final Release Who? –Later How? –Later How? –Later

Feasibility Rationale Assumptions –The user has multiple accounts –Our system is going to be reasonably fast –The user trusts our system Risks –Familiarity with technology and writing secure code –UI design experience –Other security risks