English Voice and Text to Sinhala Text

fullfattruckΚινητά – Ασύρματες Τεχνολογίες

10 Δεκ 2013 (πριν από 3 χρόνια και 4 μήνες)

49 εμφανίσεις







English Voice and Text to Sinhala Text
Translator Application for Android
Devices.


Software Requirements Specification


Degree of Bachelor of Science in
Information Technology


Sri Lanka Institute o
f Information Technology, Sri Lanka


2
th
April
, 2012




i


Project ID

:
PWD2012
-
18


Student’s Name

Student ID

Signature


Eashwarage D.B.S.




IT 10 6026 38


Dasanayaka D.M.M.L.




IT 10 6018 84



Perera U.L.P.H.




IT 10 6033 14



Jayathilaka K.K.G.I.



IT 10 6063 84


WickramanayakeW.A.V.M


IT 10 6071 38



Fernando M.L.A.S



IT 10 6066 98




27
th

February, 2012


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Mr.
Y.D. Jayaweera



ii


Table of
Contents

1 Introduction

................................
................................
................................
.............................

1

1.1

Purpose

................................
................................
................................
........................

1

1.2

Scope

................................
................................
................................
...........................

1

1.3 Definitions, Acr
onyms, and Abbreviations

................................
................................
.....

2

2 Overall Descriptions

................................
................................
................................
...............

3

2.1 Overview

................................
................................
................................
..........................

3

2.2 Product perspective

................................
................................
................................
..........

4

2.2.1
System interfaces

................................
................................
................................
......

4

2.2.2 User interfaces

................................
................................
................................
..........

5

2.2.3 Hardware interfaces

................................
................................
................................
..

8

2.2.4 Software interfaces
................................
................................
................................
....

9

2.2.5 Communication interfaces

................................
................................
......................

10

2.2.6 Memory constraints

................................
................................
................................

10

2.2.7 Operations

................................
................................
................................
...............

10

2.2.8 Site adaptation requirements

................................
................................
...................

10

2.3 Product functi
ons

................................
................................
................................
...........

11

2.4 User characteristics

................................
................................
................................
........

12

2.5 Constraints

................................
................................
................................
.....................

14

2.6 Assumpti
ons and dependencies

................................
................................
.....................

14

2.7 Apportioning of requirements

................................
................................
........................

14

3 Specific Requirements

................................
................................
................................
..........

15

3.1 External interface requirements

................................
................................
.....................

15

3.1.1 User interfaces

................................
................................
................................
........

15

3.1.2 Hardware interfaces

................................
................................
................................

18

3.1.3 Software interfaces
................................
................................
................................
..

19

3.1.4 Communication interfaces

................................
................................
......................

19

iii


3.2
Classes/Objects

................................
................................
................................
..............

19

3.3 Performance requirements

................................
................................
.............................

21

3.4 Design constraints

................................
................................
................................
..........

21

3.5 Software system attributes

................................
................................
.............................

22

3.5.1 Reliability

................................
................................
................................
................

22

3.5.2 Availability

................................
................................
................................
.............

22

3.5.3 Security

................................
................................
................................
...................

22

3.5.5 Repair ability

................................
................................
................................
...........

22

3.6 Other requirements
................................
................................
................................
.........

23

3.6.1 Safety Requirements

................................
................................
...............................

23

3.6.2 Software
Quality Attributes

................................
................................
....................

23

3.6.3 Business Rules

................................
................................
................................
........

23

Supporting Information

................................
............................

Error! Bookmark not defined.

Refere
nces

................................
................................
................................
................................

24

Appendices

................................
................................
................................
................................

A




iv


List of

Tables And Figures


Table 2(Use Case): Get Translated Text

................................
................................
..................

12


Figure 1: Input Interface

................................
................................
................................
............

5

Figure 2: Translated Interface

................................
................................
................................
....

6

Figure 3: Main Interface

................................
................................
................................
............

