GB Khidmat Application

Shah Bahadur

2018-KIU-473

Khalid Hussain

2018-KIU-462

Department of Computer Science, Faculty of Natural

Science and Engineering, KIU, Gilgit.

Oct 2022

1
 GB Khidmat Application

BY

Shah Bahadur

2018-KIU-473

Khalid Hussain

2018-KIU-462

A project submitted in partial fulfillment for the degree requirement of

BS

In

Computer Science

Department of Computer Science, Faculty of Natural science and

Engineering, KIU, Gilgit.

2022
In the Name of Allah Almighty, The Most Beneficent and
The Most Merciful

2
 CERTIFICATE

This is to certify that the project entitled “GB Khidmat App” submitted by Shah
Bahadur (2018-KIU-473) & Khalid Hussain (2018-KIU-462) in fulfillment of the
requirements for the award of Bachelor of Science in Computer sciences at the Karakoram
International University Gilgit is an authentic work carried out by them under my
supervision and guidance. To the best of my knowledge, the matter embodied in the thesis
has not been submitted to any other University/ Institute for award of any Degree or
Diploma.

Thesis Supervisor ____________________

(Mr. Zahidullah)

Chairperson/Chairman/HOD ____________________

(Dr. Zarnawab Khan Swati/HOD)

External Examiner 1 ____________________

(Name of External Examiner)

DEDICATION

3
First and foremost, we devote this humble effort to God Almighty, who is
our originator, our strong foundation, and our source of knowledge and
comprehension. We also dedicate this work to our loving parents, all of
our honorable teachers, all of whom have been a constant source of
encouragement and motivation for us and whose love, warmth, support,
and guidance have enabled us to complete this project .

4
 DECLARATION

We hereby declare that this Project is a presentation of our own work and

that it has not been submitted anywhere for any award. We also warrant,

that we have not received outside materials or involved the external

contributions, if received/involved we shall acknowledge in written

statement to authorities, otherwise we shall be liable for the cancellation

of our project thereby the degree that will be awarded.

Signature Signature

Scholar Name:____________________ Supervisor:______________________

Reg:____________________________ Name:__________________________

Date:____________________________ Date:____________________________

ACKNOWLEDGMENT

5
All praises are for Almighty ALLAH, who blessed us with courage to

copy with the odds of life and enabled us to complete this project work.

We wish to extend our gratitude to the facility of Karakorum

International university and to the teachers of computer science

department in particular invaluable guidance and advice had enable me to

achieve goal during my study at this establishment. we would also like to

admit this project to all of supporters.

We are very grateful to Sir Zahid Ullah (Project Supervisor) for his

innumerable recommendation, and guideline comment and moral support

for complete this project. Our thanks goes to respected supervisor Sir

Zahid Ullah department of computer science who made us self-

confidence to complete task in the time. We have to appreciate those

teachers who worked on our personal skill in last four year.

Thank you.

Shah Bahadur

Khalid Hussain

ABSTRACTION

6
GB Khidmat App is a strong Android Application and a leading provider of hotel

accommodation worldwide, from international chains and all-inclusive resorts and

local hotels of Gilgit Baltistan, together with all the information needed to book the

perfect stay.

On GB Khidmat App users can quickly and efficiently search for hotels and compare

price, quality, rating, location, amenities and availability in real time. GB Khidmat

App offers customers the best value for their hotel, and with Best Price Guarantee.

GB Khidmat App is an instant notification application that allows the communication

between service provider and service receiver. The GB Khidmat app provides a one

stop platform to take and receive all the services. Here in our system message request

are send towards the admin by the hotel managers to register their hotels on our App

and the users send request message for rooms to the desired hotel managers after

selecting the desired room and the hotel manager accept the request of our application

users. When the required information is seen by the Hotel managers then they

communicate with each other. We use a simple GUI (Graphic User Interface) here in

order to provide simple environment to our users.

In modern era of information technology, every person is using mobile phone in any

time, to take proper advantage of this phone for their earning they must install and

used our application. It is very simple and user-friendly application which is easy to

use. Firstly, they make their login accounts like other application then they

