Test Scope Document-Payment

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 Payment.................................................4

2
Document History
Date Name Description/Reason for change
19-07-2017 Tejendra Initial Version

Feature Summary
Collection is referred to as PAYMENT in OUCCB. Payments are made to an account to offset its debt. Payments
consist of payment segments that are distributed among the account’s typical services: Water Service,
Miscellaneous Services and Deposit.

Payments can be composed of different types of tenders, allowing flexibility of accepting multiple types of tender,
such as cash and check, under a single payment. Payments are managed by Deposit and Tender Controls.

OUCCB is capable of supporting online cashiering and external payment upload. This document deals with the
Online Cashiering only.

Abbreviations
Abbreviation Description
AIS Air Selangor
BASIS Bekalan Air Selangor Information System
CEC Collection Exchange Center
EFT Electronic Fund Transfer
GST Goods and Services Tax
HQ Head Quarter
iPOS Payment Counter System
OUCCB Oracle Utilities Customer Care & Billing
SA Service Agreement

Input Documents
Payment-To Be Process Document

3
Test Requirement/Scenario
Pre- Requisites
a. Deposit Control- Open Status
b. Tender Control-Open Status
c. Account has existing Debt against which Customer is going to make payment.

Data Requirements
 Account Id
 Deposit Control Id
 Tender Control Id

End to End Test Requirements & Test Scenarios

for Payment
S No Requirements
TR1 Create Payment Event for an Account.
Description: This requirement deals
creating a payment for an existing
account with outstanding balance.
Application/System Configuration: 1)
CCB system should be up and running
Scope: This only deals with creation of
payment at cashier counter.
Impact on sub applications: None
Test Scenarios
TS 1.1 User (Cashier) is able to create the payment event if
Deposit control and Tender control is open for the current date
and for the same user.
Description: This requirement deals creating and updating
payment on the existing account.
Pre-requisites:
CCB – Deposit Control and Tender Control open for the Tender
Type.
Data Requirements:
Middleware – No Specific data requirements.
CCB – Account Id
Indicative Cases: This scenario will cover at a high level the
following cases:

 Test that a cashier is able to add payment event using

TR2 Create Payment Event for an Account.
Description: This requirement deals
creating a payment for an existing
account with outstanding balance.
CCB screen.
TS 1.1 User (Cashier) is not able to create the payment event if
Deposit control and Tender control is not open for the current
date and for the same user.
Description: This requirement deals creating and updating

4
 Application/System Configuration: 1)
CCB system should be up and running
Scope: This only deals with creation of
payment at cashier counter.
Impact on sub applications: None
TR3 Create Payment Event for an Account
using Check as tender type.
Description: This requirement deals
creating a payment for an existing
account with outstanding balance.
Application/System Configuration: 1)
CCB system should be up and running
Scope: This only deals with creation of
payment at cashier counter.
Impact on sub applications: None
payment on the existing account.
Pre-requisites:
CCB – Deposit Control and Tender Control not open for the
Tender Type.
Data Requirements:
Middleware – No Specific data requirements.
CCB – Account Id
Indicative Cases: This scenario will cover at a high level the
following cases:
 Test that a cashier is not able to add payment event
using CCB screen.
 Error Message to be displayed, that the Current User
do not have any open tender control for current date
TS 1.1 User (Cashier) is able to create the payment event if
Deposit control and Tender control is open for the current date
and for the same user.
Description: This requirement deals creating and updating
payment on the existing account using check as tender type.
Pre-requisites:
CCB – Deposit Control and Tender Control open for the Tender
Type (check).
Data Requirements:
Middleware – No Specific data requirements.
CCB – Account Id
Indicative Cases: This scenario will cover at a high level the
following cases:
 Test that a cashier is able to add payment event using
CCB screen.
 Test that it will not allow to save the payment if Tender
Type is Check and check number is not provided.