Download as pdf or txt
Download as pdf or txt
You are on page 1of 132

PROJECT REPORT ON

SHERBIMET

SUBMITED TO

OF

DIPLOMA IN COMPUTER ENGINEERING

IN YEAR 2020-2021

BY

Sr. No. Enrollment No. Name


1 186400307088 Vidit Pujara
2 186400307091 Parth Rana
3 186400307098 Shubham Sagar

ii
R. C. Technical Institute
Sola, Ahmedabad - 60

CERTIFICATE

This is to certify that this work of PROJECT-1 Subject & 3350706 Subject Code
of 6th Sem with title: SHERBIMET represents the work of the following
students for the fulfillment of the Certificate of Diploma in Computer
Engineering at R. C. Technical Institute Sola, Ahmedabad - 60, Gujarat, during
the academic year 2 0 2 0 - 2 0 2 1 and the work is completed and found
satisfactory.

Sr. No. Enroll No. Name


1 186400307088 Vidit Pujara

2 186400307091 Parth Rana

3 186400307098 Shubham Sagar

Submitted to: Mahendra Solanki

Lecturer, Computer Engg. Dept. RCTI

Head of Computer Dept. RCTI

iii
ACKNOWLEDGEMENT

We are very thankful to Mr. Mahendra Solanki for his effective


guidance, inspiration and valuable support and help in providing us all
information regarding the project and offering valuable suggestion from
time for getting the desired information. Thanks to all those from whose
valuable suggestion and comments the text has benefited so much. We
express us gratitude towards all faculty member’s specially us internal
guide Mr. Mahendra Solanki who have guided and directed us at every
moment addition to specially thanks to all other facilities of collage for
their help & guidance that I have been receiving from last 2 semester.

We are grateful to Mr. Sanjay Dhami, HOD of computer


Department for allowing us to take project of RCTI. We are Sincerely
thankful to him time to time and valuable guidance during the training
period. We are also thankful to my family members to provide mentally
strength during my project preparation.

Once Again, I Would Like to Thank Everyone for Helping us for


our Project SHERBIMET.

Regards,
Vidit Pujara (186400307088)
Parth Rana (186400307091)

Shubham Sagar (186400307098)

iv
ABSTRACT

People are facing problems in hiring helpers. Specially migrants,


Bachelors, Students, Working Couple. Generally, People does not trust,
Anonymous workers or they don’t get satisfaction with their work.
Sometimes there is a fear of security. There are
variations in prices.

To overcome above problems, we have come with an Android build


Application based on hiring of house helpers like maids, cook, baby sitter,
elderly care. Here all workers will be verified and trusted. Here the helpers
can get a platform to work with right wages. People can hire according to
their comfort. Now both husband and wife can go for their work with a
free mind (without any tension), students who live far from their home
can study peacefully.

v
LIST OF FIGURES
SR. FIGURE PAGE
NO NO.

1 ITREAIVE MODEL 11

2 GANTT CHART 15

3 ADMIN ACTIVITY DIAGRAM 33

4 CLIENT ACTIVITY DIAGRAM 34

5 WORKER ACTIVITY DIAGRAM 35

6 LOGIN & REGISTER ACTIVITY 36


DIAGRAM

7 ADMIN USE CASE DIAGRAM 37

8 WORKER USE CASE DIAGRAM 38

9 CLIENT USE CASE DIAGRAM 39

10 ER DIAGRAM 46

11 LEVEL – 0 DFD 47

12 ADMIN LEVEL – 1 DFD 48

13 CLIENT LEVEL – 1 DFD 49

14 WORKER LEVEL – 1 DFD 50

vi
LIST OF TABLES

SR. TABLES PAGE


NO NO.

1 ADMIN_TABLE 41

2 SERVICES 41

3 USER_MASTER 42

4 PACKAGE_MASTER 42

5 WORKER_MASTER 43

6 LOGIN_INFO 43

7 BOOKING 44

8 FEEDBACK 44

9 PAYMENTS 45

10 WORKER_PAYOUT 45

vii
Index
1.0 Introduction……………………………………………………………..01
1.1 Project Summary & Profile…………………………………………..02
1.2 Purpose……………………………………………………………….03
1.3 Scope & Objectives…………………………………………………..05
1.4 Technologies…………………………………………………………06
2.0 Project Management……………………………………………………09
2.1 Project Planning……………………………………………………...10
2.1.1 Project Development Approach & Planning…………………..10

2.1.2 Roles and Responsibilities……………………………………..14


2.2 Project Scheduling…………………………………………………...15
2.3 Risk Management…………………………………………………....15
3.0 System Requirements Study……………….…………………………..19
3.1 Existing System / Scenario………………………………………......20
3.2 Proposed System………………………..……………………………23
3.2.1 Modules & Features In the New System……………………...23
3.2.2 User Characteristics…………………………...……………....26
3.2.3 Hardware & Software Requirements...………………………..27
4.0 System Analysis……………………………………………………...….29
4.1 Feasibility Study……………………………………………………...30
4.2 System Activity Diagram………………………………………….…33
4.3 Use Case Diagram……………………………………………….…...37
5.0 System Design………………………………………………..................40
5.1 Database Design/Data Structure Design…………………………….41
5.1.1 Data Dictionary………………………………………………..41
5.1.2 ER Diagram…………………………………………………....46
5.1.3 Data Flow Diagram……………………………………………47
viii
6.0 Implementation…..………...………………………………..................51
6.1 Implementation Environment……………………………………….52

6.2 SS of Forms, Report, Interface……………..……………………….53


6.2.1 User App……………………………………..………………..53
5.1.2 Worker App………………………………...………………....69
5.1.3 Admin Panel………………………………………..…………77