7

Figure 4: Speech Interface

................................
................................
................................
.........

8

Figure 5: Use Case Diagram

................................
................................
................................
....

11

Figure 6: Deployment Diagram

................................
................................
................................

A




1


1 Introduction

1.1

Purpose


This is the software requirement specification of
English Voice and Text to Sinhala Text
Translator Application for Android Devices.The purpose of this document is to present a
detailed description of the inventory handling system.

This document describes system
interfaces, user interfaces, hardware interfaces, software interfaces, communication
interfaces, memory constraints, operations required by the user and site adaption
requirements. All these parts are intended primarily for
the customers who will use this
android application. And also this will help the development team to have an overview about
the requirements of the application and work towards the target.

Furthermore this document describes the functions of this product.
This section of the
document gives the customer a brief idea about the main functionalities of the android
application. User characteristics section clearly point out the kind of users that will use this
product. This section is helpful to the development
team. They can have an idea about the
kind of users that will use this system. The constraints part of the document explains the
limitation the developers face while developing the product. This is useful for the developers.
The assumptions and dependencie
s part is helpful to both the customer and the developer.
The next section
apportioning of requirements

explains
the order in which requirements are
to be implemented.

This will be very helpful for the developers to monitor their progress.

The external int
erface requirements explain user interfaces, hardware interfaces, software
interfaces and communication interfaces in a more detailed manner.

1.2

Scope


This document covers requirements to develop the
English Voice and Text to Sinhala Text
Translator Applicat
ion

for android devices.
Today’s w
orld mobile devices have a very
important place. Because it
portable and easy to use. Among them Android devices are the
most popular. Android is a powerful OS. It has rich interfaces. Many smart phones use
android as the

operating system.Already there is an English voice detection mechanism in
2


android. It enables users to speak in English and then the application detects the voice and
displays it in English texts
. The software product we are going to develop will get
gets

that
English text and translate it into Sinhala sentence.

By using this android application
People
who likes to use Sinhala, they can send their messages in Sinha
la instead of using English or
S
inglish.

English sentence can be converted to Sinhala sentenc
e in an Android platform. This
application will take the advantage of “Voice Recognition” and the output of this application
may be the input of our system, or the sentence can be manually inputted.First English
sentence is mainly broken to three parts. Pa
rts will be rearranged to Sinhala sentence format,
the relevant subject, verb and the objects are matched and the verb sentence is detected
through online database. Word meanings are converted to Sinhala using English to Sinhala
dictionary. The Subject nou
ns are

converted to Sinhala using Singlish

format. Apply the verb
conditions to the nouns.

This android application p
rovides a basic grammatically correct English sentences or an
English voice sentence and the sentence will be translator to Sinhala text.
Application can be
used to send Sinhala se
ntences using SMS/MMS /E

Mails. Furthermore r
etrieved messages
can be converted to Sinhala if necessary.

And also this application c
an
be
use
d

to store notes.

1.3 Definitions, Acronyms, and Abbreviations

Comment:
Glossary of that will be used throughout the documents, as well as in other
documents based on this one. Usually in the form of table.

E.g.: Acronyms

IC

Imagine Cup

VB

Visual Basic

VG

Visual Gaming

3


2 Overall Descriptions

2.1 Overview


This
English voice and text to Sinhala text translator Application is design for use on Android
devices and this application using a large database witch store in a [1] remote server. This
system does not require a login
to access software and there are some requirements to use this
on Android devices. All Android Devices that use this software must support Sinhala
Unicode and [2] Google Voice API.
An Internet connection is necessary to access the system.
There must be a we
ll preforming Processor and Higher RAM integrate in Android Device
that hoping install this application to have a better
performances
of software.


Figure
1
: Overview

4


2.2 Product perspective


