DESIGN AND IMPLMENTION OF AN ONLINE SERVICE PROVIDING MOBILE APPLICATION

MAINTAINES STUDENT ID:FMS/0202/17

Table of Contents
CERTIFICATION...................................................................................................................iii
DEDICATION..................................................................................................................iv
ACKNOWLEDGEMENT..................................................................................................v
ABSTRACT......................................................................................................................vi
CHAPTER ONE................................................................................................................1
INTRODUCTION.............................................................................................................1
SCOPE OF STUDY..................................................................................................................2
PROBLEM STATEMENT.................................................................................................3
OBJECTIVES...................................................................................................................3
PURPOSE / GOALS..........................................................................................................3
Purpose.......................................................................................................................................................3

JUSTIFICATION..............................................................................................................4
REVENUE MODEL FOCUS:..................................................................................................4
BETTER DEVICES FRAGMENTATION:..............................................................................4
UNMATCHED SECURITY:....................................................................................................5
BETTER EXPERIENCE & QUALITY:..................................................................................5
FAST SOFTWARE UPDATES FOR YEARS:.........................................................................5
CHAPTER TWO...............................................................................................................6
LITERATURE REVIEW...................................................................................................6
CHAPTER 3......................................................................................................................9
SYSTEM DESIGN AND METHODOLOGY.....................................................................9
3.0 DESIGN METHODOLOGY...............................................................................................9
A software require specification document tells us what a system does and becomes input
to the design process. The purpose of design phase is to produce a solution to
probleEgivenSRS document...............................................................................................9
METHODOLOGY.............................................................................................................9
3.1 PROJECT MANAGEMENT......................................................................................10
3.2 Project Planning and scheduling................................................................................10
3.2.1 Project Development Approach...............................................................................10
3.3 Project Plan...............................................................................................................12
3.4 USER CHARACTERISTICS.....................................................................................12
3.5 USER INTERFACES................................................................................................13
CHAPTER 4....................................................................................................................17

i
SYSTEM ANALYSIS AND IMPLEMENTATION...........................................................17
4.1 Feasibility Study.........................................................................................................17
4.1.1 Technical Feasibility...............................................................................................17
4.1.2 Economical Feasibility............................................................................................17
4.1.3 Operational Feasibility............................................................................................18
4.2 Functions of System...................................................................................................18
4.2.1 Use case Diagram....................................................................................................18
4.3 Data Modeling...........................................................................................................20
4.3.1 E-R Diagram...........................................................................................................20
4.3.2 Activity Diagram.....................................................................................................21
4.3.3 Sequence Diagram..................................................................................................25
4.4 Functional and Behavioral Modeling.........................................................................29
4.4.1 Data Flow Diagram.................................................................................................29
4.5 Database Schema Design...........................................................................................32
4.6 CANVAS....................................................................................................................35
4.6.1 AEIOU SUMMARY................................................................................................35
4.6.2 EMPATHY SUMMARY..........................................................................................36
4.6.3 IDEATION CANVAS..............................................................................................37
IMPLEMENTATION......................................................................................................41
TESTING................................................................................................................................41
TEST CASE............................................................................................................................42
5.3 Important Screenshots.......................................................................................................................43

SAMPLE CODE..............................................................................................................44
CHAPTER 5....................................................................................................................46
CONCLUSION AND FUTURE WORK.................................................................................46
Conclusion........................................................................................................................46
Future work.....................................................................................................................46
References...............................................................................................................................46

ii
 CERTIFICATION

This is to certify that ALHASSAN MUNKAILA with the registration number

FMS/0202/17 carried out this project work. As a final year project in partial

fulfillment of the requirement for the award of A degree in computer science.

----------------------------- -----------------------
DATE
SUPERVISOR

----------------------- ---------------------
DATE
H.O.D

iii
 DEDICATION
I dedicate this project work to God Almighty in heaven for his immense mercies, protection
and direction to me, throughout my stay in school.

iv
 ACKNOWLEDGEMENT
I wish to express my profound gratitude to those who contributed to my Parents Mr. and Mrs.
Alhassan Tuna for their encouragement and advice, may God bless you.
An exceptional gratitude goes to my supervisor Mr. who was always there for us Seth
Gyrimia for his time, assistance and advice to make this project a successful one.
I also extended my gratitude to the good. H.O.D of computer science department in the
person of DR. Edward Bagrie and other lecturers in these department and we pray to God to
see them through.
I will not forget my good friends, well wishers and love ones that in one way or the other
contributed immensely to success of these projects, I ask almighty God to bless you all
Amen.
Finally I am loyal to the great and everlasting Father in Heaven who has been so faithful and
kind in all ramifications of my life and my days in these schools in partial fulfillment of my
degree Award. I say may His name alone be exalted Amen.

v
 ABSTRACT
Application Service Providers offer web-enabled software applications on a subscription
basis revisiting the traditional service bureau model of outsourcing, promising additional
business benefits of economies of scale, increased scope of business applications, and
enterprise application integration. This report is written in 5 chapter with chapter 1 being the
introductory chapter which explains what the entire project is about (Maintaines is an iOS
mobile application that seeks to help people out in their everyday life.
This application is used for record service request for various services like Electric, plumber,
HVAC, AC Sales & Maintenance etc. Customer can book these services and then
administrator can arrange services and keep track the service.) while chapter two is about the
literature review and chapter 3 being the methodology. In this project the water fall method
was used as it is the best method for projects of this sort. And chapter 4 being the system
analysis implementation stage which shows how the system will be implemented and the last
chapter being the conclusion of the whole project.

