Group Id= IT-F17-22 Komal Hafeez 01-235142-026 Sahira Zaheer 01-235142-068 Society solution App Supervisor

Group Id= IT-F17-22

Komal Hafeez 01-235142-026
Sahira Zaheer 01-235142-068

Society solution App

Supervisor: Sameen Arshad

Department of Computer Science
Bahria University, Islamabad
January 2018
Table of Contents
Introduction TOC o “1-3” h z u
Introduction…………………………………………………………………………………………………………….………4
Problem Description …………………………………………………….…………………………………………….….4
Project Objectives……………………………………………………….……..……………………………………………5
Project Scope…………………………………………………………………………………………………………………..5
Benefits…………………………………………………………………………………………………………………………..5
Outline……………………………………………………………………………………………………….…………………5
Literature Review
2.1 Existing System…..…………………………………………………………………………………………………………..6
2.2 Technology………………………………………………………………………………………………………………….….6
2.3 Usage………………………………………………………………………………………………………………………….…..7
2.4 Design and Testing…………………………………………………………………………………………………..………7
2.5 3G/4G Network…………………..………………………………………………………………………………..…………8
2.6 Methodology……………………………………………………………………………………………………………..……8
2.6.1 Agile methodology…………………………………………………………………………………………..……8
2.7 Conclusion………………………………………………………………………………………………………………..…..…..9
Requirement Specifications3.1Existing system…………………………………………………………………………………………………………10
3.2Application Overview……………………………………………………………………………………………….103.3intended Audience…………………………………………………………………………………………………..113.4 Software Reuirement Specification…………………………………………………………………………..11 3.4.1 Functional Requirements……………………………………………………………………………..…11 PAGEREF _Toc493712789 h 3.4.2 Non-Functional Requirements………………………………………………………………………..113.5Use Case…………………………………………………………………………..………………………………………133.6 Use case specification……………………………………………………………………………………………… 16
3.7 Use case for Worker………………………………………………………………………………………….………18
3.71 Use case specification…………………………………………………………………………………….18SYSTEM DESIGN
System Architecture…………………………………………………………………………………….……………22
4.2 System Constraints……………………………………………………………………………………….…………..23
4.3 Context Diagram…………………… ………………………………………………………………………..……….23
4.4 High level diagram……………………………………………………………………………………………..………….24
4.4.1 Data Flow Diagram ……………………………………………………………………………………………….24
4.4.2 Entity Relation Diagram…………………………………………………………………………………………25
4.4.3 Sequence Diagram………………………………..……………………………………………………………….26
4.4.4 Component Diagram………………………………..…………………………………………………….………27
4.4.5 Deployment Diagram……………………………………………………………………………………………..28
References……………………………………………………………………………………………………………………………29

Chapter 1
Introduction
INTRODUCTION
One of the most attractive feature of smartphone is the availability of a large number of apps for users to download and use. User installs and uses these apps for entertainment, financial transactions and for other purposes. The proposed project 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 of society to register a complaint and then that call center make another call to the worker to inform him and give him details about work and resident. This all process consume a lot of time, resources and sometimes resident don’t get good services. Through this application we are going to eliminate the call center so the resident can send direct request to the workers and get their services. 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 through which people can hire worker. In societies of Pakistan there is no concept of this type of app and people use call center system to get any service.

Problem Description
Now a day’s 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 different worker to take care about society in different manners. But because of the call center Residents don’t get their services on time, we will eliminate call center and the residents will be able to contact directly to the worker. Through our project the residents can get all the services of electricians, carpenters, plumbers of the colony just by using mobile app.

Project Objective
The main objective of a project is to design an application that will eliminate call center from society and provide direct communication between residents and the workers. Other objectives are as follows.

Save time of both resident and workers.