The English Voice and Text to Sinhala Text Translator
Android
Application
will
devel
op for
Translate an English sentence to Sinhala sentence. This application is not like an English
Sinhala dictionary, it converts whole sentence, not single words to Sinhala. There are several
similar applications like
English to Sinhala and Sinhala to Eng
lish dictionaries

(it converts
single words not sentence), Google translator (it translates English sentences to several
languages but not to Sinhala) and

[12] “Bilingual Expert for English to Sinhala”

(
Still it’s
under development
).


2.2.1 System
interfaces

Application will need the below requirements to execute correctly with the device

Android platform 2.3.3



5


2.2.2 User interfaces


Figure
2
:
Input

Interface

6



Figure
3
:
Translated

Interface


7



Figure
4
: Main

Interface


8



Figure
5
: Speech Interface


2.2.3 Hardware interfaces


Chipset

ARM
-
based

Single Core
Processor

For the first release, Android is primarily
targeted towards mobile handsets and po
rtions
of the platform, Dalvik VM graphics processing,
9


currently assume ARM architecture.

Memory

128 MB RAM; 256 MB
Flash External

Android can boot and run in configurations with
less memory, but it isn't recommended.

Storage

Mini or Micro SD

Not necessary for basic bring up, but
recommended.

Primary
Display

QVGA TFT LCD or
larger, 16
-
bit color or
better

The current Android interface targets a touch
-
based HVGA resolution display with a touch
-
interface no smaller than 2.8 inches in size.
Howeve
r, smaller displays will suffice for initial
porting.

Navigation
Keys

5
-
way navigation with 5
application keys, power,
camera and volume
controls


User input interface.

Sounds

Speaker and a
Microphone

R
equired for basic
Voice input and output
.

USB

Standard mini
-
B USB
interface

Android uses the USB interface for flashing the
device system images and debugging a running
device.

3G

HSPA Internet
connectivity

N
ecessary
for initial
Server connectivity
bring
up.


2.2.4 Software interfaces


10


The implementing system will be connected to some of the application inbuilt. Keyboard
interface is used to take the inputs from the users.
‘a
ndroid.speech


class interface will be
used to implement the speech recognition functions.

android.text


package
interface
will be
used to handle all the text base functions and the clipboard function with the system .
SQLite
database component will be used to access frequent data.


2.2.5 Communication interfaces

The
User

must
need to
connect to the Internet
for the f
ull functionality of the application



3G
HSPA
Connection
is required
.



System will use the basic protocols FTP
, HTTP
, WAP
.


2.2.6 Memory constraints


Application is expected to use 32MB of RAM and 20MB of external memory for database
management.

2.2.7
Operations


User will need to text the English sentence to the application. The output sentence will be
displayed and user will need to copy the translated text sentence as he/she desire, to send
SMS/MMS or to save as a note.

2.2.8 Site adaptation
requirements


Application can be downloaded through Android Market or Any source of media. If
application is from removable card the installation
file
can be directly run from the phone and
the application will be automatically installed
after confirmation
request
, if the application is
downloaded through internet it will be automatically installed after download with a
confirmation request.



1
1


2.3 Product functions






Translate to Sinhala
Paste Selected English Text
Type English Text
Speak
Get Translated Text
User
Copy Translated Text
Validate Sentence
if valid
<<extend>>
<<include>>
English to Sinhala Translator

Figure
6
: Use Case Diagram

12


2.4 User characteristics

2.4.1
Get Translated Text

Use Case

Get Translated Text

Actors

User.

Pre
-
condition

Valid English
Grammar

Sentence

Flow of Events

1.

Select “Translate”

2.

Wait Till Translate.

a.

Divide Words

b.

Process Database

c.

Validate Sentence

d.

Sinhala
Vocabulary Translator

e.

Sinhala Sentence Generator

f.

Sentence Organizer

g.

Edit post content

h.

Process valid post

Post condition

Sinhala

sentence

Alternatives

3a.

If user input
sentence

grammar

incorrect display error
message.

4a.

If “Unicode” Fonts are not installed,
Display a Massage.