communicate to their desire hotel manager. Both the persons communicate with each

other in chat portion, firstly they fix their service price/rate then the service should be

7
provided. If there is any ambiguity/problem in our App, then doesn't matter because

we are here to overcome the problem. There is also a complain portion for our users,

they also block the undesired users. People have the right to know about the safety

records of the companies rely on every day, and we believe that publishing this data

will help us developed with best practices that will prevent serious safety incidents

from occurring in the first place. We will also provide updating to our users for better

improvement in service.

8
GB KHIDMAT

9
Contents

DECLARATION....................................................................................................................5
ACKNOWLEDGMENT........................................................................................................6
ABSTRACTION.....................................................................................................................7
LIST OF ACRONYMS........................................................................................................15
Chapter 1...............................................................................................................................16
INTRODUCTION............................................................................................................16
1.1 Backgrounf of PR SYSTEM..................................................................................16
1.2 Overview..................................................................................................................16
1.3 Aim of Proposed System.........................................................................................16
1.4 Problem Statement of Proposed System................................................................16
1.5 Advantage of proposed system...............................................................................16
1.6 Product Function / Features...................................................................................17
Chapter 2...............................................................................................................................18
REVIEW OF LITERATURE..........................................................................................18
Chapter 3...............................................................................................................................20
REQUIREMENT SPECIFICATION............................................................................20
3.1.Introduction.............................................................................................................20
3.2.Functional requirements........................................................................................20
3.3.None functional requirements................................................................................22
3.3.1.Availability...........................................................................................................22
3.3.2. System resource consumption......................................................................22
3.3.3. Reliability.......................................................................................................23
3.3.4. Understand-ability........................................................................................23
3.3.7. Response time................................................................................................23
3.3.8. Security................................................................................................................23
3.4 Required Tools and Technologies..........................................................................23
3.4.1 Hardware Specification.......................................................................................23
3.4.2 Software Requirement.........................................................................................23
3.4.3 Techonologies......................................................................................................23
Chapter 4...............................................................................................................................24
DESGIN.............................................................................................................................24
4.1 System Architecture................................................................................................24
4.2 Design Methodology................................................................................................24
4.2.1 Agile Development Model...................................................................................24

10
 4.3 Database Constraint...............................................................................................25
4.3.1Flow Chart.............................................................................................................25
4.3.2 Sequence diagram................................................................................................27
4.3.3 Use Case Diagram................................................................................................27
4.3.4 Entity Relationship Diagram...............................................................................29
4.3.5Data Flow Diagram...............................................................................................30
4.3.5.1 Data Flow Diagram :level 0..............................................................................30
4.3.5.2Data Flow Diagram :level 1...............................................................................31
Chapter 5...............................................................................................................................32
SYSTEM IMPLEMENTATION.....................................................................................32
5.1 Database Architecture............................................................................................32
5.2.1 Login Interface.....................................................................................................32
5.2.2 Users Portion........................................................................................................33
5.2.3 Add Services.........................................................................................................33
5.3 Service detail...........................................................................................................33
5.4 Chat..........................................................................................................................33
5.5 Add Alert.................................................................................................................33
Chapter 6...............................................................................................................................34
SYSTEM TESTING AND EVALUATION....................................................................34
6.1 Login........................................................................................................................34
6.2 Create New Account...................................................................................................34
6.3 Services....................................................................................................................36
6.4 Alerts........................................................................................................................37
6.5 Add Contact............................................................................................................38
6.6 Profile.......................................................................................................................39
6.7 New Services............................................................................................................40
6.8 New Alert.................................................................................................................41
6.9 Chat system.............................................................................................................42
6.10 Contacts.................................................................................................................43
6.11 New Service/Alert..................................................................................................44
6.12 System Testing......................................................................................................44
6.12.1 Test Cases..........................................................................................................45
6.12.2 Test Cases..........................................................................................................45
6.12.3 Test Cases..........................................................................................................46
6.12.4 Test Cases..........................................................................................................47

11
 6.12.5 Test Cases..........................................................................................................47
