Oftware Equirements Pecification: Ndroid Latform
Oftware Equirements Pecification: Ndroid Latform
FOX
SOFTWARE REQUIREMENTS SPECIFICATION
DOCUMENT
ANDROID PLATFORM
VERSION: (1.0)
DATE: (12/10/2011)
1
12-10-2011
TABLE OF CONTENTS
1. Introduction ..............................................................................................................................................................3 1.1 Purpose ................................................................................................................................................................3 1.2 Scope....................................................................................................................................................................3 1.3 Definitions, Acronyms, and Abbreviations ..........................................................................................................3 1.4 References............................................................................................................................................................3 1.5 Overview .............................................................................................................................................................3 2. Overall Description ....................................................................................................................................................4 2.1 Product Perspective ............................................................................................................................................4 2.1.1 System Interface ..............................................................................................................................................4 2.1.2 Hardware Interfaces ........................................................................................................................................5 2.1.3 Software Interfaces ..........................................................................................................................................5 2.1.4 Communications Interfaces .............................................................................................................................6 2.2 Product Functions ...............................................................................................................................................6 2.3 User Characteristics ............................................................................................................................................7 2.4 Constraints ..........................................................................................................................................................8 2.5 Assumptions and Dependencies ..........................................................................................................................8 3. Specific Requirements ...............................................................................................................................................8 3.2 Performance Requirements .................................................................................................................................8 3.3 Logical Database Requirements ..........................................................................................................................9 Tables required :- .......................................................................................................................................................9 3.4 DesignConstraints ................................................................................................................................................9 4. Appendix ..................................................................................................................................................................10 4.1 Appendix a ..........................................................................................................................................................10
2 12-10-2011
1. INTRODUCTION
The purpose of this document is to present a detailed description of the system FOX. It will explain the purpose and features of the system, the interfaces of the system, what the system will do and the constraints under which it must operate. This document is intended for both the stakeholders and the developers of the system.
1.1 PURPOSE
The Purpose of FOX is to act as a voice based assistant informing the user about his/her schedule and daily activities through a voice based interface. The utility widgets like Calendar, Social Networking Sites and Weather etc. will be provided initially. More widgets can be added onto the framework later.
1.2 SCOPE
The system will consist of widgets. Widgets will interface the system to external applications like alarm, calendar, Weather etc. The system will speak out the data received by the widgets in a human voice. The user can interact with the system using commands. The system will process the voice input from user simultaneously as it speaks. The System starts up in two ways, one being Normal Start and second Alarm Start.
1.4 REFERENCES
(1) http://developer.android.com (2) http://code.google.com (3) http://www.ispeech.org
1.5 OVERVIEW
In coming sections we have described the product FOX in varying levels of Detail. Section 2 deals with the Product Perspective which outlines all tangible requirements of the system, its interfaces and operational procedure. In
3 12-10-2011
section 3 we go in depth of Actual functional requirements, relations and databases, constraints and attributes of the system.
2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
It is an application that will run on the users android based mobile phone. The user can perform the following operations: Set sequence of playback Play widgets. Set alarm. Example of some voice commands : a) Play b) Pause c) Next
12-10-2011
Calendar Widget Screen a. b. c. d. List of events Play button Delete Event Refresh
Settings Screen a. b. c. d. e. Voice Male/Female Sequence of events during playback Profile Facebook Connect About
Backgrounds
5 12-10-2011
Wi-Fi Wi-Fi is a mechanism for wirelessly connecting electronic devices. A device enabled with Wi-Fi, such as a personal computer, video game console, smartphone, or digital audio player, can connect to the Internet via a wireless network access point. An access point (or hotspot) has a range of about 20 meters (65 ft) indoors and a greater range outdoors 3G 3rd generation mobile telecommunications is a generation of standards for mobile phones and mobile telecommunication services fulfilling the International Mobile Telecommunications-2000 (IMT-2000) specifications by the International Telecommunication Union EDGE Enhanced Data rates for GSM Evolution (EDGE) (also known as Enhanced GPRS (EGPRS), or IMT Single Carrier (IMTSC), or Enhanced Data rates for Global Evolution) is a digital mobile phone technology that allows improved data transmission rates as a backward-compatible extension of GSM. EDGE is considered a pre-3G radio technology and is part of ITU's 3G definition 4G 4G is the fourth generation of cellular wireless standards. It is a successor to the 3G and 2G families of standards.A 4G system is expected to provide a comprehensive and secure all-IP based mobile broadband solution to laptop computer wireless modems, smartphones, and other mobile devices.It has data speed of 100 Mb/s 1 Gb/s.
2.2PRODUCT FUNCTIONS
Application Controller: get_voice_input():Accepts voice commands from user. speech_to_text(): Converts voice to text. analyze_text(): Analyzes text for commands. text_to_speech():Converts text to speech. 6 12-10-2011
scan_widgets():Checks if any new events have occurred on widgets. play_widgets():Plays widgets which have new events. set_alarm():User can set an alarm.
Widget: update_events():Updates the widget with the latest notifications. convert_events_data(): Converting notifications into a text format. delete_event(): Delete an event manually or after event expires.
2.3.1 General Users All users can be assumed to have the following characteristics: Ability to read, speak, listen and understand English. Familiarity with the operation of the basic Graphical User Interface (GUI) components of the Android operating system. Beyond the above, no further facility with computer technology can be assumed.
2.3.2 The Software Designer The Software Designer users can be assumed to have the following characteristics: A thorough knowledge of object oriented design notation. Familiarity with common design environments.
2.3.3 The Software Developer The Software developer users can be assumed to have the following characteristics: A thorough knowledge of object oriented programming. 7 12-10-2011
2.4 CONSTRAINTS
Users mobile phone must be connected to the internet for data processing. The events will be updated in real time. Incase there is no connectivity the application will not be able update the widgets dependant on internet. In absence of internet access, the application will not be able to speak out the widget data in customized human voice. Notifications will be delivered to user in default robotic voice.
3. SPECIFIC REQUIREMENTS
3.1 EXTERNAL INTERFACES
The System shall primarily have two external interfaces: Text-to-Speech engine: Facebook Connect: ispeech text-to-speech SDK shall be used. For Facebook Alerts Facebook Mobile SDK shall be used.
8 12-10-2011
4) GPRS/EDGE/Wi-Fi/3G/4G internet connectivity with minimum bandwidth of 56 Kb/s 3.2.1 System Response Time The System shall be a real-time system with 99% of interactions being less than 10 micro seconds duration. Other 1% is accounted for hardware failure and unresponsive internet connection wherein duration of Time-out would range from 50 micro seconds to 1 second. 3.2.2 System Throughput The Throughput of the System is dependent on internet connectivity. The throughput of the system is dependent on the amount of requests ispeech servers can handle, which is beyond the systems control. 3.2.3 System Concurrency The system is concurrently producing output and accepting input. The system concurrency is dependent on user input.
2.
3.4 DESIGNCONSTRAINTS
The system is designed for the Android operating system. The human voice produced as output is dependent on the sound quality of the device.
9 12-10-2011
1) Widgets Database
Attribute Name WID Name Version Ispurchased Visible Position Priority Last_Update
Attribute Type NUM VARCHAR NUM BOOL BOOL NUM NUM DATE
2) Events Database Attribute Name EID Created_time Notification_text Notification_time Attribute Type NUM DATE VARCHAR DATE Primary Key YES NO NO NO
10 12-10-2011