ramesh 12pcs049

Software RequirementsSpecification (SRS) Document

for

RSS with TTS

Version 1.0 approved

Prepared by Mark CarrollMatt Ferguson

CS490: Senior Project

10/7/2011

Software Requirements Specification for RSS with TTS

Sign-offs

I agree that this document represents our best understanding of the requirementsfor this project today and the system described will satisfy our needs. I agree tomake future changes in this baseline through the project’s defined change process.I realize that approved changes might require us to negotiate the cost, resources,and schedule commitments for this project.

Name Title Signature Date




CS 490: Senior Project I Fall 2011


Contents

Sign-offs 2

Revision History 5

1 Introduction 61.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . 61.3 Intended Audience and Reading Suggestions . . . . . . . . . . . . 61.4 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Overall Description 62.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3 User Classes and Characteristics . . . . . . . . . . . . . . . . . . 72.4 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . 72.5 Design and Implementation Constraints . . . . . . . . . . . . . . 72.6 User Documentation . . . . . . . . . . . . . . . . . . . . . . . . 72.7 Assumptions and Dependencies . . . . . . . . . . . . . . . . . . 7

3 System Features 83.1 Text to speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.1.1 Description and Priority . . . . . . . . . . . . . . . . . . 83.1.2 Stimulus/Response Sequences . . . . . . . . . . . . . . . 83.1.3 Functional Requirements . . . . . . . . . . . . . . . . . . 8

3.2 Easy to use, intuitive interface . . . . . . . . . . . . . . . . . . . 83.2.1 Description and Priority . . . . . . . . . . . . . . . . . . 83.2.2 Stimulus/Response Sequences . . . . . . . . . . . . . . . 83.2.3 Functional Requirements . . . . . . . . . . . . . . . . . . 8

3.3 Built-in feed list . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.3.1 Description and Priority . . . . . . . . . . . . . . . . . . 93.3.2 Stimulus/Response Sequences . . . . . . . . . . . . . . . 93.3.3 Functional Requirements . . . . . . . . . . . . . . . . . . 9

3.4 Built-in browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.4.1 Description and Priority . . . . . . . . . . . . . . . . . . 93.4.2 Stimulus/Response Sequences . . . . . . . . . . . . . . . 93.4.3 Functional Requirements . . . . . . . . . . . . . . . . . . 9

3.5 Sharing of articles . . . . . . . . . . . . . . . . . . . . . . . . . . 9



3.5.1 Description and Priority . . . . . . . . . . . . . . . . . . 93.5.2 Stimulus/Response Sequences . . . . . . . . . . . . . . . 103.5.3 Functional Requirements . . . . . . . . . . . . . . . . . . 10

3.6 Configurable synchronization . . . . . . . . . . . . . . . . . . . . 103.6.1 Description and Priority . . . . . . . . . . . . . . . . . . 103.6.2 Stimulus/Response Sequences . . . . . . . . . . . . . . . 103.6.3 Functional Requirements . . . . . . . . . . . . . . . . . . 10

4 External Interface Requirements 104.1 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.2 Hardware Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 104.3 Software Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 114.4 Communications Interfaces . . . . . . . . . . . . . . . . . . . . . 11

5 Other Nonfunctional Requirements 115.1 Performance Requirements . . . . . . . . . . . . . . . . . . . . . 115.2 Safety Requirements . . . . . . . . . . . . . . . . . . . . . . . . 115.3 Security Requirements . . . . . . . . . . . . . . . . . . . . . . . 115.4 Software Quality Attributes . . . . . . . . . . . . . . . . . . . . . 11

Appendices 12

A Glossary 12

B Analysis Models 12

C Issues List 12



Revision History

Name Date Reason For Changes VersionMark Carroll 10/7/2011 Initial release 1.0



1 Introduction

1.1 Purpose

This document covers RSS with TTS, along with all currently planned features, upto its initial release.

1.2 Document Conventions

Priorities for high-level requirements are assumed to be inherited by detailed re-quirements.

1.3 Intended Audience and Reading Suggestions

This document is intended for developers and project stakeholders. Suggestionsfor reading include reading in chronological order.

1.4 Project Scope

As stated in the vision and scope document, the scope of this project is a fullfeatured RSS reader with text-to-speech functionality. The project will be dividedinto two development periods, with one culminating in a demo of one major featureand the second in a full release candidate.

1.5 References

This document does not reference any external resources.

2 Overall Description

2.1 Product Perspective

