Software Requirements Specification for Android App Mobile Sensor

SOFTWARE REQUIREMENTS SPECIFICATION

(SRS)

AMS
(Android App Mobile sensor)

Computer Sciences Department

CIIT, Sahiwal
Apiril,08, 2016

COMSATS Institute of Information

Technology,
Sahiwal

Software Requirements Specification for Android App Mobile Sensor

2

Team Member
Muhammad Asif Raza (Sp13-BSCS-B9-B-097)
Sufyan Shaikh
(Sp13-BSCS-B9-B-076)

Revision History
Date

Description

Author

Reason

Document Approval
The following Software Requirements Specification has been accepted and approved
by the following:

Supervise By Signature

Table of Contents
2

Date

Software Requirements Specification for Android App Mobile Sensor

3

1. INTRODUCTION.............................................................................................. 4
1.1
1.2
1.3
1.4
1.5

PURPOSE.......................................................................................................................... 4
SCOPE............................................................................................................................. 4
DEFINITIONS, ACRONYMS, AND ABBREVIATIONS........................................................................5
REFERENCES..................................................................................................................... 5
OVERVIEW........................................................................................................................ 6

2. GENERAL DESCRIPTION..................................................................................6
2.1
2.2
2.3
2.4
2.5

PRODUCT PERSPECTIVE....................................................................................................... 6
PRODUCT FUNCTIONS......................................................................................................... 7
USER CHARACTERISTICS...................................................................................................... 7
GENERAL CONSTRAINTS....................................................................................................... 8
ASSUMPTIONS AND DEPENDENCIES........................................................................................ 8

3. SPECIFIC REQUIREMENTS...............................................................................8
3.1 EXTERNAL INTERFACE REQUIREMENTS....................................................................................8
3.1.1 User Interfaces....................................................................................................... 8
3.1.2 Hardware Interfaces............................................................................................... 8
3.1.3 Software Interfaces................................................................................................ 9
3.1.4 Communications Interfaces....................................................................................9
3.2 FUNCTIONAL REQUIREMENTS................................................................................................ 9
3.2.1 Student Registration..............................................................................................9
3.2.2 Student Attendance Management.........................................................................9
3.3 USE CASES..................................................................................................................... 10
3.3.1 Use Case Diagrame.............................................................................................. 10
3.3.2 ER Diagrame........................................................................................................ 11
3.4NON-FUNCTIONAL REQUIREMENTS........................................................................................ 11
3.4.1 Performance......................................................................................................... 11
3.4.2 Reliability............................................................................................................. 12
3.4.3 Availability............................................................................................................ 12
3.4.4 Security................................................................................................................ 12
3.4.5 Maintainability...................................................................................................... 12
3.4.6 Portability............................................................................................................. 13
3.5DESIGN CONSTRAINTS........................................................................................................ 13

Software Requirements Specification for Android App Mobile Sensor

4

1.0.

Introduction

1.1. Purpose
The purpose of this document is to present a detailed description of the
Android App with Mobile sensor. Our goal was to develop a mobile application
aimed at dynamically sensor, depending on our Android base environment. The
original idea came from the static sensor, we enhance it and make mobile sensor
capability whose detect environment temperature, gesture etc. around us and all
pair give all detail to its server. It will explain the purpose and features of the

system, the interfaces of the system, what the system will do, the
constraints under which it must operate and how the system will react to
external stimuli.

1.2. Scope of Project

Our project mobile sensor which is combination of three things Android, Web
and Cloud. We design android app which is used by a user and connect to
database which is hosted on cloud through web application programing
interface. Our goal was to develop a mobile application aimed at dynamically sensor,
depending on our Android base environment. The original idea came from the static sensor, we
enhance it and make mobile sensor capability whose detect environment temperature, gesture
etc. around us and all pair give all detail to its server.

1.3. Objectives

The objective of this project is to develop mobile systems to recognize

human activity and user context with dynamically varying sensor setups,
using goal oriented, cooperative sensing. We refer to such systems
as opportunistic, since they take advantage of sensing modalities that just
happen to be available, rather than forcing the user to deploy specific,
application dependent sensor systems.
This sensor let me know about the environment of the person who is
connected to me through is application. Also provide the facility of chatting
with paired people.
4