Table
1
(Use Case
): Get Translated Text

2.4.
2

Speak

Use Case

Speak

Actors

User.

Pre
-
condition

Valid English Grammar Speak able User

Flow of Events

1.

Open Application.

2.

Select “Text” Option.

3.

Call the Sentence.

Post condition

Speak

sentence

13



2.4.
3
Type English Text

Use Case

Type English Text

Actors

User.

Pre
-
condition

Valid English Grammar Know User

Flow of Events

1.

Open Application

2.

Select “Text” Option

3.

Type Sentence

Post condition

Type English Text

Sentence


2.4.
4
Send SMS/MMS

Use Case

Send SMS/MMS

Actors

User.

Pre
-
condition

Sinhala Generated Sentence

Flow of Events

1.

Copy
Text

2.

Open MMS/SMS application

3.

Paste

Post condition

Save Sinhala sentence


2.4.5 Paste Selected English Text

Use Case

Paste Selected
English Text

Actors

User.

Pre
-
condition

Sinhala Generated Sentence in Clipboard

Flow of Events

1.

Close/Minimize Application

2.

Open Notepad application

3.

Paste

14


Post condition

Sinhala sentence


2.5 Constraints

Since this project can easily be broken down into

many smaller functioning parts, there are
few major constraints. As long as the Android Marketplace is up and running and people are
still using the Android OS, it will be possible to market, maintain, and operate this
application.


2.6 Assumptions and
dependencies



The android version that have installed in the device should be 2.3(Gingerbread) or
higher than that.



The basic password authentication and role based security mechanisms will be used to
protect database from unauthorized access.



The device
should support /should have installed Sinhala Unicode.



The device should have installed English voice to English text translator application.

The product needs following third party product during the implementation period.



SMS/MMS Application is necessary

to Send and receive massages.



Notepad is required to store Sinhala massages.

2.7 Apportioning of requirements


In this section the new function that will be implemented after the core system functionalities
are

included.

'Essential
R
equirements' are the p
rimary
functions

for the current system. These
function

will
be implemented in the current version of the application



Text Translator.

'Desirable R
equirements' are to be implemented in future release or final release if possible,
but are not committed to b
y the developers.



SMS /MMS
receiver

Translation.

15




Speech to text translator.

'Optional Requirements' will be implemented at the discretion of developers.



English to Sinhala All in One Dictionary.


3 Specific Requirements

3.1 External interface requirements

3.1.1 User interfaces



Name of item


Translation page


o

Purpose


Selecting an option

o

Inputs

Converted text from GooglevoiceAPIs/received text message

o

Outputs

Sinhala sentence

o

Valid range

Consult the user

o

Accuracy


Consult the user

o

Tolerance


Consult

the user

o

Units of measure


Consult the user

16


o

Timing

Maximum timing is 3 seconds

o

Relationships to other inputs/outputs


Single output

o

Screen formats/organization



Supports low density, medium density, high
density

o

Window formats/organization


Supports sm
all,medium,large,x
-
large

o

Data formats

Characters/string




Name of item

Translated page


o

Purpose


Use converted text as a message or e
-
mail

o

Inputs

Sinhala sentence

o

Outputs


SMS/e
-
mail

o

Valid range


Consult the user

o

Accuracy


Consult the user

o

Tolerance


Consult the user

o

Units of measure


Consult the user

o

Timing

Maximum timing is 3 seconds

o

Relationships to other inputs/outputs


Multiple outputs

o

Screen formats/organization



Supports low density, medium density, high
density

17


o

Window formats/organiz
ation


Supports small, medium, large, x
-
large

o

Data formats



Characters/string




Name of item


Selection page



o

Purpose


Select an option

o

Inputs


Voice/text

o

Outputs


English sentence

o

Valid range


Consult the user

o

Accuracy


Consult the user

o

Tolerance


Consult the user

o

Units of measure