7.0 Testing………..…..………...………………………………..................109
7.1 Testing Plan And Strategy………………………………………….110

7.2 Testing Methods………….....……………..……………………….113

7.3 Testing Cases…………….....……………..……………………….115


8.0 Limitations and Future Enhancements…………………..................117
8.1 Limitations………………...………………………………………118

8.1 Future Enhancements……...………………………………………119

9.0 Conclusion……………………………..…………………..................120
9.1 Conclusion………………...………………………………………121

10.0 References………………………………………………..................122
10.1 Websites………………...………………………………………123

ix
SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 1
Introduction

RCTI (CE) 1|Page


SHERBIMET 186400307088 | 186400307091 | 186400307098

1.1 PROJECT SUMMARY AND PROFILE

➢ “Sherbimet” is an android application which is used to book maid and cook


online.
➢ Here one who want to get the service can register under client profile and one
who wants to provide service can register under worker profile. Admin will
have all the rights to change or update profile.

➢ User can register by providing required information and by verifying the


mobile number. On the other hand, workers need to provide all the required
information and need to verify the mobile number, documents and has to do
provide a certificate of police verification.

➢ Whichever service will the user need he/she can apply for it.

➢ The be according to the work. If he/she wants to hire for cleaning then he/she
need to enter the area of place in sq. feet. Or he/she need pricing will to hire
for cooking then he/she need to enter number of members and what they
prefer to eat.
➢ Then according to their input system will send request to workers by matching
profiles with user input and whoever will accept the request system will
allocate worker/s to the client.

➢ At any time, the user doesn’t like the work he/she can apply for replacement.
Within 48 hours system will allocate another worker to them.

➢ User has to make payments monthly, quarterly, half-year, yearly in the app
only through their credit card, debit card, net banking, Paytm, etc. He/she can
get the invoice through mail as well as in the app also.

RCTI (CE) 2|Page


SHERBIMET 186400307088 | 186400307091 | 186400307098

➢ Workers will be paid monthly according to their work done in their bank
accounts directly.
➢ User can give their feedbacks in the worker's profile.
➢ User can even refer a worker and can apply for his/her profile.

➢ Workers can also get their workplace in the app and get navigated to that
place.

➢ Workers can also apply for their profile through our call service.

1.2 PURPOSE

TRUST:

The main purpose of this application is to provide a service on which everyone


can trust. From teenagers to old age people everyone needs a maid or cook.
But in todays world a big question arises ‘Whom to trust?’ as we have heard
so many cases of fraud, theft, murder, etc done by their servants. So, people
are afraid of hiring them. And in many societies’ maids are not allowed to
enter the premise only. In hiring maid also, the trust issue arises. Here our app
“Sherbimet” solves the problem as we strictly ask for police verification
before appointing them.

MIGRANTS:

As India is a developing country, we do not have all the facilities in every city.
So, people migrant from one place to another place for different reasons like
for studies, job, business, better living, etc. But when they came to metro
cities, they face some problems as they are new here. They face major
RCTI (CE) 3|Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

difficulties in finding a house and finding a maid. The problem of finding a


house has been reduce as there are many websites and application who
provide real estate services. Finding a maid is still an issue. If they search in
neighbourhood, they may get a limited option. And from that may not get the
satisfied too. But what else they can to as they are not familiar with the city or
area.

For that our application “Sherbimet” can provide them multiple option and if
they don’t like the service, they can request for new maid also.

SAVING TIME:

In cities like Mumbai where people don’t have time to breathe, they face
difficulty in hiring maids as it takes too much time. Mumbai, where people
comes from all corners of the country. Here they can hire maid through their
mobile phones by just searching their need on “Sherbimet” and done. What
they need to do is just some clicks and everything will be on their fingertips.

WORKING PARENTS:

As the time has changed, today both husband and wife work together and
some of them have babies too. But to manage the expenses the have to work.
For their babies they can find trusted baby sitters on “Sherbimet”. As
described above all workers are verified.

RCTI (CE) 4|Page


SHERBIMET 186400307088 | 186400307091 | 186400307098

1.3 SCOPE & OBJECTIVES

SCOPE
➢ The scope defines the boundaries of the proposed system.

➢ Our project scope is limited to android only.

➢ The payment mode is limited to online only.


➢ This application is for selected cities in India for now.

➢ To be a part of our app user need to fill the registration form.

➢ Unregistered user can only access prices.

OBJECTIVE
➢ We want to provide a quality service to our users.

➢ In future we will expand our application in other cities also.

➢ We want to generate revenue from this app.

➢ We want to increase employment.


➢ We want to introduce a secure system in the market.

➢ In future will develop the app for iOS user too.


➢ To give user a user-friendly and interactive system.

➢ Clients’ time can be saved.

➢ Clients can get a proper worker according to his/her expertise.

RCTI (CE) 5|Page


SHERBIMET 186400307088 | 186400307091 | 186400307098

1.4 TECHNOLOGIES (TECHNOLOGIES REQUIRED TO


DEVELOP THE PROJECT)

Front End: Android (Java), PHP

Back End: My SQL, PHP

Platform: Windows 10

Tools: Android Studio 4.0, NetBeans 12.3

JAVA

➢ Java is a general-purpose computer-programming language that is


concurrent, class-based, object-oriented and specifically designed to have as
few implementation dependencies as possible.

➢ It is intended to let application developers "write once, run anywhere"


meaning that compiled Java code can run on all platforms that support Java
without the need for recompilation.
➢ Java applications are typically compiled to byte code that can run
on any Java virtual
➢ Java Virtual Macine (JVM) regardless of computer architecture.

