Group Id= IT-F17-22 Komal Hafeez 01-235142-026 Sahira Zaheer 01-235142-026 Society solution Application Bachelor in Information Technology Supervisor

Group Id= IT-F17-22
Komal Hafeez
01-235142-026
Sahira Zaheer
01-235142-026
Society solution Application
Bachelor in Information Technology
Supervisor: Sameen Arshad
Department of Computer Science Bahria University, Islamabad
1

ABSTRACT
One of the distinct features of smartphones is that they allow users to
install and run third-party application programs. The intended application
will help Askari society in order to improve the work structure of society.
The aim is to design and develop such a system that will solve the issues of
residents and maintain the society. This Application is eliminating call center
and allow the resident to contact directly through mobile application to the
worker and take services. We have an admin here which allow or accept the
registration of both worker/residents and manage security. In this proposed
pro ject we use password less login system so any user dont have to remember
his password in order to login to the application. For sending request user
will click the locate worker option after turning on his mobile Gps and he
will be able to see entire workers present nearby his home. When user clicks
on any worker icon he can see the workers information, rating and option of
send request.
2

Acknowledgments
We would like to thank ALLAH Almighty for his countless blessings, our
parents and Friends for support, help and giving us motivation in completing
our pro ject successfully. They always inspired us to complete each and every
task with dedication and condence. Moreover, we are very thankful to
our supervisor Mam Sameen Arshad who has given us the chance to work
on this amazing pro ject and for providing us the professional guidance to
complete this pro ject successfully. Her motivation, advice, guidance and
support throughout the pro ject is highly appreciated.
3

Contents
1 Introduction 9 1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Problem Description . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 Pro ject Ob jective . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4 Pro ject Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.5 Benets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6 Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2 Literature Review 12 2.1 Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2 Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3 Current Application . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.5 Design and Testing . . . . . . . . . . . . . . . . . . . . . . . . 14
2.6 3G/4G Networks . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7 Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7.1 Agile methodology . . . . . . . . . . . . . . . . . . . . 15
2.8 PASS WORDLESS LOGIN SYSTEM . . . . . . . . . . . . . . 15
2.9 WEB API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.10 CONCLUSION . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3 Requirement Specication 17 3.1 Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Application Overview . . . . . . . . . . . . . . . . . . . . . . . 18
3.3 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . 18
3.4 Software Requirement Specication . . . . . . . . . . . . . . . 18 3.4.1 Functional Requirements . . . . . . . . . . . . . . . . . 18
3.4.2 Non-Functional Requirements . . . . . . . . . . . . . . 19
4

3.5 USE CASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.5.1 Use case for worker . . . . . . . . . . . . . . . . . . . . 25
4 Design 32 4.1 SYSTEM DESIGN . . . . . . . . . . . . . . . . . . . . . . . . 32 4.1.1 System architecture: . . . . . . . . . . . . . . . . . . . 32
4.1.2 Context Diagram . . . . . . . . . . . . . . . . . . . . . 34
4.1.3 Data Flow Diagram(Worker/Resident) . . . . . . . . . 35
4.1.4 Entity relation diagram (ERD) . . . . . . . . . . . . . 37
4.1.5 Sequence Diagram . . . . . . . . . . . . . . . . . . . . 38
4.1.6 Component Diagram . . . . . . . . . . . . . . . . . . . 39
4.1.7 Deployment diagram . . . . . . . . . . . . . . . . . . . 40
4.1.8 System Constraints . . . . . . . . . . . . . . . . . . . . 41
5 SYSTEM IMPLEMENTATION 45 5.1 TOOLS AND TECHNOLOGIES . . . . . . . . . . . . . . . . 45 5.1.1 Android studio . . . . . . . . . . . . . . . . . . . . . . 45
5.1.2 Android Software Development kit . . . . . . . . . . . 46
5.1.3 Development/Environment languages used . . . . . . . 46
5.1.4 Android Mobile Device . . . . . . . . . . . . . . . . . . 46
5.1.5 Application Access Security . . . . . . . . . . . . . . . 46
5.1.6 MySQL Database . . . . . . . . . . . . . . . . . . . . . 47
6 SYSTEM TESTING AND EVALUATION 48 6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.2 Software Testing Techniques . . . . . . . . . . . . . . . . . . . 48 6.2.1 Graphical User Interface (GUI) Testing . . . . . . . . . 49
6.2.2 Usability Testing . . . . . . . . . . . . . . . . . . . . . 49
6.2.3 Software Performance Testing . . . . . . . . . . . . . . 49
6.2.4 Load Testing . . . . . . . . . . . . . . . . . . . . . . . 50
6.2.5 Security Testing . . . . . . . . . . . . . . . . . . . . . . 50
6.2.6 Functional Testing . . . . . . . . . . . . . . . . . . . . 50
6.2.7 Integration Testing . . . . . . . . . . . . . . . . . . . . 50
6.2.8 System Testing . . . . . . . . . . . . . . . . . . . . . . 51
6.2.9 Acceptance Testing . . . . . . . . . . . . . . . . . . . . 51
6.2.10 Installation Testing . . . . . . . . . . . . . . . . . . . . 51
6.2.11 Test Cases . . . . . . . . . . . . . . . . . . . . . . . . 51
5

