Test Scope Document-Water Tanker Sale

Test Scope Document

Table of Contents

Table of Contents..................................................................................................................... 2
Document History..................................................................................................................... 3
Feature Summary..................................................................................................................... 3
Abbreviations........................................................................................................................... 3
Input Documents...................................................................................................................... 3
Test Requirement/Scenario...................................................................................................... 4
Pre- Requisites......................................................................................................................... 4
Data Requirements.................................................................................................................. 4
End to End Test Requirements & Test Scenarios for Water Tanker Sale..................................4

2
Document History
Date Name Description/Reason for change
06-07-2017 Prasanta K Prusty Initial Version

Feature Summary
Water Tanker Sale is a special utility service provided by AIS. The service is divided into 4 different sub processes
according to the business functionality.
1. Water Relief Tanker
2. Purchase Water (AIS Owned Tanker)
3. Renting for Static Water Tanker
4. Purchase Water (Customer Owned Tanker)

Request for a Water Tanker can be taken through various ways and will be handled using Order and Case
functionality in OUCCB. The functionality will be achieved with the integration of OUCSS-OUCCB-MWM.

Abbreviations
Abbreviation Description
AIS Air Selangor
OUCCB Oracle Utilities Customer Care & Billing
OUCSS Oracle Utilities Customer Self Service
MWM Mobile Workforce Management

Input Documents
Water Tanker Sale – To Be Process Document

3
Test Requirement/Scenario
Pre- Requisites
Existing AIS Customer

Data Requirements
Mentioned with Test Scenarios.

End to End Test Requirements & Test Scenarios

for Water Tanker Sale
S No Requirements
TR1 Water Relief Tanker via Walk-in
Request
Description: This requirement deals
with creating an order to capture the
request information from the customer,
creating a case to track the request,
validating the eligibility of service
delivery and deliver the water tanker in
Water Disruption Area for legitimate
request.
Application/System Configuration: 1)
OUCCB and MWM system should be
up and running
2) The Customer data should have
exact name in both OUCCB and MWM
application system
3) The customer data mapping and
configuration should have been done
Scope: This deals with creation of
Order, Case and Field Activity in the
system
Impact on sub applications: None
Test Scenarios
TS 1.1 CRS should be able to search the customer in OUCCB,
create and complete an Order to capture the request
information. A case would be created in the system once the
order is completed.
Description: CRS will create an order by selecting the correct
campaign for Water Relief Tanker. CRS will fill the required
information as part of the order and try to complete the order.
Once the order is completed, a case would be created in the
system.
Pre-requisites:
OUCCB up and running
Data Requirements:
Middleware – No Specific data requirements.
OUCCB – Campaign, Order Id, Case Id
Indicative Cases: This scenario will cover at a high level the
following cases:
 Test that CRS can create and complete an order after
filling required information. The required case has to be
created, once the order is complete.
TS 1.2 Case is under verification and assigned to Head of
Region (HOR)/ ERP Secretariat. User would do the required
verification and can approve or reject the Case.
Description: This requirement deals with verifying the eligibility

4
of the customer for Relief Water Tanker. Upon verification, the
request can either be approved or rejected. If approved, the
case will transition to the next status, a respective field activity
would be created in the system for water delivery. If rejected,
the case will transition to Close status.
Pre-requisites:
OUCCB up and running
MWM up and running
Data Requirements:
Middleware – No Specific data requirements.
OUCCB – Case Id, FA Id
MWM – Crew Shift Availability
Indicative Cases: This scenario will cover at a high level the
following cases:

 Test that user can approve or reject the case upon

verification

TS1.3 Field Activity completed or Cancelled in MWM

Description: Should be filled by MWM Team
Pre-requisites:
OUCCB up and running
MWM - ??
Data Requirements:
Middleware – No Specific data requirements.
MWM – ??
Indicative Cases: This scenario will cover at a high level the
following cases:

 Test that a crew can change customer contact from

MWM servicing a Pending/On hold Connect Service
Point service order initiated by OUCCB and should be
dispatched in MWM
TS1.4 Case auto transition to service delivered or not delivered.
Notification to user to close the case
Description: This requirement deals with the auto transition of
the case according to the FA result. If FA is completed, the case
will move to Service Delivered. If FA is cancelled, the case
would move to Service Not Delivered. A to do notification will be
created to the respective user. User will update the comment
and manually close the case.
Pre-requisites:
OUCCB up and running
MWM up and running

5

TR2 Water Relief Tanker via Voice Call
Description: This requirement deals
with creating an order to capture the
request information from the customer,
creating a case to track the request,
validating the eligibility of service
delivery and deliver the water tanker in
Water Disruption Area for legitimate
request.
Application/System Configuration: 1)
OUCCB and MWM system should be
up and running
2) The Customer data should have
exact name in both OUCCB and MWM
application system
3) The customer data mapping and
configuration should have been done
Scope: This deals with creation of
Order, Case and Field Activity in the
system
Impact on sub applications: None
Data Requirements:
Middleware – No Specific data requirements.
OUCCB – Case Id, FA Id
Indicative Cases: This scenario will cover at a high level the
following cases:
 Test that the case is auto transitioning correctly
depending upon the FA result. User should be able to
move the case to close status.
TS 2.1 CRS should be able to search the customer in OUCCB,
create and complete an Order to capture the request
information. A case would be created in the system once the
order is completed.
Description: CRS will create an order by selecting the correct
campaign for Water Relief Tanker. CRS will fill the required
information as part of the order and try to complete the order.
Once the order is completed, a case would be created in the
system.
Pre-requisites:
OUCCB up and running
Data Requirements:
Middleware – No Specific data requirements.
OUCCB – Campaign, Order Id, Case Id
Indicative Cases: This scenario will cover at a high level the
following cases:
 Test that CRS can create and complete an order after
