MUTE ME HERE

Software Requirements Specification

Version 1.0

Group ID: F140255EAE (MC110203943)

Supervisor Name:

Usman Waheed Bhatti

Revision History
Date
(dd/mm/yyyy)

Version

Description

Author

Scope
Functional Requirements
16/01/2015

1.0

Non-Functional Requirements

F14025D8B6

Use Case Diagram

(MC110203943)

Usage Of Scenarios
Adopted Methodology
Work Plan

Table of Contents
1. Scope (of the project)
2. Functional Requirements & Non-Functional Requirements
3. Use Case Diagram
4. Usage Scenarios
5. Adopted Methodology
6. Work Plan (Use MS Project to create Schedule/Work Plan)

SRS DOCUMENT
Scope of Project:
This Project will focus on the development of a single user mobile
application that will provide the user location based and time based muting application
using smart phones GPS system and Google Maps feature as per mobile phones OS and

development frameworks. It will actually require the user to define areas on the map, at
which the smart phone shall be muted. The user should be able to use mute options
(profile selection, vibration setting, sound setting, notification settings etc. This
application will be helpful while offering prayer in a mosque, attending a meeting,
inside a library, inside a seminar hall etc because user will not have to bother about
turning off phone or setting silent options. At that places mobile phone will be muted
automatically and should be unmated when the user comes out of these places.

Functional Requirements:
1. Location Based:
This application will provide user the facility of location based
Muting on the basis of predefined locations in which Phone should be muted when
user moves into any of the pre-defined locations and it should be automatically unmuted when the user walks out of that location.

2. Time Based:
This application will provide user the facility of time based muting
on the basis of predefined time spans user set a specific time interval in which
Phone should be muted and after the specific time interval it should be
automatically un-muted.

3. Define Locations:
This application will allow the user to define one or more locations at
which the mobile phone shall be muted define areas on the map at which smart phone
shall be muted.

4. Auto Muting & Un-Muting:

This application will be able or provide to auto muting &
un-muting locations to store the last used settings before muting and unmuting to
apply or restore.

5. Additional Profile Setting :

This application will enable user to define mute settings. Moreover full
profile selection from default profiles of the phone, or define settings separately i.e.
phone settings for capacity, vibration, LED (light emitting diode) or backlight
notification (if available in the phone set)

Non-Functional Requirements:

Non-functional requirement is a requires that measures can be used to critic the action
of a system, rather than specific behaviors and describe the software will perform the
task or functions.

1. User-Friendliness:
This application should be user friendly Easy perform or to use it.
2. Performance:
Application should perform all of its functions excellently and
effectively without any inconvenience.

3. Usability:
This application can be used by a single user at a time Mobile Based
Application.

4. Security Managed:
Section in charges can only have entrance to their sections. Other section in
charge can make changes in other sections record and changing setting.

Use Case Diagram(s):

Locations Based

Time Based Muting

3.0 Settings

4.0 Mute Options

Usage Scenarios:
ASK SEQUENCE
1. Search location
2. Selects location
3. User opts to create new account

EXCEPTION
Map not available
GPS not activated
Proper information about user

4. System asks for necessary

information

Not proper information

5. System after confirmation creates

the new account
6. User provides all the required
information and opts to complete the
operation
7. System send the account creation
email to the users email address
8. Done

User select a location on map

Use Case Title

Defines Mute Settings
Use Case Id
3.0
Title
1.0 Locations based
Requirement
31.0
Use Case Id Id
Description:
Requirement IdUser 1to use mute settings such as profile selection, vibration
setting,
sound setting,
notification
settingsbased
etc. Muting captions in which Phone
Description:
This application
location
Pre
Conditions:
should
be muted.
Task
sequences
Exception
Pre Conditions:
user
select location based muting
option and defines areas on
1. On/off vibration alert
Available
the map.
2. Set ringing
tone
Task sequences
Exception
3.
ringing
volume
1. Set
Search
location
Map not available
4.
2. Done
Selects location
GPS not activated
Post Conditions: User set full
profile
of the phone.
an area
on selection
map.
Authority: User
Modification history: 3.0
1.0
Author: MC110203943
MC110203943

Methodology:
Use Case Title
2.0 Time Based Muting
Use Case Id
2.0
Requirement Id
2
Description: This application facility of time based muting on the basis of
predefined time spans.
Pre Conditions: user select time based muting option.
Task sequences
Exception
1. Select time format
Available
2. Select 12-hour
3. Select 24-hour
4. Select OK button
User select 12 hour or 24 hour
duration
Post Conditions: User set time duration.
Authority: User
Modification history: 2.0
Author: MC110203943
Different methodologies are suitable in different situation for different
projects depending upon the project. Available methodologies are as follows as below:
1. Build-and-fix model
2. Waterfall model
3. Rapid prototyping model
4. Incremental model
5. Extreme programming
6. Synchronize-and-stabilize model
7. Spiral model
8. Object-oriented life-cycle models

Adopted Methodology:
I want to choose vu process methodology as my project methodology. It is
combination of waterfall model and spiral model.

VU Process Model:
VU process Model is Combination of Water Fall model and Spiral Model.
There are following reasons for preferring VU process model for this project and those
reasons are as follows

Reasons For Selection:

1. It is sequential model with backward repetition
2. It is more concise and advanced model then waterfall model because we can go
back at any stage of development which is not allowed in waterfall model.
3. All the activities are performed in a sequence in VU Process Model.
4. If we want to do correction at any stage if we want betterment and repetition
whenever necessary then we can choose VU process model
If you want to choose Object Oriented Life Cycle model as your adapted Project
methodology or project model then you will write it as follows as below:

Object Oriented Life Cycle Model:

There are following reasons to choose this methodology for this project.

Reasons for Selection:

Reasons behind choosing this model for this project are as follows as bellows:
1. This model is sequential in nature.
2. Maintenance is very easy & smoothly working.
3. It generates complete and comprehensive documentation because it is a
document-driven model.
4. Requirements are known before design phase begins.
5.

Waterfall Model Definition:

The waterfall model is a progressive design process, often used in
software development processes, in which progress is seen as graceful increasing
downwards through the phases of Conception, Testing, Beginning, Strategy, Examines,
Structure, Construction / Execution, and Maintenance.

In this approach, Testing section that meets to shopper satisfaction. Needs section
collects computer code specifications, practical and non-practical needs in SRS
(software requirement specification). Analysis section examines cases and work set up on
the premise of computer code demand section that covers use case circumstances up to
methodology and work set up. Style section goes through with flow charts, algorithms
and graphical user interface on the premise of study section. Section generates the
particular logic of the applying and supply reasonableness

Combination of Waterfall and Spiral Model

Requirements

Software Requirements
Specification and work
plan

Project delivery with

Quality otherwise Recycle it for
further Evaluation

System Examination

Risk Analysis:
Inefficiency with Minimum risk

Designing, Coding,
and Testing

Customer Evaluation:

Graphical
User
Interface
Design
Coding

Approval

Testing

Combination of each waterfall and spiral model is termed hybrid approach of system
development that maximizes the standard of system and minimizes the disadvantages and
risk.

VU Process Model Diagram

Work Plan (Use MS Project to create Schedule/Work Plan)