7 CONCLUSION 59
7.1 Ma jor Accomplishment . . . . . . . . . . . . . . . . . . . . . . 59
7.2 IMPROVEMENTS FOR FUTURE . . . . . . . . . . . . . . . 60
6

List of Tables
3.1 login/sign-up user use case . . . . . . . . . . . . . . . . . . . . 23
3.2 View Worker’s prole user use case . . . . . . . . . . . . . . . 24
3.3 send request user use case . . . . . . . . . . . . . . . . . . . . 26
3.4 Give Feedback user use case . . . . . . . . . . . . . . . . . . . 26
3.5 Acquire request use case . . . . . . . . . . . . . . . . . . . . . 29
3.6 Accept request use case . . . . . . . . . . . . . . . . . . . . . . 29
3.7 Receive feedback use case . . . . . . . . . . . . . . . . . . . . 31
6.1 Installation of Application . . . . . . . . . . . . . . . . . . . . 52
6.2 login verication test case . . . . . . . . . . . . . . . . . . . . 53
6.3 Locate Worker test case . . . . . . . . . . . . . . . . . . . . . 55
6.4 Send Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.5 Feedback and rating . . . . . . . . . . . . . . . . . . . . . . . 58
7

List of Figures
3.1 Use Case Diagram of Resident . . . . . . . . . . . . . . . . . . 21
3.2 Login/Signup use case Diagram of resident . . . . . . . . . . . 22
3.3 View worker’s prole use case Diagram . . . . . . . . . . . . . 22
3.4 Send request use case Diagram . . . . . . . . . . . . . . . . . . 25
3.5 Give Feedback use case Diagram . . . . . . . . . . . . . . . . . 27
3.6 Use Case Diagram of worker . . . . . . . . . . . . . . . . . . . 28
3.7 Acquire Request use case Diagram . . . . . . . . . . . . . . . 30
3.8 Accept Request use case Diagram . . . . . . . . . . . . . . . . 30
3.9 Receive Feedback use case Diagram . . . . . . . . . . . . . . . 31
4.1 System architecture Diagram . . . . . . . . . . . . . . . . . . 33
4.2 context Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.3 Worker/Resident Data
ow Diagram . . . . . . . . . . . . . . 36
4.4 ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.5 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . 38
4.6 component Diagram . . . . . . . . . . . . . . . . . . . . . . . 39
4.7 Deployment Diagram . . . . . . . . . . . . . . . . . . . . . . . 40
4.8 Application logo . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.9 Login (password less login) . . . . . . . . . . . . . . . . . . . . 43
4.10 Login (password less login) . . . . . . . . . . . . . . . . . . . . 44
6.1 Login Verication . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.2 Locate Worker . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8

Chapter 1
Introduction
1.1 Introduction
One of the most attractive feature of smart phone is the availability of a
large number of applications for users to download and use. User installs
and uses these application for entertainment, nancial transactions and for
other purposes. The proposed pro ject is to make a mobile application for the
maintenance of society that will be used by both worker and residents. There
are many workers working in a society as electricians, plumbers, carpenters
etc. When resident need any services they call to facilitation center (which
provide all the facilities to the society residents) of society to register a com-
plaint and then that call center make another call to the worker to inform
him and give him details about work and resident(address). The process
consume a lot of time, resources and sometimes resident dont get good ser-
vices. This application is to eliminate the call center so the resident can send
direct request to the workers to get the services (electrician, plumber etc.).
Resident will send or post the request for work according to the particular
work category to the worker. Resident will not make call to call center for
any service he will be able to contact directly to the worker. Currently this
idea is available in New York where user post request for work and the labor
answer the request in order to provide service. In Karachi-Pakistan there is a
website named mazdooronline.pk 5. through which people can hire worker.
In societies of Pakistan there is no concept of this type of application and
people call to call center or facilitation centers to get any service.
9

1.2 Problem Description
Now a days people prefer to live in a well-managed society for better living
style and facilities. For the appropriate maintenance and to provide luxury
accommodation society hires dierent worker to take good care of society in
dierent manners. But because of the call center Residents dont get their
services on time, we will eliminate call center and the residents will be able
to contact directly to the worker. Through our pro ject the residents can get
all the services of electricians, carpenters, plumbers provided to the colony
by housing society just by using mobile application.
1.3 Pro ject Ob jective
The main ob jective of a pro ject is to design an application that will eliminate
call center from society and provide direct communication between residents
and the workers. Other ob jectives are as follows.
o Save time of both resident and workers.
o Eliminate the priority system (Sometimes society management give im-
portance to the work of those who are government employees or belong to
the leading class) which has been established in society. Residents will take
service on time.
o Improve maintenance of society.
1.4 Pro ject Scope
The intended application will help Askari society to improve the work struc-
ture of society through application. Through this Application administration
will be able to keep the track of workers and all work. The aim is to design
and develop such a system that will solve the issues of residents by pro-
viding them the services and maintain the society. This mobile application
is to eliminate the call center by allowing the residents to contact directly
to the worker of the colony for service (plumber, electrician etc.) through
mobile application. Residents will be able to take service on time and can
rate the work through feedback and ratings. Admin can see the status of
the each worker (online, o-line) .Through database record of work and each
worker will be available for society administration. We have an Admin here
which allow or accept the registration of both worker/residents and manage
10