vi
 CHAPTER ONE
INTRODUCTION
Maintaines is an iOS mobile application that seeks to help people out in their everyday life.

This application is used for record service request for various services like Electric, plumber,

HVAC, AC Sales & Maintenance etc. Customer can book these services and then

administrator can arrange services and keep track the service.

the application seeks to have the following modules

1. User Management:
 User Registration
 User Login
 Forgot User Id
 Forgot Password
 Reset Password
2. Choose Service Type
3. Register Complaint (Same layout for different services) (User can give preferred date
time for technician visit)
4. GPS- Locating user location when Registering Complaint
5. Google Maps- User can input Address and App will locate the location on Google
Maps
6. My Complaints:

 List old complaints (Filters like last x months/resolved/open)

 View Complaints details (Taping of any complaint in above list will show all
details)
 Complaint Lifecycle- Status(Open/Assigned/Appointment
Scheduled/Awaiting customer
 feedback/Resolved/Closed)
 Appointment schedule-Scheduled Time (Date/Time when technician will
arrive. For
 Closed complaints it will be Date/Time Technician closed Complaint)
  No reschedule allowed by user in system
7. Ratings- Rate Technician (For closed complaints. Admin can
configure time window for which rating will be open post complaint
is resolved)
8. Reviews- Write review (For closed complaints. Admin can configure time window for
which rating will be open post complaint is resolved. User can write brief review
when rating)
9. Payment Gateway Integration (2 factor authentication)
10. Sales enquiry
11. System generated email notifications
 Welcome email
 Complaint registration conformation email
 Complaint assignment email
 Appointment scheduled/rescheduled email
 Complaint Quotation email
 Complaint resolution confirmation email
 Password reset confirmation email
 Userid reset confirmation email
 Sales enquiry thanks email
12. Advertisement platforms integration (if there is plan for this)
13. About
14. Help

SCOPE OF STUDY
Maintaines Seeks to solve a good number of problems in our everyday lives as it will make it
very easy for users to find handy man services online to solve their basic needs such as
plumbing, electricals, Ac installers and many more.

2
 PROBLEM STATEMENT
The Maintaines app capitalizes on the convenience factor, one of the greatest constraints
plugging this sector. In the market we targeted, getting a repairman, or a specialist to one’s
house is not a convenient affair – especially when urgent repairs and services are the matter
of concern. While in many developing regions, the labor may be relatively cheap, the story is
quite different in the developed regions in Ghana.

OBJECTIVES
The aim of project is to provide the services to the customers at reasonable rate. Through this
project provide the facilities to the customer such as registration, display profile of service
provider, advertisement, QR code, map navigation etc.
Another Objective was to create a simple-to-use yet effective interface for all age groups. The
idea of the application was as follows:
 Select required services
 Check availability in real time
 Task scheduling with available tasker
 Real-time tracking
 Settle payments online
 Rate and check reviews of service providers
 Get help 24 hours a day.
Another objective behind the creation of this app is to enable service providers have a
platform where they can easily be taxed to solve the needs of users.

PURPOSE / GOALS
Purpose
The purpose of developing this project is mainly online purpose.

I have observed a number limitations in existing systems:

 Existing system is offline.

 Difficult to manage records.
 No time limit for service to be provided.
 No guarantied service.
 Difficult to find paper service provider.
 24 hours service is not available.
 No security.

3
So, our GOAL is to overcome this limitation with following features.

 House hold services easy available.

 To provide house hold services any time.
 Easy online payment.
 Saving of time.
 Make available house hold services through the mobile application.

JUSTIFICATION
Custom mobile apps development – specifically iOS and Android App development – now
plays an important role in the business development strategy of many businesses.

When it comes to custom mobile app development, the one question of whether to choose
iOS or Android is the one that most often encountered by businesses. For many smartphone
users, Apple’s iPhone is considered as one of the best and most popular smartphones in the
mobile market today. Apple has been successfully generating demands for its devices year
after year.

End-users across the world are aware of how robust and easy-to-use iPhones are. Together
with its quality devices, the Apple App store provides a very large pool of quality iPhone
apps that are created to touch upon many aspects of our lives – be it business or
entertainment.

Moreover, there’s also the concern regarding the quality of the iOS app, and Apple is best
known for consistently delivering quality apps with brilliant features. This is also one of the
main reasons influencing the decision of businesses outsourcing the iOS app development.
We examine a number of key reasons why businesses - especially start-ups and small & mid-
sized companies - should choose iOS for their mobile app development requirement:

REVENUE MODEL FOCUS:

Even though Android captures the largest market share and leading the smartphone market in
terms of the number of users[1], Apple iOS is known to produce more App Store revenue (via
in-app purchase or premium pricing) and hardware profits. If mobile app revenue plays a
major factor in your business model, then iOS app development should be the choice for your
business mobile requirement.

BETTER DEVICES FRAGMENTATION:

One issue with the Android platform is that there is a wide range of manufacturers and screen
sizes for Android-based devices. This makes the mobile developer’s job of adapting
interfaces to existing Android devices - with different screen sizes and hardware specs - quite
time-consuming and complicated. iOS, on the other hand, offers a much clearer approach in
this regard.

This is because there is not a wide selection of Apple iPhone (with different screen-size and

4
hardware specs). So, it wouldn’t be a challenge to work out if your app’s interface will fit on
screen.

In addition, to make developers jobs easier, there are special device emulators (e.g. Apple
iOS Simulator) that allow mobile developers to test applications under different iOS versions
and hardware settings.

