Blue Chat System

UOSL-Project Management Committee Version: 1.
0
Step-In Date: 20/08/2017
Step-In
SESSION: BSIT FALL 2013-2017

BATCH: BS IT (Hons)/F13/
Project Supervisor: MR. Rehmat Ullah
Submitted By:
Junaid Hamid BSIT-F13-LC-133

Najam Amjad Butt BSIT-F13-LC-150
Shahzad Hussain BSIT-F13-LC-171
Atif Shahzad BSIT-F13-LC-172
Zeeshan Aziz BSIT-F13-LC-426
Department of Computer Science & Information Technology,

University Of Sargodha Lahore Campus
UOSL-Project Management Committee Version: 1.0
STATEMENT OF SUBMISSION
This is to certify that Junaid Hamid Roll No. BSIT-F13-LC-133,

Najam Amjad Butt Roll No. BSIT-F13-LC-150, Shahzad Hussain Roll No. BSIT-
F13-LC-171, Atif Shahzad Roll No. BSIT-F13-LC-172, and Zeeshan Aziz Roll No.
BSIT-F13-LC-426 have successfully completed the final project named as: Step-In, at
the Faculty of CS/IT, University of Sargodha, Lahore Campus, to fulfill the partial
requirement of the degree of Bachelors of Science in Information Technology.
________________________________
Project Management Committee
Department of Computing and IT
University of Sargodha, Lahore Campus
_____________________________ _____________________________
Supervisor HOD
©Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
2
APPROVAL CERTIFICATE
The undersigned have examined the Project entitled ‘Step-In’ presented by Junaid
Hamid, Najam Amajd Butt, Shahzad Hussain, Atif Shahzad and Zeeshan Aziz,
candidates for the degree of Bachelors of Science (BS (Hons) in Information
Technology) and hereby certify that it is worthy of acceptance.
Date Mr. Rehmat Ullah

3
Proofreading Certificate
It is to certify that I have read the document meticulously and circumspectly. I am

convinced that the resultant project report does not contain any spelling, punctuation or
grammatical mistakes as such. All in all I find this document well organized and I am
make sure that its objectives have been successfully met.
________________________________
Mr.Rehmat Ullah
University of Sargodha Lahore Campus

4
Acknowledgement
Up and above, everything, all appreciation to Allah Almighty, the compassionate and
merciful, Who enabled us to elucidate a drop from the existing ocean of knowledge,
countless salutation be upon the Holy Prophet Muhammad (Sallallaho Alaihe wa
Aalehi Wassalam), the city of knowledge, Who has guided our “Ummah” to seek
knowledge from cradle to grave.
We truly acknowledge the cooperation and help make by Project Management Office, CS
& IT department, UOS. He has been a constant source of guidance throughout the course
of this project. It is quite delectable and to becoming to avail of this most propitious
opportunity to articulate with utmost gratification, our profound and intense sense if
indebtedness to our affectionate supervisor,
Mr. Rehmat Ullah, Software Engineer, University Sargodha, Lahore Campus, Pakistan.
Their proficient counseling, valuable suggestions, boundless forbearance, indefatigable
help with anything, anywhere, anytime, consummate advice and thought-provoking
instruction in piloting this project. Special thanks for him would always be due.
We express our thankful feeling to our friends and families whose silent support led us to
complete our project.
1- Junaid Hamid
2- Najam Amjad Butt
3- Shahzad Hussain
2- Atif Shahzad
3- Zeeshan Aziz
Date:
Sep, 05, 2017

5
Abstract
In Current age the whole world is moving towards modern technology for fast
communication. This project is designed to provide a fast communication and
interconnectivity between peoples through android application. In today's world our
social life is limited. If you want to communicate with someone, you should have his/her
phone number or email id even if someone lives to your next door. Let me put you in a
situation , you are sitting in a restaurant and you are very hungry and you want to eat
something delicious , you cannot ask to anyone in restaurant because you don't know any
one's id or phone. Here we need a mobile application by which we are able to connect
everywhere without knowing contact information of people near to you.
The main purpose is to make communication possible within surrounding
environment. People who are supposed to be close with each other in social environment
can make the best use of this application i.e. in the case of office work, neighborhood and
educational purposes etc. It wouldn’t make any difference if you are new to the
application or in an unknown environment where you are unable to communicate face to
face with somebody.

6
TABLE OF CONTENTS
Chap #: Description Pages
Chapter 1: Introduction to problem 13
1.1 Problem Statement.....................................................................................13
1.2 Purpose.......................................................................................................14
1.3 Objective....................................................................................................15
1.4 Existing Solution........................................................................................15
1.5 Proposed Solution.......................................................................................15
Chapter 2: System Requirements & Specification 17
2.1 Scope................................................................................................................18
2.2 Overall description...........................................................................................18
2.2.1 Product Perspective.......................................................................................19
2.2.2 Hardware interfaces.......................................................................................19
2.2.3 Software interfaces........................................................................................20
2.2.4 Communication interfaces.............................................................................20
2.2.5 Memory Constarints......................................................................................20
2.2.6 Operations.....................................................................................................21
2.2.7 Product functions...........................................................................................21
2.2.8 Constraints.....................................................................................................21

