Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 10

FOX Requirements Specifications Document

FOX
SOFTWARE REQUIREMENTS SPECIFICATION

DOCUMENT

ANDROID PLATFORM

VERSION: (1.0)

DATE: (12/10/2011)
1

12-10-2011

FOX Requirements Specifications Document

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

FOX Requirements Specifications Document

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.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS


User : Client Android: OS on users device. Mobile Phone: Users handheld device.

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

FOX Requirements Specifications Document

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

d) Next Widget e) f) Remind Me Stop

2.1.1 SYSTEM INTERFACE


In order of appearance: Application Icon Splash screen Menu Screen a. b. c. d. e. f. Alarm Calendar Weather Facebook Birthdays Settings

Alarm Screen a. b. c. Set Time Set Tone Repeat On Days 4

12-10-2011

FOX Requirements Specifications Document

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

2.1.2 HARDWARE INTERFACES


Minimum Mobile Phone Requirements1) Touch Screen Display 2) 512MB RAM 3) 500 MB Flash Memory 4) 400MHz Processor

2.1.3 SOFTWARE INTERFACES


1) Android 2.2 OS 2) Text to speech engine 3) Speech to text engine 4) Example of Widgets Interface a. b. c. d. Calendar Weather Birthdays Facebook Etc.

5 12-10-2011

FOX Requirements Specifications Document

2.1.4 COMMUNICATIONS INTERFACES


GPRS General packet radio service (GPRS) is a packet oriented mobile data service on the 2G and 3G cellular communication system's global system for mobile communications (GSM). GPRS will be used to connect the users mobile device to the text to speech engine and speech to text.

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

FOX Requirements Specifications Document

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 USER CHARACTERISTICS


We have identified three potential classifications of users of our system: Software Designers: They will use the system as a means of laying out the design of an as yet unimplemented system. Software Developers: These are the people that take the model generated by the designers and implement it in code. The User: They will be the end-users who would interact with the system.

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

FOX Requirements Specifications Document

An understanding of development in Android operating system.

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.

2.5 ASSUMPTIONS AND DEPENDENCIES


The user cannot control the external applications through the system. The system will not guarantee the information provided by external applications. The user will have to set the alarm on the system. The external alarm application will not be interfaced with the system. External application Authorization Widgets such as facebook will require authorization.

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.

3.2 PERFORMANCE REQUIREMENTS


The performance of this product is dependent on the underlying hardware. To ensure the specified performance can be achieved, the following hardware is required. 1) 400MHz Processor 2) 512MB RAM 3) 30 MB Flash Memory

8 12-10-2011

FOX Requirements Specifications Document

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.

3.3 LOGICAL DATABASE REQUIREMENTS


Database Management System 1) Sqlite (Mobile Phone) Tables required :1. Widgets Database --WID, Name, Version, Ispurchased, Visible, Position, Priority, last_update

2.

Events Database (Internal) -- EID,Created_time,notification_text, notification_time.

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

FOX Requirements Specifications Document

4. APPENDIX 4.1 APPENDIX A


TABLES
Database Tables :

1) Widgets Database

Attribute Name WID Name Version Ispurchased Visible Position Priority Last_Update

Attribute Type NUM VARCHAR NUM BOOL BOOL NUM NUM DATE

Primary Key YES NO NO NO NO NO NO NO

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

You might also like