Anda di halaman 1dari 20

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

PaySelfy

Software Requirement Specification

Version 1.0.0

Prepared by, UEDEVELOPER

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

Document Control

  • 1. Approval Mr. Vinay Babu Rohit and Mr. Aman Singh will approve this document.

  • 2. Document Change Control

Initial Release:

Feb 1, 2016

Current Release:

To Be Determined (TBD)

Date of Last Review:

To Be Determined (TBD)

Date of Next Review:

To Be Determined (TBD)

Target Date for Next Update:

To Be Determined (TBD)

  • 3. Revision History The following table concludes the changes made between versions of this document:-

Date

Version

Description

Author

1

st Feb, 2016

1.0

Creation

UEDEVELOPER

 

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

Table of Contents

Description

Page No.

1.0 Introduction………………………………………………………………5

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

  • 1.1 Purpose and Intended Audience

5

  • 1.2 Scope of Product…………………………………………………………

....

5

  • 1.3 Definition and Abbreviations…………………………………………

....

6

  • 1.3.1 Definitions………………………………………………………………………6

  • 1.3.2 Abbreviations………………………………………

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

7

  • 1.4 Overview of System…………………………………………………… 8 .......

  • 1.5 Technologies to be used…………………………………………………….9

  • 1.6 References…………………………………………………………… 10 ........

  • 2.0 General Description………………………… ……………………… 11

..

..

  • 2.1 Product Perspective………………………………….………………

11 .....

  • 2.2 Product Functions……………………………………………………

.....

11

.

  • 2.3 Product features………………………………………………………

....

12

  • 2.3.1 Data Management…………………………………………………….……

...

12

  • 2.3.2 Mapping of outcomes………………………………………………………

...

12

  • 2.4 User characteristics…………………………………

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

12

  • 2.4.1 Use case Diagrams and their description……… ….13 ..................................

  • 2.4.2 Stakeholders………………………………………… 22 ......................................

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

  • 2.5 Non-Behavioral Characteristics

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

25

2.5.1 Deployment Diagrams

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

26

  • 2.6 General Constraints

26 ............................................................................

  • 2.7 Assumptions and Dependencies

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

27

3.0 Specific Requirements

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

28

  • 3.1 External Interface Requirements

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

28

  • 3.1.1 User interface .............................................................................................28

Hardware interface

  • 3.1.2 .....................................................................................

32

Software interface

  • 3.1.3 32 .......................................................................................

  • 3.1.4 Communication interface

33 ............................................................................

  • 3.2 Behavioral requirements

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

33

  • 3.2.1 Class of users 33 .............................................................................................

  • 3.2.2 Stimulus 33 ......................................................................................................

  • 3.2.3 Functional 33 .................................................................................................

  • 3.3 Non-Behavioral requirements

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

34

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

  • 3.3.1 Performance Requirements

34

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

  • 3.3.2 Qualitative requirements

34

  • 3.4 Expected Future Enhancements

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

34

  • 3.5 Other Requirements

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

35

3.4.1 Database

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

35

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

1.

Introduction

  • 1.1 Purpose and Intended Audience:-

The purpose of the Software Requirement Specification (SRS) is to give the Stakeholders a clear and precise description of the functionality of the PaySelfy to be developed.

This document is intended for both Customer and Developers of the system.

For customer, the SRS will explain the purpose and features of the system, the interfaces of the system, the constraints under which it must operate and how the system will react to external stimuli.

For the Developer, it will be a reference point during software design, implementation and Maintenance.

  • 1.2 Scope of Product:-

This SRS is designed to develop a PaySelfy that establishes a process for:

The Admin to :- Ability to add/edit contests. Admin rights to reject/delete a selfie if it’s vulgar or doesn’t fulfill a criteria. Generate list of users who participated in a contests along with details. Messaging individual users regarding winners. Select advertisements. Access to data like average weekly active users etc. along with demographics.

The Customers to :- Profile creation and login. Selecting contest and uploading pictures Redeem money.

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

1.3 Definitions and Abbreviations:-

1.3.1 Definitions

The definitions in this section are given in the context of the product being developed. The intention is to assist the user in their understanding of the requirements for the system.

TERM

DEFINITION

Database

A structured query relational database (SQL Server) stored on one or more machines.

Mapping

The linkages of two objects.

Server

The main computer in a network. A central computer that connects and services clients attached to it.

Spreadsheet

The work area for entering inputs and other data that appears as a table with rows and columns.

User

A person who provides the data for a computer system, updates the data, and uses reports from the system in his or her work.

User profile

User characteristics maintained by the system

Stakeholders

All persons interested in the system

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

1.3.2 Abbreviations

ABBREVIATION

MEANING

e.g.

For example

i.e.

That is

Info.

Information

CQI

Continuous Quality Improvement

DBMS

Database Management System

GUI

Graphical user Interface

SRS

Software Requirements Specification

TBD

To Be Determined

R/W

Read/Write

1.4 Overview of the system:-