RSS with TTS is a new, self-contained product. It currently stands as the onlyproposed Android RSS reader that implements text-to-speech.

2.2 Product Features

There are several planned features for RSS with TTS. The most important of theseis text-to-speech functionality, which will be performed using native Android li-braries available for all devices using software version 1.6 and higher. Other fea-tures include: providing an easy to use, intuitive interface that includes RSS image



parsing and multiple views, providing a built-in, sortable feed list, providing built-in browser support, as well as enabling the sharing of articles and allowing forconfigurable auto-synchronization.

2.3 User Classes and Characteristics

Two user classes are anticipated: those who are familiar with RSS and those withno RSS experience. Users who are familiar with RSS will find no issue with theconfiguration of the application, while those with no RSS experience will be pro-vided assistance via included documentation. Users familiar with RSS will befavored, therefore requirements critical to those without experience will be lessimportant to satisfy.

2.4 Operating Environment

The software will operate on devices supporting Android version 1.6 and above.For proper text-to-speech functionality, these devices will also need the TTS libraryinstalled. The application, upon initialization, will check for these libraries andprovide the user with installation options.

2.5 Design and Implementation Constraints

The primary constraint will be a 32 week period of research and development, uponwhich a release candidate will be made available.

2.6 User Documentation

A user manual will be provided with the application. This manual will describe thefunctionality of RSS as well as how to properly operate the application.

2.7 Assumptions and Dependencies

It is assumed that text to speech can be implemented in the manner described inthe product description.



3 System Features

3.1 Text to speech

3.1.1 Description and Priority

This feature will provide audio for the text included within individual RSS feeds.It is of high priority.

3.1.2 Stimulus/Response Sequences

User will activate a button to load on-screen text into TTS engine and initiate audioplayback.

3.1.3 Functional Requirements

REQ-1: User must be running Android version 1.6 or higher with TTS librariesinstalled. If TTS libraries are not installed, provide prompt and ability to installfrom application.REQ-2: User must have at least one RSS feed configured and one article selected.

If no feeds are configured, provide prompt and ability to do so.

3.2 Easy to use, intuitive interface


This feature will provide the overall interface for the application. It is of highpriority.


User will have multiple available interactions, such as configuring feeds, viewmode, and other options.


REQ-1: User must be running Android version 1.6 or higher.



3.3 Built-in feed list


This feature will provide the user with a collection of pre-defined RSS feeds. It isof high priority.


User will be provided with a selectable list of RSS feeds. Upon selection, feedswill be set to appear in main application interface.



3.4 Built-in browser


This feature will provide the user with the ability to view full article content withinapplication. It is of medium priority.


User will activate a button to load corresponding full article within application.Application will create a customized WebView interface to present requested arti-cle.



3.5 Sharing of articles


This feature will provide the ability to share articles via e-mail and MMS. It is oflow priority.




User will activate a button to share corresponding article link via default email ormessaging application.


REQ-1: User must be running Android version 1.6 or higher.REQ-2: User may need to provide contact-list permission on install.

3.6 Configurable synchronization


This feature will provide the ability to configure when the application checks forupdates to RSS links. It is of low priority.


User will activate option within application settings panel.



4 External Interface Requirements

4.1 User Interfaces

The user interface will be a primary factor in development of this project. It willconsist of a streamlined set of views that provide consistent button and informationlocation.

4.2 Hardware Interfaces

The application will rely on wireless hardware, both WLAN and/or mobile data,in order to download the content of selected RSS feeds. The application will onlysupport Android devices capable of running version 1.6 and above.



4.3 Software Interfaces

The application will rely on the use of at least one SQLite database to store andaccess predefined and user-provided RSS feed content. The application will alsorequire an Android text-to-speech library to be installed in order to process play-back requests. This library requires, at minimum, Android software version 1.6.

4.4 Communications Interfaces

Standard HTTP communication will be required in order to load RSS feed contentand subsequent full article links.

5 Other Nonfunctional Requirements

5.1 Performance Requirements

The application will need to provide a responsive interface. There should be min-imal delay, other than that caused by connectivity issues, in retrieving RSS feedcontent and associated detail.

5.2 Safety Requirements

There are no safety requirements associated with this application.

5.3 Security Requirements

There are no security requirements associated with this application.

5.4 Software Quality Attributes

The software is planned to be robust and complete, in order to attract new users,while also providing an intuitive and usable interface that is free of clutter and easyto use.



Appendices

A Glossary

B Analysis Models

C Issues List


ramesh 12pcs049

Documents