security. This application can be extended city wide in future. Application
doesnt have the data of outside worker of colony.
1.5 Benets
o Society will be able to keep the track of workers.
o From the residents point of view they will take service on time without any
priority system in the society.
o It will make the workers more active in work.
o Society administration can rate every worker through residents feedback.
o Administration can add or delete any worker.
1.6 Outline
The proposed pro ject is to maintain the work system and to provide quick
services to resident for the better living style in the society through mobile
application. There are many workers who are working in the society like
electricians, plumbers, carpenters etc.
11

Chapter 2
Literature Review
This chapter includes the existing work in the eld of android and how an-
droid mobile applications became an important measure of everyones life.
It described many studies related to the applications, technology, usage and
their User Interface design (UI) that attract customers to install mobile ap-
plications and use them for their work User interface should be interactive
and easy to understand and use. Complex user interface can irritate the user.
2.1 Existing System
There are dierent mobile applications or websites in the entire world that
provide labor online. But if we see Pakistan they all are not really com-
puterized, they work manually. Mazadooronline.pk is an online extensive
quality household services providing platform based in Karachi – Pakistan.
They provide best experienced, professionally skilled workers that work 100
percent safety with full devotion. For acquiring service rst you will select
the category of work (electrician, plumber, painter, carpenter), they provide
numerous categories of worker from which you can select easily. After se-
lecting a category of service the person will call the numbers provided by
them in order to get service. After availing the services you will pay the bills
as per agreement or according to the work and work duration. You cannot
input anything about your problem, you will dene the problem to company
on phone call. Practical android applications are not available in Pakistan
which helps to get labor online without any diculty.
12

2.2 Technology
Guizani conducted a study and concluded that smart phone is now playing a
ma jor role in peoples life, becoming rst choice for sharing information 1.
One of the distinct features of smart-phones is that they allow users to install
and run third-party application programs, which are usually referred to as
applications. These applications are ocially distributed via online stores re-
ferred to as application markets. These markets provide a convenient venue
for application developers to distribute their applications and for users to ex-
plore and download new applications. This has driven the great development
rate of applications in recent years. For example according to a research in
September 2012 Google Play Store and Apple application Store had more
than 650,000 to 700,000 applications 1. Mostly user prefers Google appli-
cations because Google play use Malware detector named bouncer to scan
every application before it release, so that user can use applications from
their platform without any threat of malware 1.
2.3 Current Application
These kinds of applications not really exist in Pakistan. For example there
is a website named mazdooronline.pk which able you to get labor services
but that website works manually. First you select a particular category of
worker and then you make a call to ask them for further.
2.4 Usage
People are able to order households, groceries, books, food and various other
items while sitting at home through mobile applications. Now people also
prefer to do nancial transaction, bill payments and many other banks work
by using android applications provided by applications. Many applications
provide communication, entertainment and nancial transactions. These are
just a few of the numerous examples of how things are made easy for people
so they will not have to wait in lines of travel to shop. Applications have
user interface designs that attract and help people to know how they can use
a specic application for their work.
13

2.5 Design and Testing
Jeo Ligma explained in a study that during the mobile application devel-
opment cycle, User-Interface (UI) components of the mobile application are
typically validated against high-Fidelity mock-ups by manually comparing
screens from a mock up design to screens developed in the application 2.
Mock up assets are usually made using design tools, such as Illustrator, Fire-
works, InDesign and Keynote. In our pro ject we used illustrator/Photoshop
as a design tool to make the mock up of our User Interface (UI) and dierent
modules of pro ject. Mobile application development cycle include typically
a manual and usual test of UI, as verifying that it has been built according
to design .This helps in identifying defects. Changes in Mobile application
designs and requirement occurs due to changes in customer and technical re-
quirements, and often because of a lack in understanding the problem. From
a developer prospective, unit tests help to manage these changes. We will use
unit testing for the application because it helps to validate the User Interface
(UI) design and to increase customer interest. Except unit testing techniques
like histogram, template and feature matching provide additional and ade-
quate solutions to verify that a mobile application User interface (UI) meets
the acceptance criteria provided by the design team 2. The design team
rst makes design for the mobile application according to the requirement
provided by customer. After the design team makes all the design then its
up to the tester to verify that design according to the mockups.
2.6 3G/4G Networks
Living in the age where technology and cell phones are a ma jor part of life,
we know how essential these devices and applications for our lives. As it
became more common and new ways of gaining access to the Internet made
appearance in the form of 3G/4G, the cost of Internet access reduced a great
deal. According to the research of Zhenjiang it is determined that by 2016,
580 4G networks were launches in 188 countries which cover almost 60 percent
of the world population 3. Mobile phones are able to get a lot of data from
the Internet using 3G/4G and shared information is helping cell phones do
a lot more than just sending messages or making phone calls.
14

