Consumer Mobile App Use case:

The Consumer having set of use cases as shown in bellow

1
 Fig: Use case-1: Consumer Mobile App

Registration use case:

Diagram:

Use case-2: Consumer Registration

Brief Description
The Consumer need to register with our web application or Mobile app.

Pre-Condition:
Before this use case can be initiated, the Consumer has already accessed the Home page of the
XXXX Transportation if it is web application or Consumer has already downloaded the Mobile
App of the XXXX Transportation if it is Mobile application.

Step-By-Step Description in Web:

1. The Consumer selects to New User Registration.
2. The system presents a screen to entering the details. The Details as follows:
a. Consumer Name & Last name*
b. Consumer Mobile Number* (OTP should send to entered mobile number)
c. New Password*
d. Confirm Password*
e. Consumer Address*(Full Address- H.No, Village/Street, Panchayath/Locality,
Mandal/ULB, City, State and PIN code)
f. Consumer type*
i. Individual
ii. Mason
iii. Builder
iv. Govt. Contractor

2
 v. Others
g. Disclaimer
3. While Registering the details, Application get validate the all strings entered by Consumer
4. While Registering the details, Application should capture the bellow details:
a. Lat & Long of Device
b. Device IMEI number
5. After Registering, OTP will send to entered mobile number and system present a screen to
entering the OTP
a. System enable to Consumer to Re-Send an OTP.
6. After entering the OTP and selects Submit option, OTP will be cross verified and save the
Consumer details if OTP will be matched.
7. Application will save the Consumer details in DB and give a confirmation along with unique
Consumer ID (PK)
Inputs of Use case:
Step 1 to 6
Output of Use case:
Consumer Registered and receive a unique Consumer ID (Primary Key)

Step-By-Step Description in Mobile App:

Same procedure will be followed in Mobile App also.

Login use case:

Diagram:

Use case-3: Login Process

Brief Description

3
Consumer can access the features by login to web application or Mobile app.

Pre-Condition:
Before this use case can be initiated, the Consumer has already registered in our platform and
should be accessed the Home page of the XXXX Transportation if it is web application or
Consumer has already downloaded the Mobile App of the XXXX Transportation if it is Mobile
application.

Step-By-Step Description in Web:

1. The system presents a screen to entering the user credentials. The Details as follows:
a. Consumers User name (eMail/Mobile number)
b. Consumers Password
2. After entering and submission of credentials, application should verify the DB with entered
user credentials,
3. If credentials will match to DB, then application will allow user to Main Menu
Inputs of Use case:
Step 1 to 2
Output of Use case:
The System present the Main Menu screen to Consumer
Step-By-Step Description in Mobile App:
Same procedure will be followed in Mobile App also.

Forgot Password use case: Send PWD to registered mobile number only.

Reach & Vehicle Selection for XXXX Transportation:

Diagram:

4
 Use case-4: Vehicle Search

Brief Description
Consumer can search the available Reaches/Stockyards and vehicles to get the XXXX
transportation facility.
Pre-Condition:
Before this use case can be initiated, the Consumer has pointed his Delivery address in MAP in
our platform.

Step-By-Step Description in Web/Mobile:

1. After selection of Delivery address and Purpose of XXXX, The system presents List
of Reaches/Stockyards where XXXX is available to collect.
2. The List Consisting of bellow fields:
a. Reach/Stockyard name
b. XXXX Price
c. Quality of XXXX
d. Approx. distance to Delivery address
3. Application present Search Vehicles/Transporters option to each Reach/Stockyard.
4. Vehicles available: to transport the XXXX:
If the Consumer registered as individual, System will list all the XXXX vehicles (Retail and
Big transporters) nearby his/her location. The list consisting of bellow fields:
a. Vehicle Number
b. Vehicle Capacity
c. Location (text)
d. Mobile Number of Driver/Owner

5
 e. Owner name
If the Consumer registered as Bulk, System will list all the Big transporters available his/her
location. The list consisting of bellow fields:
a. Transporter name
b. Mobile Number
c. No. of Vehicle types having

Inputs of Use case:

Consumers delivery point/address and Transporter choice of supply.
Outputs of Use case:
List of available Vehicles (S.No-a to f)

Note-1:- Application will display the list of Vehicles which are fitted by GPS &&
Communicated only. We can violate this condition also but it leads negative impact on
business.

Send Proposal Use case:

Diagram:

Use case-5: Send Proposal