➢ Java is one of the most popular programming languages in use, particularly


for client-server web applications, with a reported 9 million developers.

RCTI (CE) 6|Page


SHERBIMET 186400307088 | 186400307091 | 186400307098

➢ Java was originally developed by James Gosling at Sun Microsystems


(which has since been acquired by Oracle Corporation) and released
in 1995 as a core component of Sun Microsystems' Java platform.

➢ The language derives much of its syntax from C and C++, but it has fewer
low-level facilities than either of them.

ANDROID

➢ Android is a mobile operating system based on the Linux kernel developed


by Google.
➢ Android is an open platform and its open source.

➢ Android is designed primarily for touchscreen mobile devices such as


smartphones and tablet computers, with a specialized user interface for
television, car, and wristwatches.

➢ Android is the most widely used operating system on a mobile phone today.

➢ The selling of android OS is higher than the windows, iOS, and Mac
operating systems.

➢ Android source code is released by Google under open source licenses.

RCTI (CE) 7|Page


SHERBIMET 186400307088 | 186400307091 | 186400307098

MY SQL

➢ My SQL is an open-source relational database management


system (RDBMS).

➢ A relational database organizes data into one or more data tables in which data
types may be related to each other.

➢ SQL is a language programmer use to create, modify and extract data from
the relational database, as well as control user access to the database.

➢ MySQL has stand-alone clients that allow users to interact directly with a
MySQL database using SQL, but more often MySQL is used with other
programs to implement applications that need relational database capability.

PHP

➢ PHP is a general-purpose scripting language especially suited to web


development.

➢ PHP code is usually processed on a web server by a


PHP interpreter implemented as a module, a daemon or as a Common
Gateway Interface (CGI) executable.
➢ Additionally, PHP can be used for many programming tasks outside of the
web context, such as standalone graphical applications and
robotic drone control.

RCTI (CE) 8|Page


SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 2
PROJECT MANAGEMENT

RCTI (CE) 9|Page


SHERBIMET 186400307088 | 186400307091 | 186400307098

2.1 PROJECT PLANNING

Project planning is one of the major tasks that are performed during the
development of the project. Using project planning, the task of finding the size
of the project is done and with that total amount of time and cost required for
the project is calculated.

The approach to develop the software system should follow some systematic
way i.e. Software Development Life Cycle. Using the upper-level analysis
and the environment of the project, Which life cycle model would fit properly
for this project was judged. After deciding the proper software development
lifecycle model, the development of this project according to the model was
done.

2.1.1 PROJECT DEVELOPMENT APPROACH AND


PLANNING
➢ How to choose the right approach for a project in a large topic. The
methodology you choose can depend on many things, including the structure
and location of the project team, the technologies being used on the project,
and the degree to which collaboration is a part of the company’s culture.

➢ The project is done based on the decided development life cycle model. We
decide on the Iterative Waterfall Model for our application.

RCTI (CE) 10 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

ITERATIVE WATERFALL MODEL

In a practical software development project, the “Classical Waterfall Model”


is hard to use. So, the Iterative waterfall model can be thought of as
incorporating the necessary changes to the classical waterfall model to make
it usable in practical software development projects. It is almost the same as
the classical waterfall model except some changes are made to increase the
efficiency of software development.

“The iterative waterfall model provides feedback paths from every phase to
its preceding phases, which is the main difference from the classical waterfall
model.”

Feedback paths introduced by the iterative waterfall model are shown in the
figure below.

RCTI (CE) 11 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

When errors are detected at some later phase, these feedback paths allow
correcting errors committed by programmers during some phases. The
feedback paths allow the phase to be reworked in which errors are committed
and these changes are reflected in the later phases. But there is no feedback
path to the stage – feasibility study, because once a project has been taken, it
does not give up the project easily. It is good to detect errors in the same phase
in which they are committed. It reduces the effort and time required to correct
the errors.

Phase Containment of Errors: The principle of detecting errors as close to


their points of commitment as possible is known as Phase containment of
errors.

ADVANTAGES OF ITERATIVE WATERFALL MODEL

➢ Feedback Path: In the classical waterfall model, there are no feedback paths,
so there is no mechanism for error correction. But in iterative waterfall model
feedback path from one phase to its preceding phase allows correcting the
errors that are committed and these changes are reflected in the later phases.

➢ Simple: The Iterative waterfall model is very simple to understand and use.
That’s why it is one of the most widely used software development models.

RCTI (CE) 12 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

DRAWBACKS OF ITERATIVE WATERFALL MODEL

➢ Difficult to incorporate change requests: The major drawback of the


iterative waterfall model is that all the requirements must be clearly stated
before starting the development phase. Customers may change requirements
after some time, but the iterative waterfall model does not leave any scope to
incorporate change requests that are made after the development phase starts.
➢ Incremental delivery not supported: In the iterative waterfall model, the
full software is completely developed and tested before delivery to the
customer. There is no scope for any intermediate delivery. So, customers must
wait long for getting the software.

➢ Overlapping of phases not supported: Iterative waterfall model assumes


that one phase can start after completion of the previous phase,
but in real projects, phases may overlap to reduce the effort and time needed
to complete the project.
➢ Risk handling not supported: Projects may suffer from various types of
risks. But the Iterative waterfall model has no mechanism for risk handling.

➢ Limited customer interactions: Customer interaction occurs at the start of


the project at the time of requirement gathering and at project completion at
the time of software delivery. These fewer interactions with the customers
may lead to many problems as the finally developed software may differ from
the customers’ actual requirements.

RCTI (CE) 13 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

2.1.2 ROLES AND RESPONSIBILITIES