7
2.2.9 Assumptions and dependencies.......................................................................22
2.3 Specific requirements.........................................................................................22
2.3.2 External interfaces..........................................................................................22

2.3.2.1 Functional Requirement:..............................................................................23
2.3.3 Performance requirements...............................................................................26
2.3.4 Logical requirements.......................................................................................26
2.3.5 Design constraints...........................................................................................26
2.3.5.1 Standards compliance...................................................................................26
2.3.6.1 Realiability...................................................................................................27
2.3.6.2 Availability...................................................................................................27
2.3.6.3 Security.........................................................................................................27
2.3.6.4 Maintainability.............................................................................................27
2.3.6.5 Portability.....................................................................................................28
Chapter 3: Use Case Description & Model 29
3.1 Use cases. ……………………………….…….………....……………….31

3.1.1 Login…......................................................................................................31
3.1.2 Search.........................................................................................................32
3.1.3 Set range.....................................................................................................33
3.1.4 Create Group..............................................................................................34
3.1.5 Create Message...........................................................................................35
3.1.6 Delete Message...........................................................................................36
3.1.7 Delete Group..............................................................................................37
3.2 Use case Model..........................................................................................38
Chapter 4: Software design description 39

8
4.1 System architectural design...........................................................................40

4.2 User interface design.....................................................................................42
4.3 Domain Model...............................................................................................42
4.4 Sequence Diagram.........................................................................................43
4.4.1 Registration Sequence Diagram.................................................................43
4.4.1 Registration Sequence Diagram.................................................................43
4.4.2 Login Sequence Diagram...........................................................................44
4.4.3 Profile Sequence Diagram..........................................................................44
4.4.4 Messages Sequence Diagram.....................................................................45
4.4.5 Create & delete group Sequence Diagram..................................................45
4.4.6 Overall Sequence Diagram.........................................................................46
4.5 Data Model....................................................................................................47
4.6 Deployment Diagram....................................................................................48
4.7 Collaboration Diagram..................................................................................48
4.7.1 Signup Collaboration Diagram...................................................................48
4.7.2 Login Collaboration Diagram....................................................................49
4.7.3 System Collaboration Diagram..................................................................49
4.8 Class Diagram...............................................................................................50
4.9 Database design.............................................................................................51
4.10 Gui Design......................................................................................................54
Chapter 5: Testing 65
5.1 Test case Registration....................................................................................66

5.2 Test sms sending or group chat creating.......................................................68

9
Chapter 6: Tool and used 71
6.1 Languages......................................................................................................72
6.1.2 XML...........................................................................................................73
6.1.3 Android.......................................................................................................73
6.2 Application....................................................................................................73
6.2.1 Adobe Photoshop........................................................................................73
6.2.2 Firebase.......................................................................................................73
6.2.3 Android Studio............................................................................................73
6.2.4 Draw.io........................................................................................................73
6.3 Physical Devices.............................................................................................74
6.3.1 Android operating system based smart phones .........................................74
Chapter 7: Lessons Learnt and future work 75
7.1 Lessons Learnt..............................................................................................76

7.2 Future Enhancement.....................................................................................77

10
TABLE OF Figures
3.1.1 Login..........................................................................................................31
3.1.2 Search.........................................................................................................32
3.1.3 Set Range.....................................................................................................33
3.1.4 Create Group..............................................................................................34
3.1.5 Create Message...........................................................................................35
3.1.6 Delete Message...........................................................................................36
3.1.7 Delete Group..............................................................................................37
3.2 Use Case Model.............................................................................................38
4.1 System Architecture Design.........................................................................41
4.3.1 Domain Model Diagram...........................................................................42
4.4.1 Registration Sequence Diagram................................................................43
4.4.2 Login Sequence Diagram..........................................................................44
4.4.3 Profile Sequence Diagram.........................................................................44
4.4.4 Message Sequence Diagram......................................................................45
4.4.5 Create & delete group Sequence Diagram................................................45
4.4.2 Overall Sequence Diagram.......................................................................46
4.5 Erd................................................................................................................47
4.6 Deployment Diagram...................................................................................48
4.7 Collaboration Diagram.................................................................................48
4.8 Class Diagram..............................................................................................50
4.9 Database design Diagram.............................................................................51
4.10 GUI Design Diagram...................................................................................53

11
Chapter 1
Introduction

12
Chapter-1
Introduction to the Problem
Analysis: Outline:
In this chapter we analyze the introduction, 1. Introduction
purpose, objective, existing and proposed 2. Purpose
solution of system very deeply. 3. Objective
4. Exiting solution
5. Proposed solution
Introduction to the Problem
1.1 Problem statement:

In today's world our social life is limited. If you want to communicate
with someone, you should have his/her phone number or email id even if someone lives
to your next door. Let me put you in a situation , you are sitting in a restaurant and you
are very hungry and you want to eat something delicious , you cannot ask to anyone in
restaurant because you don't know any one's id or phone. Here we need a mobile
application by which we are able to connect everywhere without knowing contact
information of people near to you. There are a lot of social apps, many of them are
famous and useful, and millions of people are using the apps in their daily life including
people from all fields of life to gain their various purposes. Most famous apps are FB
Messenger, Viber, What-Sapp, Line, We Chat, and Skype etc. It is obvious that all the
applications have mostly same features like video chat, voice chat, texting and media
sharing. You can only use these features if you have some in your contact list and most of
them are your friends and family members. What if you are at some place like airport, bus

13
station, railway station etc. where you don’t know anyone and you need help, how will
you get help?
The app we are going to build is Step-In Messenger. Basically it is client-

Server system with centralized Firebase database server. Step-in will connect you
everywhere with everyone in particular range of area without having any information of
other users, people can login by different user name and can chat in group and individuals
by keeping privacy. For example If someone wants to know live score of a match, he can
have it by the simple launching Step-in installed on his/her cell phone, people on his area
can reply to that unknown person about the match updates. Similarly different students in
the university will be enclosed in the group and they can ask different queries they have
in the university, i.e. if they want some help about a particular subject, assignment or
project. Moreover you can provide different reviews about different foods in the
restaurant you are sitting.
This application is need of hour. No application in the world giving these features.
Once you installed this application you will feel friendly, easy and comfortable at every
place because you will be assisted everywhere you go.
1.2-Purpose:
The main purpose is to make communication possible within the limited
range. People who are supposed to be close to each other all day can make the best use of
this application i.e. in the case of office work, neighborhood, educational
purposes(university, school, colleges) etc. As well as it wouldn’t make any difference if
you are new to the application and haven’t have any known friend on the platform. Just
Give any anonymous username as starter and communicate with any person who has
application installed in his phone. Of course, the purpose is to differentiate it from the
various other applications. Likewise, in other applications, if you want to communicate
with someone you need to have the phone number or email id of that particular person.
But Here we need a mobile application by which we are able to connect everywhere
without knowing contact information of people near to you. Of course, the chat

14
Application like Step-in Messenger can provide you with the several advantages which
includes:
 You meet new People.
 You exchange your views about certain subjects.
 If you are shy, it can be a way of making friends.
 You can relax because you don’t have to see the person physically.
1.3-Objective:
Objectives are:
 To produce a highly reliable application for public use.
 An application which can make socializing even more interesting.
 To produce an app which can provide you with the collection of user friendly as
well as better user experience environment when compared with other socializing
apps.
 To assist each other whenever and wherever you go.
1.4-Existing Solution:
There are some famous apps at present which can be found as a good
competitor of this app and are an existing solution right now. All apps only provide basic
features like chat, voice call, video call, media sharing etc. are FB Messenger, Viber,
What-Sapp, Line, We Chat, and Skype etc. You can only use these features if you have
some in your contact list and most of them are your friends and family member.
1.5-Proposed Solution:
People in IT field are working on instant messaging mobile
applications from the last few years. And everybody is eager to make this world a global
village. Now the Point to be noted here is that, everybody is working hard to make this
whole world contact with each other consisting of different creative ideas. But nobody

15
here is really interested in making conversation better between the closed range people.
Closed range people are the one who are supposed to be near to each other almost the
everyday and we can also call them the family .And the importance of family has also
been well described in Islam as well. So here we proposed a system which will have a
special attention on the close range people communication. For example suppose if you
are at some place like airport, bus station and railway station or in university etc. where
you don’t know anyone and you need help, you can make yourself at ease by the use of
this application.
We propose that we will provide a system that help the user with feature
location base chat and with a unique feature that other existing solution are not providing
that feature is Get any info anywhere in the world. (As well as the set “range feature”
which will especially allow you to get closer to the people who are sitting closer to you at
the moment.

16
Chapter 2
System Requirements
Specification

17
Chapter-2
System Requirements Specification
Analyses: Outline:
In this chapter we will analyze the system 1. scope
requirement specifications critically and 2. Overall description
will describe problem statement in details. 3. Specific requirements
2.1 Scope
The application is named as “STEP IN” (A step towards GPS Socialization).
The software product will improve the socializing trend.it will make communication
possible between different anonymous users in the Well-defined range.
The relevant benefits from the public point of view is that they can communicate
with the different people sitting around them and can ask the query regarding to the place
where they are sitting etc. Objective is :To produce an app which can provide you with
the collection of user friendly as well as better user experience environment when
compared with other socializing apps. Goal is to produce a highly reliable application for
public use. The software product is covering the modules like Group chat, current
location, Public Suggestions, Audio and video chat etc. People from all walks of the life
will be its Audience.
2.2 Overall description

The following SRS contains the detail product perspective from different
users. It provides the detail product functions of Step-in with user characteristics
permitted constraints, assumptions and dependencies and requirements subsets.

18
a) Product perspective; its GPS based android application.

