4.1 Overview4.2 Updates to the system4.3 Extensibility4.3.1 Extensible design4.3.2 Future workMercuryMessaging Requirements Document Prepared By: Vinay Krishnani Hoi Li Phuong Luong Vinay Mavinkurve Kristine Kay Surquia Andy VarvarezisRevision History REVISED BY: REVISED DATE AND TIME: Phuong Luong Friday, January 28, 2005, 08:25:40 PM Vinay Mavinkurve Tuesday, February 01, 2005, 11:33:30 PM Phuong Luong Tuesday, February 01, 2005, 12:56:30 PM Evangelos Varvarezis Friday, February 18, 2005, 8:00pm Vinay Krishnani Tuesday, February 22, 2005, 12:40 PM Phuong Luong Wednesday, February 23, 2005, 7:20 PM Vinay Krishnani Friday February 25, 2005Table of Contents 1. Introduction 1.1 Purpose 1.2 Project Scope and Product Features 2 Functional Requirements 2.1 Network Configuration 2.2 Built-in Games 2.3 Mobile text-messaging 2.4 Address Book 2.5 Conversation Logging 2.6 MercuryMessaging Email Client 2.7 Look and Feel 2.8 Live Webcam 2.9 MercuryMessaging Audibles 2.10 File Transferring 2.11 Anti-Virus software 3 Non-functional Requirements 3.1 Look and Feel 3.2 Built in games 3.3 Conversation Logging 3.4 MercuryMessaging Email Client 3.5 Live Webcam 3.6 MercuryMessaging Audibles 4 System Evolution 4.1 Overview 4.2 Internal Documentation 4.3 Updates to System 4.4 External Documentation 4.5 Extensibility 5 User Interaction 5.1 Overview 5.2 Input/Output 6 Technology Decisions 6.1 Data Storage 7 Graphical User Interface Appendix A. Glossary IndexList of Figures 1 Use Case for Instant Messaging each other2 Context Model of MercuryMessaging System3 Use Case for Built-In Games4 Use Case for Mobile Text Messaging5 Use Case for Address Book Plug-in6 Use Case for Conversation Logging7 Use Case for MercuryMessaging Email Client8 Use Case for User making individual changes to the user interface9 Use Case for User adding a skin to change the entire interface at once10 Use Case for Webcam11 Use Case for MercuryMessaging Audibles12 Use case for File Transferring 13 Sample Documentation Entry14 Screen shot of Mock Interface1 Introduction 1.1 Purpose This requirement document describes the software functional and non-functional requirements for MercuryMessaging (MM), a universal messaging system. This document is intended to be used by the members of the project team that implement and verify the correct functioning of the system, as well as for Project Managers. 1.2 Project Scope and Product Features The MercuryMessaging - Unified Messenger Software is a combination of various Instant Messaging (IM) clients into one interface. Users can view buddy lists from various services, such as AOL Instant Messenger, MSN Messenger and Yahoo Messenger, and exchange text messages with them instantly. This approach is considered largely because popular IM services do not communicate with each other. As a result, people use different IM services simultaneously on their personal computers to communicate with contacts who reside in different communities which results in a loss of useful system resources. Figure 1 1.2.1 MercuryMessaging is a Windows-based software application. This version is designed for Microsoft Windows XP. 1.2.2 MercuryMessaging supports no other than the following IM client versions: 1.2.2.1 AOL Instant Messenger Version 5.9 1.2.2.2 Yahoo Instant Messenger 6.0 1.2.2.3 MSN Messenger 6.2 1.2.2.4 ICQ 4.0 1.2.2.5 MIRC 6.16Figure 2 2 Functional Requirements This section serves to specify the requirements (features) that MercuryMessaging offers. Therefore it is here that the system’s functionality and its limitations are discussed, disregarding how they are implemented in terms of design. 2.1 Network Configuration 2.1.1 MercuryMessaging connects to the different IM Client servers using specific protocols that the clients' server uses. 2.1.2 MercuryMessaging supports utilities that are available and independent to the various clients which are2.1.2.1 Global invisibilityAn option for the user’s screen name to be hidden from other users’ buddy lists 2.1.2.2 WebcamCommunicate with other MercuryMessaging users visually via webcam. 2.1.2.3 Mobile text-messagingSend a message to another person’s mobile device from a specific client. 2.1.3 MercuryMessaging supports File Transfer capabilities within specific versions of the client software for users in both sending/receiving parties. 2.2 Built-in Games 2.2.1 System allows users to play a network-able Chess game. 2.2.2 Features include 2.2.2.1 Game on Local MachineThe game is created and executed on the local machine, allowing users to play against an opponent. 2.2.2.2 Game on the Network Game is created on the network by initializing a port that other users are able to join. Figure 32.3 Mobile text-messaging 2.3.1 System allows users to send text messages up to 160 characters to members of the buddy list. 2.3.2 Features include 2.3.3.1 Idle/Away By changing their status to 'idle' or 'away' the user has an option to forward text messages to their mobile device 2.3.3.2 Text messages are free of cost to the sender. 2.3.3.3 There is no means to communicate a reply through the Mobile device to the MercuryMessaging user. 2.3.3 The phone/pager number as well as the phone service i.e Sprint, AT&T of the recipient shall be accessible through a separate, independent module (window). Figure 4 2.4 Address Book 2.4.1 System allows users to store and retrieve information related to members on their buddy-lists. 2.4.2 Features include2.4.2.1 Name, Address, Phone Numbers, Email, Mobile Service provider The user is able to store the above information through a user-friendly module. 2.4.2.1.1 This information is fully editable to the user. 2.4.2.1.2 The aforementioned information is stored by means of a .CSV (comma separated value) file stored on the user's machine. 2.4.2.1.3 The user has the ability to search for contacts through a feature that scans the length of the user's address book. 2.4.3 Exporting Contact Lists 2.4.3.1 Mercury messaging allows exporting of the contact list in “.CSV” format. Other major into any e-mail client / address book such as Microsoft Outlook can import this file without interference configuration. Figure 5 2 .5 Conversation Logging 2.5.1 System logs the instant messaging conversation in all five instant messenger clients, 2.5.2 Features include 2.5.2.1 Search User is able to search the activity of one contact by date. 2.5.3