Our system was decomposed into different modules and we are responsible
persons for analysis, design, and implementation, documentation along with
testing.

Activity Roles & Responsibility

Vidit Pujara
Requirement Collection Parth Rana
Shubham Sagar

Vidit Pujara
Analysis Parth Rana
Shubham Sagar

Vidit Pujara
Design Parth Rana
Shubham Sagar

Vidit Pujara
Implementation Parth Rana
Shubham Sagar

RCTI (CE) 14 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

2.2 PROJECT SCHEDULING


Project scheduling consists of identifying the tasks needed to complete the
project, determine the dependency among different tasks plan the starting and
ending dates for various tasks and determines the chain of tasks that determine
the duration of projecting scheduling we decide the order in which to do the
same.

2.3 RISK MANAGEMENT

RISK IDENTIFICATION
Risk is an inevitable concept of the softer project and it mainly concerns future
happenings. We want to produce a well working system; therefore, we must
consider all the possible defects and unexpected conditions.

Following the possible risk of our project are:

➢ Human risk: Potential losses due to a human error, done willingly or


unconsciously
➢ IT/System risk: Potential losses due to system failures and programming
errors

RCTI (CE) 15 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

➢ Processes risk: Potential losses due to improper information processing,


leaking or hacking of information and inaccuracy of data processing.

RISK ANALYSIS
Risk analysis is a review of the risks associated with an event or action. It is
applied to projects, information technology, security issues and any action
where risks may be analysed on a quantitative and qualitative basis.

RISK PLANNING
A risk is a list of all risks that threaten the project, along with a plan to mitigate
some or all those risks. If there were no uncertainty, then every project plan
would be accurate, and every project would go off without a hitch. Usually at
the most inconvenient times. The risk plan is an insurance policy against
uncertainty.

Into higher the mitigation response is the action plan to eliminate, reduce or
minimize the probability of a risk event occurring and or the impact of the
project risk event should it occur.

Here are several reasons why risks may occur within a typical project:
➢ Changing circumstances, updates, and new developments.

➢ Detailed elaboration and further refinement of the overall project planning


process.
➢ Changes to the constraints (like scope, time and budget).

➢ Changes to the initial project documentation (like Project Charter) resulted


from further discussions and negotiations with the stakeholders.

RCTI (CE) 16 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

All risk management processes follow the same basic steps, although
sometimes different jargon is used to describe these steps. Together these 5
risk management process steps combine to deliver a simple and effective risk
management process.

Step 1: Identify the Risk. You and your team uncover, recognize and describe
risks that might affect your project or its outcomes. There are several
techniques you can use to find project risks. During this step, you start to
prepare your Project Risk Register.

Step 2: Analyse the risk. Once risks are identified you determine the
likelihood and consequence of each risk. You develop an understanding of the
nature of the risk and its potential to affect project goals and objectives. This
information is also input to your Project Risk Register.

Step 3: Evaluate or Rank the Risk. You evaluate or rank the risk by
determining the risk magnitude, which is the combination of likelihood and
consequence. You make decisions about whether the risk is acceptable or
whether it is serious enough to warrant treatment. These risk rankings are also
added to your Project Risk Register.

Step 4: Treat the Risk. This is also referred to as Risk Response Planning.
During this step, you assess your highest ranked risks and set out a plan to
treat or modify these risks to achieve acceptable risk levels. How can you
minimize the probability of the negative risks as well as enhancing the
opportunities? You create risk mitigation strategies, preventive plans and
contingency plans in this step. And you add the risk treatment measures for
the highest ranking or most serious risks to your Project Risk Register.
RCTI (CE) 17 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Step 5: Monitor and Review the risk. This is the step where you take your
Project Risk Register and use it to monitor, track and review risks.

RCTI (CE) 18 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 3
SYSTEM REQUIREMENTS
STUDY

RCTI (CE) 19 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

3.1 EXISTING SYSTEM / SCENARIO

EXISTING SYSTEM
➢ Existing system is partially offline.
➢ Existing system is complex to understand.
➢ In current system is difficult to manage data.
➢ There is no security provide in current system.
➢ You cannot order for services any time. There is a fix time for booking
services.

➢ If the service provider in the offline market is not someone who has been
appointed for years for a specific task, it might get difficult for you to trust
them, while in online people would be able to choose a trusted professional
by taking a dip at the reviews and ratings which makes it much easier for them
to have decision that they won’t regret almost every time.

➢ In Existing system, you will not get every type of service provider at same
place which makes it frustrating for customer to get specific task done easily
and quickly.

➢ In offline market, there is very big concern is if someone is coming to your


home for the first time, it is very difficult to judge someone.

RCTI (CE) 20 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

SCENARIO

➢ The new system is completely Online process-based system that’s why


customers can get the services at their doorsteps only. They do not have to go
outside and do not waste their time to find services providers.
➢ The new system provides more security and authorized because we recruit
service providers after police verification and also check their background as
well.

➢ The new system reduce time and reduce cost for customers. It is more efficient
for customer.

➢ New system is more user-friendly and more interactive as well.


➢ In new system a medium providing the users with multiple option both locally
and those ready to visit their areas for providing services. Because new system
has more Availability of service providers.

➢ The new system empowers customers to connect only with authorized service
providers and pick the right one based on the feedback from existing
customers and other factors.
➢ In new system customers rely upon the service providers and feel free to leave
their place with the service provider while performing their other tasks
because the Reliability of service providers is more than existing system.
➢ In new system customers get the pre-priced home services, that’s why they do
not get more confusion for fees of services they pay.

➢ The reviews and ratings help to get an idea of the quality of works the services
providers offer and thus, go with online home service provide that matches
your needs and expectations.

