An overview on BRM is discussed in our earlier posts and we would recommend beginning from that article for continuity. In this post we will discuss the data stored in the BRM Database, created by performing various BRM GUI and BRM API operations.
Given below is the structure of BRM Database:
The BRM Database is a key module in BRM Server Architecture.
The following data is stored in the BRM database:
- Customer account details (credentials, account number, service plan, price)
- Customer personal details (Name, Address)
- Customer payment information
- Available Service plans
- Billing Information
- Pricing and Rating details
- Business related information
- Call recorded data
We built a hybrid framework using Ruby/Selenium/Cucumber to test the BRM system. Using our framework, we can connect to the Browser UI, capture the necessary parameters and validate them with the data stored in the database.
Whenever an account is created, the account details including account number and device numbers (Serial_number and IMEI number) are saved in the BRM database. In order to connect to the Oracle BRM database we used ActiveRecord gem and a JDBC connection. A sample Oracle database connection is displayed:
The following details have to be mentioned to get connected to the Oracle database:
- Connection Name
- Username
- Password
- host
- port#
- Service name
The data in the BRM database is managed in tables as with any traditional database. In order to create a new account, unused device numbers such as Serial Number/IMEI are required. Once the connection to the database is made, appropriate queries are run to retrieve the unused device numbers. These numbers are replaced dynamically in the request/input every time you want to create an account. Customer accounts can be created on the BRM GUI and also by running API calls on SOAP Client. The details about how the accounts are created on browser GUI is discussed in BRM GUI Testing and how the accounts are created using service calls is discussed in BRM API Testing.
BRM database also contains call data such as
- Start time and end time of the call/data usage
- Number of minutes utilized by the call/data usage
- Rating plans
We have tested the pricing and rating plans associated with different service plans. Using our hybrid framework, which is a 3-way facilitator connecting to the browser UI (Client Applications like Customer Center & Pricing Center), backend API, and database, we have validated the data in the BRM database.