2.7 Methodology
According to a study directed by Veronika Vessel it is established that agile
methodology is decent for the software development because the method-
ologies of software development aect the cost of the software development,
time and quality of development 4. The successful execution of pro jects
and keeping them within estimated cost and prescribed schedules depend
on a methodology. Many pro jects experience extensive delays, exceed ini-
tial time schedule and cost estimate to the dislike of clients, contractors and
consultants because of the wrong methodology.
2.7.1 Agile methodology
Agile methodology is an approach to pro ject management, typically used
in software development. Software is developed in incremental, rapid cy-
cles. This results in small incremental releases with each release building on
previous functionality. Each release is thoroughly tested to ensure software
quality is maintained. Agile methodologies depend on the customer cooper-
ation instead of processes, documentation or following a plan. It increases
customer satisfaction by rapid, continuous delivery of useful software. We
choose agile methodology because our application depends on cooperation of
both workers and resident. Agile methodology also helps in dening resource
type and resource dedication. We provide a communication platform for
our customer and agile methodologies provide great communication between
client and provider.
2.8 PASS WORDLESS LOGIN SYSTEM
Passwords less login systems are those which do not require typical string of
character in order t to sign up for an account. Email authentication, Bio-
metric authentication and number authentication are some types of password
less logins systems. Users dont want to remember another password just to
access their online accounts, or make a purchase. Its likely they already have
multiple passwords to remember and adding one more to the mix could make
or break their decision to sign up for an account. Additionally, recent data
shows that password security isnt as strong as we think. Even a complex
password has the potential to be compromised with the right technology and
15

an attentive hacker. Luckily, new technology and password less login systems
are making it easier for for-prot and nonprot organizations to oer alterna-
tive solutions. Password less login do not require user to remember complex
letter, number or symbols. Plus, these systems require dierent verication
measures that make it much more dicult for hackers to crack.
2.9 WEB API
An application programming interface (API) is a set of subroutine denitions,
protocols, and tools for building application software. In general terms, it is
a set of clearly dened methods of communication between various software
components. web API is implemented in which we online our whole database
to make it more ecient by purchasing hosting. This application is designed
to automate the request worker process and to ease the resident.
2.10 CONCLUSION
Smart phone applications are necessary feature of todays live and people
prefer to use application for work instead of doing it manually. UI design
of mobile applications is validated through mock up and each module of
application is tested through unit testing and integration testing. To function
any application properly developers use dierent methodologies.
16

Chapter 3
Requirement Specication
In this chapter we are going to discuss about the current trends of the online
workers providing applications and what are the limitation they have. In
addition that, what are the requirement specication to achieve the goal of
our pro ject will also dene in it.
3.1 Existing System
There are dierent mobile applications or websites in entire world that pro-
vide labor online. But if we see Pakistan they all are not really computerized,
they work manually. Mazadooronline.pk is an online extensive quality house-
hold services providing platform based in Karachi – Pakistan. They provide
best experienced, professionally skilled workers that work 100 safety with full
dedication. For acquiring service rst you will select the category of work
(electrician, plumber, painter, carpenter), they provide numerous categories
for worker from which you can easily select. After selecting a proper cate-
gory of service person will call the numbers provided by them in order to get
service. After the avail of services you will pay the bills or as per agreement.
You cannot input anything about your problem; you will dene the problem
to them on phone call. Practical android applications are not available in
Pakistan which helps to get labor online without any diculty.
17

3.2 Application Overview
The application we proposed is going to help the resident of a particular
society to request worker whenever they require any maintenance service.
There are many housing societies providing work services to residents like
electricians, plumbers, carpenters etc. Through this application we are going
to eliminate the call center so resident can directly communicate with workers
and get their services. The main idea of this application is to provide good
services without any headache and improve the living standard of residents.
3.3 Intended Audience
This application mainly targets the people who live in a society and want
maintenance services at their doorstep. A lot of people these days, especially
the young generation of today, use cellphone and want to do everything
through a simple click of a button. Another set of people that we aim to
make this application valuable for, is working single Mother and the elderly.
Some other people also nd it hard to discover workers, invite them to home
and get their services. We intend to make the application useful for as many
people as possible.
3.4 Software Requirement Specication
This section will describe the functional and non-functional requirements of
the society solution applications.
3.4.1 Functional Requirements
Following are the functional requirements of the application.
o Signup/Login page (Password less login)
As soon as the application is launched the new user will ll the signup form
to register himself and existing users will use the login option. There will be
no need to remember the password. Password less login technique is applied
in pro ject.
18

o View User prole
After login the user will be able to see dierent options like post requests,
my prole, settings and locate worker etc.
o Locate Worker
In locate worker page the user rst select the particular type of service or
work he want. And then he will be able to locate all the workers related to
that eld to request for the work.
o Request acceptance/rejection
After posting request, the notication will be send to that particular worker
and user will wait until the request accepted by worker. User can contact the
worker for any further details after the request acceptance. If the resident
wants to change the worker he can have other workers options available for
work and if no worker is available then user have to wait. User has choice to
accept or decline the request.
o Notify User
When a worker accepts the request, the user will be notied about request.
Resident can see the workers prole, the rating he has and also can locate
the worker.
o Prompt user for Worker rating
After two hour of the acceptance of the request, the user will be prompted
to rate the worker who helped him. This rating will add up to the workers
overall rating on his prole.
3.4.2 Non-Functional Requirements
Following are the non-functional requirements of the application:
o Reliability The application must be reliable. Only worker and resident
of a specic society can sign up for that. Response should be relevant to the
request.
o Security Application will be managed by the society manager or Ad-
min, only he can see the resident personal information and allow anyone to
19