b) Product functions; private chat, group chat, location base chat, group chat.
c) User characteristics; no trained or technical user is required. Just layman user will
be able to use application with no difficulty.
d) Constraints; these will be on development side. User will be free to use application
with little problem of battery usage due to GPS and internet use.
2.2.1 Product perspective

The system to be developed here is Step-in messenger which is basically a
centralized system with centralized Fire base database server. All local clients are
connected to the Firebase Database via internet.
This Step-In application can be used for group discussion. It allows users to
find logged-in users in same area.
2.2.2 Hardware interfaces

You don’t need a specific device to run the application rather you can utilize
or access it on your own cell phone or PDA. Android phone with normal specifications
having Wi-Fi and a Ram of 512 with 1 GB disk space is well suitable to communicate
with this application.
Step-in is a mobile application for android platform. It will support all android
based devices which contains GPS in it.
We are specially designing this mobile application which will support the
highest android software version i.e. Kit Kat and the lowest android software version i.e.
Frodo. Initially it is designed and tested for jelly Beans 4.2. Data will be synchronized
between the local application and the server application. Application will send and
receive data through Wi-Fi, mobile internet and GPS to get coordinates or to get location
information.

19
2.2.3 Software interfaces

This application interacts with the user through GUI. The interface is simple,
easy to handle and self-explanatory. Once opened, user will easily come into flow with
the application and easily uses all interfaces properly.
The Step in app will develop for android operating system using java JDK
and android SDK tools.
 Name: Android
 Mnemonics: Core Software
 Specification number: 1
 Version number: 2.2 or higher
 Name: Web Server
 Mnemonics: Server side
 Source : JAVA
 Name: Android Studio
 Mnemonics: Development software
 Version numb: Latest Studio
 Source : Google
2.2.4 Communications interfaces
Step in application will have a Firebase Database .Server will
retrieve information from online database. Application is supposed to
store user information, messages and message history information on
Server database
2.2.5 Memory constraints
Minimum disk space required is 20MB and the Minimum Ram
required is 512MB.

20
2.2.6 Operations
There are some normal features like private chat, current location, public
suggestions and group chat. In the future, some features i.e. public place rating and video
chat can be added. There are some special features which are sort of a user initiative like
group creation and group chat. Meanwhile, someone has to make the group and will add
the desired users (All list of user who are in database should be shown) to make
communication possible in a circle of different people.
2.2.7 Product functions

Our product have major functions:
 Current location
 Private chat
 Group chat.
 Public places help.
 Hot topic discussions.
 Public suggestions.
2.2.8 User characteristics

As explained earlier the main objective of the application is to make it for
everyone. The intended user don’t need to have any special sort of technical expertise,
experience or education required. He just needs to install the application and start
communicating with others around him.
2.2.9 Constraints
A) Design constraints: As we are developing this app for limited mobile phone size, so
there are constraints like limited screen size, low resolution and a problem of settling
complete interface on a limited small screen.

21
B) Implementation Constraints: As we are developing the application with the help of

Firebase and android platform, so there is a possibility that we might got confuse on
recollecting the two different languages code syntax.
C) Memory Constraints: Memory constraints are to take hold of all the database for all
information.
2.2.10 Assumptions and dependencies
I. There should be internet connection.

II. There can be multiple clients.
III. To use our system there must be Android based OS on a running
system, also internet connection must be available.
2.3 Specific requirements

 Current location
 Private chat
 Group chat.
 Public places help.
 Hot topic discussions.
2.3.1 External interfaces

 Internet.
 Firebase
 Home Screen.
 Chat Screen.
 Profile screen.
 Mobile SMS service.

22
2.3.2.1 Functional Requirement:

2.3.2.1.1 Functional Requirement -1
Id FR1
Title Login
Description To use application, user must logged in.
Input Phone number
Verification Code
Output Application home screen
Dependency Null
Id FR2
Title Search
Description User can search people in their selected range.
Input User name
Group name
Output List of searched people and groups.
Dependency FR1
Id FR3
Title Set range
Description User can set range to find people.
Input Distance.
Output Selected Radius.

23
Id FR4
Title Create group
Description User can create Group of selected Users.
Input Group name
Output Group created message.
Dependency FR1
Id FR5
Title Create Message.
Description User can write Message to send to selected User or group.
Input Sender Name

Body
Output Message ready to send.
Dependency FR1
Id FR6
Title Delete Message
Description User can delete messages from inbox.
Input Inbox messages.
Output Successful notification.
Dependency FR5 , FR1

24
Id FR7
Title Delete Group
Description User can delete his group.
Input Groups to delete.

Output Successful message.
Dependency FR4,FR1

25
2.3.3 Performance requirements

Statically, Step in application will accommodate 500 to 1000 users on starting terms.
Then it will be taken care afterwards with the usage of application. English language will
be the default supported language with the option of other supported languages as well.
Input/output will be in English or numeric form.
Dynamically, under normal circumstances Application will make 90 %

transactions in 1 sec. whereas in Workload conditions, Application will make transactions
in between 5 seconds as well. Terminals will be around 5 to 10 under normal conditions.
2.3.4 Logical requirements