Chapter 7...............................................................................................................................49
CONCLUSION.................................................................................................................49
REFERENCES.............................................................................................................50

12
 List of Figures

FIGURE 4 ENTITY RELATIONSHIP DIAGRAM........................................................................................29

FIGURE 5 DATA FLOW DIAGRAM :LEVEL 0.......................................................................................30
FIGURE 6 DATA FLOW DIAGRAM :LEVEL 1........................................................................................31
FIGURE 6.1 USER LOGIN......................................................................................................................34
FIGURE 6.2 CREATE NEW ACCOUNT...................................................................................................35
FIGURE 6.3 (SERVICES)........................................................................................................................36
FIGURE 6.4 ALERTS..............................................................................................................................37
FIGURE 6.5 ADD CONTACTS................................................................................................................38
FIGURE 6.6 PROFILE............................................................................................................................39
FIGURE 6.7 NEW SERVICES.................................................................................................................40
FIGURE 6.8 NEW ALERT......................................................................................................................41
FIGURE 6.9 CHAT SYSTEM...................................................................................................................42
FIGURE 6.10 CONTACTS.......................................................................................................................43
FIGURE 6.11 NEW SERVICES/ALERTS.................................................................................................44

13
List of Tables

TABLE 3.1 MOBILE APP USER LOGIN ...........................................................................................................16

TABLE 3. 2ADD SERVICE.................................................................................................................................16
TABLE 3. 3 GENERATE ALERT........................................................................................................................17
TABLE 3. 4 CONVERSATION BETWEEN USERS...............................................................................................17
TABLE 3. 5 APP USERS CAN EDIT THEIR SERVICE/ALERT............................................................................17
TABLE 3. 6 DELETE THE SERVICE/ALERT.....................................................................................................18
TABLE 6. 12.1 LOGIN......................................................................................................................................41
TABLE 6.12.2 ADD NEW INSTITUTE.................................................................................................................42
TABLE 6.12. 3 ADD ALERT...............................................................................................................................42
TABLE 6.12. 4 CHAT........................................................................................................................................43
TABLE 6.12. 5 UPLOAD FIELD DATA...............................................................................................................43

14
 LIST OF ACRONYMS
KIU Karakuram international university

GB Gilgit Baltistan

GBKP GB Khidmat App

GUI Graphic user Interface

ERD Entity Relationship Diagram

15
 Chapter 1
INTRODUCTION

1.1 Backgrounf of PR SYSTEM

Project named is “Service Hiring App(SHA),The proposed application will
use by all people of Pakistan as an earning tool according to their occupation.The
proposed project will use many tools and techniques of computer technology and
smart phone for Android application. Programming languages like Java, and
Android ,SDK, will be used to developed application and Fire base database will be
used to store data.

1.2 Overview
We have developed mobile application which is work on the basis of
notification, service receiver and service providers. Here service providers make their
accounts for their services then the notification is send towards all the users of the app
,and the receivers contact with the required service provider in chat portion. Like this
our app will help to facilitate our users..Admin also work on their app by providing
security,and good services for their users .

1.3 Aim of Proposed System

The aim of this system is to provide a service which will help them to spend a
easier life .our app will help equally to all the professionals in Giligit-Baltistan and
also in national level. It is free of cost app all the users freely download and use it.The
intentions of owners of this app are to work on social welfare. .

1.4 Problem Statement of Proposed System

The main problem of current off-line working system is that the people which
are not the employees of any organization are suffering from difficulties to earn a
proper income . To provide a good earning we are introducing a app,which provide
them a proper system to ensure earning. This help them to work with in the whole city
not only in one Muhallah.Their good earning is one click away from them in this app.

1.5 Advantage of proposed system

The system implemented fully functional for Good Earning system .
16
 1. This system will store records of all their earning.
2. Admin will ensure security.
3. User will be feel good by using this app.
4. Mobile user will be easily communicate with each other by using this
app.

1.6 Product Function / Features

1. Login for valid Username and Password
2. Add new users easily.
3. Communication is easily with each other.
4. They can contact with each other
5. Rates are fixed .there are no extra charges.
6. GPS location is also available here in our app.
7. Service providers and service receivers both mentioned their location.
8. Provide new services for new users.
9. Adding remarks about app.
10. View profile of users and their services.