sign up as resident or worker. Workers prole will show to the resident and
he can see the information available on the prole about the worker.
o Portability This application is built on an android platform, making
it compatible with numerous cell phones that work on android operating
system.
o Extensibility If updates of the application are available, the user will
be able to update the application.
o Usability The system interface is very easy to understand and consistent
.The user just has some basic reading skills and he can easily understand
about application.
3.5 USE CASE
The use case diagram is visual representation of the event that happens
while the application is running. Use cases are the best description of the
dynamic behavior of the system. Following are the use cases of Society
solution applications.
20

Figure 3.1: Use Case Diagram of Resident
In ?? shows the interaction between the application and the Resident.
First resident will sign up for the application and after verication from the
Admin portal he will allow to login the application. After login resident
can access the application and can post request for the particular service
he need. As a response on his request resident will see the entire workers
available for work at that time of the specic category. He can see workers
prole, rating and after making his decision he will invite worker to his home
for work. After the completion of work, resident can give his feedback on
workers prole about the service.
Login/Sign-up
User will launch the application and see login page, with a link of sign-up
page on it. If he is using the application rst time then he will sign up for
the application.
21

Figure 3.2: Login/Signup use case Diagram of resident
View Workers prole
Resident will see workers prole from which he received response and if he
likes workers rating he will accept his request. Figure 3.3: View worker’s prole use case Diagram
22

Use Case ID UC-1
Title Login/Sign up(Password Less login)
Description Here resident Sign-up for the Application, after verication from Admin he will allow to login to the application.
Primary Actor Resident
Secondary Actor Admin
Pre-Condition Enter name, address, Number. Etc
Post-Condition Login Screen will appear or user prole.
Success scenario User successfully logged in to the system.
Assumption User may rst go to the sign-up page.
Exception User does not belong to the society and will not allow to login.
Flow of Events o Launch the application.
o Go to Login page
o Login to the application or go to
o the Prole Wizard
o Sign-up for the application
o Login to the application
Table 3.1: login/sign-up user use case
Send Request
After viewing the workers prole resident will invite the worker for service
by sending the request. Resident can also contact worker though phone call
now for any query.
23

Use Case ID UC-2
Title View workers prole.
Description Resident get feedback on their request through Admin and see the prole of all workers to whom request had sent.
Primary Actor Resident
Pre-Condition Request is accepted by some worker and resident check workers prole, rating.
Post-Condition Worker will be invited for work.
Success Scenario Worker with good rating accept the request and then he will be invited for work.
Exception Worker with a low prole rating accept the request.
Assumption Worker with a ve star rating on his prole accept the request.
Flow of Events o See feedback.
o Go to the workers prole.
o Check his rating and work previously he done.
Table 3.2: View Worker’s prole user use case
Give Feedback
After acquiring service he will give feedback on workers service through rat-
ing.
24

Figure 3.4: Send request use case Diagram
3.5.1 Use case for worker
In 3.5.1 displays the interaction of application and worker. When worker
logins to the application he will be able to see his prole and rating he has
acquired. when he will receive a request of work from resident, he will see his
prole and respond for the work. After providing service he will get feedback
about his work.
Acquire Feedback
After login he will start getting request of work from residents.
25

Use Case ID UC-3
Title send request
Description Resident invite the worker by sending request for service
Primary Actor Resident
Secondary Actor Worker
Pre-Condition Worker view resident prole and move toward residents home.
Post-Condition Worker will get feedback and rating for his service.
Success Scenario Worker has been successfully invited for work.
Exception Worker doesnt get the invitation because of the network or some other problem.
Assumption Worker gets invitation and may be on his way.
Flow of Events o See workers prole
o Accept request from the worker
o Invite him to home
Table 3.3: send request user use case
Use Case ID UC-4
Title Provide feedback
Description After getting service from worker, resident will give feedback to him.
Primary Actor Resident
Secondary Actor Worker
Pre-Condition Feedback and rating, Time-in and time-out
Post-Condition Worker status will become again available and ratings will be added to his prole.
Success Scenario Worker reach to place and provide service on time.
Exception Worker reach late or dont have his tool required for work.
Assumption Worker reach on time and x the problem.
Flow of Events o Give feedback in the form of stars
o Give comments if you want
Table 3.4: Give Feedback user use case
26

Figure 3.5: Give Feedback use case Diagram
Accept Request
If resident like the prole of worker he will contact worker and send request
to worker for work. When worker will accept the request the notication will
be send to the resident.
27

Figure 3.6: Use Case Diagram of worker
Receive feedback
After providing service resident will give him feedback about his work in the
form of rating and comments.
28

Use Case ID UC-5
Title Acquire Request
Description Here worker receives requests from the resident through Admin if he is free.
Pre-Condition Login to application.
Post-Condition Request is accepted by resident.
Success scenario Received requests for work.
Exception Do not receive request because he accepted another request already.
Assumption Received request and send reply for the work.
Flow of Events o Go to the society request option
o Received request from the resident
Table 3.5: Acquire request use case
Use Case ID UC-6
Title Accept Request
Description Accept Request from the worker for work.
Primary Actor Worker.
Secondary Actor resident
Pre-Condition See resident prole.
Post-Condition Status become not available and take feedback and rating about his work.
Success Scenario Received request for work and moved toward the place.
Exception Resident dont like his prole and invite any other worker for work.
Assumption Received request so may be on his way.
Flow of Events o Receive request from the resident.
o Accept request from the resident.
o Find Address and move toward his home.
Table 3.6: Accept request use case
29

