Vous êtes sur la page 1sur 8

PARLIAMO: A

COMMUNICATION SOLUTION
FOR WIRELESS LAN
Prepared by

Fakhrul Islam 081 604 540


Naimul Haider 112 1063 042
Md. Mahfuzur Rahman Siddiquee 111 0877 542

06th May 2014

ParliamoforCSE338

Pageii

TableofContents
TableofContents...........................................................................................................................ii
RevisionHistory.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1

2. OverallDescription..................................................................................................................2
2.1
2.2
2.4
2.5
2.7

ProductPerspective........................................................................................................................2
ProductFunctions...........................................................................................................................2
OperatingEnvironment..................................................................................................................2
DesignandImplementationConstraints.........................................................................................2
AssumptionsandDependencies.....................................................................................................3

3.1
3.2
3.3
3.4

UserInterfaces................................................................................................................................3
HardwareInterfaces........................................................................................................................3
SoftwareInterfaces.........................................................................................................................3
CommunicationsInterfaces............................................................................................................3

3. ExternalInterfaceRequirements...........................................................................................3

4. SystemFeatures.......................................................................................................................4
4.1 SystemFeature1............................................................................................................................4
4.2 SystemFeature2(andsoon)..........................................................................................................4

5. OtherNonfunctionalRequirements.......................................................................................4
5.1
5.2
5.3
5.4
5.5

PerformanceRequirements.............................................................................................................4
SafetyRequirements.......................................................................................................................5
SecurityRequirements....................................................................................................................5
SoftwareQualityAttributes............................................................................................................5
BusinessRules................................................................................................................................5

6. OtherRequirements................................................................................................................5
AppendixA:Glossary....................................................................................................................5
AppendixB:AnalysisModels.......................................................................................................5
AppendixC:ToBeDeterminedList............................................................................................6

SoftwareRequirementsSpecificationforParliamo

1.

Introduction

1.1

Purpose&ProductScope

Page1

Parliamo was born of a need for an internal communication infrastructure inside NSU as most of
the mobile operators have limitations near or inside Bashundhara and also the fact that much
cash is wasted on mobile bills for making calls that last only some few seconds, generated only to
know a specific persons location in the campus or his/her status as in, if that person is in the
class or not in which case we switch to texting. Therefore to negate these problems and provide
students with a means of free communication, both voice and text, Parliamo was designed taking
account of the existing network infrastructure of NSU as its backbone. For now it is designed and
deployed in Android phones.

2.

OverallDescription

2.1

ProductPerspective

Parliamo is a Viber-like application for the Android platform providing both voice communications
and text communications over the NSU internal wireless network to whoever owns an Android
phone and has Parliamo installed in it. The following diagram explains the major components of
the system:

Parliamo

Voice

Text

SoftwareRequirementsSpecificationforParliamo

2.2

ProductFunctions

2.3

Page2

Account Registration
Authentication
Search Friends
Add Friend
Text Messaging
Voice Call (future projection)
Video Call (future projection)

OperatingEnvironment

Parliamo has been designed and developed targeting the Android phone users. Android platform
has been in the market for a long time now. Brought out by Google it is an open source and
robust platform for smart phone communication and operation which has since been adopted by
many service operators and mobile phone manufacturers around the world for its simplicity and
ease of access .The hardware required to run Android OS is cheap and readily available.

2.4

DesignandImplementationConstraints

Time was the main constraint that was faced during the design and development of Parliamo.
Due to time constraints we couldnt implement voice and video calling features along with NAT
traversal routines ensuring the app can operate beyond a single home routers LAN
environment.

3.

ExternalInterfaceRequirements

3.1

UserInterfaces

<Describe the logical characteristics of each interface between the software product and the
users. This may include sample screen images, any GUI standards or product family style guides
that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that
will appear on every screen, keyboard shortcuts, error message display standards, and so on.
Define the software components for which a user interface is needed. Details of the user interface
design should be documented in a separate user interface specification.>
Each of the user functions have their own GUIs operating inside the app. The interface consists
mainly of simple buttons and text box inputs. The following screenshots will give an overview of
the user functions and how do they look.

SoftwareRequirementsSpecificationforParliamo

The Account Registration Interface

The Authentication Interface

Page3

SoftwareRequirementsSpecificationforParliamo

The Main Action Interface

The Find and Add Friends Interface

Page4

SoftwareRequirementsSpecificationforParliamo

3.2

Page5

HardwareInterfaces

<Describe the logical and physical characteristics of each interface between the software product
and the hardware components of the system. This may include the supported device types, the
nature of the data and control interactions between the software and the hardware, and
communication protocols to be used.>
The supported devices for the app include Android smartphones with Android version 4.0 (Ice
Cream Sandwich) upwards.

3.3

SoftwareandCommunicationInterfaces

The data is being enumerated to talk with the server. The following steps explains how the data
is being exchanged:
One client sends messages to others using their IP addresses and port numbers
Each client also works as a sever for receiving the messages from other clients
The server plays the role of a matchmaker to the connected devices when they send an intent
to communicate with other devices which are online. The exact role of the server are the
following:

Provides information about other clients


Retrieves information from database according to clients requests
Stores clients information in database
Server creates a new thread each time a client connects to the server and sends a
request. As a result, server can serve multiple client simultaneously.

The figure below outlines the system communication infrastructure of the different components
involved.

Server

Client 2

Database

Client 1

SoftwareRequirementsSpecificationforParliamo

4.

Page6

SystemFeatures

<This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section by
use case, mode of operation, user class, object class, functional hierarchy, or combinations of
these, whatever makes the most logical sense for your product.>

4.1

AccountRegistration

<Dont really say System Feature 1. State the feature name in just a few words.>

4.1.1

DescriptionandPriority
Account Registration is a high priority feature of the entire app and is reasonably so
to protect the privacy are one of the imperative objectives for any app of this sort...

4.2

Authentication
4.2.1

DescriptionandPriority
Authentication was implemented to check for authorized machine access.

4.3

FriendsearchandFriendadd
4.3.1

DescriptionandPriority
If there were no friends in the app then nothing can be done with.

5.

OtherNonfunctionalRequirements

5.1

SecurityRequirements

The app had a privacy issue regarding disappearing machines as one machine tends to leave the
network for some reason so the following were done to prevent that:
Check IP before sending messages
Discard message in case of wrong recipient

Vous aimerez peut-être aussi