17
 Chapter 2

REVIEW OF LITERATURE

Service Hiring App (SHA) is an instant notification application that allows the
communication between service provider and service receiver.The SHA provides a
one stop platform to take and receive all the services. Here in our system,
notifications are send towards all the users of our application.when the required
notification is seen by the service receiver then they communicate with each other.
We use a simple GUI (Graphic User Interface) here in order to provide simple
environment to our users.

It is very crucial to get proper earning in time by different occupation holding

people, in order to overcome this problem, we are introducing an application. And for
the purpose of helping needy persons, we are introducing Service Hiring App. This
application covers all services i.e., plumber service, blood service, tailor service, taxi
etc.

In modern era of information technology, every person is using mobile phone

in any time, to take proper advantage of this phone for their earning they must install
and used our application. It is very simple and user-friendly application which is easy
to use. Firstly, they make their login accounts like other application then they
communicate to their desire service with suitable person. Both the persons
communicate with each other in chat portion ,firstly they fix their service price/rate
then the service should be provided.. If there is any ambiguity/problem in our App
then doesn't matter because we are here to overcome the problem. There is also a
complain portion for our users ,they also block the undesired users. It represents the
latest in a series of actions in a Service Hiring App has taken to continually improved
the safety of our plate-form for all who use it. People have the right to know about the
safety records of the companies rely on every day, and we believe that publishing this
data will help us developed with best practices that will prevent serious safety
incidents from occurring in the first place.we will also provide updation to our users
for better improvement in service.
18
 The firebase Real Time Data base is a cloud-hosted NoSQL Database.Build
serverless apps.it stores and synchronize data between our users in
realtime.collaborate across device with ease.Release apps confidently. Cloud firestore
enables you to store ,sync and query app data at global scale.Real time synchronizing
make it easy for our users to access their data from any device: web or mobile, and it
helps our users collaborate with one another. Realtime Database ships with with
mobiles and web SDKs so we can build apps without the need of servers. When users
go offfline, the realtime Database SDKs use local cache on the device to serve and
store changes .When the device come online ,the local data is automatically
synchronize. It is also secure ,we use declarative security model to allow access based
on users identity or with pattern matching on our data.Firebase helps us to develop
high quality apps,grow your userbase and earn more money.

Android studio provides the fastest tools for building apps on every android
device. Building without limits .Eliminate tiresome tasks.Build rich
experiences.Optimize code workflow.the android SDK is a software development kit
that includes a comprehensive set of development tools. These include a debugger,
libraries,a handset emulator based on QEMU,documentation,sample code,and
tutorial.Here we use android studio IDE .

19
 Chapter 3
REQUIREMENT SPECIFICATION
3.1.Introduction
The most important and initial phase of any software development is
requirement analysis or requirement specification. The functionalities of any software
or application are highly dependent on this phase because without understanding the
actual requirements one cannot design or developed a software or application. Once
the requirements have been fully understood and analyzed, it will be easy for
developers to design and implement the solution as a functional system or product.

3.2.Functional requirements
Functional requirements specify the behavior or the functionalities of a
system. The functional requirements of this application are given below.

Table 3. 1 :Mobile App User Login

Table 3.1 Mobile App User Login

ID FR1
Title Service Hiring App
Requirement Application should allow login as a user
Source User
Rationale To login
Restrictions and
Risk None
Dependencies None
Priority High

Description:The mobile application should allow user to login with username and
password.
Table 3. 2add service
ID FR2
Title Add service
Requirement Login credentials should be correct
Source Admin

20
 Rationale Access able allover functionalities

Restrictions and None

Risk
Dependencies None
Priority High
Description:The application should allow as User to login and access the dashboard
with correct credential user name and password.

Table 3. 3 generate alert

ID FR3
Title User can generate Alert
Requirement Application should allow to generate new notifications
Source Admin
Rationale
Restrictions and
Risk
Dependencies FR1,FR2
Priority High

Description:Application should allow to generate Alert.