Consult the user

o

Timing

Maximum timing is 3 seconds

o

Relationships to other inputs/outputs


Single output

o

Screen formats/organization



Supports low density, medium density, high
density

o

Window formats/organizati
on



Supports small, medium, large, x
-
large

o

Data formats



Characters/string



18









Name of item


Voice recognition page



o

Purpose


Opens Google voice recognition facility

o

Inputs


English voice

o

Outputs


English text

o

Valid range


Consult the user

o

Acc
uracy


Consult the user

o

Tolerance


Consult the user

o

Units of measure


Consult the user

o

Relationships to other inputs/outputs


Single output

o

Screen formats/organization



Supports low density, medium density, high
density

o

Window
formats/organization



Supports small, medium, large, x
-
large

3.1.2 Hardware interfaces

This application deals with android devices. Such as android phones, pads, tablets.

19


3.1.3 Software interfaces

The application interacts with a voice to text
application
. That

application detects the users’
voice and translates it to English sentence.

3.1.4 Communication interfaces

The application uses internet only to send e
-
mails. To connect to the internet, the application
uses devices’ integrated internet
accessing me
thod
.

3.2 Classes/Objects

20


.


21


3.3 Performance requirements


The system we are developing
is an

experimental and advance system for English to Sinhala
Dictionary and this system depend on online data storage (online database),

the performance
of the system will depend on the client requests and the limited bandwidth of the server, the
system is mainly developed to use client resources so that the system server load will be
reduced and to increase the system performance.

As we
take the core performance of the system implementation, we haven’t given any
unwonted process for client
Android devices

as well as Server Machines
.

We have optimized the system with these areas,

Android version of Client Android Device

Performances of Cli
ent Android Device

Limitations of Google Voice API

Pronunciations of users


The performance of this Application
software

is very important. If the system gets too much
time to translate a sentence it would become a negative effect on the user who are using

the
Application. User, who will be using this system, will not be accepting to wait any delays for
Translations
. The performance of the system will depend on the Android phone processing
power and the Internet bandwidth of the ISP
.
The
Application will use
the
system
phone

resources
for the main translation
process,

however the translation process may need to
access the database stored in the server to get the Sinhala words and the correct Sinhala
sentence. To increase the performance, we will be using the i
nbuilt database functionality for
the frequent required queries, so that the application may not get delayed.


3.4 Design constraints

We have decided to develop this procedure under Prototyping Methodology. As our project
member are fully understand about the project, It will be more significant to use Prototyping
22


Methodology as it’s parallel phases will give our team members to develop
the system more
quickly and effectively .

This product will be developed basically using the IDE software as
Eclipse
which include
Java
,
XML
, programming

language
with SQL capabilities, and for support as a sub tools we
use
[2] Google Voice API, Android S
MS MMS functions

for
text contortion process

for
better optimization and for faster performances
of software.

3.5 Software system attributes

3.5.1 Reliability


When user wants to
translate
English

sentence to
Sinhala

sentence application

should
correctly deliver s
ervices as expected by the user
without

any mistake and user friendly.

The
reliability of the system shall be good if it delivers services as specified.
All
sentenceswill be
patterns

update
d

to the
database for the correcttranslat
ion
format.
Otherwise, reliability is bad
and it shall produce unexpected output
.

3.5.2 Availability

When the application has any request at any given time, application should be available
running in the phone

without any
exceptions

or any
time delays
, it
should be up and running
and able to deliver useful translation for
English

to
Sinhala

sentence at
any

time.
For this we
will be using a high priority concurrent server to serve better services to the customer
.

3.5.3 Security


Maintains of

system has res
triction for the

ordinary

users
and there are only maximum six
user have permission to maintain this system

, this way the security has been increased to
maintain a good quality system
.

For avoid hackers interaction system have

