Software Requirements Specification
Version 1.0.0
Project Title: Self Adaptive Event Generation in Mobiles
Guide: Ms. N. Radhika
College: Amrita School Of Engineering, Coimbatore
Members:
Ravi Diwakar Shreyas Dhoke Sumit Kamra
INTRODUCTION
The project forms its foundation on an observation that the user conversation if processed can be a powerful tool for controlling various mobile in-built applications and facilities. The raw conversation can be obtained in a text form using any of the efficient mobile editions of speech to text tools. This raw text will be processed further by SAEG system to find a match in the predefined conversation patterns (These are the most general conversation used by almost all of us while talking over a mobile phone; they are enlisted in an organized fashion). Every event is associated with certain set of patterns. When a pattern is matched an event related to it is invoked. This entire decision is made when the conversation is over. So there are chances that more than one pattern is found and for every matched set the corresponding event is generated. In such case the system will make use of static or dynamic priority. In order to make user comfortable with the system certain customization options are also provided. The system will behave smartly by analyzing the user behavior over a period of time and take in to account the event requirement of the user. The reliability of text and in turn the performance of the system depends on how efficiently the speech to text tool is performing. In current mobile market a whole lot of phones are available having one or the other smart feature on a heavy price or low performance. In such situation such kind of project can be a great success where we are aiming at integration and enhancement of existing features and introduction of new smart features without increasing cost and performance requirements.
PURPOSE
The objective of the project is to deliver a reliable and user friendly functionality for existing mobile phones, which facilitates users to control the events (automatically generated by the cell phone based on conversation) To provide various possible automations in 3G mobile phones with minimal processing power and memory usage within real time. To bring the features of smart phones and PDAs in common hands.
To make the mobile phones less hectic and more user friendly by relating the functionality to their daily activities and providing suitable customization option.
Implementing the conversation based processing of events generated in a mobile phone. Conversation on phone gives clues of the user task schedule and help in synchronizing events with it.
Implementing the user behavior analysis i.e. how the user uses the phone, whether he is a message maniac or talks a lot or gives more miscalls etc. Based on this the events can be easily prioritized
Providing options for setting the static and dynamic priority of the events. Dynamic priority will be adjusted by the system based on the user behavior analysis results. The static priority can be set randomly.
Building cost effective software with more general usage as the jar file can be deployed in most of the java supporting operating systems with a specified minimum storage and processing speed.
Lessening the manual effort to remember calling, messaging etc .The reminders will be generated for each task based on the conversation analysis results.
DOCUMENT CONVENTIONS
Throughout this document, the following conventions have been used: -
Font Times New Roman Size 16 for Main Headings Size 14 for Sub Headings Size 12 for the rest of the document.
INTENDED AUDIENCE
This document is intended to serve the needs of the developers of SAEG mainly. It could also be of great use to the users and testers of the SAEG system. It aims at describing the approach to the development of the system and the procedures to implement it in a mobile phone. It can also be used to familiarize the user with the system with an overall
idea. So far, there has been no significant advancement on this idea which is relatively new but could be a great commercial success.
SCOPE
Only user can tell accurately what he wants and when he wants. So instead of relying completely on the keypad and screen input we can make use of user conversation over mobile. The conversation will be a clue to the user schedule and activities. Processing the conversation we can easily predict what type of service he wants to use and at what time. Getting some basic time information the event can be invoked at that time. The events like making a call, sending a message and setting an alarm can be automatically generated.
LIST OF ABBREVIATIONS
API CDC CLDC JAD JAR J2ME KVM MIDP SAEG Application Programming Interface Connected Device Configuration Connected Limited Device Configuration Java Application Descriptor Java Archive Java 2 Micro Edition K Java Virtual Machine Mobile Information Device Profile Self Adaptive Event Generation
REFERENCES
o [Link] o [Link] o [Link] o [Link]
o [Link] o J2ME in NUTSHELL by O`Reilly o The Complete Reference J2ME o Antero Taivalsaari, JSR 30: J2ME Connected, Limited Device Configuration, [Link] o Jim Van Peursem, JSR 37: Mobile Information Device Profile for the J2ME Platform, [Link] o Wireless Tech Tips, J2ME Tech Tips: February 26, 2002.
[Link] o Digia. (2003). Programming for the Series 60 Platform and Symbian OS. John Wiley & Sons. o de Jode, M. (2004). Programming the Java 2 micro edition for Symbian OS: a developer's guide to MIDP 2.0. John Wiley & Sons, Ltd. o Lindholm, T. & Yellin, F., Java(TM) Virtual Machine Specification, Second Edition, Addison-Wesley, 1999, 496p <[Link] o Sun Microsystems, Inc, Connected, Limited Device Configuration, Specification Version 1.0 <[Link] [Link]> o Sun Microsystems, Inc, J2ME(TM) Connected Device Configuration, Proposed Final Draft, 30.08.2000 <[Link] o Sun Microsystems, Inc, Java(TM) 2 Platform Micro Edition (J2ME(TM)) Technology for Creating Mobile Devices, White Paper, 19.05.2000 <[Link] o Sun Microsystems, Inc, Mobile Information Device Profile, JCP Specification, 1.9.2000 <[Link]
OVERALL DESCRIPTION
PRODUCT PERSPECTIVE
The SAEG system aims to make the mobile phone smarter than ever without putting extra burden on storage and processing requirements. Now a days people are getting more and more busy. With the revolution in mobile communication, a mobile is proved to be one of the best personal assistants. Practically it is not possible for all to carry a PDA or high functionality mobile phone to assist them. The project mainly aims at solving this problem. The end product can be deployed on any 3G mobile running java based operating system.
PRODUCT FUNCTIONS
The proposed system makes use of the user conversation over mobile phone instead of purely depending on the key pad or screen input. o The conversation is converted into text using a speech to text tool. o The tool uses a grammar to identify the words. o The words are redirected to a storage structure e.g. File. o The system maintains a set of text patterns to map words in conversation with the events. o The system predicts the events and notify them to user automatically o Now its up to the user whether to accept or discard the event. The proposed system provides automation without compromising on the simplicity and processing capability of the existing system. Moreover it can be expanded for most of the 3g mobile sets. The users need not to remember all tasks now, as we have a system to monitor the entire conversation. He can also configure system according to his wish, whether he want to turn it off, increase the priority of a particular event or reminder etc.
USERS AND CHARACTERSTICS
The user of SAEG system would be a general mobile phone user who possesses a java enabled phone. The phone should have an in- built speech to text converter. The user might have to train the system with his voice. This would ensure a better performance from the system. It is also assumed that the user converses in English language only, that too in the standard language i.e. does not uses much slang.
OPERATING ENVIRONMENT
S/W Environment
o Netbeans 5.5.1 IDE o Netbeans Mobility pack Includes packages needed to develop mobile applications with a default emulator. o J2ME J2ME is a family of specifications that defines various downsized versions of the standard Java 2 platform; these downsized versions can be used to program consumer electronic devices ranging from cell phones to highly capable Personal Data Assistants (PDAs), smart phones, and set-top boxes.
H/W Specifications
128 kilobytes memory for Java runtime 32 kilobytes memory for runtime memory allocation Limited user interface Network connectivity -- typically wireless
S/W Specifications
Speech to text conversion tool Java enabled Mobile OS Java Application Loader
GENERAL CONSTRAINTS, ASSUMPTIONS, DEPENDENCIES, GUIDELINES
It is assumed that the user possess a java enabled mobile phone which has an in built speech to text converter. In addition, it is also assumed that the efficiency of the speech to text converter is very high and is trained according to the voice of the user. It is assumed that the user is proficient in spoken English and converses in formal English only. It is important for the speech to text conversion as well as the working of the system. The system is also dependent on the location of the user. The noises around the system can cause disturbances and may result into malfunctioning of the system.
EXTERNAL INTERFACE REQUIREMENTS
USER INTERFACE
The user interface would largely depend on the mobile phones implementation. The input to the system would be through the text to speech converter. The events generated could be viewed one by one after the call finishes. The events could be executed at that moment
or could be added to the To Do List for a later time. The reminders to the user would be in the form of alarms generated through the AMS of the mobile.
SOFTWARE INTERFACE
The user can edit the settings of the software by enabling or disabling the software. The user can also protect it by applying a password to the system. The user can also choose to enable or disable a particular kind of events. The events related to a particular person could also be enabled or disabled.
SYSTEM FEATURES
SETTINGS
There are two types of settings in the system, Security settings and the System settings. The security settings are related to enabling/ disabling of the system along with the password settings. The System settings consist of enabling or disabling a particular type of event. It also consists of settings for a particular person i.e. blocking the particular person from the system so that no events would be generated for that person.
EVENT GENERATION
The events would be generated based on user conversation. The generated events could be seen immediately after the call ends. The events could be triggered to the use, denied or could be saved in a To Do List for future. There would be different options for different events. For example, an event related to calling would have an option of address book while an event related to saving a number would have options in the form of yes or no only.
ADDING AND REMOVING VERBS
New verbs could be added to the system and existing verbs can be removed. While adding a new verb, the action related to that particular verb would have to be specified.
For example, if we are adding the verb speak, the corresponding action would be the call event. The existing verbs and their respected actions can be viewed and could be deleted from the system. There would be a few initial verbs provided in the system.
PRIORITY
The events will have priority among themselves. A higher priority event would be generated ahead of a lower priority event. The events related to the current time would have a higher priority than future evens. The priority of various events could be interchanged by moving them up or down in the organize priority list.
OTHER NON-FUNCTIONAL REQUIREMENTS
PERFORMENCE REQUIREMENTS
The performance of the system is highly dependent on the efficiency of the speech to text converter. The richness of the grammar of the system would also be an important factor in the performance of the system. Higher the number of verbs in the system, the better would be the performance. The length of the call would also be an important factor. A long call would result into a longer input file which would require higher processing.
SECURITY REQUIREMENTS
It is advised to use the security settings of the system because an alteration from some other entity may result into the degradation of the performance of the system. It is also advised to disable the events which are not frequently used. This would result in a better performance of the system.
SOFTWARE QUALITY ATTRIBUTES
The system has been programmed in Java which makes it platform independent and portable. The software could be ported to any java enabled system. It could be ported
through cable or Bluetooth. The software could be further altered to implement new types of events with ease.