Table 3. 4 conversation between users
ID FR4
Title Users can start chat with each other in chat box.
Requirement

Source Admin
Rationale None
Restrictions and Risk

Dependencies FR1,FR2
Priority High

Description:The application should allow t o chat user with each other.

Table 3. 5 App users can Edit their service/alert

ID FR5
Title Edit service/alert
Requirement Mobile app users can edit their services
Source User
Rationale None

21
Restrictions and User must add service in application
Risk
Dependencies FR2,FR2
Priority High

Description: App users can edit their service

Table 3. 6 Delete the service/alert

ID FR6
Title App users can delete their service/alert
Requirement
Source User
Rationale
Restrictions and
Risk None
Dependencies FR1,FR2
Priority High
Description: App users can also delete their service

3.3.None functional requirements

Non-functional requirements are requirements that specify criteria that can be
used to judge the operation of a system, rather than specific behaviors.

3.3.1.Availability
The application should be available at all times on the user’s
Mobile/tablet, as long as the device in proper working condition.

3.3.2. System resource consumption

Resource consumption of this application should not reach an amount that
render the lepton device unusable. The application should be capable of operating
in the background should the user wish to utilize other application.

3.3.3. Reliability
The application should meet all the functional requirements without any
unexpected behavior.

22
3.3.4. Understand-ability
Application’s User Interface should be easy to understand. The admin and user
should easily understand about how the features of application can access.

3.3.7. Response time

Response time of this application is depending upon the system performance
or speed.

3.3.8. Security
The application is fully secured to use .There is no fear of theft of data or
information.

3.4 Required Tools and Technologies

3.4.1 Hardware Specification
Mobile or Tablet

Andriod version of lollypop or high

RAM 4GB or more.

3.4.2 Software Requirement

Android studio

Firebase Database

3.4.3 Techonologies
Andriod studio

Visual code, Java

Chapter 4
DESGIN
4.1 System Architecture
The system architecture is one of the most important components and it is a
key entity and plays major role in developing an effective system. This chapter is
mainly concerned about the system architecture of service hiring app, its front-end

23
development and back-end development. The front-end of service hiring app is very
user friendly and easy to use.

4.2 Design Methodology

The design methodology is an important part for designing an effective

software, among the various methodologies we have seen different models such as
waterfall model in which the working and design is done in a sequence from top to
bottom and other is an agile model. These models describe about different methods
that how should a model be developed to make an effective system or software that
could be beneficial as well as that could be redesigned in an easy manner by the
system/software developer.

4.2.1 Agile Development Model

Agile model as a software development model is effective design

methodology for any proposed model design as compared to that of other models such
as waterfall model, we had chosen agile development model because of its flexibility
that would be useful if there is any modification to be made in the system. In waterfall
model the software is to be redesigned in any case of modification, because it is a
model in which a sequence has to be followed always, if there’s any mistake found
than in that case we should start from first but in agile development model if any
mistake is found or modification is to be made than we can modify or make correction
of the related error at that specific place and we don’t have to start from the first.

Advantages of Agile development model:

The advantages of agile development model are as under:

i. Due to its flexibility this model is cost effective.

ii. Much effort is not to be made in case of any modification.
iii. Continuous attention to technical excellence and good design.

Iiv. Less time and less cost are consumed in case of any modification.

4.3 Database Constraint

The design constraints are more important things which are used to show the
flow of data of proposed system in a pictorial form as to have an interactive design of
any system. its data entities should be represented in a graphically manner first. The
24
design constraints are shown in this chapter with the help of Flow chart, Sequuence
Diagram,Use case Diagram, ERD (Entity Relationship Diagram) & Data Flow
Diagram(dfd)

4.3.1Flow Chart

The flow chart is an important part of describing a model in manner way with
the help of different symbols used for different functionalities, it is a step by step
procedure to solve a problem. The different shapes used for purpose of start operation
(Oval shape), process operation (rectangle shape), decision making (diamond shape)
and lines to show the flow of data. These symbols help us to understand the flow of
data very easily and a user with less knowledge can also understand the purpose of
drawing a flowchart.