➢ In new system we provide a majority home-related service options at the same


platform. This makes it convenient for someone to look into different services
RCTI (CE) 21 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

without jumping from one platform to another. Because in new system we


have significant convenience.
➢ In new system, we have Considerable flexibility therefore while the customers
get an opportunity to enjoy multiple services at the same platform, the service
provides obtain the freedom to choose their own working hours and
conditions.
➢ In new system we have Simplified appointment scheduling, therefore
customers have more the opportunity to check their calendar and fix an
appointment for the job accordingly. This way, they can manage that the task
is fulfilled on the day of their availability or the day with better optimal
solutions.

➢ In new system we have Ease of payment, therefore customers can get more
efficient way of payment than offline market. Customer have more efficient
way for manage billing and payment transactions.

➢ With ease of payment feature the service providers an escape from the stress
of the payment and avails their best efforts into their responsibilities. This
feature is also more helpful for the customers to pay in different forms, apart
from cash.

➢ By this new system we provide a platform to the service providers to connect


with a greater audience and transform their service offering into a wholesome
business.

RCTI (CE) 22 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

3.2 PROPOSED SYSTEM

The main purpose of the system is to provide a better service to the people on
which the can relay. They can get same quality of service any location (if the
area is serviceable).

3.2.1 MODULES AND FEATURES IN THE SYSTEM

R1: Registration
User needs to register to use features of the application.

R.1.1: Click on Registration


input: "Registration" button.
output: Form will open of register detail.
R.1.2: Register details
input: Fill up details as required.
output: If input filled true then successfully register.

R2: Login
User needs to login to use the service. As the features will be different for
workers and client.

R.2.1: Click on the login


input: "login" button.
output: Will be asked by the system for username and password.
R.2.2: Fill up the form and click
input: Type username and password.
output: Login successful.

RCTI (CE) 23 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

R3: Search

R3.1: Find Service

input: type your service or service category


output: display available services.

R3.2: After Selecting service


Input: enter required details need for quoting the service.

Output: display the quate.

R4: Payments

R4.1: Select plan

Input: select plan as monthly/quarterly/yearly.


Output: display the amount.

R4.2: Select Mode of payment

Input: select mode of payment from the available options.


Output: redirect to payment gateway.

R4.3: Confirmation of payment.


invoice. If failed display error message.

R5: Complaints
R5.1: Select worker

Input: select the worker who was allocated to them.


Output: Complaint category selection will pop-up.

RCTI (CE) 24 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

R5.2: Describe Complaint

Input: Give a detail information of problem.


Output: Complaint number will be generated.

R6: Feedback

R6.1: User can give a feedback about the service on worker’s profile.
Input: give star rating and describe.
Output: Thank you message will be displayed.

R7: Booking
R7.1: After selecting service user can book workers.

Input: User needs to select time range.

Output: worker will be informed.

R8: Profile
R8.1: User can view workers profile and documents.
Input: User can select on worker profile to view.
Output: Worker’s profile will open and display the information experience
and documents.

R9: My Accounts
R9.1: User or Worker can view and update their profile.
RCTI (CE) 25 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

R9.1: User Profile update

Input: Can update address, cuisine, house details, family members, visiting
hours.
Output: Data will be updated in database and will reflect on user’s profile.

R9.2: Worker Profile Update


Input: can update their skills, working hours, distance he/she can travel, area
to served.

Output: Data will be updated in database and will reflect on user’s profile.

R10: Payment
Input: Select the date of payment.

Output: Invoice will be displayed and can be downloaded.

3.2.2 USER CHARACTERISTICS

ADMIN:
Admin is a user who manages the whole system. He has the maximum rights.
He can Prove or reject worker profile, and can manage their bookings too.
Admin also look after the compliments registered by users. He also manages
the payments.

CLIENT:
Client is a person who want the service he needs to verify only his mobile
number to register. He can easily book service from the app anytime.

RCTI (CE) 26 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

WORKERS:
The people who needs work can register as a worker. They need to provide
some documents and police verification, to register.

RCTI (CE) 27 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

3.2.3 HARDWARE & SOFTWARE REQUIREMENTS

➢ Admin Hardware Requirements:


Processor: Intel Core i3 7th Gen. / Amd Ryzen 3
Hard Disk Space: Min. 10GB
RAM: Min. 4GB

➢ Admin Software Requirements:


Operating System: Any Windows OS
User Interface: Java, Android
Programming Language: Android
IDE/ Workbench: Android Studio
Database: SQLite Database

➢ Client Software Requirements:


Operating System: Android
Mobile Version: Android
Android Version: Minimum 4.3.2
Android Version (Name): Ice-cream Sandwich

➢ Client Hardware Requirements:


Mobile Storage Space: 10MB-100MB
RAM: Minimum 3GB
Mobile Compatibility: Android

RCTI (CE) 28 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 4
SYSTEM ANALYSIS

RCTI (CE) 29 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

4.1 FEASIBILITY STUDY

Feasibility is defined as the practical extent to which a project can be


performed successfully.
To evaluate feasibility, a feasibility study is performed, which determines
whether the solution considered to accomplish the requirements is practical
and workable in the software. Information such as resource availability, cost
estimation for software development, benefits of the software to the
organization after It is developed and cost to be incurred on its maintenance
are considered during the feasibility study. The objective of the feasibility
study is to establish the reasons for developing the software that is acceptable
to users, adaptable to change and conformable to established standards.
Various other objectives of feasibility study are listed below.

➢ To analysis whether the software will meet organizational requirements

➢ To determine whether the software can be implemented using the current


technology and within the specified budget and schedule