filling required information. The required case has to be
created, once the order is complete.
TS 2.2 Case is under verification and assigned to Head of
Region (HOR)/ ERP Secretariat. User would do the required
verification and can approve or reject the Case.
Description: This requirement deals with verifying the eligibility
of the customer for Relief Water Tanker. Upon verification, the
request can either be approved or rejected. If approved, the
case will transition to the next status, a respective field activity
would be created in the system for water delivery. If rejected,
the case will transition to Close status.
Pre-requisites:
OUCCB up and running
MWM up and running
Data Requirements:
6
Middleware – No Specific data requirements.
OUCCB – Case Id, FA Id
MWM – Crews Shifts Availability
Indicative Cases: This scenario will cover at a high level the
following cases:

 Test that user can approve or reject the case upon

verification

TS2.3 Field Activity completed or Cancelled in MWM

Description: Test that Crew successfully completed the Water
Tanker Delivery in field and completed the Activity and in case
failed to deliver the Tanker completed the Activity with
Incomplete Status.
Pre-requisites:
CCB up and running
MWM - Scheduler Up and Running
Data Requirements:
Middleware – No Specific data requirements.
MWM – Crew Shifts available.
Indicative Cases: This scenario will cover at a high level the
following cases:

 Test that a crew can change customer contact from

MWM servicing a Pending/On hold Connect Service
Point service order initiated by OUCCB and should be
dispatched in MWM
 Test that Crew can successfully complete the Activity
on Device and completion Information will be send to
CC&B
 Test that in case of failed delivery of Water Tanker to
Customer, Crew will complete the Activity on Device
with Incomplete status & Reason and Cancellation
Message will be send to CC&B.
TS2.4 Case auto transition to service delivered or not delivered.
Notification to user to close the case
Description: This requirement deals with the auto transition of
the case according to the FA result. If FA is completed, the case
will move to Service Delivered. If FA is cancelled, the case
would move to Service Not Delivered. A to do notification will be
created to the respective user. User will update the comment
and manually close the case.
Pre-requisites:
OUCCB up and running
MWM up and running

7

TR3 Water Relief Tanker via OUCSS
Description: This requirement deals
with handling the Water Relief Tanker
request from OUCSS, creating a case
in OUCCB to track the request,
validating the eligibility of service
delivery and deliver the water tanker in
Water Disruption Area for legitimate
request.
Application/System Configuration: 1)
OUCSS, OUCCB and MWM system
should be up and running
2) The Customer data should have
exact name in OUCSS, OUCCB and
MWM application system
3) The customer data mapping and
configuration should have been done
Scope: This deals with creation of Case
and Field Activity in the system
Impact on sub applications: None
Data Requirements:
Middleware – No Specific data requirements.
OUCCB – Case Id, FA Id
Indicative Cases: This scenario will cover at a high level the
following cases:
 Test that the case is auto transitioning correctly
depending upon the FA result. User should be able to
move the case to close status.
TS 3.1 OUCSS related scenario to be explained
TS 3.2 A case would be created in the system and to do
notification will be created for Head of Region (HOR)/ ERP
Secretariat. User would do the required verification and can
approve or reject the Case.
Description: This requirement deals with verifying the eligibility
of the customer for Relief Water Tanker. Upon verification, the
request can either be approved or rejected. If approved, the
case will transition to the next status, a respective field activity
would be created in the system for water delivery. If rejected,
the case will transition to Close status.
Pre-requisites:
OUCCB up and running
MWM up and running
Data Requirements:
Middleware – No Specific data requirements.
OUCCB – Case Id, FA Id
MWM – ?
Indicative Cases: This scenario will cover at a high level the
following cases:
 Test that user can approve or reject the case upon
verification
TS3.3 Field Activity completed or Cancelled in MWM
Description: Test that Crew successfully completed the Water
Tanker Delivery in field and completed the Activity and in case
failed to deliver the Tanker completed the Activity with
Incomplete Status.
Pre-requisites:
CCB up and running
MWM - Scheduler Up and Running
Data Requirements:
Middleware – No Specific data requirements.
MWM – Crew Shifts available.
8
Indicative Cases: This scenario will cover at a high level the
following cases:

 Test that a crew can change customer contact from

MWM servicing a Pending/On hold Connect Service
Point service order initiated by OUCCB and should be
dispatched in MWM
 Test that Crew can successfully complete the Activity
on Device and completion Information will be send to
CC&B
 Test that in case of failed delivery of Water Tanker to
Customer, Crew will complete the Activity on Device
with Incomplete Status & Reason and Cancellation
Message will be send to CC&B.
TS3.4 Case auto transition to service delivered or not delivered.
Notification to user to close the case
Description: This requirement deals with the auto transition of
the case according to the FA result. If FA is completed, the case
will move to Service Delivered. If FA is cancelled, the case
would move to Service Not Delivered. A to do notification will be
created to the respective user. User will update the comment
and manually close the case.
Pre-requisites:
OUCCB up and running
MWM up and running
Data Requirements:
Middleware – No Specific data requirements.
OUCCB – Case Id, FA Id
Indicative Cases: This scenario will cover at a high level the
following cases:

 Test that the case is auto transitioning correctly

depending upon the FA result. User should be able to
move the case to close status.