Brief Description:
After viewing the details of Vehicles, Consumer can send a proposal to
Vehicle/Transporter by selecting Transporter will pay option.
Pre-Condition:

6
 NA
Step-By-Step Description in Web/Mobile:
1. If the Consumer registered as individual and selected one retail Transporter, System
presents an option against to each and every Vehicle to send a proposal.
2. If Consumer select the Send Proposal with Transporter will Pay or Self Pay option,
application capture the bellow fields and stores in DB
a. Consumer ID
b. Transporter ID
c. Vehicle No
d. Consumers Delivery Address Text and Lat & Lan
e. Transaction Date & Time
f. Unique/Sequence ID
3. After saving the proposal details, Application will give the response with Booking ID to
Consumer and same details will go to respective Transporters login of selected vehicle.
4. If the Consumer registered as Bulk and selected one big Transporter, application will list
the bellow details and ask for Consumer input on required Vehicles.
a. Available Vehicle Type & Capacity
b. How many required?
i. Auto calculation of Required Quantity (Capacity of vehicle * No. of
required)
c. Auto calculation of sum of Required quantities and its Royalty
Note: If payable amount of Royalty is zero (Free XXXX), then application directly Send the
Proposal to Transporter without asking either Consumer Pay or Transporter will Pay. If
there is Royalty to be pay, then application will ask for payment.
Inputs of Use case:
S.No 2a to 2e
Outputs of Use case:
Booking ID

Payment of Royalty:
Diagram:

7
 Use case-5.1: Payment or Royalty
Brief Description
Consumer can pay the Royalty directly by selecting Self-Pay option while sending the
Proposal to Transporter.
Pre-Condition:
Before this use case can be initiated, the Consumer has already having an account of m-
wallet or [having any online Net banking account]. And Transporter has already agreed with
Self pay option.
Step-By-Step Description in Web/Mobile:
1. Consumer selects Self pay option, then system presents payment Gateway options
along with Sum of amount to be Paid. Usually sum of amount is XXXX Price per
CuM * Quantity of Vehicle Capacity or [XXXX Price per CuM * required quantity]
2. Payment gateway will connect to respective Users login page.
3. If consumer logins to his account, and account having sufficient balance then
application seeks one more confirmation and send a SUCCESS response to our
application.
a. If Wallet doesnt have sufficient balance in account, that will suggest
Consumer to pay through Online banking system.
4. After payment successful, wallet send a SUCCESS response to our application.
5. If application receive a SUCCESS response, then application confirm the booking,
save and send same information to Transporters login.
a. If application receive FAILURE response, then application should inform the
same information to Consumer and present a Retry option

Cancel Proposal:
Diagram:

8
 Use case-6: Cancel Proposal

Brief Description:
After sending the proposal, application enable a facility to cancel the proposal if
Transporter/driver not accepted his proposal yet.
Pre-Condition:
Consumer has already sent a proposal
Step-By-Step Description in Web/Mobile:
1. Consumer can cancel his proposal by selecting Cancel proposal option.
2. Along with Cancel proposal option, application will display the proposal details as
follows:
a. Proposed Date & Time
b. Vehicle No.
c. Vehicle Capacity
d. Owner/Driver name
e. Mobile No.
f. Status of Proposal ( Proposal sent/ Transporter Accepted/ Vehicle Started/etc)
3. Cancel Proposal option will enable if Transporter not yet accepted or not yet
started.
4. If any case, transporter has agreed and Consumer has already paid the Royalty, then
application facilitate the Postponement to Consumer.
5. Remarks fields are mandatory if Consumer selects Cancel Proposal. List of
Remarks are follows:
a. Price is very high (This will effect to Transporters rating)
b. Transporter not willing (This will effect to Transporters rating)

9
 c. Transporter not picking the calls
d. Quality of XXXX not matched
e. Distance is so long
f. Etc
6. After submission of Cancel Proposal application presents a Success message of
Cancellation of Proposal.
Inputs of Use case:
Proposal ID (pk)
Outputs of Use case:
Proposal will be cancelled.

Vehicle Tracking Use case:

Diagram:

Use case-7: Vehicle Tracking

Brief Description:
This Use case will give the Tracking of Vehicle which is booked by Consumer and which
transporter has already agreed to Consumers proposal.
Pre-Condition:
Before initiative of this Use case, Transporter has already agreed to Consumers proposal
and Consumer need to access his transaction history in his account.
Step-By-Step Description in Web/Mobile:
1. System present an option to track the Vehicle if transporter has already agreed the
proposal of Consumer.
2. If consumer selects the Vehicle Tracking, application will give the Location of
Vehicle in MAP.

