Department Of XXXXXXXXX

Software Requirements
Specification

For

<Text To Speech>

Prepared by

XXXXXXX,

XXXXXX.
Table of Contents

1. Introduction............................................................................2
1.1 Purpose..........................................................................................................2
1.2 Document Conventions.................................................................................3
1.3 Intended Audience and Reading Suggestions...............................................3
1.4 Project Scope.................................................................................................3
1.5 References.....................................................................................................3

2. Overall Description................................................................3
2.1 Product Perspective.......................................................................................3
2.2 Product Features............................................................................................3
2.3 User Classes and Characteristics...................................................................4
2.4 Operating Environment.................................................................................4
2.5 Design and Implementation Constraints.......................................................4
2.6 User Documentation.....................................................................................4

3. System Features.....................................................................4
3.1 System Feature 1...........................................................................................5
3.2 System Feature 2 (and so on)........................................................................5

4. External Interface Requirements.........................................5

4.1 User Interfaces..............................................................................................5
4.2 Hardware Interfaces......................................................................................5
 4.3 Software Interfaces.......................................................................................6
4.4 Communications Interfaces...........................................................................6

1. Introduction
1.1 Purpose

Among the many definitions that could be given of text-to speech, the one that
describes it as a way of having a computer audibly communicate information to the user
is probably the most relevant within the context of this statement. In situations where
visual feedback is inadequate or even impossible, audible feedback may be an essential
feature; in other situations it may just add extra value to a product. Generally, text-to-
speech provides a very valuable and flexible alternative for digital-audio recordings in
cases where:

 Recordings are too expensive.

 Disk storage is insufficient to store recordings.
 The application does not know ahead of time what it will need to speak.
 The information varies too much to record and store all the alternatives.

1.2 Document Conventions

To prepare this SRS we had used the lettering style of Times New Roman
and Font size for sub headings is 14 with bold. The matter which is mentioned in this
SRS is 12 with a lettering style Times New Roman. Then headings are of lettering
style Times New Roman with Font size 12. Then the important points in our SRS are
shown in italics.

1.3 Intended Audience and Reading Suggestions

This SRS can be read by all developers. The rest of the part of the SRS
mentions the benefits of our project, how to use the project, how the project was
developed, what are the major things we have taken in to consideration.
1.4 Project Scope

The term "Text-to-Speech," or TTS for short, refers to the process by which plain text is
converted into digital audio and then "spoken." This "speaking" can be in the form of
actually sending the audio through a computer's speakers (or other capable device), or
simply saving the converted audio for later playback.

For the most part, all TTS conversion engines can be broken out into one of three
methods used to convert phonemes (the smallest phonetic unit in a language that is
capable of conveying a distinction in meaning, such as the m of mat and the b of bat in
English) into audible sound. The supplied Microsoft Speech engines use the second
method. The three methods are described in the following paragraphs.

1.5 References

1. Orely Text to speech book.

2. In order to get the overview of ‘Text To Speech’ we have visited the website
“google.com” for overall description.

2. Overall description

2.1 Product Perspective

Text to speech program that lets you type-in any English or Spanish text and then
plays it as an audio stream. Streams also can be downloaded and saved as standard
MP3 files.

Instantly convert desired text to MP3 file.

Converting files into Speech format .File can be doc, txt, pdf.

Supported language : English

Save converted text as an MP3 file.

2.2 Product Feature developer applications

Different implementations of text-to-speech systems exist. This section

discusses some of the concepts on which these systems are built. Generally, a
text-to-speech system can be broken down into three main parts: a linguistic,
a phonetic and an acoustic part. First, an ordinary text is input to the system.
A linguistic module converts this text into a phonetic representation. From
this representation, the phonetic processing module calculates the speech
parameters. Finally, an acoustic module uses these parameters to generate a
synthetic speech signal.

2.3 User Classes and Characteristics

Using this product user can listen his entered text or selected text. He or she can
listen given input file text which can be doc, txt, pdf format.
User can listen IE browser text by selecting text from IE browser.
User can save converted text into MP3 Format.

2.4 The Operating Environment

Software Requirements used are Windows XP and any other latest editions.,
Java Technologies.
Hardware Requirements used are P4processor, 512MB of Main Memory
(RAM) and 40GB hard disk and base memory.

2.5 Design and Implementation Constraints

 Design constraints developers. All modules are coded thoroughly based
on requirements from software organization. The software is designed in such a
way that the user can easily interact with the screen. Software is designed in such
a way that it can be extended to the real time business.

2.6 User Documentation

In our user manual we are going to keep the information regarding our
product, which can be understandable by a new person who is going to use it. If a
new person is using it, online help will be provided in that. We are going to
explain each and every step clearly about our product so that any user can easily
understand it.

3. System Features
In this we have 6 modules

 Entered Text or Selected Text to Speech conversion

 Text File conversion Module

 Doc File conversion Module

 PDF File conversion Module

 Internet explorer Browser Text into Speech Module

 Text to MP3 Conversion Module

Entered Text or Selected Text to Speech

In this module user has to enter some text and he can listen the
speech by clicking the read button .user can listen select text from entered text.
In this module we have to design GUI which provides text area to enter text and
buttons like read, stop, pause and browse for giving the input file from System
directories.
Text File conversion Module

In this module,
 User can give the text file as input for converting text into speech .In this
module functionalities are

 Getting path of input file

 Open the file using path
 Reading File
 Read text passed to speech method

Doc File conversion Module

In this module,
 User can give the doc file as input for converting text into speech .In this
module functionalities are
 Getting path of input file
 Open the file using POI API which is designed to read Microsoft
Doc File from Java
 Reading File using POI API
 Read text passed to speech method

PDF File conversion Module

In this module,
 User can give the PDF file as input for converting text into speech .In this
module functionalities are
 Getting path of input file
 Open the file using pdfbox API which is designed to read PDF
File from Java
 Reading File using pdfbox API
  Read text passed to speech method
IE Browser Text conversion Module

In this module,
 User can Listen IE browser text by selecting some text in the browser .In
this module functionalities are
 Adding context menu item to IE
 Provide action for context menu item
 Reading selected text using JavaScript
 Writing text in to temporary text file
 Command passed to execute our desktop application
 Reading text from temporary text file
 Read text passed to speech
Text to MP3 conversion Module

In this module,
 User can save text as mp3 format .In this module functionalities are
 Save the selected text in temporary memory
 Convert it into MP3 format
 Save the MP3 file in desired location.

4: External Interface Requirements

4.1 User Interfaces

This application include GUI standards or product family style guides that
are to be followed, screen layout constraints, standard buttons and functions that
will appear on every screen, error message display standards, and so on.
4.2 Hardware Interfaces

We require Internet connection for interacting with IE browser data and

local computers for any help or any other requirement. We use TCP/IP protocol
for communicating with local hosts. We also need system with P2 or above
processor; 128MB+ RAM and database memory.

4.3 Software Interfaces:

3.1 Java, AWT, swings for designing GUI

3.2 Java APIs like POI, pdfbox, freeTTS for reading text and converting into speech

3.3 In this project and we follow Microsoft predefined way of adding IE context
menu item.

3.4 Eclipse IDE for writing the programs.

3.5 Operating System can be Windows XP, LINUX and Mac etc.

4.4 Communications Interfaces

The communication function required by this product is WEB connection.