UNMATCHED SECURITY:

As mentioned in the previous article, for the past few years, Android has been leading in
terms of the number of users when compared to iOS.

However, as Android is an open-source, Android users might sometimes encounter viruses

and other malicious software that can be harmful to their devices. iOS, on the other hand,
leaves practically no loopholes for viruses and malicious hacking software. Apps published
on the Apple App store usually have to go through a thorough vetting process, thus delivering
a perfectly safe app for end-users meeting security standards.

BETTER EXPERIENCE & QUALITY:

Before being officially listed on App Store, iOS apps must undergo a strict vetting process to
meet App store rules as well as quality standards. This is one way to encourage mobile
developers to build high-quality iPhone, iPad, and wearable apps. Apple offers a pleasant
user experience not only in using its devices but also by consistently enforcing high standards
for all the app available on its ecosystem.

Such strict adherence to quality is one factor that differentiates iOS apps from other
competitors. Thus, this is one of the key reasons making businesses decide to outsource iOS
development over Android.

FAST SOFTWARE UPDATES FOR YEARS:

One of the biggest advantages iOS has over Android is in the software updates frequency:
Apple usually supports new iPhones and other iOS devices (iPad and wearable) with iOS new
updates up to five to six years after their initial release. All of those iOS devices are available
for the new updates at the same time.

iOS users will get new iOS features and apps, as well as receiving updates for security
protocols, and patches for both online security threats and flaws that leave the phone
vulnerable to hacking. This helps make your iOS app compatible with many iOS devices
ranging from the newest iPhone to older iPhone models released 5 – 6 years ago.

Android devices, in return – with the exception of Google’s Pixel phones and a handful of
other models that are guaranteed prompt updates— only get the support of new updates two
or three years from the device’s release date.

5
 CHAPTER TWO
LITERATURE REVIEW
Firstly, this chapter shall focus on discussing what is meant by an online service providing
application and how the definition has evolved until the present day. Secondly it shall discuss
the opportunities and limitations related to this application. This chapter also relates two of
the most common models that might be applied to the adoption of technological innovation
and investigates the stages through which technological innovation can happen.

We have observed so many problems which occur in our daily routine, for example the
problem of electricity, if the electricity goes there are many problems occurs in our work, like
we cannot charge the phones, batteries etc. the electric devices which are used in kitchen
cannot be work.

In existing system the whole process is offline and customer can not get proper solution for
the problem. The existing system is not available for 24 hours, so the customer can not get
solution for any time.

We also observe the problem of plumbing at our home, there is one type of plumbing
problem is occur, In that situation what we will do. Firstly we call the plumber and take his
appointment if available or we directly meet him for the appointment to fix the problem. This
process is very time consuming and it is not sure that we get the appropriate solution for our
problem.

We also noticed that if we are going somewhere and our vehicle is get suddenly stop. In this
situation what we will do is that we call the mechanic to fix the problem which occur in our
vehicle, and at one moment if we block in some place where no network is available in our
phone and at that place the rush of traffic is very less so which kind of problem we have to
faced. Firstly We have to find the mechanic and ask him for fix the problem. This process is
very time consuming and it is not sure that we get the solution for the problem because many

6
problems are occurs in that situation like mechanic is busy in other work or his payment is
very high according to the problem etc.

By observing these type of problems we thought that, how can we get the solution of these
type of problem in easy and appropriate way, then we get the idea to developing our android
application and website where people can get any type of services like plumbing, electrical,
electronics, pain, pest control etc.

In this stage of technology our application is very simple and easy to understand.

2.1 Overview

This chapter investigates the factors affecting the acquisition of handyman services. It
discusses the extent of the existing systems to automate the process of finding and acquiring
handyman services. It outlines the technologies that have been used and their deficiencies. It
also focusses on the modern technology and how it will be used to create a model that would
help improve the process of acquiring handyman services within a certain locality.

2.2 FACTORS AFFECTING THE ACQUISITION OF HANDYMAN

SERVICES

According to Greengrass (2006), handyman services are often perceived as small

maintenance jobs, including tasks associated with repairing furniture, installing shelving and
curtains, hanging artwork, changing lighting fixtures, and many other tasks also referred to as
handyman services. In Ghana, handyman services fall under the category of informal sector.
According to United Nations Economic Commission for Africa (2015) report, Ghana has one
of the highest informal sector employments.

LOCATION BASED MOBILE SERVICES

Location based mobile services is the use of mobile devices to be able to provide users with
location sensitive information such that a user can access information based on a suitable or
preferred location. Mobile location-based services make use of the Geographic location of
personal phone or navigational device and use embedded satellite navigation receivers or
network-based technologies like triangulation from the location of the base station