25
Figure 1:Flowchart

26
4.3.2 Sequence diagram

Figure 2:Sequence Diagram

In the above Sequence Diagram, different user can interact to a system and what type
of user operation will perform by user in sequential order.

4.3.3 Use Case Diagram

A use case diagram describe and representation of a user's interaction with the system
that shows the relationship between the user and the different modules in which the
user is involved.

27
Figure 3:Use Case Diagram

28
4.3.4 Entity Relationship Diagram
The ER Diagram is a diagram that is used to illustrate entities and their
relationships. An entities are represented by the rectangular box. The name of the
entity appears in the box, and its attributes appear below. An entity is a representation
of a class instance that is used

to react to class information. We can access and save data from entities in a database.

Figure 4 Entity Relationship Diagram

29
4.3.5Data Flow Diagram
The data flow diagram(DFD) maps out the flow of information for any process
or system which is easily understood.by using different symbols and lines one can
easily understand the flow of our data.

4.3.5.1 Data Flow Diagram :level 0

Figure 5 Data Flow Diagram :Level 0

30
4.3.5.2Data Flow Diagram :level 1

Figure 6 Data Flow DIagram :level 1

31
 Chapter 5
SYSTEM IMPLEMENTATION

5.1 Database Architecture

The service Hiring App data set is created in Firebase Realtime Database.The
Firebase Realtime Database is a cloud-hosted NoSQL database that lets you store and
sync data between users in real time.Cloud Firestores enables users to store ,sync and
query app data at global scale.The firebase Real Time Data base is a cloud-hosted
NoSQL Database.Build serverless apps.it stores and synchronize data between our
users in realtime.collaborate across device with ease.Release apps confidently. Cloud
firestore enables you to store ,sync and query app data at global scale.Realtime
synchronizing make it easy for our users to access their data from any tablet or
mobile, and it helps our users collaborate with one another. Realtime Database ships
with with mobiles and web SDKs so we can build apps without the need of servers.
When users go offline, the realtime Database SDKs use local cache on the device to
serve and store changes .When the device come online ,the local data is automatically
synchronize. It is also secure ,we use declarative security model to allow access based
on users identity or with pattern matching on our data.Firebase helps us to develop
high quality apps,grow your userbase and earn more money.

5.2 Interface Architecture

There are five entities in this application.Each entity has given interface in which
user can work on it.Some of important entities are given blow.

5.2.1 Login Interface

The application of Login is for app user’s need to enter the valid credential
like username and password. In Mobile app dashboard user will view and add service
details and like this they can generate the notification.
32
5.2.2 Users Portion
In this portion we can add new app user from admin dashboard. Here users
can sign up the credentials required by the side .then their accounts are created in our
app.like this their accounts are created next time they can login into the side by their
e-mail and password.

5.2.3 Add Services

In this portion users can add a new services according to their profession, in
their profile and then notification is generated and that notification is send towards all
the users of our app.like this the service receivers of our app read the notification and
then take approach to that profile which the service they need .They chat with each
other in our chat portion and get access to each other.

5.3 Service detail

The type of service which is added by provider ,here they can add the details
of their service like working time,pay,working conditions all the details are provided
here in this section.

5.4 Chat
After login the service providers/receivers can also chat with each other in
order to confirm the service.then they get the address etc where the service is
provided.

5.5 Add Alert

In this section user can add alerts to provide the information that they need the
service .And then that alert is send to all the service providers.

33
 Chapter 6
SYSTEM TESTING AND EVALUATION
6.1 Login
User can login into our app from the following GUI.

Figure 6.1 User Login

A user can login to Application to access dashboard in our system.

34
6.2 Create New Account

Figure 6.2 Create New Account

35
6.3 Services

Figure 6.3 (Services)

36
6.4 Alerts
Here our users can generate new alerts to find service providers.

Figure 6.4 Alerts

37
6.5 Add Contact
Here in contacts users can Add Contacts to their phone.

Figure 6.5 Add Contacts

38
6.6 Profile
Here in this portion users can visit their profiles.they can add their details also
edit and delete their data.