Figure 3.7: Acquire Request use case Diagram
Figure 3.8: Accept Request use case Diagram
30

Figure 3.9: Receive Feedback use case Diagram
Use Case ID UC-7
Title Receive feedback
Description Receive Feedback about the service he provided.
Primary Actor Worker.
Secondary Actor resident.
Pre-Condition Provide service.
Post-Condition Ratings will updated and status will again become Available.
Success Scenario Reached on time provided service and get ve star rating.
Assumption Do not have tools for work or may be do not understand the work.
Flow of Events o Get feedback in the form of stars.
o Receive Comments on your work
Table 3.7: Receive feedback use case
31

Chapter 4
Design
4.1 SYSTEM DESIGN
Systems design is the process of designing the architecture, modules, inter-
faces, and data for a system to satisfy the requirements. This chapter give a
background of the application that how application will work and what are
the processes and modules in the system.
4.1.1 System architecture:
A system architecture the conceptual model that denes the structure and
behavior of any system or pro ject to accomplish goal or to satisfy require-
ments. There are three levels of architecture in proposed system.
32

Figure 4.1: System architecture Diagram
Graphical user interface: Graphical user interface is to interact the
application. In over system interfaces are created using XML so resident and
workers can interact application.
Logic layer: In logic layer back-end of the application is created that
how system will interact with application and database. Java (program-
ming language) coding is used and a web API. Web API is an application
programming interface for a web server. It is a web development concept,
usually limited to a web application’s client-side. web API is implemented in
which we online our whole database to make it more ecient by purchasing
hosting. This application is designed to automate the request worker process
and to ease the resident.
Data layer: In data layer there are shared preferences ad MySQL.
Shared preferences are used to store and retrieve the data in the form of
key values of the system. In this system shared preference is used to store
and retrieve the data (i.e. Password). MySQL is database where data will
be stored of the application.
33

4.1.2 Context Diagram
The context diagram is to show the functionality,
ow and relation with each
other. Figure 4.2: context Diagram
34

4.1.3 Data Flow Diagram(Worker/Resident)
Data
ow diagram is the graphical representation of the
ow of data.
35

Figure 4.3: Worker/Resident Data
ow Diagram36

4.1.4 Entity relation diagram (ERD)
. It shows all the entities and relation with each other of the system. Figure 4.4: ER Diagram
37

4.1.5 Sequence Diagram
A sequence diagram that shows the representation of processes operate with
one another and in which order. It is also called event scenario and event
diagram. In this diagram the sequence of process between resident and em-
ployees is showed. In this diagram sequence of our application is showed
Resident/worker both will login/signup (password less logins) to proceed
further. Resident will send the Request to the worker for the service through
mobile application. That application will be processed and data will be
stored in database. Then Worker will respond to the service to perform the
service. Figure 4.5: Sequence Diagram
In this diagram the sequence of process between resident and employees
is showed.
38

4.1.6 Component Diagram
It denes the dierent components and work of the system. Figure 4.6: component Diagram
The gure shows that there are 3 components of the application. Resi-
dents Workers System output The gure shows that there are 3 components
of the application. Residents Workers System output The work of resident
is to request the service which they want. Workers have to perform that ser-
vice according to the residents request. And application has to act towards
the output.
39

4.1.7 Deployment diagram
Deployment diagram is to show individual hardware and software compo-
nents which are deployed in a system. In below diagram is showing all the
hardware and softwares related to the system i.e. Internet, users (workers),
workers (employees), android application. Figure 4.7: Deployment Diagram
40

4.1.8 System Constraints
This application is only for android users not for IOS users.
Users will be bound to sign up and sign in to use this application.
Only Admin of the society can add and delete the employee.
Complete information like name, address, and contact number of both resi-
dents and workers will be required.
Followings are the dierent modules of Application.
Logo of Application
Login (password less login)
There are two techniques used for login.
Log In via phone
Log In E-mail.
Admin Panel:
Admin will manage the system through add or delete the workers and resi-
dents.
He can check the prole of every resident and worker and can also check the
work rating and work progress of worker.
41

Figure 4.8: Application logo
42

Figure 4.9: Login (password less login)
43

Figure 4.10: Login (password less login)
44

Chapter 5
SYSTEM
IMPLEMENTATION
Implementation is the process in which idea is moved from concept to reality.
Through programming and deployment, the system implementation is real-
ized by technical specication, computer systems and dierent components
of software. The system architecture of society solution application based on
5.1 TOOLS AND TECHNOLOGIES
Tools and technologies which were involved in implementing the pro ject are
dened below
5.1.1 Android studio
Android studio is a tool for the productivity of android application with the
ocial integrated development environment (IDE) 6 It provides more than
one features which enhances the ability of producing brilliant applications.
Such as:
a. Testing tools and frameworks.
b. Fast emulator for debugging the program.
c. GitHub integration to run sample codes.
d. Multiple APK le generation and build variants.
e. A rich layout with drag and drop editing theme support.
45