The PaySelfy is divided into two major modules:-

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

  • 1. The customers who interact with the front end interface of PaySelfy. These users can:-

Profile creation and login.

Selecting contest and uploading pictures.

Taking instant selfies or uploading from the old ones.

Redeeming money

Contact administrator

  • 2. Admin is solely responsible for the operation of the software. Admin can:-

Ability to add/edit contests.

Advertisements selection

Admin rights to reject/delete a selfie if it’s vulgar or doesn’t fulfill a criteria.

Generate list of users who participated in a contests along with details.

Messaging individual users regarding winners.

Access to data like average weekly active users etc. along with demographics.

1.5 Technologies to be used:-

J2EE(Java 2 Enterprise Edition):-

 

Java Platform, Enterprise Edition

Java

or

API

EE

is

Oracle's

enterprise

computing

platform

provides

The

 

an

and runtime environment for

other large-scale, multi-tiered, scalable, reliable, and secure network applications.

developing and running

and

Android Studio:-

 

Android Studio

is the official integrated development environment (IDE) for developing

platform. It was announced on May 16, 2013 at the Google I/O

for the

Android

is freely available under the Apache License 2.0.

conference. Android Studio

 

JAVA:-

Java

is

a

set

several

of

and

specifications

developed

by

Sun

acquired

later

by
by
 

provides

that

system

a

for

environment

developing

and

deploying

in

it

computing

a

Apache Tomcat Server:-

 

Tomcat server is the market-leading Internet infrastructure software for building, running, and integrating business applications across a variety of computing platforms. Built

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

according to clients’ desires for innovative, standards-based, highly reliable, and scalable software,

SQL Server:

 

It is a no-charge database used in development and deployment. Providing the same core data server features, development interfaces, and system limits, As SQL server is in a smaller package, it offers a solid base to build and deploy all applications.

Ajax (Asynchronous Java script and XML):-

 

Ajax

is a group of interrelated

techniques used on the

to

create

<a href=asynchronous " id="pdf-obj-8-62" src="pdf-obj-8-62.jpg">

XML (Extension Markup Language):-

Extensible Markup Language

encoding documents in a

that defines a set of rules for

which is both

(XML) is a

and
and
that defines a set of rules for <a href=machine-readable markup language human-readable which is both (XML) is a and " id="pdf-obj-8-95" src="pdf-obj-8-95.jpg">

MS Visio:

Microsoft Visio

is

a

application by Microsoft

diagramming

graphics

vector

users to connect their diagrams to data sources and to display their data graphically

Visio capabilities intended to make it easy for

Corporation used for UML development.

and
and

Eclipse IDE:-

 

The Eclipse IDE is developed by an open source community that focuses on developing a universal platform of frameworks and powerful tools that make it easy and cost-effective to build and deploy software’s.

1.6 References:-

W3schools.com.

Macromedia Dreamweaver tutorials.

Toadworld.com SQL Wikis.

JSSOR Slider tutorials

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

2.

General Description

  • 2.1 Product Perspective:-

PaySelfy is designed to provide Admin and stakeholders with tools that facilitate easy control and access.

It will help the Admin to manage:- Ability to add/edit contests. Admin rights to reject/delete a selfie if it’s vulgar or doesn’t fulfill a criteria. Generate list of users who participated in a contests along with details. Messaging individual users regarding winners. Advertisements selection Access to data like average weekly active users etc. along with demographics.

  • 2.2 Product Features:-

2.2.1 Data Management:-

Data management includes the entry, storage, manipulation and deletion of different Records that exist in database. By Data management we mean:

Add new information to the database.

Edit existing information in the database.

Organize, view and generate information in different ways.

Share the information with the user.

  • 2.3 User Characteristics:-

The Users are expected to be non-technical users, once he/she will make an account by signing- up, he will be able to participate in the different selfie related tasks showing on his app’s screen. Because the system will have a GUI with a standard format, the users will need not to have a high level of technical expertise.

The Admin is expected to be technical stakeholder and will manage all the activities regarding adding/editing contests, advertisements selection, choosing winners, managing users’ accounts as well.

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

2.3.1 Use Case Diagrams and their description:-

Use Case For Administrator :-

Use Case

Admin

Name

Brief

The Admin will be able to view all the functionalities of the system including

Description

management of users and contests.

Actor

 

Administrator

Scenario

Maintain client/customer details

Adding/Editing Contests

Winners selection

Prize money Transfer

Personal messaging to users

Advertisements selection

Use case for Customer/Clients :-

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

Use Case

Customer

Name

Brief

The Customer can sign-up, sign-in and update their details.

Description

Actor

Customer

Scenario

Update profile details.

Change password.

Contest selection to participate

Redeeming money

Taking instant selfies or uploading from the old ones

Contact administrator

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

PaySelfy Version 1.0.0 Software Requirements Specification 1 Feb, 2016 UEDEVELOPER

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

2.3.2 Stakeholders of the System:-

PaySelfy Consists of Following Stakeholders:-