➢ To determine whether the software can be integrated with other existing


software.

TECHNICAL FEASIBILITY:

RCTI (CE) 30 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Technical feasibility assesses the current resources (such as hardware and


software) and technology, which are required to accomplish user
requirements in the software within the allocated time and budget. For this,
the software development team ascertains whether the current resources and
technology can be upgraded or added in the software to accomplish specified
user requirements. Technical feasibility also performs the following tasks.

➢ Analyses the technical skills and capabilities of the software development


team members
➢ Determines whether the relevant technology is stable and established

➢ Ascertains that the technology chosen for software development has many
users so that they can be consulted when problems arise, or improvements are
required.

OPERATIONAL FEASIBILITY:

Operational feasibility assesses the extent to which the required software


performs a series of steps to solve business problems and user requirements.
This feasibility is dependent on human resources (software development
team) and involves visualizing whether the software will operate after it is
developed and be operative once it is installed. Operational feasibility also
performs the following tasks.

➢ Determines whether the problems anticipated in user requirements are of high


priority
➢ Determines whether the solution suggested by the software development team
is acceptable
RCTI (CE) 31 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

➢ Analyses whether users will adapt to a new software.

➢ Determines whether the organization is satisfied by the alternative solutions


proposed by the software development team.

RCTI (CE) 32 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

4.2 SYSTEM ACTIVITY DIAGRAM

ADMIN ACTIVITY DIAGRAM:

Fig 4.1 Admin Activity Diagram

RCTI (CE) 33 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

CLIENT ACTIVITY DIAGRAM:

Fig 4.2 Client Activity Diagram


RCTI (CE) 34 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

WORKER ACTIVITY DIAGRAM:

Fig 4.3 Worker Activity Diagram

RCTI (CE) 35 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

LOGIN AND REGISTER ACTIVITY DIAGRAM

Fig 4.4 Login and Register Activity Diagram

RCTI (CE) 36 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

4.3 USE CASE DIAGRAM:


ADMIN USE CASE DIAGRAM

Fig 4.5 Admin Use Case Diagram

RCTI (CE) 37 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

WORKER USE CASE DIAGRAM

Fig 4.6 Worker Use Case Diagram

RCTI (CE) 38 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

CLIENT USE CASE DIAGRAM

Fig 4.7 Client Use Case Diagram

RCTI (CE) 39 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 5
SYSTEM DESIGN

RCTI (CE) 40 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

5.1 DATABASE DESIGN/DATA STRUCTURE DESIGN

5.1.1 DATA DICTIONARY (TABLES AND


RELATIONSHIP)

• ADMIN_TABLE

Column Name Datatype (Size) Constraint

admin_id Varchar (10) Primary Key

admin_name Varchar (20) Not Null

admin_email Varchar (30) Unique

admin_password Varchar (25) Not Null

• SERRVICES

Column Name Datatype (Size) Constraint

Service_id Varchar (10) Primary Key

Service_name Varchar (15) Unique

Service_photo_path Varchar (100) Not Null

RCTI (CE) 41 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

• USER_MASTER

Column Name Datatype (Size) Constraint

User_id Varchar (10) Primary Key

User_name Varchar (20) Not Null

User_gender Varchar (6) Not Null

User_email Varchar (30) Unique

User_mobile Varchar (10) Unique

User_address Varchar (50) Not Null

• PACKAGE_MASTER

Column Name Datatype (Size) Constraint

Package_id Varchar (10) Primary Key

Package_name Varchar (15) Unique

Package_details Varchar (30)

Package_price Number (7,2) Not Null

Package_duration Varchar (10) Not Null

RCTI (CE) 42 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

• WORKER_MASTER

Column Name Datatype (Size) Constraint

Worker_id Varchar (10) Primary Key

Worker_name Varchar (20) Not Null

Service_id Varchar (10) Foreign Key

Worker_photo Varchar (100) Not Null

Worker_gender Varchar (6) Not Null

Worker_email Varchar (30) Unique

Worker_mobile Varchar (10) Unique

Worker_documents Varchar (100) Not Null

Worker_details Varchar (100)

Worker_Expertise Varchar (15)

• LOGIN_INFO
Column Name Datatype (Size) Constraint

Email Varchar (30) Foreign Key

Password Varchar (25) Foreign Key

RCTI (CE) 43 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

• BOOKING

Column Name Datatype (Size) Constraint

Booking_id Varchar (10) Primary Key

Worker_id Varchar (10) Foreign Key

Package_id Varchar (10) Foreign Key

Booking_date Varchar (15) Not Null

Booking_amount Number (7,2) Not Null

Booking_status Varchar (10) Not Null

• FEEDBACK

Column Name Datatype (Size) Constraint

Feedback_id Varchar (10) Primary Key

Worker_id Varchar (10) Foreign Key

User_id Varchar (10) Foreign Key

Feedback_details Varchar (200) Not Null

Feedback_date Varchar (15) Not Null

RCTI (CE) 44 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

• PAYMENT

Column Name Datatype (Size) Constraint

Payment_id Varchar (10) Primary Key

Booking_id Varchar (10) Foreign Key

Payment_amount Number (7,2) Not Null

Payment_details Varchar (20)

Payment_method Varchar (15) Not Null

Payment_date Varchar (15) Not Null

Payment_status Varchar (10) Not Null

• WORKER_PAYOUT

Column Name Datatype (Size) Constraint

Worker_payout_id Varchar (10) Primary Key

Worker_payout_amount Number (7,2) Not Null

Worker_id Varchar (10) Foreign Key

Worker_payout_date Varchar (15) Not Null

RCTI (CE) 45 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

5.1.2 ER DIAGRAM

