Software Requirements Specication

LetzTalk Android Application

Project LetzTalk
Computer Science Department
California Polytechnic State University
San Luis Obispo, CA USA
Dec 7, 2010
Version 1.0.0
LetzTalk PR contact: Yewon Peter Lee: (503) - 453- 4850
ylee06@calpoly.edu
Contents
Revision History 3
1 Introduction 4
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Intended Audience and Reading Suggestions . . . . . . . . . . . . . . . . . . . 4
1.4 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Overall Description 4
2.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 User Classes and Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5 Design and Implementation Constraints . . . . . . . . . . . . . . . . . . . . . . 5
2.6 User Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.7 Assumptions and Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.8 Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Use Cases 6
4 System Features 6
5 External Interface Requirements 7
5.1 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.2 Hardware Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.3 Software Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.4 Communications Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6 Other Nonfunctional Requirements 7
6.1 Performance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2 Safety Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.3 Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.4 Software Quality Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7 Other Requirements 7
LetzTalk PR contact: Yewon Peter Lee: (503) - 453- 4850
ylee06@calpoly.edu
Revision History
Name Date Reason for Changes Version
Yewon Peter Lee April 15, 2012 Initial Draft 1.0
LetzTalk PR contact: Yewon Peter Lee: (503) - 453- 4850
ylee06@calpoly.edu
1 Introduction
1.1 Purpose
This SRS describes the software functional and nonfunctional requirement for release 1.0 of
the LetzTalk Android application (hereby called LetzTalk). This document is intended to
be used by potential developers of the project to implement and verify correct functional
of the system. Unless otherwise noted, all requirements specied here are high-priority and
committed for release 1.0.
1.2 Document Conventions
This document uses the following standards to rank requirements and priorities:
1. High: This item must be satised or documentented as infeasable as part of the project
success criteria. See Business Objectives and Project Scope section in the Vision and
Scope document.
2. Medium: This item should be satised as part of the project success criteria. However,
in the case of limited resources, such as time or budget, high priority items must be
satised rst.
3. Low: This item could be satised if enough resources are available after higher priority
items are satised.
1.3 Intended Audience and Reading Suggestions
This document presents a detailed, formal description of LetzTalk requirements. Readers
must be familiar with fundamental architecture of Android. Readers not familiar with An-
droid are suggest to read through Android Basics section on the Android Dev Guide page
[4].
1.4 Project Scope
The scope of the project is currently limited to Android platform. Eventually, the application
will be available on Apples App Store.
1.5 References
Please refer to references section of this document.
2 Overall Description
2.1 Product Perspective
LetzTalk is an Android platform chat application which allows users to chat or video-chat
with one or more random people around world. The system will incorporate an achievements
feature (reward users based on a certain set of criteria) to provide fun to users. The system
is expected to evolve over several dierent releases, ultimately to other platforms.
LetzTalk PR contact: Yewon Peter Lee: (503) - 453- 4850
ylee06@calpoly.edu
2.2 Product Features
LetzTalk will contain a few unique features. LetzTalk will implement text-chat mechanism
using Jabber/XMPP client. It will also implement video-chat mechanism using Flex 4 and
Adobe AIR and it will be powered by LiveCycle Collaboration Service [1]. Additionally,
LetzTalk will ensure an user can maintain active communication with other people despite
evolving network conditions (in such condition where there is no network, the system wont
function properly). Finally, LetzTalk will implement an achievement system which rewards
users based on certain set of criteria. Please refer to the System Features section for detailed
information regarding product features and priorities.
2.3 User Classes and Characteristics
User Class Priority Description
Regular User High The primary users of LetzTalk. They will be provided
with limited functionality.
2.4 Operating Environment
While LetzTalk users may be distributed worldwide, each installation will have all of its com-
ponent devices available locally and users are required to have an Android platform system.
Due to the limited battery-life of mobile devices, LetzTalk may consider power use as a design
factor. This is a low priority extension to LetzTalk.
In addition, due to existence of many dierent type of Android devices LetzTalk will follow
the compatibility guide line that Google provided on Dev page [2].
2.5 Design and Implementation Constraints
1. The system must run on a Android platform operating system.
2. The system must be conserve the battery life.
3. The system must be able to operate on many dierent type of Android devices.
2.6 User Documentation
This project will deliver multiple documents in PDF format, including:
1. Description for installing and running LetzTalk.
2. Description for using LetzTalk.
2.7 Assumptions and Dependencies
1. At this stage of the project, LetzTalk will not support operating systems other than
Android.
LetzTalk PR contact: Yewon Peter Lee: (503) - 453- 4850
ylee06@calpoly.edu
2.8 Business Rules
[BR - Completeness of Service] If a user wants to search for another person to chat
and there exists another person in the network, then LetzTalk must facilitate that connection.
3 Use Cases
Use cases are located in a separate document. Please refer to the Use Case document.
4 System Features
1. Login/Registration Screen
(a) Login/Registration screen will display text elds for inputting user ID and pass-
word, or if user never registered, it will direct users to the registration screen.
(b) Registration screen will take ID, password, users gender and age.
(c) If a user have logged in previously on a device, it will save the information and will
not ask for login information again unless the user clears the cache of the system.
2. Main Screen
(a) Main Screen will provide an option to nd a chat partner.
(b) Main Screen will display the users friends recent activities.
3. Chat Screen
(a) LetzTalk will display the option to enable video-chat.
(b) LetzTalk will display the option to add another person as a friend.
4. Option Screen
(a) Option screen must be accessible from every other screens.
(b) Option screen will have following selections:
i. Background Color
ii. Automatic video-chat setting
iii. Integrate with Facebook
iv. Integrate with Twitter
v. Integrate with Google+
vi. Setup prole
LetzTalk PR contact: Yewon Peter Lee: (503) - 453- 4850
ylee06@calpoly.edu
5 External Interface Requirements
5.1 User Interfaces
1. LetzTalk will meet the high quality of user interface by following Googles Android
Design guide. Please refer to the Android Design Guide for the detail information [3].
5.2 Hardware Interfaces
N/A
5.3 Software Interfaces
N/A
5.4 Communications Interfaces
N/A
6 Other Nonfunctional Requirements
6.1 Performance Requirements
1. LetzTalk is recreational and thus does not require constraints on performance.
6.2 Safety Requirements
N/A
6.3 Security Requirements
1. LetzTalk will not modify users data.
6.4 Software Quality Attributes
N/A
7 Other Requirements
N/A.
LetzTalk PR contact: Yewon Peter Lee: (503) - 453- 4850
ylee06@calpoly.edu
References
[1] Adobe. Adobe collaboration. http://www.adobe.com/devnet/ashplatform/services/collaboration.html,
2012.
[2] Google. Adobe compatibility. http://developer.android.com/guide/practices/compatibility.html,
2012.
[3] Google. Android design guide. http://developer.android.com/design/index.html, 2012.
[4] Google. Android developers. http://developer.android.com/guide/basics/what-is-
android.html, 2012.
LetzTalk PR contact: Yewon Peter Lee: (503) - 453- 4850
ylee06@calpoly.edu