The Administrator of the system will be able to manage the adding/editing contests, advertisements selection, choosing winners, managing users’ accounts.

The User can Update profile details, change password, contest selection to participate, redeeming money and contact administrator.

2.4 Non-behavioral Characteristics:-

2.6.2 Deployment Diagram:-

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

PaySelfy Version 1.0.0 Software Requirements Specification 1 Feb, 2016 UEDEVELOPER 2.5 General Constraints :- The general

2.5 General Constraints:-

The general constraints on the development of the system are as follows:-

User Interface Constraints:

Using the PaySelfie must be fairly simple and intuitive. A user must have to be familiar with the basic browser navigation skills to be able to understand all functionality provided by the system.

Hardware Constraints

The PaySelfie should work on most mobile phones which support Android operating system.

Software Constraints

The PaySelfy would be intended to run on Android 4.0 and above.

Data Management Constraints

PaySelfy shall be able to interface with other components according to their specifications.

Operational Constraints

The PaySelfy is limited by its operating server in terms of the maximum number of users it can support at a given time.

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

2.6 Assumptions and Dependencies:-

The assumptions are as follows:

Each user has access to an Android device having an internet browsing capability.

The information should be stored in database so that it is easily accessible.

The PaySelfy should support fast transaction.

Users must have correct username and password so as to enter into their online accounts and do action.

The Dependencies are as follows:

The Specific Software on which the PaySelfy will run.

The Specific Hardware on which PaySelfy will be running.

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

3.

Specific Requirements

  • 3.1. External Interface Requirements This section of PaySelfy discusses the requirements related to the interfaces used to communicate with external entities. These entities include human users and other hardware and software interfaces that permit the system to carry out its tasks. 3.1.1 User Interfaces

3.1.1.1.

Interface Formats

All screens have the name of the system displayed on the screen

After the login screen, the resulting screen will provide the user with the ability

to navigate through system i.e., to select different functionalities. The Administrator will have the option to save changes to information stored in

the local database. The user will have the option to print displayed information.

3.1.1.2.

System Entry

Upon entry, the App will display the following welcome screen:-

3.1.1.3.

Login screen

Login screen shown by App is shown below:

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

  • 3.1.2 Hardware Interfaces

This section describes the basic requirements for client & server system:

For Client system:

RAM - 32 MB

Storage - 32 MB

System software platform: Android OS based Device

For Server system:

RAM- 1GB

HDD- 50 GB

System software platform: Windows xp/vista/7/8/8.1/10 for Admin Panel

Application Software platform:

JavaScript and XML enabled Web browser

MySQL

Tomcat Server

  • 3.1.3 Software Interfaces

The system will interface with the following software systems:

MySQL(Back end)

Tomcat Server

A basic Browser to access internet.

Android Studio

  • 3.1.4 Communication Interfaces

The PaySelfy will run over the World Wide Web (internet).

The PaySelfy will be developed as a client-server application with the server providing data access services only.

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

3.2 Behavioral Requirements

3.2.1

Class of Users

To use the PaySelfy the user must be authorized. The requirements in this section address authorization and access issues.

 

When the user logs into PaySelfy, it will ask the user to enter a password.

Only users whose logins are authorized, or who own the Corresponding section, will be able to update their profile details or view their previous booking details.

Stimulus

3.2.2

The following requirement applies to all user-entered values in PaySelfy:-

 

After the user enters a login and password, the system will validate the password. If the password is validated, then the respective functionality screen will appear otherwise the system will display and error message.

If the user selects the option to change his/her password, the system will prompt the user for a new password and will ask the user to renter the password.

3.2.3

Functional

PaySelfy provides 24x7 Availability.

In PaySelfy, only registered Users can access the Login Sections.

Registered users must have Valid Login ID and password to access their respective

sections. Valid ranges and values should be checked against the specification of the tables, if the user enters an invalid value or range, an error message will be displayed. Whenever the user submits information to the database, the system will ask the user to confirm the submission.

Non-Behavioral requirements:-

3.3

Performance Requirements

3.3.1

Performance requirements include human interaction to the App as a whole. The PaySelfy fulfills all the minimum level of Static (Response time, Recovery time and starting-up/power-off time) and Dynamic (Throughput, utilization rate and no. of concurrent users) requirements of the standard systems.

Qualitative requirements

3.3.2

Security:-

PaySelfy

Version 1.0.0

Software Requirements Specification

1 st Feb, 2016

UEDEVELOPER

The PaySelfy will be able to control unauthorized access to the system.

Maintainability:-

The

PaySelfy is

changes:-

being

designed in such

a

way

so

as

to allow

the following

Use of database queries.

Portability:-

The PaySelfy is capable of running on multiple Android versions.

Reusability:-

The PaySelfy is capable of being reused in another system.

3.4 Expected Future Enhancements:-

The system will be designed for the following future extensions:

Extension to ios mobile application.

Enhanced functionality.

______________

______________

______________

Aman Singh

Vinay Babu Rohit

Pankaj Rathore