a) Types of information used by various functions;
Text and media.
b) Frequency of use;
It depends on usage of system by the users.
c) Accessing capabilities;
Not a high accessing capabilities of the system.
d) Data entities and their relationships;

e) Integrity constraints;
User privacy.
2.3.5 Design Constraints

Application is for portable or moveable android devices having small and medium
size screen sizes.
2.3.5.1 Standards compliance

a) Report format;
Only textual data.

26
2.3.6.1 Reliability
Reliability factor should have been there in the application to make sure.
That the software is reliable enough and is ready to accommodate as much a load as
possible in extreme circumstances. This factor is just a core need of software. As the
software isn’t hang or stopped under some circumstances. Step-In application is reliable
and in good working condition. It will not crash even if device memory is full or server is
loaded with high traffic. It will provide proper messages to user to accommodate user for
better user experience. All the features will be ready to use at any time and with no extra
wait. Battery usage will be optimized by putting minimum load on battery and maximum
usage. Location is optimized by getting location by different sources. All the screens are
designed according to HCI point of view by providing simple, informative and interactive
designs. All the network activities are highly secure and reliable. User privacy is highly
taken care of by providing all possible security and privacy features.
2.3.6.2 Availability
Application will be available to use if you have any internet source like Wi-Fi
or mobile data.
2.3.6.3 Security
Security is the one thing that should have been looked after with the great
care if you want to build a location based application. In our app several
cryptographically techniques will be highly preferred just to make the maximum security
of user. block just to add more security if in some cases i.e. Somebody is not feeling
secured from the other person.
2.3.6.4 Maintainability
Just to make and run the software is not enough. Its maintainability should
have been highly preferred just to make it reliable from time to time. Its defects, errors,
faults needs to be removed on scheduling bases. Time to time improvement of the
software adds the maintainability feature in the software. Some requirements will be
applied here just to check out the complexities and interfaces in spite of all requirements .

27
2.3.6.5 Portability
Step in is a location based application designed especially for Android Mobile
operating system. Almost 80 % of its code and components are host dependent. the
biggest and wide variety of android devices are just enough to prove the portability factor
as every person has one these days and they can take it everywhere they would like.
a. Organizing the specific requirements
No specific training should be necessary for a user to begin using this

application. The system shall respond to each user input within 2 seconds.
Copyright laws and license agreements must be respected for any third party software
used in the creation of this system.

28
Chapter 3
Use case description
and model

29
Chapter-3
Use Case Description and Model
Analyses: Outline:
In this chapter we analyze all the use case 3.1 Use cases
model and write it down.
1. Signup
2. Login
3. Search
4. Set Range
5. Create Message
6. Delete Message
7. Create Group
8. Delete Group
3.2 Use case Model

30
3.1 Use cases:
3.1.1 Login
Figure 3.1.1 Login

Use case Table:
Use case number 1
Use case name Log in
Actor User
Description User must login for using this app.
Precondition Not login
Basic flow User enter the Username Password.
Alternative flow Already logged in.

Incorrect code.
Post condition Login Successfully.

31
3.1.2 Search
Figure 3.1.2 Search

Use case Table:
Use case 2
number
Use case Search
name
Actor User
Description User can search people.
Precondition No Search
Basic flow People found
Alternative Search again
flow
Post Successfully.
condition

32
3.1.3 Set range:
Figure 3.1.3 Set Range
Use case table:
Use case 3
number
Use case Set range
name
Actor User
Description User can set range to find people.
Precondition Range not set.
GPS available.
Basic flow Select radius of area.
Set range.
Alternative Range not set.
flow Location not available.
Post Range set Successfully.
condition

33
3.1.4 Create Group:
Figure 3.1.4 Create Group
Use case table:
Use case 4
number
Use case Create Group
name
Actor User
Description User can create Group.
Precondition Group create
Basic flow Creating group
Alternative Group not create
flow
Post Successfully
condition

34
3.1.5 Create Message:
Figure 3.1.5 Create Message
Use case table:
Use case 5
number
Use case Write Message
name
Actor User
Description User can write Message.
Precondition Message create.

Basic flow Message creating.
Alternative Message not create.
flow
Post Successfully.
condition

35
3.1.6 Delete Message:
Figure 3.1.6 Delete Message
Use case table:
Use case 6
number
Use case Delete Message
name
Actor User
Description User can delete messages from inbox.
Precondition Message should be in inbox.
Basic flow Go to inbox.
Select message.
Go to options and delete.
Alternative No message to delete.
flow
Post Message no more present in inbox.
condition
Result Successfully deleted.

36
3.1.7 Delete Group:
Figure 3.1.7 Delete Group
Use case table:
Use case 7
number
Use case Delete Group
name
Actor User
Description User can delete his group.
Precondition User should be its admin.
Group should be present.
Basic flow Go to group options.
Select the delete options.
Alternative Not the admin of the group.
flow
Post Group not available anymore.
condition
Result Successfully deleted.

37
3.2 Use case Model:
Figure 3.2 System Use Case Model

38
Chapter 4
Software Design
Description