Software Requirements Specification for Android App Mobile Sensor

5

1.3. Glossary
Term
Cloud
Asp
Database
Sql
Field
.Net

Definition
Data is hosted on cloud (a server)
Active Server Page is a server side language
Collection of all the information monitored by
this system.
Structure Query Language
A cell within a form.
A framework build by Microsoft Basically a
collection of classes

Member

A member of the Historical Society

listed in the HS database.

Reader
Review

Anyone visiting the site to read articles.

A written recommendation about the
appropriateness of an article for publication;
may include suggestions for improvement.
A person that examines an article and has the
ability to recommend approval of the article for
publication or to request that changes be
made in the article.
A document that completely describes all of
the functions of a proposed system and the
constraints under which it must operate. For
example, this document.
an open-source operating system used for
smartphones and tablet computers
Students and Teachers

Reviewer

Software
Requirements
Specification
Android
User

1.4. References
http://stackoverflow.com/questions/3706913/recommend-a-good-

android-tutorial-with-step-by-step-examples
http://www.sitepoint.com/12-android-tutorials-beginners
http://developer.android.com/training/index.html

http://www.fromdev.com/2013/12/Top-Android-Books.html
http://www.onlineprogrammingbooks.com/android/
https://www.youtube.com/watch?v=rwrMNL21dHY

Software Requirements Specification for Android App Mobile Sensor

6

1.5. Overview of Document

The next chapter, the Overall Description section, of this document gives an
overview of the functionality of the product. It describes the informal
requirements and is used to establish a context for the technical
requirements specification in the next chapter. The third chapter,
Requirements Specification section, of this document is written primarily for
the developers and describes in technical terms the details of the
functionality of the product. Both sections of the document describe the
same software product in its entirety, but are intended for different
audiences and thus use different language.

2. General Description
2.1 Product Perspective
The product Mobile Sensor, is an independent product and does not depend
on any other product or system. The product will automate various tasks
associated with handling student details and better organizing the stored
information and optimum performance, thus helping the teachers to ensure
smooth working of these processes.

2.2 Product Functions

Our system has two types of accessing modes,
1. Administrator
2. User

i) Administrator:
All Information is managed by Administrator. Administrator has to update and
monitor the pair people details, add a new user, provide register number for
all users, assign each user a security code etc., Administrator can update his
profile, and also can give help to the all users.
This subsection of the SRS should provide a summary of the functions that
the software will perform.

ii) User:

There are two types of users:

EDUCATIONAL LEVEL: At least user of the system should be

comfortable with English language.

Software Requirements Specification for Android App Mobile Sensor

7

TECHNICAL EXPERTISE:

User should be comfortable using

general purpose applications on the mobile phones.

This software gives access to two kinds of users.

1. Administrator: The personnel and Developer will have administrator

access to add, delete and modify information stored in the database.

2. Authorized User: Authorized People will have access to only view the
data stored in the database and can update the collected Information in the
form of formatted reports.

2.4 General Constraints

Android Studio is required for running android application
Visual studio 2013 is using for web application
Sql 2014 is using for storing data in to database server

2.5 Assumptions and Dependencies

There are following Assumptions and Dependencies of our Mobile Sensor
Application

The application needs to tell people about the save place should have the updated and
complete maps
Application is dependent on access to internet for the location access.
Users with administrator access should be careful in deleting or modifying
any information knowingly or unknowingly which will lead to inconsistency
of the database
The end users of this software are assumed to have basic level of android
mobile knowledge i.e. point and click.

3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
GUI along with meaningful Frames and buttons etc.
7

Software Requirements Specification for Android App Mobile Sensor

8

Reports are generated as per the requirement

Android App which is used by faculty member for take attendance of
student

3.1.2 Hardware Interfaces

Hardware Environment Dual Core 2nd generation

Android Mobile Devices
Workstation with RAM 6 GB

Operating system Windows XP/Vista/7/8/8.1