Fig 5.1 ER Diagram

RCTI (CE) 46 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

5.1.3 DATA FLOW DIAGRAM (CONTEXT DIAGRAM, 0-


LEVEL AND 1-LEVEL)

LEVEL – 0 DFD

Fig 5.2 Level – 0 DFD

RCTI (CE) 47 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

ADMIN LEVEL -1 DFD

Fig 5.3 Admin Level – 1 DFD

RCTI (CE) 48 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

CLIENT LEVEL – 1 DFD

Fig 5.4 Client Level – 1 DFD

RCTI (CE) 49 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

WORKER LEVEL – 1 DFD

Fig 5.5 Worker Level – 1 DFD

RCTI (CE) 50 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 6
Implementation

RCTI (CE) 51 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

6.1 IMPLIMENTATION ENVIRONMENT


Basically, we worked on the ANDROID STUDIO which led us to the completion of our Application.

• GUI vs Non-GUI:
➢ This application has both GUI and Non-GUI based Implementation
Environment.
➢ As we all know that every system has GUI to interact with user, and,
our System also have Non-GUI environment.

• Single vs Multiuser:

➢ Our project has multi user Environment.

➢ One is Admin and others are the one who uses the application or
you can say society members.

RCTI (CE) 52 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

6.2 SCREENSHOTS OF FORMS, REPORT &


INTERFACE

USER APP:

RCTI (CE) 53 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 54 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 55 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 56 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 57 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 58 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 59 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 60 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 61 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 62 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 63 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 64 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 65 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 66 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 67 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 68 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

WORKER APP:

RCTI (CE) 69 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 70 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 71 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 72 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 73 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 74 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 75 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

RCTI (CE) 76 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

ADMIN PANEL:
• Forms and layout

Login Page

Login Email Error


RCTI (CE) 77 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Login Password Error

Wrong Username or Password Popup

RCTI (CE) 78 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Login Successful Popup

Dashboard

RCTI (CE) 79 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Service Page

Add Data Service Page

RCTI (CE) 80 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Service Page Error

Display Data Service Page

RCTI (CE) 81 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Edit Service Page

Add Subservice Page

RCTI (CE) 82 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Data Subservice Page

Add Subservice Page Error

RCTI (CE) 83 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Display Data Subservice Page

Edit Subservice Page

RCTI (CE) 84 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Package Page

Add Data Package Page

RCTI (CE) 85 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Package Page Error

Display Data Package Page

RCTI (CE) 86 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Edit Package Page

Add User Page

RCTI (CE) 87 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Data User Page

Add User Page Error

RCTI (CE) 88 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Display Data User Page

Edit User Page

RCTI (CE) 89 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Worker Page

Add Data Worker Page

RCTI (CE) 90 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Worker Page Error

Display Data Worker Page

RCTI (CE) 91 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Edit Worker Page

Display Booking List Data Page

RCTI (CE) 92 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Display Feedback List Data Page

Add City Page

RCTI (CE) 93 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Data City Page

Add City Page Error

RCTI (CE) 94 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Display Data City Page

Edit City Page

RCTI (CE) 95 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Area Page

Add Data Area Page

RCTI (CE) 96 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Area Page Error

Display Data Area Page

RCTI (CE) 97 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Edit Area Page

Add Pincode Page

RCTI (CE) 98 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Data Pincode Page

Add Pincode Page Error

RCTI (CE) 99 | P a g e
SHERBIMET 186400307088 | 186400307091 | 186400307098

Display Data Pincode Page

Edit Pincode Page

RCTI (CE) 100 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Language Page

Add Data Language Page

RCTI (CE) 101 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Add Language Page Error

Display Data Language Page

RCTI (CE) 102 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Edit Language Page

• Reports In Admin Panel

Service Wise Subservice Report

RCTI (CE) 103 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Area Wise User Report

Package Wise Worker Report

RCTI (CE) 104 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

User Wise Booking Report

User Wise Feedback Report

RCTI (CE) 105 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

• Settings In Admin Panel

Change Password Page

Change Password Page Error

RCTI (CE) 106 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Change Password Data Filled Page

Change Admin Page

RCTI (CE) 107 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Change Admin Data Filled Page

RCTI (CE) 108 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 7
Testing

RCTI (CE) 109 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

7.1 TESTING PLAN AND STRATEGY


This state a number of rules that can serve well as testing objectives:
Testing is a process execution of a program with the intent of finding an
error.
A good test case is one that has a high probability of finding an as-yet
undiscovered error.
A successful test is one that uncovers an as-yet undiscovered error. These
objectives imply a dramatic change in viewpoint for some hardware
developers. They move counter to the commonly held view that a
successful test is one in which no errors are found. Our objective is to
design tests that systematically uncover different classes of errors and to do
so with minimum amount of time & effort.

THERE ARE MAINLY FIVE TESTING PRINCIPLES WHICH


ARE DESCRIBED BELOW:

PRINCIPLE #1: ALL TESTS SHOULD BE TRACEABLE TO


CUSTOMER REQUIREMENTS.
The objective of software testing is to uncover errors. It follows that the
most server defects are those that cause the program to fail to meet its
requirements.

PRINCIPLE #2: TEST SHOULD BE PLANNED LONG BEFORE


THE ACTUAL TESTING BEGINS.
Planning can begin as soon as the analysis model is complete. Detailed
definition of test cases can begin as soon as the design model has been
solidified.
Therefore, all tests can be planned and designed before any code has been
generated.

RCTI (CE) 110 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

PRINCIPLE # 3: THE PARETO PRINCIPLE APPLIES TO