Eliminate the priority system (Society management give importance 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.

Project Scope
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 project eliminate call center and allow the resident to contact directly through mobile application to the worker and take services. Residents will be able to take service on time. We have an admin here which allow or accept the registration of both worker/residents and manage security. This application can be extended city wide in future. Application doesn’t have the data of outside worker of colony.

Benefits
Society will be able to keep the track of workers.

From the residents point of view they will take service on time without any priority system in the society.

It will make the workers more active in work.

Society administration can rate every worker through resident’s feedback.

Administration can add or delete any worker.

Outline
The proposed project 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.

Chapter 2
LITERATURE REVIEW
This chapter includes the existing work in the field of android and how android apps became an important measure of everyone’s life. It will explains many studies related to the apps technology, usage and their UI design that attract customer to install apps and use them for their work.

2.1 Existing System
There are different apps or websites in the entire world that provide labor online. But if we see only Pakistan they all are not really computerized, 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% safety with full devotion. For acquiring service first you will select the category of work (electrician, plumber, painter, carpenter), they provide numerous categories of worker from which you can easily select. After selecting a category 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 define the problem to company on phone call. Practical android apps are not available in Pakistan which helps to get labor online without any difficulty.

2.2 Technology
Guizani conducted a study and concluded that smart phone is now playing a major role in people’s life, becoming first choice for sharing information 1. One of the distinct features of smartphones is that they allow users to install and run third-party application programs, which are usually referred to as apps. These applications are officially distributed via online stores referred to as app markets. These markets provide a convenient venue for app developers to distribute their apps and for users to explore and download new apps. This has driven the great development rate of apps in recent years. For example according to a research in September 2012 Google Play Store and Apple App Store had more than 650,000 to 700,000 apps 1. Mostly user prefers Google apps because Google play use Malware detector named bouncer to scan every app before it release, so that user can use apps from their platform without any threat of malware 1.
2.3 Usage
People are able to order households, groceries, books, food and various other items while sitting at home through these apps. Now people also prefer to do financial transaction, bill payments and many other banks work by using android apps provided by apps.Many apps provide communication, entertainment and financial 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. Apps have user interface designs that attract and help people to know how they can use a specific app for their work.
2.4 Design and Testing
Jeo Ligma explains in a study why during the mobile app development cycle, User-Interface (UI) components of the mobile app are typically validated against high-?delity mockups by manually comparing screens from a mockup design to screens developed in the app 2. Mockup assets are usually made using design tools, such as Illustrator, Fireworks, InDesign and Keynote. In our project we will use illustrator/Photoshop as a design tool to make the mockup of our UI design. Mobile app 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. Mobile app designs and requirement changes occur due to customer and technical requirements changing, and often because of a simple lack of understanding in the problem space.
From a developer prospective, unit tests help to manage these changes. Except unit testing, histogram and color-distribution comparing, template and feature matching these techniques also provide additional and adequate solutions to verify that a mobile app UI meets the acceptance criteria provided by the design team 2. We will use unit testing for the application because it help in design validation of UI design and increase customer interest.

2.5 3G/4G Networks
Living in the age where technology and cellphones are a major 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.
2.6 Methodology
According to a study directed by Veronika Vesela it is established that agile methodology is decent for the software development because the methodologies of software development affect the cost of the software development, time and quality of development 4.

2.6.1 Agile methodology
Agile methodology is an approach to project management, typically used in software development. Software is developed in incremental, rapid cycles. 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 cooperation 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 defining resource type and resource dedication. We provide a communication platform for our customer and agile methodologies provide great communication between client and provider.

2.7 CONCLUSION
Smartphone apps are necessary feature of today’s live and people prefer to use app for work instead of doing it manually. UI design of mobile apps is validated through mockup and each module of app is tested through unit testing and integration testing. To function any app properly developers use different methodologies.

CHAPTER 3
REQUIREMENT SPECIFICATION
In this chapter we are going to discuss about the current trends of the online workers providing apps and what are the limitation they have. In addition that, what are the requirement specification to achieve the goal of our project will also define in it.

3.1 Existing System
There are different apps or websites in entire world that provide labor online. But if we see only Pakistan they all are not really computerized, 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% safety with full dedication. For acquiring service first 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 category 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 define the problem to them on phone call. Practical android apps are not available in Pakistan which helps to get labor online without any difficulty.

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 mantainence service. There are many housing societies which have workers 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 mantainence 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 find 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.

Software Requirement Specification
This section will describe the functional and non-functional requirements of the society solution app.

3.4.1 Functional Requirements
Following are the functional requirements of the application.

Signup/Login page
As soon as the application is launched the user will see the select service page on which user select service and post request. If the user has not yet logged in, then user will see the login page which also contains a link to the sign-up page.

Admin verification
When user fill the signup form and click the signup button, the request will go the admin that will verify the request from the database. If the user belongs to the resident or workers of the society he will allow signup otherwise not.

View User profile
After login the user will see different options like post requests, my profile, setting, locate worker etc.

Request page
On his first page he will see a button of request page and goes to the request page in order to post request.

Request Worker
When the user post request system will ask him to select particular type of service and mention what type of problem he is facing. The user also has option of uploading pic related to the service he need.

Request acceptance/rejection
After posting request, the notification will be send to all the available workers and wait until the request accepted by some worker. User can call the worker for any further detail after the request acceptance. If the resident wants to change the worker he can have other worker’s options available for work and if no worker is available then user have to wait.

Notify User
When a worker accepts the request, the user must be notified that the worker is on his way. Resident can see the worker’s profile , the rating he have and also can locate the worker.

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 profile.3.4.2 Non-Functional RequirementsFollowing are the non-functional requirements of the application:
Reliability
The application must be reliable. Only worker and resident of a specific society can sign up for that. Response should be relevant to the request.

Security
Application will be managed by the society manager, only he can see the resident personal information and allow anyone to sign up as resident or worker. Workers profile will show to the resident and he can see the information available on the profile about the worker.

Portability
This application is built on an android platform, making it compatible with numerous cell phones that work on android operating system.

Extensibility
If updates of the application are available, the user will be able to update the application.

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 apps

Figure 3.1: User use case Diagram
In figure 3.1 shows the interaction between the application and the Resident. First resident will sign up for the application and after verification 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 specific category. He can see worker’s profile, 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 worker’s profile about the service.

3.6 User case Specification
Following represent specification of use case diagram of the Worker’s side system. In Use Case table format as shown in figure 3.11, 3.12, 3.13, 3.14, 3.15 and 3.16.

Login/Signup
User will launch the application and see login page, with a link of signup page on it. If he is using the application first time then he will sign up for the application.

Use Case ID UC-1
Title Login/Sign up
Description Here resident Signup for the Application, after verification from Admin he will allow to login to the application.

Primary Actor Resident
Pre-Condition Enter name, address, Number.

Post-Condition Login Screen will appear or user profile.

Success scenario User successfully logged in to the system.

Assumption User may first go to the signup page.

Exception User does not belong to the society and will not allow to login.

Table 3.11
Post Request
After login to the application he will view page have different options including Post Request option. When he goes to the request posting page he will see different categories of workers and other different options.

Use Case ID UC-2
Title Post Request
Description Resident post request for work
Primary Actor Resident
Pre-Condition Post request about work, also mention any detail related to work (upload pic).

Post-Condition Request sends to all the workers of that category.

Success scenario Request has been posted successfully waiting for the reply.

Exception Request goes to the pending or may be user doesn’t mention about work clearly.

Assumption Request posted
Table 3.12
Acquire feedback
When resident post request successful, it will go to the admin database and will notify all the workers of that particular category available for work. Workers will response to the request and their profiles will show to the resident
Use Case ID UC-3
Title Acquire feedback
Description Resident get feedback on their request through admin about the available workers
Primary Actor Resident
Pre-Condition Get feedback from the entire workers available for that particular service.

Post-Condition Worker will get notification about resident request and invitation.

Success Scenario Request will send to all the available worker and the available workers send their feedback on the request
Exception Request rejected because no worker of that specific group is available
Assumption Get a list of worker to whom request has been sent
Table 3.13
View Worker’s profile
Resident will see worker’s profile from which he received response and if he likes worker’s rating he will accept his request.

Use Case ID UC-4
Title View worker’s profile
Description Resident get feedback on their request through admin and see the profile of all workers to whom request had sent.

Primary Actor Resident
Pre-Condition Request is accepted by some worker and resident check worker’s profile, 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 profile rating accept the request
Assumption Worker with a five star rating on his profile accept the request
Table 3.14
Invite worker
After viewing the worker’s profile resident will invite him to his home. Resident can also contact worker though phone call now for any query.

Use Case ID UC-5
Title Invite worker
Description Resident invite worker for work to his home
Primary Actor Resident
Pre-Condition Worker view resident profile and move toward resident’s home.
Post-Condition Worker will get feedback and rating for his service.

Success Scenario Worker has been successfully invited for work.

Exception Worker doesn’t get the invitation because of the network or some other problem.

Assumption Worker gets invitation and may be on his way
Table 3.15
Give Feedback
After acquiring service he will give feedback on worker’s service through rating.

Use Case ID UC-6
Title Provide feedback
Description After getting service from worker, resident will give feedback to him.

Primary Actor Resident
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 profile
Success Scenario Worker reach to place and provide service on time
Exception Worker reach late or don’t have his tool required for work
Assumption Worker reach on time and fix the problem
Table 3.16
FLOW OF EVENTS
The flow of events of a use case contains the most important information derived from use-case modeling work. It should describe the use case’s flow of events clearly enough for an outsider to easily understand it. The flow of events should present what the system does, not how the system is design to perform the required behavior
3.71 Basic Flow of Events of Resident
Login/Signup
Launch the application.

Signup for the application or login to the application.

See different options after signup.

Post Request
Clicked to the request posting option.Get Feedback
See worker’s respond to the request
Invite Worker
Accept request from the worker
Invite him to home
Locate worker
Locate worker and check his location
Get Service
Get maintenance service
Give Feedback
Give feedback in the form of stars
3.8 USE CASE FOR WORKER
In figure 3.2 displays the interaction between application and the worker. When Worker logins to the application he will be able to see his profile and rating he has acquired. When he received a request of work from resident, he will see his profile and respond for work. After providing service he will get feedback about his work which will improve or decline his profile rating.

Figure 3.2: Worker use case Diagram
3.81 Use case Specification
Following represent specification of use case diagram of the Worker’s side system. In Use Case table format as shown in figure 3.21, 3.22, 3.23 and 3.24.

Login / Signup
Worker will open the application and see login page, with a link of signup page on it. If he is using the application first time then he will sign up for the application.

Use Case ID UC-1
Title Login/Sign up
Description Here Worker Signup for the Application, after verification from Admin he will allow login to the application
Primary Actor Worker
Pre-Condition Enter name, Work area, Number, CnicPost-Condition Login Screen will appear or his profile will open
Success scenario Worker successful login to the application
Exception Worker may first go to the signup page
Assumption Worker does not belong to the society or don’t know how to signup
Table 3.21
Acquire Request
After login he will start getting request of work from residents.

Use Case ID UC-2
Title Acquire Request
Description Here worker receives requests from the resident through admin if he is free.

Primary Actor Worker
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.

Table 3.22
Received invitation
When he replied to any request the notification will be send to the resident. If resident likes his profile he will contact him or send invitation to him for work
Use Case ID UC-3
Title Received Invitation
Description Receive Invitation from the resident for work
Primary Actor Worker
Pre-Condition See resident profile
Post-Condition Status become not available and take feedback and rating about his work
Success Scenario Received invitation for work and moved toward the place
Exception Resident don’t like his profile and invite any other worker for work
Assumption Received invitation so may be on his way
Table 3.23
Received Feedback
After providing service resident will give him feedback about his work in the form of rating and comments.

Use Case ID UC-4
Title Received Feedback
Description Receive Feedback about the service he provided
Primary Actor Worker
Pre-Condition Provide service
Post-Condition Ratings will updated and status will again become Available
Success Scenario Reached on time provided service and get five star rating
Exception Do not reach on time
Assumption Do not have tools for work or may be do not understand the work
Table 3.24
3.91 Basic flow of Worker
Login/Signup
Launch the application.

Signup for the application or login to the application.

See different options after signup.

Get Request
Received request from the resident
Send Feedback
Send response to the request
Accept Invitation
Accept Invitation from the Resident
Find Address and move toward his home
Provide Service
Provide maintenance service
Get Feedback
Get feedback in the form of stars
CHAPTER 4
SYSTEM DESIGN
Design is actually a plan or blueprint produced to show the look and functioning of any software, project, building or other object before it made. In this chapter we will discuss about the design of our project in very detail .This chapter will give a technical background of the application that how application will work and what are the process will going to perform in it.

4.1 System architecture:
System design is to define the methodology, work flow, modules, architecture and interfaces of any system or project to accomplish goal or to satisfy requirements.

There are three levels of architecture in proposed system.

4.2 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 residents and workers will be required,
4.3 Context Diagram:
The context diagram is to show the functionality, flow and relation with each other.

4.4 High level diagram:
High level design is the architecture for software development which provide the structure of entire system and its components and their interfaces.

4.4.1 Data Flow Diagram.

4.4.2 Entity relation diagram (ERD).

4.4.3 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 employees is showed.

4.4.4 Component Diagram:
It defines the different components and work of the system.

The figure 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 service according to the resident’s request. And application has to act towards the output.

4.4.5 Deployment diagram
Deployment diagram is to show individual hardware and software components which are deployed in a system.

REFERENCES
He, D., Chan, S., & Guizani, M. (2015). Mobile application security: malware threats and defenses
Kieseberg, P., Fruhwirt, P., Schrittwieser, S., & Weippl, E. (2015). Security tests for mobile applications — Why using TLS/SSL is not enough.

Zhu, Zhenjiang. “Android application development.” (2012)
Vesela, V., & Krbecek, M. (2016). Development methodologies of mobile applications. 2016