3.1.3 Software Interfaces

Front End is of website is made in asp.net and Back-End we are using Sql
Database server, also use as a front End android application
Back end: MySQL, PHP, Asp.net
Front end: Android Studio, Eclipse

3.1.4 Communications Interfaces

The system will communicate through Internet Wi Fi signal to access central

data base

3.2 Functional Requirements

The functional requirements of system are following:
REQ-F1: The Admin will be able to manage all the data about fields.
REQ-F2: The Admin will be able to manage all the users.
REQ-F3: The system will generate auto password in case of forget
password.
REQ-F4: The Admin will be able to manage or update all the questions
asked from the user about different crops.
REQ-F5: The system will be able to manage the daily growth of data on the
backend.
REQ-F6: The system will give auto response to the user on the base of rules
defined on backend.

3.3.1 Use case Diagram

Software Requirements Specification for Android App Mobile Sensor

9

3.3.2 ER Diagram

3.3.2 Data Flow Diagram

Software Requirements Specification for Android App Mobile Sensor

10

3.4 Non-Functional Requirements

Non-Functional requirements can be defined as the constraints or checks on
the function or services provided by the system such as constraint of time,
constraints on the development process and standards.

REQ-NF1: System shall provide better Performance and response.

REQ-NF2: System shall provide Security and Safety to the user.
REQ-NF3: System shall provide good Quality in case of better suggestions
about his/ her queries.

REQ-NF4: System must be efficient.

REQ-NF5: System must be user interactive.
3.4.1 Performance
Easy tracking of records and updating can be done. All the requirements
relating to performance characteristics of the system are specified in the
section below. There are two types of requirements.
10

Software Requirements Specification for Android App Mobile Sensor

11

A. Static Requirements
These requirements do not impose any constraints on the execution
characteristics of the
system These are:

1) Number of Terminals:
The software makes use of an underlying database that will reside at the
server, while the front end will be available online to the administrative and
departmental computers as well as students and teachers.

2) Number of Users:
The number of users may vary, as this software finds applications in almost
all department of the organization.

B. Dynamic Requirements
These specify constraints on the execution characteristics of the system.
They typically include response time and throughout of the system. Since
these factors are not applicable to the proposed software, it will suffice if the
response tine is high and the transactions are carried out precisely and
quickly.

3.4.2 Reliability
The software will not be able to connect to the centralized database in the
event that the college LAN fails or in the event of the server being down due
to a hardware or software failure.

3.4.3 Availability
The software will be available only to authorized users of the company or
organization. User always be a known person.

3.4.4 Security
The security requirements deal with the primary security. The software
should be handled only by the administrator and authorized users. Only the
administrator has right to assign permission like creating new accounts and
generating password. Only authorized users can access the system with
username and password.

3.4.5 Maintainability
Backups for database are available. This app will be easily
maintainable.

11

Software Requirements Specification for Android App Mobile Sensor

12

3.4.6 Portability
The Software is an Android and web-based application and is built in Android
studio, Asp.net and SQL server so it is platform independent and is
independent of operating system.

3.5 Design Constraints

This software provides security. The login form prevents the system from
being misused by unauthorized users. Only an authorized operator will be
granted rights to modify as per requirements. This software is also reliable
and fault tolerant. The system developed is designed to handle invalid
inputs. Since reliability is major area of concern the system has a backup to
avoid data loss. The user should know the programming language very well
that is used to develop a software.

3.5.1 Standard Compliance: This specifies the requirements for the

standards the system must follow. The standards may include the report
format and accounting properties.

3.5.2 Hardware Limitations: The software may have to operate on

some existing or predetermined hardware, thus imposing restrictions on the
design. Hardware limitations can include the types of machines to be used in
ambulances, operating system available on the system, languages supported
and limits on primary and secondary storage.

3.5.3

Reliability and Fault Tolerance:

Fault tolerance
requirements can place a major constraint on how the system is to be
designed. Fault tolerance requirements often make the system more complex
and expensive. Requirements about system behavior in the face of certain
kinds of faults are specified. Recovery requirements are often an integral part
here, detailing

12