f. Built in support for Google platform, easier to implement cloud services 8.
5.1.2 Android Software Development kit
Android software development kit requires tools, which help the users in com-
pilation and assembling various applications of android. Java language is the
initial approach for the development of android applications. 5.1.3 Android
Mobile Framework Gives an opportunity to the users to write applications
for android phones by using Android Framework developers. UI designs and
text eld intents are helpful tools. Android application consist of programs
that have useful information for your application.
5.1.3 Development/Environment languages used
Java is an ob ject oriented programming language, which is widely used. This
pro ject has been developed in Java. It supports vast number of libraries
and including wide range of APIs and other tools that are required for the
development of mobile applications e-g Android SDK. Dierent tools are
available like Android-Platform tools, Android emulator, and a version of
Eclipse IDE with the ADT plug-ins, all are provided by the Google in dierent
packages. Java is synchronized, ob ject oriented base and intended to rare
execution predictions 7.
5.1.4 Android Mobile Device
Android working system device, which is a set of software, designed for mobile
phones that have core application and operating systems`6. Smart phone,
e-book reader are considered as Android Mobile Devices.
5.1.5 Application Access Security
The designed system will be deployed for Android Devices. The environment
of the developed system will be secured considering all the security norms.
We worked throughout its security to ensure the quality of the product.
This system will be used by users having the issue of car breakdown and the
mechanics who will be looking forward for the requests from the users for
services. Authorized people with specic identity will have the access to the
system.
46

5.1.6 MySQL Database
SQL databases for storing data in database using SQL query such as SE-
LECT,DELETE,UPDATE etc.SQL query can be expressed as given below;
SELECT attribute from source table name WHERE condition.
47

Chapter 6
SYSTEM TESTING AND
EVALUATION
6.1 Introduction
Software Testing is the methodology to ensure that the system that is being
developed is according to the software requirements. Testing is a process of
planning, preparation and measuring aimed at establishing the characteris-
tics of an information system and demonstrating the dierence between the
actual and the desired outcome. Every module is checked under all the stan-
dards and procedures to ensure the quality level criteria of the product. The
ma jor purpose of software testing is to make the product to meet the quality
standards.
6.2 Software Testing Techniques
There are several testing strategies in regard to the system testing process.
They are divided into four steps:
1. Function Testing
2. Performance Testing
3. Acceptance testing
4. Installation testing
The following are dierent types of testing that should be considered
during System testing:
48

6.2.1 Graphical User Interface (GUI) Testing
Graphical user interface testing is an important aspect of any system. It is
basically how a user interacts with the system. GUI explains user how to
use the system in a sucient manner. It should be easy and simple to use
so every common user could easily and eciently interact with the system.
In the GUI of our application the theme of all the activities is kept constant.
The interface is User-friendly with simple buttons, menus and Text-Views
are designed to perform the required actions without any diculty.
6.2.2 Usability Testing
It is a way to see how it is easy to use the system components by testing it
with respect to real users. Usability is dicult to evaluate and measure as
it is according to user but still can be evaluate using certain parameters like
time to learn, speed of performance, skills to use the software, sub jective sat-
isfaction etc. It is practical implementation of Human Computer Interaction
(HCI). Our System have been used by the user and he/she hardly nd any
bug or error in the system, was easy to handle and felt quite satised using
our system. The feedback was good and satisfactory for us.
6.2.3 Software Performance Testing
Software performance testing mainly focuses on non-functional requirements
() of the system such as performance of the system, reliability and eciency.
It is dicult to cost performance of a new system that performance test
eorts which begin at the inception of the development pro ject. The perfor-
mance of our system was quite satisfactory for the user.
Compatibility Test
Compatibility testing is a process to ensure that system run on dierent
operating systems, to ensures whether the application runs on dierent plat-
forms or not. The present application is developed in Android studio and is
compatible with dierent smart phones and versions of android software that
have android operating system Ice cream sandwich or above running should
easily be able to use this application.
49

Exception Handling
Exception Handling is an important is system evaluation and testing. System
may generate an exception when the user register for the application due to
the wrong format. Also, If the text elds are left empty. Therefore, the
credentials must be entered correctly, in order to avoid the error.
6.2.4 Load Testing
Load testing test the behavior of the system under certain conditions. It is
performed to determine dierent conditions and systems performance. The
GPS system depends on the Internet speed, the speed of 3G/4G connection
or the users network connection. If the data is limited so the system may
not get overload.
6.2.5 Security Testing
Security tests ensure that the security requirements are met or not. The
Android based application will be deployed on android phones. Secured En-
vironment is preferred while developing the application by considering all
the security norms. We test system characteristics related to availability, in-
tegrity, and condentiality of data and services. Security test was conducted
eciently in our system.
6.2.6 Functional Testing
In functional testing Functions are tested by feeding inputs to get outputs.
6.2.6.1 Unit Testing Unit testing is the testing of the every individual program
as they are written. Unit testing took place by testing each component occurs
within the access to our code. IF/Then rules were tested here.
6.2.7 Integration Testing
Integration testing is a process of verication of the interaction between sys-
tem components. Integration testing are mainly of two types such as top-
down or bottom-up, are used with, ordinarily and hierarchically strategies
which are architecture driven, which implies integrating the software compo-
nents or subsystems based on identied functional aspects.
50

6.2.8 System Testing
System testing is concerned with the behavior of a whole system. Testing
of the group of programs. Our system went through system testing and
the output was according to the requirements declared with respect to the
respective input. In this rules were tested in correspondence to the input of
the system.
6.2.9 Acceptance Testing
Acceptance testing is dened as Testing to verify the working of program
for implementation or use. For our system the acceptance testing criteria is
to send work request to the worker and request accept by the worker done
successfully.
6.2.10 Installation Testing
It is the process of ensuring that the application is successfully installed for
the platform on which it was developed. The application is tested on dierent
versions of android and did not oer any issue regarding installation or while
operating on the devices.
6.2.11 Test Cases
Installation of Application
51

Test Case ID TC1
Unit of Test Test for installation of application Successfully.
Function to be tested Open the application Society solution.
Input Application installation from play store.
Expected output Application installed.
Post-Conditions Notication of installation.
output Application installed.
Status Pass
Table 6.1: Installation of Application
The 6.2.111 describe about the installation process of the application from
play store.
52

Test Case ID TC2
Function to tested Test to verify the number or email of the user.
Input Users and worker need to insert number in order to get access to the application.
Pre-Condition User must have credentials.
Expected output System should check if the number is valid and if the user is new then sign-up into the system.
Post-Condition User sign-up into the system.
Output User gets login into the system.
Status Pass
Table 6.2: login verication test case
The 6.2.11 describe about the login process of the application. After in-
stallation user will open the application see two options login through email
or through number. After entering number or email the user will receive a
verication code through email, message or call. After entering that verica-
tion code the user will see the sign-up form which stores other details of user.
53

Figure 6.1: Login Verication
54

Test Case ID TC3
Function to be tested Test to locate nearest worker.
Input Open locate worker by clicking on the locate worker button, it will locate the current position of the worker.
Pre-Conditions GPS signals are visible.
Expected output Shows the current location of the worker.
Post-Conditions GPS signals visibility on the display.
Output Shows current location.
Status Pass
Table 6.3: Locate Worker test case
The ??describe about the process of locate work. On clicking the button
of locate worker user can locate all the workers in colony and on clicking
their icons user can see their information and rating.
55

Figure 6.2: Locate Worker
56

Test Case ID TC4
Function to tested Test to send request to the nearest worker.
Input After locating nearest worker send request by clicking on the man icon.
Pre-Conditions GPS, Wi-Fi or Mobile Data for accurate location estimation.
Expected Output Shows the current location/rating and information of the worker.
Post-Conditions Shows about the status of request (accepted/pending).
Output Shows current location and status of request.
Status Pass.
Table 6.4: Send Request
The 6.2.11 describe about the process of sending request to workers. On
clicking the worker icon resident can send request to the worker present near
his residence.
57

Test Case ID TC5
Function to be tested Test to check about feedback/rating resident will give to worker.
Input User needs to give feedback to the worker about his work.
Pre-Conditions Work should be completed.
Expected Output Feedback submitted and terminates application.
Post-Conditions Application must show the phone menu.
Output Application terminates.
Status Pass
Table 6.5: Feedback and rating
The table 6.5 describe about the process of feedback and rating from the
resident. After nishing work resident will give feedback to the worker in the
form of comments and ratings.
58

Chapter 7
CONCLUSION
In conclusion, the proposed society solution application implemented suc-
cessfully. The system allow users to request worker and get their services by
using this application. This pro ject will promote the online services and we
are able to provide ease of services to the people of society. Providing the
ease to the residents of housing societies is a huge ob jective of this applica-
tion. This system used account kit to register customer which is the best
verication and registration system among all. Account kit system makes
the security of this application stronger by assigning a unique Account ID
to both worker and resident. The application used Card layout for its inter-
face which makes the appearance of the application more interactive. The
application is really ecient and easy to use hence it can be utilized by the
societies to make their maintenance much better.
7.1 Ma jor Accomplishment
One of the ma jor diculty was in applying account kit login system which
give more security to the application. Account kit system verify user on
the basis of their number hence no need of remembering your password.
Another is implementing web API in which we online our whole database to
make it more ecient by purchasing hosting. This application is designed to
automate the request worker process and to ease the resident which we think
we did successfully.
59

7.2 IMPROVEMENTS FOR FUTURE
In future this pro ject can be extended to other societies in order to improve
maintenance services. By consulting certain societies and worker providing
companies this application can be enhanced more with advance feature
60

Bibliography
1 He.D, Chan.S, Guizani.M, Mobile application security: mal-ware threats and defenses, IEEE Wireless Communications , 22,
(2015)138-144.
2 Kieseberg, P., Fruhwirt, P., Schrittwieser, S., Weippl, E. (2015). Security tests for mobile applications Why using TLS/SSL is
not enough.
3 Zhu, Zhenjiang. “Android application development.” (2012)
4 Vesela, V., Krbecek, M. (2016). Development methodologies of mobile applications. 2016
5 http://mazdooronline.pk/
6 Android Developer Tools Essentials: Android Studio to Zipalign
7 M Rozwandowicz , W Zabierowski, A Napieralski(2010). Java language interactive course:
8 https://developer.android.com/studio/index.html
61