INTEGRATION PLAN V 1.

0
JBVNL I~EASYPAY

SRUJAN CH
IDEAINFINITY IT SOLUTIONS PVT LIMITED
INFANTRY ROAD, BANGALORE
Integration Plan

Revision History
Ver. / Release Date Prepared by Reviewed by Approved by Remarks/Revision
Rel. No Details

1.0 08-02-2022 Srujan CH Nithin G Vinay MC Initial Document

JBVNL_i~Easypay Project Page 1 of 8

Integration Plan

Contents
Revision History.........................................................................................................................................1
1. Introduction...............................................................................................................................3
1.1 Purpose......................................................................................................................................3
1.2 Scope.........................................................................................................................................3
2. Definitions, Acronyms, and Abbreviations..................................................................................3
2.1 System Components...................................................................................................................3
2.2 ATP Database............................................................................................................................3
2.3 ATP Server.................................................................................................................................3
2.4 ATP Services...............................................................................................................................4
2.5 Data Entities..............................................................................................................................4
2.6 Technical Terms.........................................................................................................................4
2.7 References.................................................................................................................................5
2.8 Overview...................................................................................................................................5
3. Component Architecture Description:.........................................................................................5
3.1 ATP Application..........................................................................................................................5
3.2 ATP Server Database..................................................................................................................5
3.3 Admin Access.............................................................................................................................5
4. Integration Tests........................................................................................................................5
4.1 ATP Application– Login Interface................................................................................................6
4.2 ATP Interface – ATP Server Database.........................................................................................6
4.3 Admin Access – ATP Server Database.........................................................................................7

JBVNL_i~Easypay Project Page 2 of 8

Integration Plan

1. Introduction
1.1 Purpose
The purpose of the integration test plan is to describe the necessary tests to verify that all of the
modules of Any-Time Payment are properly worked. Integration testing ensures that the unit-tested
modules interact correctly.

1.2 Scope
“Any-Time Payment is the methodology and software that an organization uses to do the payment
of electricity bill with ease and convenient process, so that more and more transactions can be done
through the system”.

An effective Any-Time Payment (ATP) improves short and long-term business performance by

1. Providing an ease and interactive platform to do the payment.

2. Providing user interactive environment.
3. Minimal process flow between consumer and the government.
4. Direct posting of payment from our system to the third-party system.

2. Definitions, Acronyms, and Abbreviations

This section provides definitions for common terms used throughout the document. They are
provided to help minimize ambiguity throughout the document.

2.1 System Components

The ATP is the overall platform, and the components of this platform work together to provide the
platform between Customer and the JBVNL system.

2.2 ATP Database

SQL Server Database is the storage systems containing all the data that is necessary for a finalized and
fully functional Accounting system to display all of the data layers that were included in its design.
The prime focus of ATP SQL Server Database is to acquire, process, distribute, use, maintain, and
preserve Accounting data.
The following types represent the major Features of SQL Server
• Indexes, Functions, Procedures help to perform application better.
• Using Indexes Execution time of Queries reduces.

2.3 ATP Server

The ATP Server is the core server used for creating and managing WCF/Web services, applications,
and data. The ATP Server can be either deployed on-premises within the organization’s service-
oriented architecture (SOA).
It creates a secured environment to publish the Application to the external world. The ATP Server
will focus on providing Everything as a Service to their user.

JBVNL_i~Easypay Project Page 3 of 8

Integration Plan

2.4 ATP Services

The ATP Service will provide communication with Other application to Get and Post data when
required.

2.5 Data Entities

2.4.1 Product Input Data – Shape data in various formats provided by user to fit into the
defined structure.
2.4.2 Print option - User can print their operations performed on the application as per extent
information.
2.4.3 Formats Output – User can download their data in various formats such as PDF, Excel for
the user's repository and specific usage.

2.6 Technical Terms

 C# - C# Language is simple, easy to learn and provides object Oriented concepts. We can
able to develop Console, Windows and Web Application.

 MVC – MVC provides separation of Concerns (SOC), Easy integration with JavaScript
Framework. It reduces the burden on server from Postback.

 JavaScript – It Helps to run immediately within the client-side browser. JavaScript as

being Client side reduces the demand on the Website Server.

 jQuery – It simplifies the HTML document traversing, event handling, animating, and
Ajax interactions for rapid web development.

 HTTP - Hypertext Transfer Protocol (HTTP) is a request/response protocol between

clients and servers.

 URL – A uniform resource locator (URL) is a unique address for locating a file.

JBVNL_i~Easypay Project Page 4 of 8

Integration Plan

2.7 References
The following references are supplemental to the material found in this document:
Software Requirements Specification for ATP, Project Management Plan.

2.8 Overview
The table below describes the organization of content across the sections in this document.
Section Description
1 - Introduction Define the purpose, scope, and overview of this document.

Error! Reference source not Describe each of the components of ATP.