Figure 6.6 Profile

39
6.7 New Services
In this section new services and service details are added to their profiles
regarding to their services.

Figure 6.7 New Services

40
6.8 New Alert
In this section new alerts are added by servitce receivers.

Figure 6.8 New Alert

41
 6.9 Chat system
Here in this section both the service provider/receiver can communicate with each
other.

Figure 6.9 Chat System

42
6.10 Contacts

Figure 6.10 Contacts

43
6.11 New Service/Alert

Figure 6.11 New Services/Alerts

6.12 System Testing

System testing verifies and evaluates that an application performs task as
designed. After successfully completion of unit testing and the integration testing,
this application is tested as complete and unified system.
44
 6.12.1 Test Cases
Software: Service Hiring App Module:Login

Test ID: 1 Test Name: Login

table 6. 12.1 Login

Preconditions Application must be installed on Mobile

1. Fill all the existing field with valid data

Actions 2. Click on Login button

1. Correct user name and password login successfully

Expected Results

Status 1.Pass
Test Description: This test verifies that the user and admin login successfully by
providing his user name and password.

Testing Environment: Mobile

Tested By: Shazia Ali,Shabi ul Hussain

6.12.2 Test Cases

Software: SERVICE HIRING APP Module: add alert

Test ID: 2 Test Name: add alert

table 6.12.2 add new institute

Preconditions Application must be installed on phone

45
 1.Fill all the field with valid data

Actions 2.Click on save button

2. Record Save successfully

Expected Results

Status 1.Pass
Test Description: This test verifies that add service successfully by providing
required information.

Testing Environment: Mobile

Tested By: Shazia Ali,Shabi ul Hussain

6.12.3 Test Cases

Software: Service Hiring App

Module: Add Service

Test ID: 3 Test Name: add service

table 6.12. 3 add alert

Preconditions Application must be installed on mobile
1.Fill all the field with valid data

Actions 2.Click on save button

1. Record Save successfully

Expected Results

Status 1.Pass

Test Description: This test verifies that new service is added successfully by providing
required information.

Testing Environment: mobile

Tested By: Shazia ali, Shabi ul Hussain

6.12.4 Test Cases

Software: service Hiring App Module: Chat
46
 Test ID: 4 Test Name: Chat

table 6.12. 4 Chat

Preconditions Application must be installed on mobile

1.click on chat button

Actions 2.start conversation with required person

1. Message send and received successfully

Expected Results

Status 1.Pass

Test Description: This test verifies that conversation is successfully done betweeen users.

Testing Environment: Mobile

Tested By: Shazia ali, Shabi Ul Hussain

6.12.5 Test Cases

Software: Service Hiring App Module: Edit data

Test ID: 4 Test Name: upload field data from mobile app to webisit

table 6.12. 5 upload field data

Preconditions Application must be installed on mobile

1.Fill all the field with valid data

Actions 2.Click on save button

1. Record Uploaded successfully

Expected Results

Status 1.Pass

Test Description: This test verifies that field data is uploaded successfully from app by
providing required information.
47
Testing Environment: Laptop, PC

Tested By: Shazia ali, shabi ul Hussain

48
 Chapter 7
CONCLUSION
The main problem of current situation is to find an earning for living is very
hectic job.All the day people live to find earning or turn around here and there but
they did not find suitable work and income also.To resolve such problem we
introduced an app to find every kind of work /service , Early people did not do proper
work due to pandemic and now new diseases are attacking humans .In such worst
system there is much more difficult to find a suitable work .

Our App is very useful for ever user whether that is service provider or service
receiver and vice versa.it provides benefit for both the service receiver and service
provider.There is no need to go out and search for work and service .they simply find
the service by opening and clicking on the app.

The App provides very simple user friendly GUI(Graphic User Interface) .
they use the app by simply touching or clicking it.We use Agile model Which is very
good and easy to modify.

49
REFERENCES
[1} www.W3schools.com

[2] https://www.w3schools.com/js/default.asp

[3] https://youtu.be/fis26HvvDII

[4] https://commonsware.com/Android/Android-FINAL.pdf

50
51