Professional Documents
Culture Documents
P: -
Batch: - 1
D.O.S: -
1. INTRODUCTION
1.1 Purpose:
The purpose of this SRS is to document requirements for MOBILE TRACKING
SYSTEM to manage various activities. The main purpose of this system is an
important area of research, for emergency as well as for commercial services. Mobile
services in cellular network will provide several services such as , locating stolen
mobile ,locating employees ,live monitoring , SOS ,etc.
1.2 Scope:
The system currently is not providing better scheduling and planning, also could not
track employees and provide reports. A light-weight app installed in GPS enable
Android phones of the employees or any on field staff which silently work in
background and send information to the server.
1.3 Overview:
Mobile tracking system is an Android application for mobile. This application or app
will use for tracking employees of office. The administrators have full access of
application.
The employees can report to office with this app. This app will provide all details of
employees to admin.
2. GENERAL DESCRIPTION
The Software Requirement Specification document itself states in precise and
explicit language those functions and capabilities a software system (i.e., a software
application, an e-Commerce Web site, etc.) must provide, as well as states any required
constraints by which the system must abide. The SRS contains Functional and Nonfunctional requirements
User-friendly interface
2.2Product Function:
Live Monitoring
SOS
Image Memo
Geo-tagged Images
Place Mark
Text Memo
Geotagged Data
2.3User Characteristics:
We have identified five potential classifications of users of our system:
Software Designers: These are the most obvious users. They will use the system as a
means of laying out the design of an as yet unimplemented system.
Software Developers: These are the people that take the model generated by the
designers and implement it in code. They may also use the system to identify the design
of an existing system in order to maintain it.
Quality Engineers: These users are usually responsible for ensuring that a design is
feasible and/or reliable. They will therefore also need to be looking at the output from our
system.
System Administrator: Due to the client/server/concurrent nature of the system, some one
needs to be responsible for security and maintenance of the system. This is the System
Administrators role. The Administrator of the system, project or model need not be a
member of the any of the other roles identified here.
The Client: More often than not, software is designed for a client. The client may wish to
see the design as lay out by the system and be able to see what exactly they are buying.
3. SPECIFICATION REQUIREMENT:
3.1Functional Requirement:
a.
b.
c.
d.
e.
Be
Be
Be
Be
Be
able
able
able
able
able
to
to
to
to
to
3.2Non-Functional Requirement:
a.
b.
c.
d.
e.
Functionality
Performance
Environment
Usability
Other Constraints
Hardware Interface:
Operating system: windows XP and higher
Hard disk: 100 GB
RAM: 1GB
Processor: Pentium(R)Dual-core CPU
3.3.3
User Interface:
The software provides good graphical interface for the user any
administrator can operate on the system, performing the required
task such as login, update, viewing the details of the employees.
Allows user to view quick reports like daily updates in between
particular time.