39
Chapter-4
Software design description
Introduction: Outline:
This chapter is all about overall 1. System Architectural
Software design description. Design
2. User interface design
3. Data base Design
4. Data Flow diagram
5. System Sequence diagram
4.1 System Architectural Design:

A system architecture or systems architecture is the conceptual model that defines
the structure, behavior, and more views of a system. An architecture description is a
formal description and representation of a system, organized in a way that supports
reasoning about the structures and behaviors of the system. Step-in will contain the
following core components.
 Signup / Login
 Firebase Authentication
 Profile
 Set Range
 Near by
 One 2 One chat
 Group Chat

40
System Architecture Design:
Figure 4.1 System Architecture Design

41
4.2 User interface design:

User interface design (UI) or user interface engineering is the design of user
interfaces for machines. The goal of user interface design is to make the user's interaction
as simple and efficient as possible, in terms of accomplishing user goals (user-centered
design).
4.3 Domain model

After understanding the use case model now we will try to understand the
domain model with the help of domain model diagram. Remember its only
conceptual domain model diagram which will help us to understand our complete
project.
Basically we will try to understand
 What User can do

 How it is done
 And much more…..
4.3.1 Domain model Diagram
Figure 4.3

42
4.4 Sequence Diagram:

Sequence diagrams describe interaction among classes in term of an exchange
of messages over time. They’re also called event diagrams. A sequence diagram is a good
way to visualize and validate various runtime scenario.
Sequence diagrams are typically use to model:
 Usage scenarios
 The logic of methods
 The logic of services
Sequence of actions that are used in this project are
 Signup
 Login
 messages
 Create & Delete Group
 System Sequence diagram
4.4.1 Registration Sequence Diagram:
Figure 4.4.1 Registration Sequence Diagram:

43
4.4.2 Login Sequence Diagram:
Figure 4.4.2 Login Sequence Diagram
4.4.3 Profile Sequence Diagram:
4.4.3 Profile Sequence Diagram

44
4.4.4 Messages Sequence Diagram
Figure 4.4.4 Message Sequence Diagram
4.4.5 Create & Delete Group Sequence Diagram:
Figure 4.4.5 Create and Delete Group Sequence Diagram

45
4.4.6 Overall System Sequence Diagram:
Figure 4.4.6 Overall System Sequence Diagram

46
4.5 Data Model (ER Diagram):
ER model is a data model for describing the data or information aspects of a business
domain or its process requirements, in an abstract way that lends itself to Ultimately
being implemented in a database such as a relational database. The main components of
ER models are entities (things) and the relationships that can exist among them.
Figure 4.5 Data Model Diagram

47
4.6 Deployment diagram:
Figure 4.6 Deployment Model Diagram
4.7 Collaboration diagram:

The interaction between objects is describe by collaboration diagram. Collaboration diagrams for
this project are following
4.7.1 Signup Collaboration diagram:
Figure 4.7.1 Signup Collaboration Diagram

48
4.7.2 Login Collaboration diagram:
Figure 4.7.2 Login Collaboration Diagram
4.7.3 System Collaboration diagram:
Figure 4.7.3 Overall System Collaboration Diagram

49
4.8 Class diagram:
Figure 4.8 Class Diagram

50
4.9 Database design:
4.9.1 Groups:
Figure 4.9.1 Groups Database Design Diagram
Location:
Figure 4.9.2 Location Database Design Diagram

51
4.9.3 Group Chat:
Figure 4.9.3 Group Chat Database Design Diagram
4.9.4 Online Users:
Figure 4.9.4 Online Users Database Design Diagram

52
4.9.5 Users:
Figure 4.9.5 Overall Users Database Design Diagram

53
4.10 Gui Design:
4.10.1 Signup form:
Figure 4.10.1 Signup Form

54
4.10.2 Number Verification form:
Figure 4.10.2 Verification

55
4.10.3 Login form:
Figure 4.10.3 Login Form

56
4.10.4 Profile form:
Figure 4.10.4 Profile Form

57
4.10.5 nearby form:
Figure 4.10.5 nearby Form

58
4.10.6 Group Chat form:
Figure 4.10.6 Group Chat

59
4.10.7 nearby form:
Figure 4.10.7 nearby Form

60
4.10.8 Select user for group chat form:
Figure 4.10.8 Select User for Group Chat

61
4.10.9 Group chat activity:
Figure 4.10.9 Group Chat Activity

62
4.10.10 loading application:
Figure 4.10.10 Application Loading

63
4.10.11 Forget Password:
Figure 4.10.11 Forget Password

64
Chapter 5
Testing

65
Chapter-5
Testing
Introduction
This chapter contains all the information about the testing of the step in messenger.
5.1 Testing Registration

In this module input validations tested which are given below.
 Check whether Email is entered correctly or not
 Check whether Password is entered correctly or not.
 Check whether Contact No. is entered correctly or not.
 Check whether 4 digit verification code send or not.
a. Test Case Id: TC #1
Test Case Name: Test Email entered

