LET’S SHARE APPLICATION

Team Members:
V.S.Akhila

K.Neelima

Use Case Description:

Let’s Share is one of the leading car and bike pools in India. It offers bike and
car sharing options for daily travellers, and frequent travellers. It also offers its
customers the facility to choose the people or a group of people they desire to
travel with. The application also allows the traveler to plan and choose the
best pool option with other people when one wants to save time and you are
in a hurry. It’s currently maintaining its process through offline records. Let’s
share wants to automate the process using Pega.

Requirements:
⮚ Signup:
● A Traveler clicks on the “Sign Up” to provide email and other
information.
● Once the mandatory fields are filled in the Traveler id is
generated.

⮚ Driver Registration:
● The Driver registers with the profile information which includes car type
and no of seats .
 ● The Driver also needs to provide the car no and needs to submit license,
car papers and pollution certificate.

⮚ Approval:
● Let's Manager reviews the Driver and the traveller’s details and
approves/negotiates/rejects it. In case of rejection/ negotiation the
reason and alternatives needs to be provided.

⮚ Enrollment:
● A driver can enroll himself for a single company/ multiple
companies/others trips with driver id (auto create).
● If he enrolls for a single company then the company names should be
displayed, otherwise no company names should be displayed.

⮚ Group creation:
● A user can create or join any group.
● A member can opt out of the group at this stage by leave group.

⮚ Facility: Once the group is created, the Let's Manager approves the
group and based on the driver preference he allocates a driver for the
group.

⮚ Feedback: Feedback should be taken from all the travellers in the group.

Actors:
1.Traveller

2.Let's Manager

3.Driver

Application Structure: Implementation only(Built on PEGA RULES)

Organisation Name: LS

Application Name: Vehicle Pooling

Enterprise Class Structure:

Access Groups:
1.Vehicle Pooling Application: Manager (Reviews the details)

2.Vehicle Pooling Application: Traveller (Signup)

3.Vehicle Pooling Application: Driver (Registration, Enrollment)

Roles:

Manager
 Traveller

Driver

Case Design:

Main Case Type:Administration

Child Case Type: Signup

Child Case Type: Registration

Data Model:
Routing Details
Work Queues

1. TLWB – for approving information provided by Traveller

2. ManagerWB – for approval

3.DriverWB-for Manager to supervise Driver work

Work Group

1.Manager@LS

Operators

1.Manager@LET’S SHARE-Manager

2. Traveller@LET’S SHARE -Traveller

3.Driver@LET’S SHARE-Driver

Portals

1. Manager-Case Manager
2. Traveller- Case Worker
3. Driver-Case Worker