HARDWARE TESTING.
Stated simply, the Pareto principle implies that 80 percent of all errors
uncovered during testing will likely be traceable to 20 percent of all
program components. The problem of course, is to isolate these suspect
components and to thoroughly test them.

PRINCIPLE # 4: TESTING SHOULD BEGIN “IN THE SMALL”


AND PROGRESS TOWARD TESTING “IN THE LARGE.”
The first test planned and executed generally focuses on individual components. As
testing progresses, focus shifts in an attempt to find errors in integrated clusters of
components and ultimately in the entire system.

PRINCIPLE # 5: EXHAUSTIVE TESTING IS NOT POSSIBLE.

The number of path permutations for even a moderately sized program is


exceptionally large. For this reason, it is impossible to execute every
combination of paths during testing. It is possible, however, to adequately
cover program logic and to ensure that all conditions in the component-level
design have been exercised.

TOP DOWN TESTING:


In top-down testing, testing starts with the most abstract components and
works downwards.

BACK-TO-BACK TESTING:
It is used when different versions of a system are available. They are tested
together and their outputs are compared. Testing can be done to check the
performance of the product.

RCTI (CE) 111 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

SYSTEM TESTING:
System Testing typically involves running through every possible input to
verify that it results in the right outputs using the software as an end-user
would. It is needed to improve the performance of the system so user can
have fast processing of all work.

RCTI (CE) 112 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

7.2 TESTING METHODS

BLACK-BOX TESTING:
The technique of testing without having any knowledge of the interior
workings of the application is called black-box testing. The tester is
oblivious to the system architecture and does not have access to the source
code. Typically, while performing a black-box test, a tester will interact with
the system's user interface by providing inputs and examining outputs
without knowing how and where the inputs are worked upon.

Fig. 7.27
WHITE-BOX TESTING:
White-box testing is the detailed investigation of internal logic and structure
of the code. White-box testing is also called glass testing or open-box
testing. In order to perform white-box testing on an application, a tester
needs to know the internal workings of the code.
The tester needs to have a look inside the source code and find out which
unit/chunk of the code is behaving inappropriately.

GREY-BOX TESTING:
Grey-box testing is a technique to test the application with having a
limited knowledge of the internal workings of an application. In software
testing, the phrase the more you know, the better carries a lot of weight
while testing an application.
RCTI (CE) 113 |
Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Mastering the domain of a system always gives the tester an edge over
someone with limited domain knowledge. Unlike black-box testing, where
the tester only tests the application's user interface; in grey-box testing, the
tester has access to design documents and the database. Having this
knowledge, a tester can prepare better test data and test scenarios while
making a test plan.

RCTI (CE) 114 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

7.3 TEST CASES

Different types of Test Cases

PURPOSE REQUIRED INPUT EXPECTED OUTPUT


If username exceeds more
than 15 characters, display
"Username is too long". If
username contains
USERNAME whitespace show error
"Whitespaces are not
allowed". If username is
repeated, display "Username
exists".

Any other character rather


REGISTRATION than 0-9 digits or exceeds or
MOBILE NUMBER less than 10 digits, "Invalid
Phone number" error will
generate.

If email address does not


EMAIL contain "@", display "Invalid
Email Address".

If any other city is selected


which is not in the list then ,
CITY
“invalid city” error will
generate.

User enters both things valid,


Valid Username and Valid then, the user will be
LOGIN redirected to dashboard
Password
screen.

RCTI (CE) 115 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

If any of the field is incorrect,


then error will be generated
of the incorrect field. And,
Invalid Username or Invalid
until the user inserts the
Password
correct information, he/she
will not be re-directed to the
dashboard screen.

Incorrect username will generate


Username
error

The password will be reset if the


Forgot or Reset Password new password matches the
New Password conditions. And if it is same as the
old password, then "Password
exists" error will be occurred.

If user clicks on "edit the details"


and changed any detail and click
on "update" button, the data will
be updated. If user clicks the
User profile Updating the user's details
button but does not do any
changes, then a short message
will be shown to user that "New
Data is as same as Old Data"

RCTI (CE) 116 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 8
Limitations and Future
Enhancement

RCTI (CE) 117 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

LIMITATIONS

➢ This app is only available for citizens resiting in :


o Andheri

o Bandra
o Borivali
o Church Gate

o Colaba

o Dadar
o Gathkopar
o Juhu

o Malabar Hills

o Malad

o Marins
o Mulun

o Parel

o Thane
o Valkeshvar

o Versova

➢ Same service worker is required for booking.

RCTI (CE) 118 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

FUTURE ENHANCHMENT

➢ In coming time we want to launch this app in all the metropolitin cities
of india.
➢ To make app more attractive and responsive.

➢ To generate more employment.


➢ We want to an ® in our app.

➢ We want generate more and more revenue from this app.

RCTI (CE) 119 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 9
Conclusion

RCTI (CE) 120 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

CONCLUTION

Till now, we conclude that we complete our documentation and also


implementation of our application. We also conclude that till now the
implementation we had done in our application was the best experience of all
things, because, we had somewhat kind of advanced Android by using new
types of designing and coding style. We also conclude that we have learnt so
many new concepts of testing methods and strategies and different types of
waterfall models and many more things while doing the whole
documentation.

We finally can conclude that according the contents of the above


documentation, our Application have been built.

RCTI (CE) 121 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

Chapter 10
REFERENCES

RCTI (CE) 122 |


Page
SHERBIMET 186400307088 | 186400307091 | 186400307098

WEBSITES: -

• www.w3schools.com
• https://stackoverflow.com
• www.youtube.com
• https://developer.android.com/
• www.github.com
• http://www.tutorialspoint.com

RCTI (CE) 123 |


Page

You might also like