7
transmission cells to be able to determine the position of the device (EGNOS, n.d.).
According to Taiga (2013), context specific information may be delivered to the user by first
establishing the users’ location by using existing technologies and services such as Radio
Frequency identification, Bluetooth, Near Field Communication (NFC), wireless networks
and location-based systems using Global Positioning Services (GPS) technologies. The
information is then used to identify relevant information that is relied to the user using short
messaging service (SMS), Mobile applications and WAP (Wireless Application Protocol).
All these technologies are suitable and applicable in high end devices that support WAP or
are JAVA enabled, but are not readily available or accessible universally to all types of
mobile devices (Azene, 2014 ; TechTarget, 2009

8
 CHAPTER 3
SYSTEM DESIGN AND METHODOLOGY
3.0 DESIGN METHODOLOGY
A software require specification document tells us what a system does and becomes input to
the design process. The purpose of design phase is to produce a solution to probleEgivenSRS
document.

METHODOLOGY
1: STRATEGY, RESEARCH & ANALYSIS
Any mobile app development team needs to prepare a proper strategy for evolving your idea
into a successful app. You must develop an innovative and compelling vision to enhance your
overall enterprise mobility strategy. In this phase, developers have to analyze the app users
with its goals and objectives deeply.
All the essential details related to your apps, like its look, features, and functions, clearly
explain your business app developers. Developers work hard to grab your target audiences’
attention by providing exceptional features to their app.

2: GO THROUGH APPLE’S GUIDELINES

Before designing the iOS app, developers must promote their app on Apple App Store to
make it available for target users. Users can then download the app, post their feedback and
reviews, and give a high star rating. But before promoting your app, it is essential to keep
yourself updated as per Apple’s App Store guidelines.
These policies make developers aware of all safety standards by providing legal and business
formalities regarding the iOS app development process. It prevents developers from spending
extra time on app modifications so that the iOS store can accept your app right from the
beginning.

3: PRIORITIZE THE APP DESIGN

The app designing process is essential, primarily to deliver a flawless business app for the
iOS platform. You can easily access all the information related to Dos and Don’ts tips for
iOS app design on the Apple official website.
Developers ensure that the iOS app they are developing is as per proper optimization to offer
easy navigation and control to users. To target your app users significantly, developers use an
intuitive User Interface and engaging User Experience to generate outstanding design
prototypes.

9
4: PREPARE WIREFRAMES & PROTOTYPES
Mobile app designers can begin the iOS app designing process with sketches on paper.
Wireframes are the digital form of sketches that any iOS app development company can use
to prepare conceptual layouts as per the app’s functional requirements. It is a cost-effective
and straightforward approach to create wireframes for designing app layouts.
Prototypes simulate the user experience and the app’s workflows, but prototype development
is quite a time-consuming process. It also offers early-stage testing of your app’s design and
functionality to identify modifications as per the app’s functionality.
5: APP TESTING
It is essential to test the application before submitting it to the Apple App Store. The app
testing team must ensure that the mobile app is free of bugs and can render super-fast
performance. The iOS app development team must go thoroughly to the app after completing
the app development process.
6: Post Maintenance of the App
Once you are done with the app development and submission process on the iOS store,
updating the app regularly is very important. Developers must update the app regularly, even
after releasing it on the iOS store for download. Make sure that the development team can
support regular maintenance as per iOS updates.
Routine maintenance helps in minimizing several issues that users might face while using
your app. It also makes users enjoy the wonderful experience of your business app.

3.1 PROJECT MANAGEMENT

3.2 Project Planning and scheduling
3.2.1 Project Development Approach
This project is developed using specific software development lifecycle. Software
development approach is best suited for the project depends on the requirement and other
factors. A process model is a development strategy that is used to achieve a goal that satisfies
the requirements abiding by the constraints.

Iterative Water Fall Model

10
Figure 1 : Iterative Waterfall Model

Advantages of Iterative Waterfall Model

 This model is simple and easy to understand and use.

 It is easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
 In this model phases are processed and completed one at a time. Phases do not
overlap.
 Waterfall model works well for smaller projects where requirements are very well
understood.

Analysis:The aim of the requirement analysis is to understand the exact requirements of the
customer and to document them properly.

Requirement gathering and analysis: This activity consists of first gathering the
requirement and then analyzing the gathered requirement.

Requirement Specification: The customer requirement identified during the requirement

gathering and analysis activity are organized into a software requirements specification
(SRS).

Design: The goal of the design phase is to transform the requirements specified in the SRS
document into a structure that is suitable for implementation in some programming language.
In technical, during the design phase the software architecture is derived from the SRS
document.

Traditional Design Approach: The traditional design technique is based on the data flow-
oriented design approach. While using this technique the design phase consists of two
important activities: first a structured analysis of the requirement specification is carried out
where the detailed structure of the problem is examined.

11
Object-oriented design approach: Object-oriented design approach (OOD) is a relatively
new technique. In this technique, various objects that occur in the problem domain and the
solution domain are first identified and the different relationships that exist among these
object are identified.

Code:The purpose of the coding of software development is to translate the software design
into source code. The coding phase is also sometimes called the implementation phase since
the design is implemented into a workable solution in this phase. Each component of the
design is implemented as a program module. The end-product of this phase is a set of
program modules that have been individually tested. To enable the engineers to write good
quality program, every software development organization normally formulates its own
coding standards that suits itself. A coding standard addresses issues such as the standard
ways of laying out the program code, the template for laying out the function and module
headers, commenting guidelines, variables and function naming conventions, the maximum
number of source lines permitted in each module, etc.

Testing:System testing is normally carried out in a planned manner according to a system

test plan document.

Maintenance:Maintenance of a typical software product requires much more effort than the
effort necessary to develop the product itself. Maintenance effort is roughly in 40:60 ratio.

3.3 Project Plan

3.4 USER CHARACTERISTICS

The users of the system include:

1. Admin
2. Service Provider
3. Customer

12
ADMIN

Administrator has maximum privileges to access the system. He maintains user login details,
can assign access rights to a user, can manipulate data and do all the transactions.
Administrator is the super-user of the system.

 He/She can verify service provider and customer.

 He/She manages all the categories of service.
 He/She can take the payment from the customer.
 He/She can add the new advertisement.
 He/She can send notification to the customer and service provider.
 He/She can give order for service instrument to the shopkeeper.
 He/She can also comment to user.

SERVICE PROVIDER:

In this IOS application service provider first does registration and then login after this process
the service provider can view the service which are ordered by user and send
acknowledgement to the user in positive reply. After that service provider get the QR code
which is matched with the QR code of customer.in this application we are providing the map
for the service provider to find his location. The then service provider comes at the place of
customer then he verify the QR code with the customer and then do his work.

CUSTOMER:

In this application the customer first do registration and then do login, after the user search
for the particular service and receiver the list of service available on our android application.
The user then selects the service and request for the service after this process. He/she can get
acknowledgement as reply and get QR code which is unique for every user.

3.5 USER INTERFACES

MAINTAINES: consist of the following interfaces:

 Splash Screen
 User Registration
 User Login
 Forgot User Id
 Forgot Password
 Reset Password
 Service Screen
 Update details

13
 Splash Screen User Registration Tab

14
 Account Information Update Log in Screen

15
 Service Request Form Address Form

16
 CHAPTER 4
SYSTEM ANALYSIS AND IMPLEMENTATION
4.1 Feasibility Study
Feasibility study is carried out when there is a complex problem or opportunity. It is
considered as the primary investigation which emphasizes on “Look before You Loop”
approach to any project .A Feasibility study is undertaken to determine the possibility of
either improving the existing system or developing a completely new system. We are going
to develop the new system which is feasible as our application is very user friendly and easy
to understand.

4.1.1 Technical Feasibility

In this type of study the current technology in used in an organization is checked such as the
existing software, hardware, and personnel staff to determine whether it will work for the
proposed system or completely new ones is to be used. The technology that was important in

developing a new system such as Development tools, back-end database system were
available from within the organization. The proposed system is capable of adding, changing,
enhancing functionality, features etc. The proposed system is capable of handling large
storage of data. The back-end and front-end technology has greater important for providing
an accurate, error-free, frequencies of data to be used.

Our project is technically feasible in terms of current technology. Our project will provide
latest platform like android technology.

4.1.2 Economical Feasibility

For proving that system developed is economical, the economical feasibility study takes place
to check the cost of developing a system against the benefits that it provides. If the cost are
less and benefits are more than we can define our system to be economically developed. User
saves time in searching for a particular product to be purchased by simply few clicks. The
registration process is speedier than the registered manually. The saving of papers as all data
are stored computerized. The record is of free of human errors as there is less chance of
mistakes. The above benefits are in terms of saving time, minimize errors and provide
efficiency in work done.

17
In terms of economical feasibility our application is very reasonable in cost. So application is
economically feasible.

4.1.3 Operational Feasibility

The operational feasibility is concerned with the operability of the system after it has been
installed. That is, some programmer may not like changes in their routine method of work or
has fear that they will lose their peer group .The following areas will have the operational
feasibility in the proposed project

 The organization has approved this system as their working system.

 The User of the system has accepted the proposed system as their new working
system and realized the benefits of it.
 The system will work in a proper way after it has been installed and the installation
process is easy to use.

4.2 Functions of System

The function of the system consist of the Usecase Diagram which represents how the
customer, Service Provider & admin interact with the system.

4.2.1 Use case Diagram

Use case diagrams are a set of use cases, actors and their relationships. They represent the use
case view of a system. A use case represents a particular functionality of a system. So use
case diagram is used to describe the relationships among the functionalities and their
internal/external controllers. These controllers are known as actors.

ADMIN

18
Figure 4.1 Use Case Diagram For Admin

SERVICE PROVIDER

Figure 4.2 Use Case Diagram For Service Provider

CUSTOMER

19
Figure 4.3 Use Case Diagram For Customer

4.3 Data Modeling

It consists of :

 E-R Diagram
 Activity Diagram
 Sequence Diagram

4.3.1 E-R Diagram

An entity-relationship diagram (ERD) is a graphical representation of an information system
that shows the relationship between people, objects, places, concepts or events within that
system. An ERD is a data modeling technique that can help define business processes and can
be used as the foundation for a relation database.

20
Figure 4.4 E-R Diagram

4.3.2 Activity Diagram

Activity diagram describes the flow of control in a system. So it consists of activities and links.
The flow can be sequential, concurrent or branched.

Activities are nothing but the functions of a system. Number of activity diagrams are
prepared to capture the entire flow in a system.

Activity diagrams are used to visualize the flow of controls in a system. This is prepared to
have an idea of how the system will work when executed.

21
LOGIN & REGISTRATION

Figure 4.5 Activity Diagram For Login & Registration

ADMIN

22
Figure 4.6 Activity Diagram For Admin

SERVICE PROVIDER

23
Figure 4.7 Activity Diagram For Service Provider

CUSTOMER

24
Figure 4.8 Activity Diagram For Customer

4.3.3 Sequence Diagram

A sequence diagram is an interaction diagram that shows how processes operate with one
another and in what order. It is a construct of a Message Sequence Chart. A sequence
diagram shows object interactions arranged in time sequence. It depicts the objects and
classes involved in the scenario and the sequence of message exchanged between the objects
needed to carry out the functionality of the scenario. They are typically associated with use
case realization in the Logical View of the system under development.

ADMIN:

25
Figure 4.9 Sequence Diagram For Admin

SERVICE PROVIDER

26
Figure 4.10 Sequence Diagram For Service Provider

CUSTOMER

27
28
Figure 4.11 Sequence Diagram For Customer

4.4 Functional and Behavioral Modeling

It gives the basic description of the functions and the behavior of the system.

4.4.1 Data Flow Diagram

A data flow diagram is a graphical representation of the “flow” of data through an
information system, modeling its process aspects.

A DFD shows what kind of information will be input to and output from the system, where
the data will come from and go to, and where the data will be stored. It does not show
information about the timing of process or information about whether processes will operate
in sequence or in parallel.

DFD DIAGRAM LEVEL 0

Figure 4.12 DFD Diagram Level 0

29
ADMIN

Figure 4.13 DFD Diagram Level 1 For Admin

SERVICE PROVIDER

30
Figure 4.14 DFD Diagram Level 1 For Service Provider

CUSTOMER

31
Figure 4.15 DFD Diagram Level 1 For Customer

4.5 Database Schema Design

ADMIN_LOGIN TABLE :

Table 1: Admin_Login Table

32
 COLUMN DATATYPE INDEXES ALLOW NULLS
USERNAME VARCHAR(50) PRIMARY KEY
PASSWORD VARCHAR(10)

SERVICE_REGISTRATION TABLE :

Table 2: Service_Registration Table

COLUMN DATATYPE INDEXES ALLOW NULLS

S_REGIS_ID INT(10) PRIMARY KEY
S_NAME VARCHAR(50)
ADDRESS VARCHAR(255)
CITY VARCHAR(50)
STATE VARCHAR(50)
MOBILE NO VARCHAR(10)
EMAIL ID VARCHAR(50)
PASSWORD VARCHAR(10)
CAT_ID INT(10) FOREIGN KEY
S_LICENSE VARCHAR(50)
PROFILE_DESCRIPTION VARCHAR(255)
SERVICE_RATE INT(10)
STATUS INT(1)

CUSTOMER_REGISTRATION TABLE :

Table 3: Customer_Registration Table

COLUMN DATA TYPE INDEXES ALLOW NULS

C_REGIS_ID INT(10) PRIMARY KEY
C_NAME VARCHAR(50)
ADDRESS VARCHAR(255)
CITY VARCHAR(50)
STATE VARCHAR(50)
MOBILE_NO VARCHAR(10)
EMAIL_ID VARCHAR(50)
PASSWORD VARCHAR(10)
AADHAR_IMAGE VARCHAR(50)
STATUS INT(1)

ORDER_SERVICE TABLE :

Table 4: Order_Service Table

COLUMN DATA TYPE INDEXES ALLOW NULLS

ORDER_ID INT(10) PRIMARY KEY
C_REGIS_ID INT(10) FOREIGN KEY
S_REGIS_ID INT(10) FOREIGN KEY
DESCRIPTIO INT(10)
N
33
 ADDRESS VARCHAR(255)
CITY VARCHAR(50)
MOBILE_NO VARCHAR(10)
BOOK_DATE DATE
QR CODE VARCHAR(20)
STATUS INT(1)

CATEGORY TABLE :

Table 5: Category Table

COLUMN DATA TYPE INDEXES ALLOW NULLS

CAT_ID INT(10) PRIMARY KEY
CATEGORY VARCHAR(50)
CAT_IMAG VARCHAR(50)
E

REPLY_DETAIL TABLE :

Table 6: Reply_Detail Table

COLUMN DATATYPE INDEXES ALLOW NULLS

REPLY_ID INT(10) PRIMARY
KEY
REPLY_DATE DATE
S_REGIS_ID INT(10) FOREIGN KEY
C_REGIS_ID INT(10) FOREIGN KEY
REPLY_MSG VARCHAR(255)
SENDER_TYPE VARCHAR(50)

FEEDBACK TABLE :

Table 7: Feedback Table

COLUMN DATA TYPE INDEXES ALLOW NULLS

FEEDBACK_ID INT(10) PRIMARY KEY
S_REGIS_ID INT(10) FOREIGN KEY
DESCRIPTION VARCHAR(255)
FEEDBACK_DATE DATE

34
4.6 CANVAS
4.6.1 AEIOU SUMMARY

Description :

Environment

Environment describes the whether and atmospheric of a particular place at a given point of
time.

Interaction

User will be interacting with the application to search the services, select the service,
payment and booking the tickets.

The admin will be interacting with the application for validating the user by checking id
proofs.

Objects

The objects that will be used while getting the whole process done are mobile, internet, ID
proofs. The problem may occur while using these are invalid proofs, mobile number crashing.

Activities

35
The various activities that are performed while running the application are searching the
services, selecting the services, booking the services and doing the payment. The admin will
perform the activities like updating the services and other information.

Users

The users using the application can be customer, admin and service provider the problems
can be there when the admin does not reply to the customers request and service provider is
not ready for the providing the service.

4.6.2 EMPATHY SUMMARY

Description :

Input through AEIOU framework

The AEIOU framework gives us the summary of activities, environment, interaction, objects,
and users involved in the system. The activities performed are uploading the services. The
environment while using the system can be crowdy, noisy, warm. The interaction involved in
the system can among customer and admin, service provider and admin, admin and
shopkeeper, service provider and customer. The objects used in the system are mobile,
laptop, computer and internet connection. The users involved are admin, service provider and
shopkeeper.

Scouted Challenges

36
The challenges faced while using the system are time consuming, no commitment, there is no
fix payment amount for service. Among these problems the exact problem is offline system is
available to overcome these problems.

4.6.3 IDEATION CANVAS

Description :

People

This system is useful and will solve the many problems of the people like customer and
shopkeeper. The users involves in this system are admin, customer, service provider and
shopkeeper.

Activities

The various activities related to our application are search service, booking service, select
services, scanning QR code.

Situation/Context/Location

The situation can be different for different places for example at home the situation of power
cut problem, at institute the situation of circuit fault will occur.

Props/Possible Solution

37
The different props that will be used while creating and using the system are mobile, laptop,
computer, printer and internet connection.

4.6.4 PRODUCT DEVELOPMENT CANVAS

Description :

Purpose

Our application targets at removing the problem of customer like taking the appointment of
service provider with personal meeting with him or by calling, it is very time consuming and
not giving appropriate result which is quite frustrating.

Product Experience

The application is created on android plateform so users can easily download it in their
mobile and can book the services.

Components

The android application can be easily downloaded in the mobile and then can be used for
searching the services and booking the services. The QR code scanner will be used for
validating the user. Internet facility is necessary to run the application.

38
People

The list of people for whom both these application will be useful are customer, admin,
service provider and shopkeeper.

Product Function

Product function deliver the product experience. The function we have included in our system
to meet the customer experience are booking the service through android application, service
cancellation facility.

Product Features

The features that we have included to enhance our system are QR code generating on in the
application as security and the customer checking through QR code scanner for validating the
user.

Customer Revalidation

To discover new user needs to know their reviews and solve their queries related to the
application we have provided feedback and notification facility.

4.6.5 BUISSNESS MODEL CANVAS

Description :

39
Customer Segments:

Customer Segment block is to present the list of Persons, organized by Customer Segment. If
you have more than one segment. It is always recommended to prioritize them.

Examples:

 Industry: problem occurs related to machinery at industry at that time our system is
used.
 Collages: When the electronics parts may damage at collages our system can be used.
 Home: when furniture related problem occurs, our system may used.
 School: Our system is used when the problem of short circuit occurs at school.
 Hospital: when the problem occurs like electricity loss at hospitals our system can be
used.
 Company: our system is used when some problem like pipeline block and leakage
problem is occurred.

Value Propositions

The Value Propositions business block aims at providing answers to the following questions:

 What value do we deliver to the customer?

 Which one of our customer’s problems are we helping to solve?
 What bundles of products and services are we offering to each Customer Segment?
 Which customer needs are we satisfying?

Examples:

 Apply for the service: In this system user can apply for the services.
 View the services: User can view the services when he or she will apply for the
services.

Channels

This business block comprises of a list of important Channels, linked to Personas or

Segments if they differ substantially. Make notes on what steps are relevant for each-
promotion, sales, service, etc. This business block provides answers to the following
questions:

 Through which Channels do our Customer Segments want to be reached?

 How are we reaching them now?
 How are our Channels integrated?
 Which ones work best?
 Which ones are most cost-efficient?
 How are we integrating them with customer routines?

Examples:

 Website: user can also use the website of our system for applying for the services.

40
  Smart phone application: our system is android base so the user use this app with
the help of smart phone.
 Internet: user will be able to use this app with the help of internet.

Customer Relationship

The customer relationship business block answers the following questions:

 What type of relationship does each of our Customer Segments expect us to establish
and maintain with them?
 Which ones have we established?
 How are they integrated with the rest of our business model?
 How costly are they?

Examples:

 Email: user can also give the feedback through email or user can communicate with
the system.
 Chat Support: user can communicate with the operator with the help of chat support.
 Feedback: user can give feedback related to services.

Revenue Streams

Revenue Streams block of Business Model Canvas aims at answering the following
questions:

 For what value are our customers really willing to pay?

 What do they currently pay?
 How are they currently paying?
 How would they prefer to pay?

IMPLEMENTATION
TESTING

Software testing is a critical element of software quality Assurance and represents the
ultimate review of specification, design and code generation. Testing is an internal part of any
system or project. If a system is implemented without being tested it may lead to an
erroneous working and dissatisfaction on part of the customer. It will also prove disastrous to
the reputation of the organization or the person who developed the system and lead to loss in
business.

Keeping all these things in view, we left no stone unturned in testing our systems. It was
tested keeping in view the different possibilities on part of the user. As human beings are
prone to commit errors under different working conditions, we had to keep our vigil on
different possibilities that can occur on part of the user.

The system was tested for validation, functional implementation and its navigation.

1. Validation Testing:

41
The user must login to the system with his/her unique login name and password. The user
must enter all mandatory fields. If he/she fails to do so then a warning message is issued.

2. Functional Testing:

The entire system was divided into sub modules. Adding/Updating of user Information in the
database is done.

3. Navigational Testing:

The system was tested so that all the pages are properly accessible with their respective links.

To uncover the errors in the system we have done testing as follows:

1. Input Checking:

In this phase we tested the validation process only. When users enter the data in the given text
box or in grids, proper input format is checked. If entry required numeric data user is
bounded to enter only numeric. If text (alphanumeric)data, then user is bounded to enter text
data only also check for null values. Like this all entries of all input areas are tested.

2. Condition Testing:

Condition testing is a method that exercises the logical condition contained in program
module. All relational statements were individually examined and tested. Extreme case
values are given for testing.

3. Loop Testing:

Loops are cornerstones for the vast majorities of all implementation in software. Each loop is
examined separately. Its end point values were given and terminating condition each case
tested.

4. Output Testing:

First step of testing is checking how friendly it is. Then its accuracy is checked, that is
whether it can be present all relevant information, it can report missing less, data etc.

5. Acceptance Testing:

In this type we run the system live data by actual user.

TEST CASE

42
Test Test case Input Expected Output Actual Output Observation
name
case

id
1 User login Email id Homepage open Homepage open Pass
and
Password
2 User login Email id Homepage open Error message Fail
and “Incorrect Email
Password id or password”.
3. User Status 1.Active Access to When verified Pass
homepage through Database

2.Inactive
4. User Status 1.Active Access to When not verified Fail
homepage through Database

2.Inactive
5 Apply for Apply for Successfully Apply for the Pass
the services the services apply for the services
services successful
6 Apply for Apply for unsuccessfully Apply for the Fail
the services the services apply for the services
services unsuccessful
7 Generate Generate the Successfully Generated details Pass
the customer generate the success
customer details details
details
8 Generate Generate the unsuccessfully Generated details Fail
the customer generate the unsuccessful
customer details details
details

5.3 Important Screenshots

IOS APPLICATION

 HomePage
 Service Provider Registration Page
 Customer Registration Page:
 Login Page:
 Manage Category
 Verify Customer

43
  Booking Detail
 Chat
 View Services Page
 Order Form
 Booking Detail Report
 Mobile Message
 Payment page

SAMPLE CODE
Registration page:

#import <UIKit/UIKit.h>
#import "SlideNavigationContorllerAnimator.h"
#import <CoreText/CoreText.h>
@class ShowAlert;
@class AppDelegate;

@interface signUpViewController :
UIViewController<SlideNavigationContorllerAnimator,UIScrollViewDelegate
,UITextFieldDelegate>
{

AppDelegate *appdelegate;
ShowAlert *alert;
IBOutlet UIScrollView *scrollView;
IBOutlet UITextField *nameTextField;
IBOutlet UITextField *emailTextField;
IBOutlet UITextField *phoneTextField;
IBOutlet UITextField *passwordTextField;
IBOutlet UITextField *rePasswordTextField;
IBOutlet UITextField *dateOfBirthTextField;
IBOutlet UIButton *dateOfBirthButton;
IBOutlet UITextField *referralCodeTextField;
IBOutlet UIButton *checkBoxButton;
IBOutlet UILabel *termsLabel;
IBOutlet UILabel *andConditionsLabel;
IBOutlet UIButton *termsButton;
IBOutlet UIButton *conditionsButton;
IBOutlet UIButton *createAccountButton;
IBOutlet UIButton *loginButton;
IBOutlet UIButton *signUpButton;

// for date Picker

UIDatePicker *datePicker;
UIView *subView;
UIToolbar *toolbar;
BOOL isPickerLaunced;
NSString *pickerValue;

44
 bool textFieldflag;
bool userIdflag;

UIAlertView *signupAlert;
IBOutlet UIView *bottomView;
}
- (IBAction)dateOfBirthButtonClicked:(id)sender;
- (IBAction)checkBoxButtonClicked:(id)sender;
- (IBAction)termsButtonClicked:(id)sender;
- (IBAction)conditionsButtonClicked:(id)sender;
- (IBAction)createAccountButtonClicked:(id)sender;
- (IBAction)loginButtonClicked:(id)sender;
- (IBAction)signUpButtonClicked:(id)sender;
@end

LOGIN PAGE :

#import <UIKit/UIKit.h>
#import "SlideNavigationContorllerAnimator.h"
#import "Reachability.h"
@class ShowAlert;
@class AppDelegate;

@interface loginViewController :
UIViewController<SlideNavigationContorllerAnimator,UIScrollViewDelegate
,UITextFieldDelegate>
{

AppDelegate *appdelegate;
ShowAlert *alert;
IBOutlet UIButton *loginButton;
IBOutlet UIButton *signUpButton;
IBOutlet UITextField *emailTextField;
IBOutlet UITextField *passwordTextField;
IBOutlet UIButton *forgotPasswordButton;

NSUserDefaults *standardUserDefaults;

bool userIdflag;

// for forgot Password

bool forgotEmailFlag;

// to make background invisible or blurry

UIView *dimView;

IBOutlet UIScrollView *scrollView;

IBOutlet UIView *bottomView;

45
}
- (IBAction)forgotPasswordButtonClicked:(id)sender;

- (IBAction)loginButtonClicked:(id)sender;
- (IBAction)signUpButtonClicked:(id)sender;
@end

CHAPTER 5
CONCLUSION AND FUTURE WORK
Conclusion
An IOS application and website is developed which provide online service booking. The IOS
application and website will provide a good user friendly interface for booking the services. It
will give us security by generating QR code in the android application and website itself. It
will provide notification so that the user keeps updated every time. It will provide the
comments on feedback. Generating the QR code in the application itself will be more
secured. No need of carrying print outs for proofs as the data is stored in the application
itself. If the QR code is available with the user, the service provider will validate it by
matching the QR code and if it is not available with the user, then that user is not valid.

Future work
In future we developed an android application and website in which we will put a map
navigation for the service provider for find the location of user and the advertisement of
shopkeeper where the shopkeeper can sell his equipment.

References
Websites:

[1] : https://www.canvs.in/

[2] : https://en.wikipedia.org/wiki/Service_%28economics

[3] : https://openfuel.org/

[4] : http://hservices.ca/

[5]: www.helpguru.com

[6] : www.justdial.com

[7] : https://patents.google.com/

46
Books :

For making UML diagrams:

[1] : Software Engineering by Roger S. Pressman

[2] : PL/SQL- by Steven Feuerstein

[3]: Software Engineering by Mrs. Anuradha A. Puntambekar

47