found. - Error! Reference
source not found.

4 - Integration Tests Detail each test necessary to ensure proper integration of ATP
Components in Web application.

3. Component Architecture Description:

The ATP system can be divided into several components. Listed below are the five components and a
brief description of each component’s purpose.

3.1 ATP Application

ATP is the software that is running on the windows. This application provides a methodology that a
consumer uses to get their due data of their household electricity payment and to pay their bills.

3.2 ATP Server Database

The ATP Server is the core server used for creating and managing WCF/Web services, applications,
and data. The ATP Server can be either deployed on-premises within the organization’s service-
oriented architecture (SOA).

3.3 Admin Access

The Admin Access allows a system administrator to view the status, provide permissions, access limit
to users for convenient and flexible across the system users.

4. Integration Tests
This section details the black box tests needed to ensure that each module of ATP is interacting with
other module as expected. These tests are extremely important in the context of ATP because of its
online server access environment.

JBVNL_i~Easypay Project Page 5 of 8

Integration Plan

4.1 ATP Application– Login Interface

4.1.1 Internet Secure Access
Purpose The purpose of this test is to ensure that secure access of information across
users.
External Ensure that the Internet Connection availability
Dependencies
Test Description 1) Open ATP Windows application
2) Enter the username and password
Expected Results As long as internet connection exists, the ATP application redirects to the
dashboard

4.1.2 Login Success

Purpose The purpose of this test is to ensure that the System User can login to the
ATP
Application
External The user has a user account.
Dependencies
Test Description 1) Type the username and password into the web app login screen
2) Click the “Login” button
Expected Results The user is directed to the Dashboard

4.1.3 Incorrect Login Failure

Purpose The purpose of this test is to ensure that incorrect username and password
pairs do not allow the user to enter into ATP Application Dashboard
External External invalid username and password input
Dependencies
Test Description 1) Type the incorrect username and password pair into the windows app
login screen
2) Click the “Login” button
Expected Results Display Validation Message as ‘UserName and Password Pair is Incorrect’

4.2 ATP Interface – ATP Server Database

4.2.1 Invalid Product Input Data Result
Purpose The purpose of this test is to ensure that the ATP Interface can handle invalid
input data.
External Invalid data input by the user
Dependencies
Test Description 1) Check the user input data type with Database datatypes.
Expected Results The window system displays valid error message to user.

JBVNL_i~Easypay Project Page 6 of 8

Integration Plan

4.3 Admin Access – ATP Server Database

4.3.1 Login Success
Purpose The purpose of this test is to ensure that the Admin User can login to the
Admin Application.
External The user has an Admin account.
Dependencies
Test Description 1) Type the username and password into the Admin Application login screen
2) Click the “Login” button
Expected Results The user is directed to the Dashboard screen.

4.3.2 Incorrect Login Failure

Purpose The purpose of this test is to ensure that incorrect username and password
pairs do not allow the user to access the main features of the Admin
Application.
External The user knows an incorrect Admin account username and password pair.
Dependencies
Test Description 1) Type the incorrect username and password pair into the Admin
Application login screen
2) Click the “Login” button
Expected Results Display Validation Message as ‘Username And Password Pair is Incorrect”.

4.3.3 Add System User

Purpose The purpose of this test is to ensure that Application User accounts can be
verified and added.
External None
Dependencies
Test Description 1) Login to the Admin Application
2) Click “Masters -> Users”
3) Enter Required User Details in User Entry Screen.
4) Provide access permission to users based on Roles.
5) Perform the login access with the username and password.
Expected Results 1) No error message appears.
2) The same results from the Login Success test.

4.3.4 Remove System User

Purpose The purpose of this test is to ensure that Application user accounts can be
removed.
External Know the username and password of an existing Application user.
Dependencies
Test Description 1) Login to the Admin Application
2) Click “Masters -> Users”
3) Select an Application user account whose username and password you
know
4) Click on Deactivate the user option and click on save button.
5) Click the “Logout” button
7) Perform the Incorrect Login Failure test with the username and password.

JBVNL_i~Easypay Project Page 7 of 8

Integration Plan

Expected Results 1) No error message appears after step (5)

2) The same results from the Incorrect Login Failure test.

4.3.5 Change Admin User Password

Purpose The purpose of this test is to ensure that the password of an Admin User
account can be modified.
External Know the username and password of an Admin User.
Dependencies
Test Description 1) Login to the Admin Application.
2) Click on Admin Profile.
3) Click on Change Password.
4) Enter the existing password, a valid new password, and a confirmation of
the new password
5) Click the “Submit” button
6) Click the “Logout” button
7)Perform Incorrect login failure with the username and old password
8) Perform the login success with the username and new password
Expected Results 1) No error message appears after step (5)
2) The same results from the Incorrect Login Failure test after step (7)
3) The same results from the Login Success test after step (8)

JBVNL_i~Easypay Project Page 8 of 8