10
 3. [Application will give tentative ETA to reach the Destination by calculation of
distance.] Next Phase.
4. Application should display Delivery location and Vehicles current location in MAP
Inputs of Use case:
Delivery location and Current location of Vehicle
Outputs of Use case:
Application displays the current location of vehicle and delivery address in MAP

Delivery Confirmation Use case:

Diagram:

Use case-8: Delivery Confirmation

Brief Description:
Consumer should confirm the Delivery of XXXX
Pre-Condition:
Before initiative of this Use case, Vehicle has already reached to Delivery location and
Transporter has already taken the Destination Reached option.
Step-By-Step Description in Web/Mobile:
1. If vehicle entered into Delivery location with radius of [30]* meters, Application will
give an alert to Consumer stating that, Vehicle arrived for un-load the XXXX
2. If Transporter selects the Destination Reached and Un-Loaded the XXXX option,
System automatically displays a screen to Consumer to select Delivery
Confirmation.
Inputs of Use case:

11
 Vehicle location, increased geo-fence of Delivery point and Response of Destination
reached from transporter.
Outputs of Use case:
Delivery of XXXX load has successfully confirmed by Consumer.

Submit Rating Use case:

Diagram:

Use case-9: Submit Rating

Brief Description:
This facilitate to submit the rating on Delivered XXXX and its transportation
Pre-Condition:
Before initiative of this Use case, Delivery confirmation has been done by Consumer.
Step-By-Step Description in Web/Mobile:
1. After submission of Delivery Confirmation, System presents a screen to Consumer
to Submit Rating/Feedback on XXXX Transportation.
2. The screen will give bellow choices:
a. XXXX received with in expected time?*
i. Yes
ii. No
b. How is supplied XXXX Quality?
i. Matched with transporters words
ii. Partially matched

12
 iii. Not matched
c. Rating on XXXX price
i. Decreased compare to earlier prices
ii. Average
iii. High
iv. Very High (Not decreased)
d. Rating on Driver behavior
i. Good
ii. Average
iii. Bad
e. Overall Rating to Transporter*
i. 1 to 5 starts should be displayed
f. Specific Remarks if any?
i. Text area field should be displayed to enter remarks

3. After submission of above screen, application will give a response to Consumer

stating that Thanks for submitting the Rating, have a nice day Mr. [User]
Inputs of Use case:
Delivery confirmation from both sides
Outputs of Use case
Rating/feedback has successfully submitted by Consumer.

User Characteristics
The Consumer is expected to be Internet literate and be able to use a browser or mobile
app. The main screen of the Website will have the New User Registration, Real time
Dashboard and a link to download the Mobile app.
The Consumer is expected to be Windows and Mobile app literate and to be able to use
button, pull-down menus, and similar tools.

Non-Functional Requirements
The website of XXXX Transportation will be on a server with high speed Internet
capability. The software developed here assumes the use of a tool such as Tomcat for

13
connection between the Web pages and the database. The speed of the Consumers connection
will depend on the hardware used rather than characteristics of this system.
The Consumer will run on the Mobile app in his Mobile and will create a local storage.
This local storage will give a fast access to mobile app in respect of Lunching, to access History,
to know the User details which will not depend on server connection.

Security
The server on which the XXXX Transportation resides will have its own security to

prevent unauthorized access on Write/delete. There is no restriction on read access. The mobile

app on which the Consumers resides will have its own security. There is no special protection

built into this system other than to provide the credentials to Consumer with write access.

OTHER IMPORTANT ASPECTS OF SOFTWARE:

The software should be;
1. Application should be High available to public
2. Performance should be good
3. Screens should have rich UI/UX and should be User friendly.
4. Navigation b/w screen to screen should be easier.
5. Functionality and appearance of all screens of Website should be same to all
Browsers (means Browser compatibility)
6. Mobile app should be downloaded the compatible to all popular models of
mobile devices.
7. Web application/ Mobile application should run on minimum Hardware
capacity of Desktop/Laptop/Mobile.
8. Mobile application should maintain local storage also.
9. Mobile application should automatically detect the updates and automatically
updates if User accessing Wi-Fi in his Mobile device or Application should ask
permissions to User to Update the App.

14
10. Web application/ Mobile application should have internationalization (Local
Language).

15