Pre-Condition Registration UI is Open
Sr Action Expected Result Status
1 Enter Email in “Email” input Email Structure is OK

box Valid
Table 1: Test Email (Test Case)

66
b. Test Case Id: TC #2
Test Case Name: Test Password entered

Pre- Registration UI is Open
Condition
1 Enter Password in Password is same in OK

“Password ” and “Confirm both input box
Password” Input box
Table 2: Test Password (Test Case)
c. Test Case Id: TC #3
Test Case Name: Test Mobile No entered

Pre-Condition Registration UI of App is Open
1 Enter integer value for phone Valid OK

Number
Table 3: Test Mobile No (Test Case)
d. Test Case Id: TC #4
Test Case Name: Test verification code is received

Pre-Condition Confirmation Dialog box appear
1 Enter integer value for 4 digit Valid OK

verification code
Table 4: Test Confirmation Sms (Test Case)

67
5.2 Testing Sms sending or Group Chat creating

 Check whether Sms send to single user or not.
 Check whether Chat Group is created or not.
 Check whether Sms Sending in a group or not
Test Case Name: Test Send Sms to Single user

Pre-Condition Main Chat UI Tab
1 Write and Send sms Message sent OK
Table 5: Test Single Chat (Test Case)
Test Case Name: Test Group for Chat is created

Pre-Condition Database of User list appear To create a group
1 Select User from database Group Created OK

and Click on Create button
Table 6: Test Create Group Chat (Test Case)
c. Test Case Id: TC #7
Test Case Name: Test Send Sms to Group Chat

Pre-Condition Send Sms to Group Chat
1 Write and Send sms Message sent OK
Table 7: Test Group Chat (Test Case)

68
5.3 Testing Login

 Check Entered Email and Password are matching in database or not.
d. Test Case Id: TC #8
Test Case Name: Test Login

Pre-Condition 1. Email should be valid.
2. Password should be valid.
1 Click Login button Login Success OK
Table 8: Test Login (Test Case)
5.4 Testing NearbyDevices

 Check whether Nearby Users showing or not
Test Case Name: Test Showing NearbyDevices Using this App.

Pre-Condition 1. Location Service is On.
2. Set the range bar in km.
1 Click on Nearbydevices icon Show the list of OK

Tab. User in this range
having this App.
Table 9: Test NearbyUsers (Test Case)

69
5.5 Testing Profile Setting

 Check whether Profile picture Upload or not.
 Set your number privacy public or private.
Test Case Name: Test Whether the profile pic is uploaded or not
Pre-Condition Profile Setting Tab UI is Open.
1 Click on edit profile picture Your profile picture OK

icon. Click on upload is updated.
Table 10: Test NearbyUsers (Test Case)

Test Case Name: Test Privacy of phone Number

Pre-Condition Profile Setting Tab UI is Open.
1 1.Set Public to show public On Public show

2.Set Private to keep it number to all.
private. On private keep OK
Phone Number
Private.
Table 11: Test Privacy of Phone Number (Test Case)
5.6 Testing forget password

 Check whether Password is Send to Gmail or not
Test Case Name: Test Forget Password

Pre-Condition Open Forget Password UI of App.
1 Enter a User email. Click on Your password is OK

Reset Password. send to email.

70
Chapter 6
Tool and used

71
Chapter-6
Tool and used
This chapter makes know 1. Languages
technical expertise and other readers 2. Application
about the tools which are used to 3. Physical Devices
develop this android application
project.
Introduction:
This chapter will let people know about the tools i.e. (Languages, Applications
and other physical devices) used to build this android Application.
This Chapter is all about the tools used in this application to develop the app named STEP
IN: (A Step towards GPS based Socialization).The tools are divided into three categories
and are as follow:
1-Languages.
2-Applications and Software Products.
3-Physical Devices.
These three tools will be discussed in this chapter in detail.
6.1- Languages
6.1.1 Java
The application step in is developed for android operating system supported
devices. While working on SDK, the programing language of android application is java
programing language which is different from java SE and java ME. The android’s version

72
of java programming language does not directly relate to java SE although it used a
subset of apache Harmony SE 6 libraries and tools.it also uses other custom libraries too.
6.1.2 XML
To Design the front end of the android application, XML is used. Using
Android’s XML vocabulary UI layouts and the screen elements they contain, are
designed.
6.1.3 Android
Android has been used here for server side of Step In Messenger. Which is
used on the server side and acts as a bridge between client side local database and the
server side Firebase database.
6.2 Applications:
The Applications and software used are as follows:
6.2.1 Adobe Photoshop:

Adobe Photoshop is mostly used for graphics designing and is also used
for image editing Purposes. People use this application to make web graphics of different
types like application Logos, banners etc. The Logo of STEP IN Messenger is designed in
adobe Photoshop.
6.2.2 Firebase:
Firebase is an online database
6.2.3 Android studio:

STEP IN Messenger has been developed using Android Studio.
6.2.4 Draw.io and EDRAW:

Draw.io and mostly EDRAW is diagramming and design software. These
applications can be used to create Flowcharts, Gantt Charts, info graphics, UML designs,
website wireframes, Circuit board designs and many other diagrams in the likes of

73
component diagram, System Sequence diagram, class diagram, deployment diagram,

domain model, ERD diagram etc in the tools mentioned.
6.3 Physical Devices:
The following Physical devices are used to develop STEP IN Application.
6.3.1: Android operating System based Smart Phones:

As the STEP IN Messenger is designed for the Android based smart
phones. So Android based smartphones are required to run and test the software
application. So two smartphones are used to develop the application.
1-Samsung Galaxy S4 –Android 4.4.2 (Kit Kat).
2-LG G2-Android 4.4.2(Kit Kat).

74
Chapter 7
Future Enhancement

75
Chapter 7
Lessons Learnt and Future work/Enhancement
This chapter contain lessons 1. Lessons Learnt.
we have learnt by working on this 2. Future Enhancement
project. This chapter also contain the
future work and enhancement of our
software product.
7.1 Lessons Learnt:

The project was very tremendous source of learning for us. The journey,
which was of two semesters in (almost one year) was very great indeed. During whole
year, we have come cross many challenges. This was first time in our eight semester
degree program we worked on a large project as from now; we will do in our professional
life, In SHAA ALLAH. In addition, we (the team) were new to android development and
this was the first time to deal with programming on handheld systems. In beginning, we
were new to the programming in android systems, so we have spent massive time on
studying the specification of the system and to learn programming mobile application for
android handheld systems. However, those spent time were worthwhile.
This project really made us realize the value of working together as a team,
and a new and great experience in this learning environment. This is the most precious
thing we have learnt in this project .this project really provided us opportunity to make
our friendship stronger as we spent more and more time together for project discussions.
Moreover, there are a lot of memorable moments which are worthwhile for us.

76
7.2 Future Enhancement:
The main objective of the application was to develop an application which

will be specifically for the people of Pakistan and other countries. At the current moment,
this is an android based chat messenger from which you may sent and receive message to
the people.in the near future following enhancement to the application might be made.
7.2.1 Media Files Transfer
Using later releases of Step in, one might be able to send and receive
media file like images, and audio files through this messenger. Step in will also provide a
feature to send an audio recorded message to your friends.
7.2.2 Cross-Plate Form:
The Step In Messenger is currently available only for android based
handheld devices .We will make this application available to other plate forms too, which
includes IOS, Window and Black Berry.
7.2.3 Video and Audio Calls:
Another Enhancement which can be made to this Step in Messenger is to allow users
audio and video calls though Wi-Fi and mobile data.

77

Blue Chat System

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Blue Chat System

Загружено:

Авторское право:

Доступные форматы

UOSL-Project Management Committee Version: 1.

SESSION: BSIT FALL 2013-2017

Junaid Hamid BSIT-F13-LC-133

Department of Computer Science & Information Technology,

This is to certify that Junaid Hamid Roll No. BSIT-F13-LC-133,

©Project Management Committee

Date Mr. Rehmat Ullah

©Project Management Committee

It is to certify that I have read the document meticulously and circumspectly. I am

University of Sargodha Lahore Campus

©Project Management Committee

©Project Management Committee

©Project Management Committee

Chap #: Description Pages

Chapter 1: Introduction to problem 13

1.1 Problem Statement.....................................................................................13

1.4 Existing Solution........................................................................................15

1.5 Proposed Solution.......................................................................................15

Chapter 2: System Requirements & Specification 17

2.2 Overall description...........................................................................................18

2.2.1 Product Perspective.......................................................................................19

2.2.2 Hardware interfaces.......................................................................................19

2.2.3 Software interfaces........................................................................................20

2.2.4 Communication interfaces.............................................................................20

2.2.5 Memory Constarints......................................................................................20

2.2.7 Product functions...........................................................................................21

©Project Management Committee

2.2.9 Assumptions and dependencies.......................................................................22

2.3 Specific requirements.........................................................................................22

2.3.2 External interfaces..........................................................................................22

3.1 Use cases. ……………………………….…….………....……………….31

Chapter 4: Software design description 39

©Project Management Committee

4.1 System architectural design...........................................................................40

5.1 Test case Registration....................................................................................66

©Project Management Committee

Chapter 6: Tool and used 71

Chapter 7: Lessons Learnt and future work 75

7.1 Lessons Learnt..............................................................................................76

©Project Management Committee

©Project Management Committee

©Project Management Committee

Introduction to the Problem

Introduction to the Problem

1.1 Problem statement:

©Project Management Committee

The app we are going to build is Step-In Messenger. Basically it is client-

©Project Management Committee

 An application which can make socializing even more interesting.

 To assist each other whenever and wherever you go.

©Project Management Committee

©Project Management Committee

©Project Management Committee

System Requirements Specification

2.2 Overall description

©Project Management Committee

a) Product perspective; its GPS based android application.

2.2.1 Product perspective

2.2.2 Hardware interfaces

©Project Management Committee

2.2.3 Software interfaces

©Project Management Committee

2.2.7 Product functions