different storage medias.
Database of system and
maintain panel will be store in [1] outside server. The main Software can be install inside
Client`s android device.

3.5.5
Repa
i
r ability


23


When the system is used, system failures are inevitable. The disruption caused by failure can
be minimized if the system can be repaired quickly. So, the system should be possible to find
the problem, access the component that has failed and make changes to fix that component.
When the system has a repair, the source code should be modified
.


3.6
Other requirements


3.6.1
SafetyRequirements


For security issues, database or server may crash due to power failure or virus attacks

of
server
. Due to lack of

[1]

Database server space in the
Server
, system will have a backup
database for important data only. The backup database may contain
English to Sinhala
Dictionary Database
.

3.6.2
Software Quality Attributes


This system will be very user friendly and the user will be able to find the necessary
information with three steps clicks

or insert Text by using [2] Voice function
.

To improve
System in future there is an option to get feedbacks from users.


3.6.3
Business Rules


System will be implemented
using

[
3
]
Eclipse
IDE software for self
-
generated
codes and with
the inheritance of GPL license and team self
-
coded.

For other Google Services the Google
Inc.
has

gave permission to use those services with set of conditions.


24


References


[
1
] NQ Mobile Security Research Center, "Security Alert: New Andr
oid
Malware
DKFBootKi

Moves Towards The First Android BootKit | NQ Mobile U.S. Security
Research Center" research.nq.com. 2,
March
.
28
, 20
12
.[Online]. Available:
http://research.nq.com/?p=391 [Accessed:
March
.
28
,20
12
].

[
2
]
Android Developers
, "
Speech Input
| Android Developers
"
http://developer.android.com
.Jan
.
28
, 20
11
.[Online]. Available:
http://developer.android.com/resources/articles/speech
-
input.html
[Accessed:
March
.
28
,20
12
].

[
3
]
Eclipse
, "
Eclipse Public License
-

Version 1.0
"
http://www.eclipse.org
.
[Online].
Available:
http://www.eclipse.org/legal/epl
-
v10.html
[Accessed:
March
.
28
,20
12
].

[4] Android Developers, “User Interface Guidelines", 29 Mar 2012. [Online]. Available:
http://developer.android.com/guide/practices/ui_guidelines/index.html [Accessed
: March. 28,
2012].

[5] Android Developers, “Supporting Multiple Screens", 14 Mar 2012. [Online]. Available:
http://developer.android.com/guide/practices/screens_support.html [Accessed: March. 28,
2012].

[6] Android Developers, “package android. Hardware
", 08 Feb 2012. [Online]. Available:
http://developer.android.com/reference/android/hardware/package
-
summary.html [Accessed:
March. 28, 2012].

[7] University of new Hampshire, “iPod, iPad, and Android Apps for College Students”,
2010.[online].Available: ht
tp://unh.edu/d Software system attributesisabilityservices/ipod
-
ipad
-
and
-
android
-
apps
-
college
-
students [Accessed:March.28,2012].

[8] Systems and internet infrastructure security, “Mobile Phone Security”,
2010.[online].Available: http://siis.cse.psu.edu/pho
nes.html[Accessed:March.28,2012].

[9] Team 6g,” Software Requirements Specification for FACETs Mobile”, vol 2.0, pp 9
-
11,
Nov.2010.

25


[10] C. L. Anderson and M. Nguyen. A Survey of Contemporary Instructional Operating
Systems for use in Undergraduate Courses
. Journal of Computing Sciences in Colleges,
21:183
-
190, October 2005.

[11] Benjamin Carpenter, Ryan Daugherty, Jack Dehlin, Jay Greene , “Android Game Suite
Software Design Specification”,vol CS 430, pp 9
-
10, Mar.2010.

[12] BuddithaHettige,” BEES: Bilingu
al Expert for English to
Sinhala”[online].Available:http://www.dscs.sjp.ac.lk/~budditha/bees.htm.[Accessed: Feb
8,2012]




A


Appendices


Deployment Diagram


Figure
7
: Deployment Diagram