A PROJECT REPORT

ON

Easypay

By

AKASH J. GUPTA
DAYASHANKAR R. CHAUHAN

Towards The Partial Fulfillment of the

Bachelor of Computer ApplicationSEM-VI

SHAILENDRA EDUCATION SOCIETY’S

COMPUTER CENTER (SESCOM)
Mumbai 400 068

Tilak Maharashtra Vidyapeeth, Pune

Department of Computer Science

2019-2020
 CERTIFICATE

This is to certify that the project

Easypay
Has been satisfactorily completed by

AKASH J. GUPTA
DAYASHANKAR R. CHAUHAN

Towards The Partial Fulfillment of the ‘Bachelor of Computer

ApplicationSEM-VI’,For the Academic 2019-20 At Shailendra Education Society’s
Computer Center (SESCOM), Mumbai 400 068. Tilak Maharashtra Vidyapeeth, Pune
(Department of Computer Science), and it is approved.

Project Guide Examiner Head of Department

SESCOM-Mumbai 68
 ACKNOWLEDGEMENT

With immense please we are presenting “Easypay” Project report as part of the curriculum of
‘Bachelor of Computer Application’. We wish to thank all the people who gave us unending
support.

We express our profound thanks to our head of department MrBhushan Pimple,project

guideProf. R. H. Goheland project in-chargesand all those who have indirectly guided and
helped us in preparation of this project.

Akash J. Gupta
Dayashankar R. Chauhan
 INDEX

1. Introduction Page
1.1. Introduction To Easypay ………………………………………….. 1-2
1.2. Problem In Existing System ……………………………................ 2-3
1.3. Purpose Of The Easypay ………………………………................. 3
1.4. Scope Of These Easypay ………………………………………… 4

2. System Analysis
2.1.Need For Developing ……………………………………................ 5-6
2.2.System Specification ……………………………………………… 7-9
2.3.Process Models Used With Justification …………………………… 9-11
2.4.Design Principles & Methodology ………………………................ 11-15
2.5.System Architecture ……………………………………................. 16-17
2.6.The Genesis Of UML ………………………………………………. 18-20

3. Feasibility Study
3.1. Technical Feasibility ………………………………………......... 21-24
3.2. Economic Feasibility …………………………………............... 24-25
3.3. Operational Feasibility ………………………………………… 25-26

4. Software Requirement Specifications

4.1. Modules ……………………………………………………….. 27-32
4.2. Literature Survey …………………………………………….. 33-35
4.2.1. Introduction To Java Framework ………………………… 35-36
4.2.2. Java ………………………………………………………… 36-37
4.2.3. NetBeans IDE 8.1…………………………………………… 37-38
4.2.4. MySql Server ……………………………………………….. 39-40
5. System Design
5.1 . Introduction UML ……………………………………………. 41-42
5.2 UML Diagrams ………………………………………………. 42
5.2.1 Use Case Diagram ………………………………………... 43-45
5.2.2 Activity Diagram ………………………………………… 46-48
5.2.3 Collaboration Diagram …………………………................ 49-51
5.2.4 Sequence Diagram ………………………………............. 52-53
5.2.5 Class Diagram …………………………………................. 54-56
5.3 Gantt Chart …………………………………………............... 57
5.4 Data Dictionary ………………………………….................... 58-62

6. Screenshots …………………………………………………. 63-70

7. Testing
7.1. Psychology Of Testing ……………………………………............... 71-73
7.2. Testing Objectives …………………………………………………. 73
7.3. Levels Of Testing ………………………………………………….. 74
7.3.1. Unit Testing ………………………………………………. 74-75
7.3.2. Integration Testing ……………………………………….. 75
7.3.3. System Testing …………………………………………… 75-76
7.3.4. Validation Testing ………………………………………… 76
7.3.5. Output Testing ……………………………………………. 76-77
7.3.6. User Acceptance Testing …………………………………. 77-78

8. Conclusion ………………………………………….............. 79
9. Bibliography …………………………………………........... 80
 1 INTRODUCTION

1.1. INTRODUCTION TO EASYPAY

Easypay (formerly known as Easypay Money) is one of the best payment gateways to accept online
payments with minimal development effort, easy sign-up, and quick onboarding process. You can
start accepting payments securely and seamlessly within your Windows app, within minutes, with
our 100% online hassle-free on boarding process.

“Easy Pay” is digital payment gateway system. Which has aim to gives fast transactions with
security of money which is now a days very helpful for money transfer to any state any and country
in one click. This application provides various of payment system (mobile recharge, gas payment,
water bill, electricity bill, etc.) for customer and merchant get join easy pay. There is high level of
security in application . client comes to join by other reference or advertises by newspaper or
posters etc. Receptionist takes the join if the client wants to pay money using a easy pay by wallet ,
or if the merchant but you don’t have account on easy pay wants to register and join easy pay, the
receptionist will take enquiry from filled by client.

. Admin is giving all security it will be authorization to delete your account but not see your
password and payment withdrawal your account, Admin manages records. Admin offering new
offers by posters or other advertise processes. We have a customer care provides the notes to 24 x 7
for better learning. Customer care display the result by notice board. Admin advertise various
courses by advertises processes (posters, newspapers etc.). Admin hires new update for payment
system and receptionist for receptionists.

Any large, small, individual, trust, NGO, e Commerce, etc can easily register on EasyPay and use the
payment gateway for receiving online payments. The customers will get multiple payment options to
make a payment on the PayKun checkout.

1
The ways these payments are made can be cumbersome, error prone, and expensive. Growth, after
all, is often messy. Payments systems set up decades ago continue to be used sometimes retrofitted,
sometimes force-fitted—to meet the needs of modern corporations. processes to make optimal use of
them. Solution providers (both banks and non-banks) also face challenges, struggling to cobble
together old systems to meet new demands.

1.2. Problem In Existing System

Electronic Payment Gateway is present in our country but it’s not very secure. The existing
payment architecture was also lacking the security factor. Most people Doesn’t trust on online
shopping or online transaction because of security. Security is the main issues behind designing of
Gateway. That’s why the proposed architecture is made secure by the implementation of secure
electronic transaction methods. Because of this now only authentic customers can now buy products
from merchant’s site whose bank accounts is enough to buy the required product. At first it’s
checked if the customer is authorized one or not then the whole transaction takes place.

The electronic payment gateway is made secure enough that any authorized customer can easily
trust on it and fearlessly or confidently make payments over the Internet. If this system is to be
implemented in developing countries then strong support of government of that country is required
as there is not much awareness of electronic transaction in developing countries.

Since the actual processing of the data takes place on the remote client the data has to be transported
over the network, which requires a secured format of the transfer method. How to conduct
transactions is to be controlled by the client and advanced techniques implementing the
cryptographic standards in the executing the data transfer transactions. Present day transactions are
considered to be “un-trusted” in terms of security, i.e. they are relatively easy to be hacked. And also
we have to consider the transfer the large amount of data through the network will give errors while
transferring. Nevertheless, sensitive data transfer is to be carried out even if there is lack of an
alternative. Network security in the existing system is the motivation factor for a new system with
higher-level security standards for the information exchange.

People for long time have tried to sort out the problems faced in the general digital communication
system but as these problems exist even now, a secured and easy transfer system evolved and came

2
to be known as the Encryption and Decryption of the data and converting the file to audio format to
be transferred using the ryptographic standards and Steganography. The advantages of this Audio
Steganography are.

1.3. Purpose Of The Easypay

The project was designed to eliminate the long-standing problem of inefficiency and corruption in
the maintenance of land records at dispersed and poorly supervised .

Developing a Easypay is a digital payments platform that allows you to transfer cash into the
integrated wallet via online banking, debit cards, and credit cards, or even by depositing cash via
select banks and partners. Using the money in the Easypay wallet, you can pay for a number of
goods without using cash.

You can also use Easypay to pay for Mobile recharges, utility bill payments, book movie or travel
tickets among other things on this Easypay system . Using the money in the Easypay wallet, you can
pay for a number of goods without using cash. Among the transactions you can make on Easypay are
recharges for mobile phones, DTH cable, data cards, etc, as well as postpaid payments for mobile
phones, landline/ broadband, electricity, water and gas bills, etc.

In a cashless economy, all transactions are carried out using different types of payment methods and
this does not involve the physical use of money for the purchase of various goods and services.
Digital payment methods are often easy to make, more convenient and provide customers the
flexibility to make payments from anywhere and at anytime. These are a good alternative to
traditional methods of payment and speeden up transaction cycles.

When digital payments—whether on mobile phones, cards, or online —become available to

everyone, everyone in the economy can benefit from the outcomes! These include:

 Cost savings through increased efficiency and speed

 Transparency and security by increasing accountability and tracking, reducing corruption
and theft as a result
 Financial inclusion by advancing access to a range of financial services, including savings
accounts and insurance products

3
1.4. Scope Of These Easypay

What is meant by digital payment ?

Digital payment is a type of cashless payment where the payment is made through digital nodes.
These digital nodes are used by both, the payer and the payee. Also called electronic payment, no
hard cash or physical form of cash is used in digital payments. Digital payments are entirely made
online and they are convenient, instant, and time-saving.

In order to encourage and promote digital payments in India, the government of India has been
taking several steps. One such step is digital payments. The digital India payments is a part of Digital
India campaign. The aim of digital payment is to make India a paperless, cashless, and digitally
empowered economy.

When we talk about cash payments, we first have to withdraw cash from the bank account. Then, we
can use the cash to pay at stores, shops, etc. Lastly, the shopkeeper goes to the bank and deposits the
cash paid by you. This entire process is time-consuming. On the contrary, in digital payment, the
money is transferred directly from the payer’s bank account to the payee’s account instantly.

The digital payment system in India is convenient and offers the flexibility of making a payment
anytime and anywhere. This method has speeded up the transaction cycle. In addition, post
demonetization, people have slowly started taking the digital payment method. Today, even small
shop owners and small-time merchants are accepting digital payment.

Top 5 type of digital payment in india

1. Banking card (debit card & credit card)

2. Unstructures supplementary service data (USSD)
3. Aadhaar enabled Payment system (AEPS)
4. Unified Payment interface (UPI)
5. Mobile wallets (Paytm, Freecharge, Mobikwik etc.)

4
 2 System Analysis

2.1 Need For Developing

Thear maney of people living in india do not have bank accounts. But 75% have something
that could be just as good: This computer system have the capacity to make digital payments.

 Using a digital payment platform called bKash, People can send money easily and
inexpensively from one Computer wallet to another and receive cash payments at any one of
100,000 agents — mostly mom-and-pop stores — distributed throughout the country. Mobile
transactions always give you the next level of competition for perfection. Consumers are
getting more and more relied on the smart devices.
 Leading the race of smart devices, smart phones have made an impeccable space in the lives
of people.
 Not only the entertainment segment, but people are vigorously using the technology to buy
and sell everything ranging from grocery to booking tickets for their weekend getaway.
 Easy accessibility
 Using a mobile wallet for day to day transactions is really simple to begin with. Downloading
the app and creating a user ID and password is all you need to do here.
 It is as simple as logging in to your Gmail or Facebook account from your smartphone.
 Simple to load money
 You can add money to your wallet in easily via net banking, credit card or debit card.
 Being able to store these details saves you from the hassle of entering these details every time
you make a transaction and saves time.

.There are many reasons that the world's poorest people have not been considered attractive banking
customers. It's hard for banks to achieve sufficient margins of equity by processing smaller
transactions, and prohibitively expensive to do so when those transactions are made almost entirely
in cash.Digital payments jump right over these barriers. Poor households typically have high
transaction volumes — an attractive proposition for mobile carriers. And customers can build equity
and experience with formal banking by using cash-in cash-out systems operated by networks of

5
agents. Moreover, digital payment products are the ideal medium to reach a large customer base
across a wide territory. Thanks to scale, digital products can be both cheap and profitable.
Leading the race of smart devices, smart phones and computers have made an impeccable space in
the lives of people.

2.2. System Specification

Digital payment methods are often easy to make, more convenient and provide customers the
flexibility to make payments from anywhere and at anytime. These are a good alternative to
traditional methods of payment and speeden up transaction cycles. Post demonetization, people
slowly started embracing digital payments and even small time merchants and shop owners started
accepting payments through the digital mode.

Software Requirement

 Windows Xp,Windows 7, Windows 10(ultimate,enterprice)

 MySql
 Netbeans

Hardware Requirement

 Hard Disk - 5 GB
 Memory -1 GB

Digital Payment
Digital payment occurs when goods or services are purchased through the use of various electronic
mediums. There is no use of cash or cheques in this type of payment method.

6
Requirements for Digital Payment Systems

The success or failure of any on-line payment systems depends not only on technical issues but also
on user’s acceptance. The user’s acceptance depends on a number of issues such as advertisement,
market position, user preferences etc.

1. Atomicity

Atomicity guarantees that either the user’s on- line payment transaction is completed or it does not
take place at all. If the current on-line payment transaction fails then it should be possible to recover
the last stable state. This feature resembles the transactional database systems, in which either a
transaction is committed or rolled back.

2. Anonymity/Privacy

Anonymity suggests that the identity, privacy and personal information of the individuals using the
on- line payment methods should not be disclosed. In some on- line payment methods, it is possible
to trace the individual’s payment details. In case of purchases using Debit Card, it is possible to find
out the purchase details as that information is registered at the vendor and the bank’s databases. So
some on- line payment systems like

3. Scalability

As the on- line payment methods are getting more and more acceptance of the users, the demand for
on- line payment infrastructure will also be increasing rapidly. Payment systems should handle the
addition of users without any performance degradation. To provide the required quality of service
without any performance degradation, the payment systems need a good number of central servers.
The central servers are needed to process or check the payment transactions. The growing demand
for the central servers, limits the scalability of the on- line payment systems.

4. Security

Security is one of the main concerns of the on- line payment methods and it is one of the crucial
issues which decide the general acceptance of any on- line payment methods. Internet is an open
network without any centralized control and the on- line payment systems should be protected
against any security risks to ensure a safe and reliable service to the users.

7
When users are paying on- line they want to be sure that their money transaction is safe and secure.
On the other hand, banks and payment companies and other financial institutions want to keep their
money, financial information and user information in a secure manner to protect it against any
possible misuse.

5. Reliability

As in any other business activity, even in on- line payment methods, the user expects a reliable and
an efficient system. Any on- line payment system would fail, despite of it’s advanced technological
features, if it fails to get the users acceptance and pass their reliability tests. There are many reasons,
which can make the system unreliable to the users. Some of them are Security threats, poor
maintenance and unexpected breakdowns.

6. Usability

Usability is an important characteristic of an interactive product like on- line payments. On-line
payment systems should be user friendly and easy to use. Any on- line payment system with
complicated procedures, complex payment process and other associated complications with the
payment environment, can’t get users acceptance. Poor usability of a web shopping or a payment
method could also discourage on- line shopping. To make the online payments simple and user
friendly, some of the on- line payment systems allow the users to make payments with minimum
authorization and information inputs.

7. Inter operability

In on- line payment Technologies, different users prefer different payment systems. The different
payment systems use different kinds of currencies and the payment systems should support
interoperability between them. If a payment system is inter operable, then it is open and allows other
interested parties to join without confining to a particular currency. In the real life situation, there
should be some sort of mutual agreement between various on- line payment systems to provide the
interoperability. Interoperability can be achieved by the means of open standards for data
transmission protocols and infrastructure. An interoperability system can gain much acceptance and
high level of applicability than individually operating payment systems.

Because of the rapid technological changes, it’s not always easy to get interoperability between
various payment systems.

8
2.3. Process Models Used With Justification

What is Easypay?

Easypay is India’s first computer payments, e-wallet, and commerce platform. Though started as a
recharge platform in 2020, Easypay has subsequently changed its business model to a marketplace
and a virtual bank model. It is also one of the pioneers of the cashback business model.
The company has transformed itself into one of the Indian giants dealing in mobile payments,
banking services, marketplace, gold, recharge and bill payments, etc. who serve around 100 million
registered users.

Model of Easypay

Easypay Business Model is a marketplace-cum-payments-bank business model which also deals in

recharge & bill payments and provide users with an e-wallet and reservation/booking options.

Easypay Revenue Model can be divided into following categories.

1. Recharge Services
2. Bill Payments
3. Payment Solutions
4. Easypay Wallet
5. Easypay Bank

Recharge Services

There was a time when Easypay Business Model consisted just mobile recharge and bill payment
services. Times have changed and online recharge services for pc subscriptions, TV channels
subscriptions, data-card, and metro card, etc have been added to the revenue model of Easypay.

The company, just like other recharge services providers, charge commissions from these operators.

Bill Payment

In addition to the recharge facilities, the customers can even pay their electricity, telephone, water,
mobile, broadband, gas, etc. bills on Easypay. Apart from these, Easypay has also partnered with
several education and financial organizations and act as a portal to accept education fees and
insurance instalments.

9
Revenue, just like recharge services, is generated by charging commissions from these providers.

Payment Solutions

Easypay offers smart payment solutions for online businesses. The payment solutions allow them to
accept online payments through Easypay.The payment option comes with no setup fee and
maintenance charges. However, the company charges a commission of 1.99% on every transaction.

Easypay Wallet

Cashbacks are credited to the users in their Easypay wallets. Easypay has already rolled out its new
marketing strategy where it has planned to focus more on the digital currency prospects. Hence, all
of its core marketing and promotional strategies enforce the use of Easypay Wallet. This is a very
clever move as Easypay will get the first mover advantage and through its extensive distribution
strategy (which is far better than its competitors like Freerecharge, Ola Money, etc.), will be able to
increase its brand preference. This will eventually help it to carry out its future plans.

What exactly is Easypay wallet?

Easypay wallet is a semi-closed wallet (approved by RBI) used to store currency in digital form
which can be used to buy goods and services (including financial services) at identified merchant
locations or establishments (like petrol pumps, a supermarket, your barber’s shop, movie hall, etc.)
which have a specific contract with the company to accept these payment instruments.Easypay wallet
doesn’t permit cash withdrawal.

How does Easypay earn through Easypay wallet?

Easypay wallet can be used to pay for almost anything, everywhere. It has created a new market for
digital currency users because of its ease of use.

Money can be transferred between the Easypay wallets of two users with just a few taps on the
pc.As per the RBI guidelines, the money deposited by users in Easypay wallet is deposited by
Easypay in an Escrow Account with a partner bank. This escrow account deposit fetches Easypay
certain interest which is decided as per the contract between the bank and Easypay.

10
Easypay Bank

Paytm wallet is no more just a semi-closed wallet. The company has revamped itself as a payments
bank.A payments bank is a digital bank which can accept deposits and give out interests on the
deposits but can’t offer loans to its customers.

2.4 Design Principles & Methodology

Data Flow Diagram

A data flow diagram is graphical tool used to describe and analyze movement of data through a
system. These are the central tool and the basis from which the other components are developed.
The transformation of data from input to output, through processed, may be described logically and
independently of physical components associated with the system. These are known as the logical
data flow diagrams. The physical data flow diagrams show the actual implements and movement of
data between people, departments and workstations. A full description of a system actually consists
of a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation
develops the data flow diagrams. Each component in a DFD is labeled with a descriptive name.
Process is further identified with a number that will be used for identification purpose. The
development of DFD’S is done in several levels. Each process in lower level diagrams can be
broken down into a more detailed

DFD in the next level. The lop-level diagram is often called context diagram. It consists a single
process bit, which plays vital role in studying the current system. The process in the context level
diagram is exploded into other process at the first level DFD. The idea behind the explosion of a
process into more process is that understanding at one level of detail is exploded into greater detail at
the next level. This is done until further explosion is necessary and an adequate amount of detail is
described for analyst to understand the process.

Larry Constantine first developed the DFD as a way of expressing system requirements in a
graphical from, this lead to the modular design.

11
A DFD is also known as a “bubble Chart” has the purpose of clarifying system requirements and
identifying major transformations that will become programs in system design. So it is the starting
point of the design to the lowest level of detail. A DFD consists of a series of bubbles joined by data
flows in the system.

DFD SYMBOLS:

In the DFD, there are four symbols

1. A square defines a source(originator) or destination of system data

2. An arrow identifies data flow. It is the pipeline through which the information flows

3. A circle or a bubble represents a process that transforms incoming data flow into outgoing data

CONSTRUCTING A DFD:

Several rules of thumb are used in drawing DFD’S:

1. Process should be named and numbered for an easy reference. Each name should be
representative of the process.

2. The direction of flow is from top to bottom and from left to right. Data traditionally flow from
source to the destination although they may flow back to the source. One way to indicate this is to
draw long flow line back to a source. An alternative way is to repeat the source symbol as a
destination. Since it is used more than once in the DFD it is marked with a short diagonal.

3. When a process is exploded into lower level details, they are numbered.

4. The names of data stores and destinations are written in capital letters. Process and dataflow
names have the first letter of each work capitalized

12
1.Zero level Data Flow Digram

Enroll get service

User Service provider
0

Invoice Easypay Service provide

Report

Admin

13
2.Level 1 Data Flow Diagram

1.0
Credential
user Login/registration User Table
s validate

. Validate user

Provider
1.1
Add Bank Bank Details Select
Payment
mode
Select payment service provider

Wallet Table Sand request

Give detail Available bill 1.2

Electricity
pay
1.5
1.3
Wallet Source of payment
Check Bill
Details History report

User Table Credentials validate

Validate Credentials validate
Validate Credentials validate 1.4

Bill
Payment

Admin

14
2.Level 2 Data Flow Diagram

user Home Page

2.0

Bill pay

2.1

Water bill

provider

2.2

Bill 2.4
generation
Bill details

2.3
EWTB History report
Payment

15
2.5 System Architecture

ER Diagram

-Diagram, which not only

specifics the existential entities but also the standard relations through which the system exists and
the cardinalities that are necessary for the system state to continue.

ERD is the notation that is used to conduct the date modeling activity the attributes of each data
object noted is the ERD can be described resign a data object descriptions.

The primary purpose of the ERD is to represent data objects and their relationships.

An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database. An
entity in this context is an object, a component of data. An entity set is a collection of similar entities.
These entities can have attributes that define its properties.

By defining the entities, their attributes, and showing the relationships between them, an ER diagram
illustrates the logical structure of databases.
ER diagrams are used to sketch out the design of a database

16
 Password Mobile No
U_ID rdd
Prepaid
Name E-mail
Postpaid

User Paid
A/c No 1
Mobile no
Bank
Name m User ID
Bank
Details

Payment n Amount
Mode Recharge
1 Branch 1
MTNL
Bank
Ifsc code
1 Operator
A/c Type
Add Us_ID has
Money
Balance

Saving jio
m Current Idea
1
Wallet pay Payment airtel
Money 1 Money m

U_Name
User_ID

Mobile No
W-Balance

17
2.6. The Genesis Of UML

The first object-oriented language is generally acknowledged to be Simula-67, developed by Dahl

and Nygaard in Norway in 1967. This language never had a large following, but its concepts were a
major inspiration for later languages. Smalltalk became widely available in the early 1980s, followed
by other object-oriented languages such as Objective C, C++, and Eiffel in the late 1980s. Object-
oriented modeling languages appeared in the 1980s as methodologists, faced with a new genre of
object-oriented programming languages and increasingly complex applications, began to experiment
with alternative approaches to analysis and design. The number of object-oriented methods increased
from fewer than 10 to more than 50 during the period between 1989 and 1994.

Many users of these methods had trouble finding a modeling language that met their needs
completely, thus fueling the so-called method wars. A few methods gained prominence, including
Booch's method, Jacobson's OOSE (Object-Oriented Software Engineering), and Rumbaugh's OMT
(Object Modeling Technique). Other important methods included Fusion, Shlaer-Mellor, and Coad-
Yourdon. Each of these was a complete method, although each was recognized as having strengths
and weaknesses. In simple terms, the Booch method was particularly expressive during the design
and construction phases of projects; OOSE provided excellent support for use cases as a way to drive
requirements capture, analysis, and high-level design; and OMT was most useful for analysis and
data-intensive information systems.

As we began our unification, we established three goals for our work:

1. To model systems, from concept to executable artifact, using object-oriented techniques

2. To address the issues of scale inherent in complex, mission-critical systems
3. To create a modeling language usable by both humans and machines

Devising a language for use in object-oriented analysis and design is not unlike designing a
programming language. First, we had to constrain the problem: Should the language encompass
requirements specification? Should the language be sufficient to permit visual

programming? Second, we had to strike a balance between expressiveness and simplicity.

18
Too simple a language would limit the breadth of problems that could be solved; too complex a
language would overwhelm the mortal developer. In the case of unifying existing methods, we also
had to be sensitive to the installed base. Make too many changes and we would confuse existing
users; resist advancing the language and we would miss the opportunity to engage a much broader
set of users and to make the language simpler. The UML definition strives to make the best trade-
offs in each of these areas.

The UML effort started officially in October 1994 when Rumbaugh joined Booch at Rational. Our
project's initial focus was the unification of the Booch and OMT methods. The version 0.8 draft of
the Unified Method (as it was then called) was released in October 1995. Around the same time,
Jacobson joined Rational and the scope of the UML project was expanded to incorporate OOSE. Our
efforts resulted in the release of the UML version 0.9 documents in June 1996. Throughout 1996, we
invited and received feedback from the general software engineering community. During this time, it
also became clear that many software organizations saw the UML as strategic to their business.

We established a UML consortium, with several organizations willing to dedicate resources to work
toward a strong and complete UML definition. Those partners contributing to the UML 1.0 definition
included Digital Equipment Corporation, Hewlett-Packard, I-Logix, Intellicorp, IBM, ICON
Computing, MCI Systemhouse, Microsoft, Oracle, Rational, Texas Instruments, and Unisys. This
collaboration resulted in the UML 1.0, a modeling language

that was well-defined, expressive, powerful, and applicable to a wide spectrum of problem domains.
Mary Loomis was instrumental in convincing the Object Management Group (OMG) to issue a
request for proposals (RFP) for a standard modeling language. UML 1.0 was offered for
standardization to the OMG in January 1997 in response to their RFP.

Between January 1997 and July 1997, the original group of partners was expanded to include
virtually all of the other submitters and contributors of the original OMG response, including
Andersen Consulting, Ericsson, ObjecTime Limited, Platinum Technology,

Eykholt of Rational, to formalize the UML specification and to integrate the UML with other
standardization efforts. A revised version of the UML (version 1.1) was offered to the OMG for

19
standardization in July 1997. In September 1997, this version was accepted by the OMG Analysis
and Design Task Force (ADTF) and the OMG Architecture Board and then put up for vote by the
entire OMG membership. UML 1.1 was adopted by the OMG on November 14, 1997.

For several years, UML was maintained by an OMG Revision Task Force, which produced versions
1.3, 1.4, and 1.5. From 2000 to 2003, a new and expanded set of partners produced an updated
specification of UML, version 2.0. This version was reviewed for a year by a Finalization Task Force
(FTF) headed by Bran Selic of IBM, and the official version of UML 2.0 was adopted by the OMG
in early 2005. UML 2.0 is a major revision of UML 1 and includes a large number of additional
features. In addition, many changes were made to previous constructs based on experience with the
previous version. The actual UML specification documents .

UML is the work of a large number of individuals, and the ideas in it come from a wide range of
previous works. It would be a major historical research project to reconstruct a complete list of
sources, and even more difficult to identify the many predecessors who have influenced UML in
manners large and small. As with all scientific research and engineering practice, UML is a small hill
atop a large mountain of previous experience.

20
 3 Feasibility Study

Due to the availability and acceptance by consumers, the computer is expected to be the best carrier
of payment functionalities and to replace the use of cash money It is seen as a very suitable
technology to replace cash, since it provides convenience and computers have an important role in
the daily life of consumers. Due to the costs involved with cash money, like storage, theft and errors,
retailers are looking for methods to reduce cash payment volumes.

The actual development and acceptance of computer payments in the markets around the world have
not met the expectations yet however. Only in very specific markets computer payments have
reached mass market, but in most European markets no large success has been reported. When
looking at the Netherlands, several attempts to introduce computer payments have been made, but
most failed and disappeared again, others only have reached small niche markets. Why is the
development in the Dutch market so difficult and slow?

Several solutions for computer payments with Near Field Communication (NFC) technology could
be feasible in the Netherlands. NFC computer payments are made by holding a smartphone very
close to a reader in a shop. However, contactless payments with cards will also be taken into
account, since they use similar technology and require the same acceptance infrastructure. Three
main solutions have been determined and will be analysed as possible implementations to introduce
NFC payments in the Dutch market on a short term:

3.1. Technical Feasibility

In this work, the technical feasibility of passive secure payments for brick-and-mortar points of sale
is analyzed. The core element of the proposed approach is a new application for

context-based risk and trust assessment. It allows for dynamic selection of payment authorization
methods that constitutes accurate trade-off between security and convenience. Particularly, the
payments can be performed and authorized in the

21
-17-Due to the availability and acceptance by consumers, the computer is expected to be the best

carrier of payment functionalities and to replace the use of cash money It is seen as a very suitable
technology to replace cash, since it provides convenience and computers have an important role in
the daily life of consumers. Due to the costs involved with cash money, like storage, theft and errors,
retailers are looking for methods to reduce cash payment volumes. The actual development and
acceptance of computer payments in the markets around the world have not met the expectations yet
however. Only in very specific markets computer payments have reached mass market, but in most
European markets no large success has been reported. When looking at the Netherlands, several
attempts to introduce computer payments have been made, but most failed and disappeared again,
others only have reached small niche markets. Why is the development in the Dutch market so
difficult and slow?

Several solutions for computer payments with Near Field Communication (NFC) technology could
be feasible in the Netherlands. NFC computer payments are made by holding a smartphone very
close to a reader in a shop. However, contactless payments with cards will also be taken into account,
since they use similar technology and require the same acceptance infrastructure. Three main
solutions have been determined and will be analysed as possible implementations to introduce NFC
payments in the Dutch market on a short term:
In this work, the technical feasibility of passive secure payments for brick-and-mortar points of sale
is analyzed. The core element of the proposed approach is a new application for context-based risk
and trust assessment. It allows for dynamic selection of payment authorization methods that
constitutes accurate trade-off between security and convenience. Particularly, the payments can be
performed

background using biometric means (face recognition), without user’s explicit action. Generally, in
the proposed approach, multiple devices are used for authorization: mobile, wearables, or stationary,
client’s or seller’s, and multiple authorization methods are used: biometric, knowledge-based, and
possession-based. The reported research includes requirement identification, novel architecture and
protocol proposition, proof-of-concept prototype system deployment, and evaluation-based lessons
learned. The research confirms that with the proposed approach, it is possible to take advantage of
client-seller trust dynamism to simplify the payment process while maintaining the security level.

bought every day in the same café on the way to work, quick lunch at a self-service restaurant near
the office, or a few times a month, the fuel payment at a neighbor gas station. Despite the fact that

22
the recurring transactions usually involve small amounts, there are also medium- or high-amount
ones, so that they constitute a larger set of operations than those that could be conveniently handled
using a contactless smart card.

The simplification of the payment process concerns reducing its execution time and minimizing the
number of operations required to be performed by the client. Analyzing the sequence of actions
required by a traditional contactless payment procedure, it is clear that simplification of this process
is possible only by eliminating the need to authorize the payment by the client. In such scenario, the
client orders products/services, receives them, and leaves without having to search for the wallet and
pulling out her payment card or any other attribute necessary to authorize the payment. Payments
made in this way are referred to as passive payments in this article. If a process of passive payment
authorization does not require communication with user’s device, it is referred to as passive
deviceless payment. In the proposed concept, the decision how to authorize the payment (passively
or actively; with biometrics, possession, or knowledge; choice of a specific method from these
classes; choice of the device) is done by a payment operator (e.g., a bank, a payment platform) on
behalf of the client.

In this paper, requirement identification is followed by a proposal of a system architecture that

enables passive deviceless payments, a listing of technologies which could be used to build such a
system, and conclusions from a proof-of-concept prototype deployment. The construction of such a
system requires defining a sequence of operations that eliminates payment authorization on the client
side and allows for making it on the payment operator side. Therefore, it is necessary to introduce a
phase of user identification, performed by the operator and transparent for the client, i.e., passive, to
avoid offsetting the benefits of payment process automation.

Regardless of the functional requirements, it is important to ensure practical applicability of the

developed solution and take into account existing alternatives. It can be assumed that market
adoption is difficult if the new solution does not offer anything more than just technical innovations.
Therefore, another requirement for the developed system is to provide all the actors of the payment
process: the client, the seller, and the operator of the payment system with appropriate added value.

The assumed goals of this work are the following:

To validate specification of a system that enables context-aware passive payments for physical point
of sale (PoS)

23
To prove added value provided by the system to each of the three actors: the client, the seller, and the
payment operator

3.2. Economic Feasibility

The digital economy is rapidly developing worldwide. It is one of the most important drivers of
innovation, competitiveness and growth. Digital technologies and big data now allow financial
service providers to more effectively serve the financially excluded, with a “customer-centric”
approach. By announcing a ban on the old Rs. 1,000 and Rs. 500 notes and by putting a cap on
withdrawals from banks and ATMs, Prime Minister Narendra Modi floated the idea of a cashless
society. The demonetization move that initially paralyzed the economy is now catalyzingthe
country’s digital payments ecosystem. We are witnessing an economic transition right now.

India aims to create a cleaner, more transparent economy via digitalization that will lead to an
improved climate for foreign investment, boost economic growth, and ultimately propel the
country to the next chapter of its emerging markets story. The long-term impact will be a
paradigmshift to the digital fintech platforms.

According to a study, "The cost of cash places a huge burden on the Indian economy equivalent to
1.7 per cent of gross domestic product (GDP). This high cost of cash stems fromlarge volumes of
cash flow in the Indian economy. Global consulting firm McKinsey has said digital finance is a $700
billion opportunity for India, offering 11.8 per cent boost to GDP by 2025,benefitting millions of
people. Digital financial services delivered via mobile phones, the Internet or cards linked to a
digital payment system could be a boon to individuals, businesses, and governments across the
developing world boosting GDP and making the aspiration of financial inclusion a reality.

A few months ago, I blogged about the intersection of social protection and financial inclusion and
wondered if these regular, consistent payments from governments could be a catalyst for bringing
beneficiaries more easily into the formal financial system. Digital

24
payments hold particular promise, and the key question is: What is the cost-benefit for a government
to connect all households to an Digital payment system.

3.3. Operational Feasibility

There’s disruption happening in the Indian payments space. Since demonetisation took place a year
before, both banks and e-wallets are aggressively promoting digital payments. And, many
individuals who were happy using cash have had to go the digital way. It’s not easy.

While everything is just ‘a click’ or ‘a scan’ away sounds great, it comes with a host of issues.
Individuals new to a digital payment system can end up transferring money to a wrong account. Or
as happens sometimes, transactions simply fail.

Digital payments have evolved hugely in recent years, with contactless payment cards technology
and the emergence of new services from financial and technology players changing the way
individuals and businesses conduct financial transactions.

There is much more to come, though. Continuing and fierce competition in the financial services
sector, demographic changes and the adoption of emerging technology, are all playing a role.

As we enter a new year, we’ve come up with the three trends that we think are most likely to impact
digital payments in 2019 and beyond.

1. Mobile banking reaches another level

While the uptake of mobile payments has been slower than expected , this is likely to change as open
banking and the greater availability of APIs lay the way for improved customer experiences beyond
the functional elements offered by most mobile payments apps.

These developments will enable payments players to bring together the power of mobile technology,
the wider technology ecosystem and data sharing to deliver better payments experiences. Services
such as immediate rewards and proactive balance alerts will provide value beyond the transactions.

25
2. The influence of Gen Z continues to grow

Generation Z, the age group following the Millennials, is making its presence felt in the workplace
and wider global economy. This generation have never known a world without Google, Apple,
Facebook and Amazon and are comfortable with digital technology.

These young adults and older teens will soon represent a significant proportion of the payments
industry customer base.

This age group is also interested in digital tools to manage payments, bills, expenses and personal
finance. More Gen Z consumers (69 per cent) use mobile banking apps daily or weekly than any
other generation. They are likely to be the first generation to forego a physical wallet in favour of a
digital one.

As an example of their thirst for faster payment methods, as well as personal control, 68 per cent of
Generation Z consumers surveyed by Accenture said they were interested in instant person-to-person
payments – more than any other group.

3. Greater industry collaboration

Fintech companies are now more willing to work with traditional financial services providers and
retailers, while banks are starting to innovate like fintech players.

Banks are embracing connected networks to multiply impact, and to collaborate in new and
disruptive ways. According to Accenture, these ecosystems will result in new payment routes, bank
networks and alternative forms of payment.

26
 4 Software Requirement Specifications

The software, Site Explorer is designed for management of web sites from a remote location.

INTRODUCTION

Purpose: The main purpose for preparing this document is to give a general insight into the analysis
and requirements of the existing system or situation and for determining the operating characteristics
of the system.

Scope: This Document plays a vital role in the development life cycle (SDLC) and it describes the
complete requirement of the system. It is meant for use by the developers and will be the basic
during testing phase. Any changes made to the requirements in the future will have to go through
formal change approval process.

4.1. Modules

 User Module
 Admin module

 User Module

User Login :- A Easypay login defines a name and a password for a user to allow access to Adaptive
Server. When you execute create login, Adaptive Server adds a row to assigns a unique system user
ID (suid) for the new user, and fills in specified attribute information. When a user logs in, Adaptive
Server looks in syslogins for the name and password

provided by the user. The password column is encrypted with a one-way algorithm so it is not
readable.A easypay login profile is a collection of attributes to be applied to a set of login accounts.
The attributes define login characteristics, such as default roles or the login script associated with

27
each login bound to the profile. Easypay Login profiles save save time for the system security
administrator because attributes of login accounts are set up and managed in one place.

User Ragistration :- A registered user is a user of a Easypay or other system who has
previously registered. Registered users normally provide some sort of credentials (such as a
username or e-mail address, and a password) to the system in order to prove their identity: this is
known as logging in. Systems intended for use by the general public often allow any user to register
simply by selecting a register or sign up function and providing these credentials for the first time.
Registered users may be granted privileges beyond those granted to unregistered users.

Rationale :-User registration and login enables a system to personalize itself. For example, a
website might display a welcome banner with the user's name and change its appearance or behavior
according to preferences indicated by the user.

-
The system may also allow a logged-in user to send and receive messages, and to view and modify
personal files or other information

28
Privacy concerns :- Registration necessarily provides more personal information to a system than it
would otherwise have. Even if the credentials used are otherwise meaningless, the system can
distinguish a logged-in user from other users and might use this property to store a history of users'
actions or activity, possibly without their knowledge or consent.

Easypay Payment Mode

1. Recharge Services
2. Bill Payments
3. Paytm Wallet
4. Paytm Bank

Recharge Services :- There was a time when Easypay Business Model consisted just mobile

recharge and bill payment services. Times have changed and online recharge services for mobile
subscriptions, TV channels subscriptions, data-card, and metro card, etc have been added to the
revenue model of easypay.

The company, just like other recharge services providers, charge commissions from these operators.

29
Bill Payments:- In addition to the recharge facilities, the customers can even pay their electricity,

telephone, water, mobile, broadband, gas, etc. bills on Easypay. Apart from these, Paytm has also
partnered with several education and financial organizations and act as a portal to accept education
fees and insurance instalments.

Easypay Wallet :- Easypay wallet is a semi-closed wallet used to store currency in digital form
which can be used to buy goods and services (including financial services) at identified merchant
locations or establishments (like petrol pumps, a supermarket, your barber’s shop, movie hall, etc.)
which have a specific contract with the company to accept these payment instruments.Easypay wallet
doesn’t permit cash withdrawal.

30
Admin module
Application Administrators aren't developers and they're not users, but they are critical to keeping the
applications your organization relies on running. They install, update, tune, diagnose, and babysit
both internal and third-party applications.

The applications they support can include ERP (Enterprise Resource Planning), CRM (Customer
Relationship Management), POS (Point of Sale), BPM (Business Process Management), budgeting
and forecasting, HR (Human Resources), legal matter management, AP (Accounts Payable)/ AR
(Accounts Receivable), payroll, general ledger, SOX (Sarbanes Oxley) compliance tracking,
training, time tracking, supply chain, database engines, and messaging, i.e., e-mail.

While software can be readily licensed from a vendor, it still requires a significant amount of effort
on the part of the acquiring organization. Someone has to prepare the servers that it will run on.

Then someone has to install it, configure it, load data into it, tune it, upgrade it, and generally keep
the package up and running.

31
If errors occur, someone has to report them to the vendor and work with vendor technicians to
correct the prob- lems. These are all tasks that an Application Administrator handles.

In many cases, corporations are absolutely dependent that these applications be kept running. What
would be the response of employees if the payroll application broke down?

What would happen to the organization's financial situation if invoices weren't sent out to customers?
What if new employees couldn't be added to the HR system?

The importance of Application Administrators and their level of expertise shouldn't be over- looked.
Since the trend of relying upon third-party software isn't going to decrease in the foreseeable future,
the role of Application Administrator won't be going away either.

Every company employs them even if their official job title doesn't sound at all like "Application
Administrator." A job title of "system application administrator" might be for a position that covers
both application administration and systems administration. Since there is a significant degree of
overlap between these two positions, this isn't uncommon.

32
4.2 Literature Survey

“Easy Pay” is digital payment gateway system. Which has aim to gives fast transection with security
of money which is now a days very helpful for money transfer to any state any and country in one
click. This application provides various of payment system (mobile recharge, gas payment, water
bill, electricity bill, etc.) for customer and merchant get join easy pay. There is high level of security
in application . client comes to join by other reference or advertises by newspaper or posters etc.
Receptionist takes the join if the client wants to pay money using a easy pay by wallet , or if the
merchant but you don’t have account on easy pay wants to register and join easy pay, the
receptionist will take enquiry from filled by client.

Admin is giving all security it will be authorization to delete your account but not see your password
and payment withdrawal your account, Admin manages records. Admin offering new offers by
posters or other advertise processes. We have a customer care provides the notes to 27 x 7 for better
learning. Customer care display the result by notice board. Admin advertise various courses by
advertises processes (posters, newspapers etc.). Admin hires new update for payment system and
receptionist for receptionists Saves time: digital wallets hold the amount in the electronic form so as
to ease the payment.

Security: There is a good amount of security when payments are made through e wallets since the
wallet does not pass the payment card details to the website. These virtual wallets allow users to lock
their wallet.

Objective of Study
Improve the ease of conducting card/digital transactions for an individual.
Reduce the risks and costs of handling cash at the individual level.
Reduce costs of managing cash in the economy.
Build a transactions history to enable improved credit access and financial inclusion.
Reduce tax avoidance.
Reduce the impact of counterfeit money

Scope:

33
Provide access to financial payment services to every citizen along with ability to conduct card /
digital transactions.
Digitalize Government collections by equipping each collection point with a method to accept
card/digital payments.
Migrate payment transactions from cash dominated to non-cash through incentivization of card
digital transactions and disincentivization of cash based transactions.
Enhance acceptance infrastructure in the country to promote digital transactions.

Encourage corporate, institutions and merchant, establishments to facilitate card / digital payments.

Goal:
The goal of the proposed policy changes is to provide the necessary incentives to use digital financial
transactions to replace the use of cash-either in government transactions, or in regular commerce
over a period of time through policy intervention.

RESEARCH METHODOLOGY

The current study is based on primary data collected from 150 respondents from the different parts of
Delhi. A well-structured questionnaire was designed to collect the information from the respondents
the questionnaire was designed to study perception of customer towards adoption of digital payment
mode. Likert five point scales were used for obtaining responses. The responses have been collected
by means of face-to-face interviews by authors.

Sampling Plan

Sampling unit: This call is for defining the target population to be surveyed. In this research the

sampling unit was the customers who have been using the digital payment modes.

Sample size: In this survey the sample size decided was 150.

Sampling procedure: We adopted Intercept interview method for collection of primary data, as it
is not possible to take appointment from a large number of respondents. Purpose of this research was
told to respondents and questions were explained to them in case there was any need for
understanding any particular question. There had been no personal bias or distortions were allowed
while recording the responses.

34
Research and Statistical Tools Employed

The research and statistical tools employed in this study are ANOVA and frequency analysis. SPSS
19 was used to perform statistical analysis. Cronbach’s Alpha test was used to find the reliability of
the data. Frequency analysis on the main factor under study, indicate overall satisfaction levels of
respondents with digital payment mode. ANOVA was carried out to find the variance in the
responses and to test the hypothesis.

4.2.1.Introduction of Java frameworks

Java Frameworks are the bodies of pre-written code through which you are allowed to add your own
code. But there are a lot of frameworks out there which have various applications. So, in this article,
I’ll discuss the top 10 Java frameworks you should master.

Let’s look at the topics to be covered in this article:

 What are Java frameworks?

 Top Java frameworks used
o Spring
o Hibernate
o Struts
o Google web toolkit [GWT]
o Java Server Faces [JSF]
o Grails
o Vaadin
o Blade
o Dropwizard
o Play

Let’s get it started!

What are Java frameworks?

Frameworks are large bodies of pre-written code to which you add your own code in order to solve a

35
problem. You make use of a framework by calling its methods, inheritance, and supplying callbacks,
listeners, or other implementations of the patterns.

A framework will often dictate the structure of an application. Some frameworks even supply so
much code that you have to do very little to write your application. This can be good or bad,
depending on how easy it is to use. Frameworks are the substance of programming. You build on top
of a good one, your program is solid and fast and comes together beautifully. You build on top of a
bad one, your life is miserable, brutish, and short.

4.2.2.Java

Java is a popular programming language, created in 1995.

It is owned by Oracle, and more than 3 billion devices run Java.

It is used for:

 Mobile applications (specially Android apps)

 Desktop applications
 Web applications
 Games
 Database connection

 And much, much more!

 Web servers and application servers

Why Use Java?

 Java works on different platforms (Windows, Mac, Linux, Raspberry Pi, etc.)
 It is one of the most popular programming language in the world
 It is easy to learn and simple to use
 It is open-source and free
 It is secure, fast and powerful
 It has a huge community support (tens of millions of developers)

36
  Java is an object oriented language which gives a clear structure to programs and allows code
to be reused, lowering development costs
 As Java is close to C++ and C#, it makes it easy for programmers to switch to Java or vice
versa

Wat is Java

Java produces applets (browser-run programs), which facilitate graphical user interface (GUI) and
object interaction by Internet users. Prior to Java applets, Web pages were typically static and non-
interactive.

Java applets run in a Web browser with Java Virtual Machine (JVM), which translates Java bytecode
into native processor instructions and allows indirect OS or platform program execution. JVM
provides the majority of components needed to run bytecode, which is usually smaller than
executable programs written through other programming languages. Bytecode cannot run if a system
JVM.

4.2.3. NetBeans IDE 8.1

Best Support for Latest Java Technologies

NetBeans IDE is the official IDE for Java 8. With its editors, code analyzers, and converters, you can
quickly and smoothly upgrade your applications to use new Java 8 language constructs, such as
lambdas, functional operations, and method references.

Batch analyzers and converters are provided to search through multiple applications at the same
time, matching patterns for conversion to new Java 8 language constructs.

With its constantly improving Java Editor, many rich features and an extensive range of tools,
templates and samples, NetBeans IDE sets the standard for developing with cutting edge
technologies out of the box.

37
Fast & Smart Code Editing

An IDE is much more than a text editor. The NetBeans Editor indents lines, matches words

and brackets, and highlights source code syntactically and semantically. It lets you easily refactor
code, with a range of handy and powerful tools, while it also provides code templates, coding tips,
and code generators.

Easy & Efficient Project Management

Keeping a clear overview of large applications, with thousands of folders and files, and millions of
lines of code, is a daunting task. NetBeans IDE provides different views of your data, from multiple
project windows to helpful tools for setting up your applications and

managing them efficiently, letting you drill down into your data quickly and easily, while giving you
versioning tools via Subversion, Mercurial, and Git integration out of the box.

Write Bug Free Code

The cost of buggy code increases the longer it remains unfixed. NetBeans provides static analysis
tools, especially integration with the widely used FindBugs tool, for identifying and fixing common
problems in Java code. In addition, the NetBeans Debugger lets you place breakpoints in your source
code, add field watches, step through your code, run into methods, take snapshots and monitor
execution as it occurs.

4.2.4. MySql Server

What is a Database?

A database is a separate application that stores a collection of data. Each database has one or more
distinct APIs for creating, accessing, managing, searching and replicating the data it holds.

Other kinds of data stores can also be used, such as files on the file system or large hash tables in
memory but data fetching and writing would not be so fast and easy with those type of systems.

38
Nowadays, we use relational database management systems (RDBMS) to store and manage huge
volume of data. This is called relational database because all the data is stored into different tables
and relations are established using primary keys or other keys known as Foreign Keys.

A Relational DataBase Management System (RDBMS) is a software that −

 Enables you to implement a database with tables, columns and indexes.

 Guarantees the Referential Integrity between rows of various tables.

 Updates the indexes automatically.

 Interprets an SQL query and combines information from various tables.

RDBMS Terminology

Before we proceed to explain the MySQL database system, let us revise a few definitions related to
the database.

 Database − A database is a collection of tables, with related data.

 Table − A table is a matrix with data. A table in a database looks like a simple spreadsheet.

 Column − One column (data element) contains data of one and the same kind, for example
the column postcode.

 Row − A row (= tuple, entry or record) is a group of related data, for example the data of one
subscription.

 Redundancy − Storing data twice, redundantly to make the system faster.

 Primary Key − A primary key is unique. A key value can not occur twice in one table. With
a key, you can only find one row.

 Foreign Key − A foreign key is the linking pin between two tables.

 Compound Key − A compound key (composite key) is a key that consists of multiple
columns, because one column is not sufficiently unique.

 Index − An index in a database resembles an index at the back of a book.

 Referential Integrity − Referential Integrity makes sure that a foreign key value always
points to an existing row.

39
MySQL Database

MySQL is a fast, easy-to-use RDBMS being used for many small and big businesses. MySQL
is developed, marketed and supported by MySQL AB, which is a Swedish company. MySQL is
becoming so popular because of many good reasons −

 MySQL is released under an open-source license. So you have nothing to pay to use it.

 MySQL is a very powerful program in its own right. It handles a large subset of the
functionality of the most expensive and powerful database packages.

 MySQL uses a standard form of the well-known SQL data language.

 MySQL works on many operating systems and with many languages including PHP, PERL,
C, C++, JAVA, etc.

 MySQL works very quickly and works well even with large data sets.

 MySQL is very friendly to PHP, the most appreciated language for web development.

 MySQL supports large databases, up to 50 million rows or more in a table. The default file
size limit for a table is 4GB, but you can increase this (if your operating system can handle
it) to a theoretical limit of 8 million terabytes (TB).

 MySQL is customizable. The open-source GPL license allows programmers to modify the
MySQL software to fit their own specific environments.

40
 5 System Design

5.1 Introduction UML

Unified Modeling Language (UML) is a general purpose modelling language. The main aim of UML
is to define a standard way to visualize the way a system has been designed. It is quite similar to
blueprints used in other fields of engineering.
UML is not a programming language, it is rather a visual language. We use UML diagrams to
portray the behavior and structure of a system. UML helps software engineers, businessmen and
system architects with modelling, design and analysis. The Object Management Group (OMG)
adopted Unified Modelling Language as a standard in 1997. Its been managed by OMG ever since.
International Organization for Standardization (ISO) published UML as an approved standard in
2005. UML has been revised over the years and is reviewed periodically.

UML is a standardized graphical display format for of (software) systems. It offers a set of
the visualization, specification, design and documentation standardized diagram types with which
complex data, processes and systems can easily be arranged in a clear, intuitive manner.

UML is neither a procedure nor a process; rather, it provides a "dictionary" of symbols - each of
which has a specific meaning. It offers diagram types for object-oriented analysis, design and
programming, thereby ensuring a seamless transition from requirements placed on a system to final
implementation. Structure and system behavior are likewise shown, thereby offering clear reference
points for solution optimization.

UML is linked with object oriented design and analysis. UML makes the use of elements and forms
associations between them to form diagrams. Diagrams in UML can be broadly classified as:

1. Structural Diagrams – Capture static aspects or structure of a system. Structural Diagrams

include: Component Diagrams, Object Diagrams, Class Diagrams and Deployment Diagrams.

41
 2. Behavior Diagrams – Capture dynamic aspects or behavior of the system. Behavior diagrams
include: Use Case Diagrams, State Diagrams, Activity Diagrams and Interaction Diagrams.

5.2. UML Diagrams

There are two broad categories of diagrams and they are again divided into subcategories −

 Structural Diagrams

 Behavioral Diagrams

Structural Diagrams
The structural diagrams represent the static aspect of the system. These static aspects represent
those parts of a diagram, which forms the main structure and are therefore stable.

These static parts are represented by classes, interfaces, objects, components, and nodes. The four
structural diagrams are −

 Class diagram

 Object diagram

 Component diagram

 Deployment diagram

Behavioral Diagrams

Any system can have two aspects, static and dynamic. So, a model is considered as complete when
both the aspects are fully covered.

Behavioral diagrams basically capture the dynamic aspect of a system. Dynamic aspect can be
further described as the changing/moving parts of a system.

UML has the following five types of behavioral diagrams −

 Use case diagram

 Sequence diagram

 Collaboration diagram

 Statechart diagram

 Activity diagram

42
5.2.1 Use Case Diagram

Use case diagram consists of use cases and actors and shows the interaction between them. The key
points are:

’s perspective.

-user of the system or an external system.

Updating

Verificatio
visit n

Registrati Add User

visiter
on
Admin

Login
Transactions
Report
Recharge

user Login View Report

service Provider

Logout

43
User Use Case Diagram

Login

Add Bank
Logout

Feedback Recharge
and Bill Pay
user

Manage A/c View Report

Change
Password

44
Admin Use Case Diagram

Login

Logout

Mange user and

full Application

Mange
Payment

Admin
Add User

Updating

Verifications
Mange
Payment mode

45
4.2.2 Activity Diagram

Activity diagrams provide a way to model the workflow of a business process. An activity diagram is
typically used for modeling the sequence of Activities in a process. Activity diagrams can model
many different types of work flows. A software company could use activity diagrams to model a
software development process. The following tools are used on the activity diagram toolbox to
model activity diagrams.

Before drawing an activity diagram, we should identify the following elements −

 Activities

 Association

 Conditions

 Constraints

Once the above-mentioned parameters are identified, we need to make a mental layout of the entire
flow. This mental layout is then transformed into an activity diagram.

Where to Use Activity Diagrams?

The basic usage of activity diagram is similar to other four UML diagrams. The specific usage is to
model the control flow from one activity to another. This control flow does not include messages.

Activity diagram is suitable for modeling the activity flow of the system. An application can have
multiple systems. Activity diagram also captures these systems and describes the flow from one
system to another. This specific usage is not available in other diagrams. These systems can be
database, external queues, or any other system.

1. Identify candidate use cases, through the examination of business workflows

2. Identify pre- and post-conditions (the context) for use cases
3. Model workflows between/within use cases
4. Model complex workflows in operations on objects
5. Model in detail complex activities in a high level activity Diagram

46
User Activity Diagram

Login/Registration

Is
user

Excising user New User

Registration
Login/Registration

Login

Select a
servic

Recharge Add to Wallet Transfer Money View History Third Party

Payment

Make another
Transection ?

yes
No

Logout

47
Admin Activity Diagram

Home Page

Enter credentials

Login

Validate details
No

yes

User Approve service Manage Update new View Manage

verification provider request system features Report payment

Logout

48
5.2.3 Collaboration Diagram

Collaboration diagram is an interaction diagram that shows the order of messages that implement an
operation or a transaction. Another type of interaction diagram is the collaboration diagram. A
collaboration diagram is a set of objects related in a particular context, and interaction, which is a set
of messages exchanged among the objects within the collaboration to achieve a desired outcome. In a
collaboration diagram, objects are shown in figures. As in a sequence diagram, arrows indicate the
message sent within the given use case. In a collaboration diagram, the sequence is indicated by
numbering the messages. Some people argue that numbering the messages makes it more difficult to
see
the sequence than drawing the lines on the page. However, since the collaboration diagram is more
compressed, other things can be shown more easily. A collaboration diagram provides several
numbering schemes.

What is a Collaboration?

 A Collaboration is a collection of named objects and actors with links connecting them.
They collaborate in performing some task.
 A Collaboration defines a set of participants and relationships that are meaningful for a
given set of purposes

Why Collaboration Diagram?

Unlike a sequence diagram, a collaboration diagram shows the relationships among the objects.
Sequence diagrams and collaboration diagrams express similar information, but show it in
different ways.
Because of the format of the collaboration diagram, they tend to better suited for analysis
activities (see Activity: Use-Case Analysis). Specifically, they tend to be better suited to
depicting simpler interactions of smaller numbers of objects. However, if the number of objects
and messages grows, the diagram becomes increasingly hard to read. In addition, it is difficult to
show additional descriptive information such as timing, decision points, or other unstructured
information that can be easily added to the notes in a sequence diagram. So, here are some use
cases that we want to create a collaboration diagram for:

49
  Model collaborations between objects or roles that deliver the functionalities of use cases
and operations
 Model mechanisms within the architectural design of the system
 Capture interactions that show the messages passing between objects and roles within the
collaboration
 Model alternative scenarios within use cases or operations that involve the collaboration of
different objects and interactions
 Support the identification of objects (hence classes) that participate in use cases

In UML, the two types of interaction diagrams are collaboration and sequence diagrams. While both
types use similar information, they display them in separate ways. Collaboration diagrams are used
to visualize the structural organization of objects and their interactions. Sequence diagrams, on the
other hand, focus on the order of messages that flow between objects. However, in most scenarios, a
single figure is not sufficient in describing the behavior of a system and both figures are required.

User Collaboration Diagram

1.Login() 3.Select payment option()

User Database Payment mode

4.View bill Details()

2.user verify()

Bill details

5.Pay bill()

Pay bill
6. validate credentials

7.Pay wallet()
Wallet

50
Admin Collaboration Diagram

2.Enter credentials 3.verified

Admin Login

1. Open app
4.Login check
Home Page

8.Response massage
clslogin

5.Execute query

Database DALsqlHelper

6.Execute

7.verified

51
5.2.4 Sequence Diagram

A sequence diagram is a graphical view of a scenario that shows object interaction in a time based
sequence-what happens first, what happens next. Sequence diagrams establish the roles of objects
and help provide essential information to determine class responsibilities and interfaces. A sequence
diagram has two dimensions: the vertical dimension represents time; the horizontal dimension
represents different objects. The vertical line is called the object’s lifeline. The lifeline represents the
object’s existence during the interaction. This form was first popularized by acobson. An object is
shown as a box at the top of a dashed vertical line. A role is a slot for an object within a collaboration
that describes the type of object that may play the role and its relationships to other roles. However, a
sequence diagram does not show the relationships among the roles ort eh association among the
objects. An object role is shown as a vertical dashed line, the lifeline.

Sequence Diagrams Represent the objects participating the interaction horizontally and time
vertically.

Sequence diagrams are time focus and they show the order of the interaction visually by using the
vertical axis of the diagram to represent time what messages are sent and when.
Sequence Diagrams captures interaction in different level of granularity:

1. high-level interactions between user of the system and the system, between the system and other
systems, or between subsystems (sometimes known as system sequence diagrams)
2. the interaction that takes place in a collaboration that either realizes a use case or an operation
(instance diagrams or generic diagrams)
3. Represent objects interact in (Model, View / Controller) MVC pattern of software framework

Sequence diagrams can be useful references for businesses and other organizations. Try drawing a
sequence diagram to:

 Represent the details of a UML use case.

 Model the logic of a sophisticated procedure, function, or operation.
 See how objects and components interact with each other to complete a process.
 Plan and understand the detailed functionality of an existing or future scenario.

52
User Server Service provider Wallet

Login/ Registration

Authentication

Recharge plan request

Response
Sand plan

Select plan

Recharge
Wallet pay

Authentication

Sand details
[user valid ]
Recharge successful

Commit Logout

Confirm

53
5.2.5 Class Diagram

Class diagram is a static diagram. It represents the static view of an application. Class diagram is
not only used for visualizing, describing, and documenting different aspects of a system but also for
constructing executable code of the software application.

Class diagram describes the attributes and operations of a class and also the constraints imposed on
the system. The class diagrams are widely used in the modeling of objectoriented systems because
they are the only UML diagrams, which can be mapped directly with object-oriented languages.

Class diagram shows a collection of classes, interfaces, associations, collaborations, and constraints.
It is also known as a structural diagram.

Purpose of Class Diagrams

1. Shows static structure of classifiers in a system

2. Diagram provides a basic notation for other structure diagrams prescribed by UML
3. Helpful for developers and other team members too
4. Business Analysts can use class diagrams to model systems from a business perspective
A UML class diagram is made up of:
 A set of classes and
 A set of relationships between classes
What is a Class

A description of a group of objects all with similar roles in the system, which consists of:
 Structural features (attributes) define what objects of the class "know"
 Represent the state of an object of the class
 Are descriptions of the structural or static features of a class
 Behavioral features (operations) define what objects of the class "can do"
 Define the way in which objects may interact
 Operations are descriptions of behavioral or dynamic features of a class
Class Notation

A class notation consists of three parts:

1. Class Name

54
  The name of the class appears in the first partition.
2. Class Attributes
 Attributes are shown in the second partition.
 The attribute type is shown after the colon.
 Attributes map onto member variables (data members) in code.
3. Class Operations (Methods)
 Operations are shown in the third partition. They are services the class provides.
 The return type of a method is shown after the colon at the end of the method
signature.
 The return type of method parameters is shown after the colon following the
parameter name.
 Operations map onto class methods in code

The graphical representation of the class - MyClass as shown above:

 MyClass has 3 attributes and 3 operations
 Parameter p3 of op2 is of type int
 op2 returns a float
 op3 returns a pointer (denoted by a *) to Class6
 A role is a directional purpose of an association.
 Roles are written at the ends of an association line and describe the purpose played by that
class in the relationship.
 E.g., A cell is related to an expression. The nature of the relationship is that the expression
is the formula of the cell.

55
 User
Add bank
-U_name :String
+Bank A/C number : - + U-id :number
number -Email : String
-Bank name : String -Password: number
-Branch name : String +Mobile No :number
-Account type : String -Date :: String
-Ifsc code : String -Time :: String
-Users id : number (1…*) +Registration :void()
-Balance : number +Login : void()
+Transfer money: void() +Bank add: void()
+Payment service provide : +Recharge/payment:
void() void()
(1…*) ( 1…*)
Admin
(0…*) 1
-Admin_id : String
-Password :number
+Manage user : void()
+View Report : void()
+Verify user : void()
+update new features : void()
(1…*) +manage payment : void()
1
(1…*) (1…*)

(1…*) (1…*) (1…*) (1…*)

User wallet Mobile recharge Electricity bill pay Dth Recharge

-Prepaid postpaid : - -State : String -Operator : String

-Usre name : String String -Bord : String -Co_number : number
-Mobile.no: number -Operator : String -Co_number : number -Amount : number
-User_id : number -Mobile no : number -Amount : number -Date : String
-Date : String -Amount :number -Time : String -Time : String
-Tiem : String -Time : String -Date : String -User_id : number
-Balance : number -Date : String
-User_id : numbet

+Paid mobile +Check bill :void() +Check recharge : void()

+Recharge and bill:void() +Pay bill : void() +Recharge dth: void()
payment service
+Recharge mo: void() +Pay bill history : void() +Recharge history : void()
provider : void() +Check history :void()

(1…*) (1…*)

Wallet to bank Wallet to wallet Gas bill Pay Gas book

-A/C number : number
-Amount : number
-Date : String
-Time : String
-User_id :number
+Wallet to bank
transfer money : void()
-Mo. number : number -Provider : String -Provider : String
-Amount : number -Co_number : number -Co_number : number
-Date : String -Amount : number -State
-Time : String -Date : String -City
-User_id :number -Time : String -Gas agency
-User_id : number -Amount
-User_id
+Wallet to wallet transfer +Check available bill +Gas book : void()
money : void :void() +Gas book history
+Bill pay : void() :void()
+Bill pay history : void()

Water bill pay (1...*) (1...*) Feedback (0…1) All Transactions

-Board : String -Feedback type : String -Mode : String

-Rr_number :number -Feedback : String -T_number : number
-Amount : number -Name -Amount : number
-Date : String -Email -User_id : number
-Time : String -Date : String
-User_id :number -Time : String

+Check available bill :void() +Sand feed back : void() +Check transactions
+Bill pay : void() history : void()
+Bill pay history : void()

56
5.3 Gantt Chart

Gantt charts, such as the Accelo Gantt chart, are smart tools that are intuitive and track where you are
in a specific project. They’re great at helping to plan and schedule projects and are one of the best
visual project management tools that you can use to increase transparency across the board. Gantt
charts take a project and break it into small, easy to swallow pieces with checkpoints along the
way. The smartest Gantt charts will even automatically update project timelines when upstream
dependencies have been met - so all you need to do is focus on the task at hand.

2020
Software development fab 25 10 mar 25 mar 20 April 25 may

Selection of project

Software requirements

Requirements analysis

Feasibility study

Planning and scheduling

Conceptual module
design
Systems design

Ifebmplementation

Testing

Development

57
5.4 Data Dictionary

After carefully understanding the requirements of the client the the entire data storage requirements
are divided into tables. The below tables are normalized to avoid any anomalies during the course of
data entry.
MySQL Server incorporates a transactional data dictionary that stores information about database
objects. In previous MySQL releases, dictionary data was stored in metadata files, nontransactional
tables, and storage engine-specific data dictionaries.

1) User Registration

A registered user is a user of a application, program, or other system who has

previously registered. Registered users normally provide some sort of credentials (such as a
username or e-mail address, and a password) to the system in order to prove their identity: this is
known as logging in.

2) User Bank Add

Yes you can definitely start using easypay without a bank account. ... As for loading money you
will need a bank account from where you can debit money to add it to your wallet. Or what you

58
could do is ask your friend or family member to load money into your easypay wallet from
their bank and you pay them in cash.

3) Easypay wallet

You can use the easypay Wallet only for merchant payments such as recharges, bill payments, online
shopping or payments at your favourite stores that accept easypay Wallet.

59
4)Mobile Recharge/bill pay

5) Electricity bill Pay

6) Gas bill pay

60
7) Gas Book

8) Water bill pay

9) user feedback

61
10) Transfer money

11) wallet to wallet transfer money

62
 6.Screenshots

1)Easypay home Page

2) About

63
3)User Registration

4)Add Bank

64
5)Easypay Login

6)Add Wallet Money

65
7)Mobile recharge

8) Electricity bill pay

66
9) GAS Bill pay

10) Gas book

67
11) Tv Recharge

12) Water Bill pay

68
13) Money Transfer

14) Feed back

69
15) Wallet to wallet Transfer Money

16)All Process history

70
 7.Testing

7.1 Psychology Of Testing

Psychology of testing is a type of testing which fully depends on the mindset of developers and
tester. When we are building the software, we working positively towards the software never think
about negative things. The mindset should be different while testing and reviewing developing
software. With the correct mindset, the programmer can test their own code. At a certain point
independence tester often makes the tester more

effective to finding defects.

Levels of Independence Tester in Psychology of testing

 Tests designed by the person who wrote the software under test
 Tests designed by another person
 Tests designed by a person from a different organizational group or test specialists
 Tests designed by a person from a different organization or company

In Psychology of testing, People and projects are driven by objectives. While developing the
software, programmer writing code to build software, that time Programmers test their code then

71
pass through the next phase but as we already mentioned, It is difficult to find our own mistakes.
That’s why independence tester highly recommendable. Because they are testing specialists or
professional testers. In Psychology of testing communication also matters, tester and test lead need
good interpersonal skill to communicate. In Psychology of testing Tester and others can improve
communication by

 Starting collaboration instead of battles.

 Everyone should have a common goal of the quality software.
 Improve mutual understanding while working.
 Confirm that the other person has understood what you have said.

WHITE BOX TESTING is testing of a software solution's internal structure, design, and coding. In
this type of testing, the code is visible to the tester. It focuses primarily on verifying the flow of
inputs and outputs through the application, improving design and usability, strengthening security.
White box testing is also known as Clear Box testing, Open Box testing,

Structural testing, Transparent Box testing, Code-Based testing, and Glass Box testing. It is usually
performed by developers.

It is one of two parts of the Box Testing approach to software testing. Its counterpart, Blackbox
testing, involves testing from an external or end-user type perspective. On the other hand, Whitebox
testing is based on the inner workings of an application and revolves around internal testing.

72
The term "WhiteBox" was used because of the see-through box concept. The clear box or WhiteBox
name symbolizes the ability to see through the software's outer shell (or "box") into its inner
workings. Likewise, the "black box" in "Black Box Testing" symbolizes not being able to see the
inner workings of the software so that only the end-user experience can be tested.

BLACK BOX TESTING is defined as a testing technique in which functionality of the Application
Under Test (AUT) is tested without looking at the internal code structure, implementation details and
knowledge of internal paths of the software. This type of testing is based entirely on software
requirements and specifications. In BlackBox Testing we just focus on inputs and output of the
software system without bothering about internal knowledge of the software program.

The above Black-Box can be any software system you want to test. For Example, an operating
system like Windows, a website like Google, a database like Oracle or even your own custom
application. Under Black Box Testing, you can test these applications by just focusing on the inputs
and outputs without knowing their internal code implementation.

7.2 Testing Objectives

A TEST PLAN is a detailed document that describes the test strategy, objectives, schedule,
estimation and deliverables and resources required for testing. Test Plan helps us determine the effort
needed to validate the quality of the application under test. The test plan serves as a blueprint to
conduct software testing activities as a defined process which is minutely monitored and controlled
by the test manager.

73
7.3 Levels Of Testing

tests are grouped together based on where they are added in SDLC or the by the level of of detailing
they contain. In general, there are four levels of testing: unit testing, integration testing, system
testing, and acceptance testing. The purpose of Levels of testing is to make software testing
systematic and easily identify all possible test cases at a particular level.

There are many different testing levels which help to check behavior and performance for software
testing. These testing levels are designed to recognize missing areas and reconciliation between the
development lifecycle states. In SDLC models there are characterized phases such as requirement
gathering, analysis, design, coding or execution, testing, and deployment.

1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance Testing

Each of these testing levels has a specific purpose. These testing level provide value to the software
development lifecycle.

74
7.3.1 Unit testing:A Unit is a smallest testable portion of system or application which can be
compiled, liked, loaded, and executed. This kind of testing helps to test each module separately.

The aim is to test each part of the software by separating it. It checks that component are fulfilling
functionalities or not. This kind of testing is performed by developers.

UNIT TESTING is a type of software testing where individual units or components of a software are
tested. The purpose is to validate that each unit of the software code performs as expected. Unit
Testing is done during the development (coding phase) of an application by the developers. Unit
Tests isolate a section of code and verify its correctness. A unit may be an individual function,
method, procedure, module, or object.

7.3.2 Integration testing:

Integration means combining. For Example, In this testing phase, different software modules are
combined and tested as a group to make sure that integrated system is ready for system testing.

Integrating testing checks the data flow from one module to other modules. This kind of testing is
performed by testers.

NTEGRATION TESTING is defined as a type of testing where software modules are integrated
logically and tested as a group. A typical software project consists of multiple software modules,
coded by different programmers. The purpose of this level of testing is to expose defects in the
interaction between these software modules when they are integrated

7.3.3 System testing:

System testing is performed on a complete, integrated system. It allows checking system's

compliance as per the requirements. It tests the overall interaction of

components. It involves load, performance, reliability and security testing.System testing most often
the final test to verify that the system meets the specification. It evaluates both functional and non-
functional need for the testing.

75
SYSTEM TESTING is a level of testing that validates the complete and fully integrated software
product. The purpose of a system test is to evaluate the end-to-end system specifications. Usually,
the software is only one element of a larger computer-based system. Ultimately, the software is
interfaced with other software/hardware systems. System Testing is actually a series of different tests
whose sole purpose is to exercise the full computer-based system.

7.3.4 Validation Testing

Validation Testing, carried out by QA professionals, is to determine if the system complies with the
requirements and performs functions for which it is intended and meets the organization’s goals and
user needs. This kind of testing is very important, as well as verification testing. Validation is done at
the end of the development process and takes place after verification is completed.

Stages of Validation testing Process:

 Validation Planning – To plan all the activities that need to be included while testing.
 Define Requirements – To set goals and define the requirements for testing.
 Selecting a Team – To select a skilled and knowledgeable development team (the third party
included).
 Developing Documents – To develop a user specification document describing the operating
conditions.
 Estimation/Evaluation – To evaluate the software as per the specifications and submit a
validation report.
 Fixing bugs or Incorporating Changes – To change the software so as to remove any errors
found during evaluation.

7.3.5 OUTPUT TESTING (FUNCTIONAL TESTING)

FUNCTIONAL TESTING is a type of software testing that validates the software system against the
functional requirements/specifications. The purpose of Functional tests is to test each function of the
software application, by providing appropriate input, verifying the output against the Functional
requirements.

76
  FUNCTIONAL TESTING is a type of software testing whereby the system is tested against
the functional requirements/specifications.
 Functions (or features) are tested by feeding them input and examining the output. Functional
testing ensures that the requirements are properly satisfied by the application. This type of
testing is not concerned with how processing occurs, but rather, with the results of
processing. It simulates actual system usage but does not make any system structure
assumptions.
 During functional testing, Black Box Testing technique is used in which the internal logic of
the system being tested is not known to the tester.
 Functional testing is normally performed during the levels of System Testing and Acceptance
Testing.

7.3.6 Acceptance testing:

Acceptance testing is a test conducted to find if the requirements of a specification or contract are
met as per its delivery. Acceptance testing is basically done by the user or customer. However, other
stockholders can be involved in this process.

USER ACCEPTANCE TESTING (UAT)

User Acceptance Testing (UAT) is a type of testing performed by the end user or the client to
verify/accept the software system before moving the software application to the production
environment. UAT is done in the final phase of testing after functional, integration and system
testing is done.

The main purpose of UAT is to validate the end to end business flow. It does NOT focus on
Cosmetic errors, Spelling mistakes or System testing. User Acceptance Testing is carried out in a
separate testing environment with production-like data setup. It is a kind of black box testing where
two or more end-users will be involved. The Full Form of UAT is User Acceptance Testing.

Who Performs UAT?

 Client
 End users

77
Need of User Acceptance Testing:

Once software has undergone Unit, Integration, and System testing the need of Acceptance Testing
may seem redundant. But Acceptance Testing is required because

 Developers code software based on requirements document which is their "own"

understanding of the requirements and may not actually be what the client needs from the
software.
 Requirements changes during the course of the project may not be communicated effectively
to the developers.

her Types of Testing:

 Regression Testing
 Buddy Testing
 Alpha Testing
 Beta Testing

78
 8 Conclusion

Finally it can be said that, Digital Payment System is the latest technology to make a great and
convenient banking and payment process. Going digital will help in keeping track of the monetary
transactions taking place and will pose more security on individual’s wealth. Digital payments will
also be a step for an eco friendly environment as the usage of paper reduces. A drawback factor to
the making of a digital India will be the high rates of illiteracy and poverty.

 Easypay saves customer’s time on going to separate websites for separate payments.
 Most importantly, it's very easy to use.
 In a nutshell, it is one useful app that can really come in “handy for customers” and is definitely
worth a try.

The app is best app so you don’t have to worry too much about the authenticity and security. So you
should use it for recharge and payment for your bills. There is nothing wrong in getting some bucks
for making payments.
Easypay is a great app undoubtedly. It has all the features that a payments app should have. You can
make and receive payments in moments. It is secure, fast and easy to use.
Digital payments are future. In coming years we will see payment methods transitioning from
physical cash to the digital payment methods. Before the transition concludes, many new trends will
appear and disappear. These trends will play a vital role in shaping our future payment methods.

Easypay is a payment app that encompasses different aspects as well . However, just like other
payment apps, it also comes with a maximum limit on the quantum of transactions that is possible
through the app in 24 hours. The best part about the app is that you do not have to load the wallet
again and again to make any transaction. It is much easier to keep track record of the incoming and
outgoing money via bank statements.

79
 9.BIBLIOGRAPHY

https://www.guru99.com/
http://softwaretestingfundamentals.com/
https://scholar.google.com/
https://www.google.com/
https://www.javatpoint.com/
https://www.w3schools.com/
https://www.youtube.com/channel/UCBTuzjmeuyMkkDCSNKUxJiw
https://www.youtube.com/channel/UCmlllk0gmFt6nOtyuOhYEpg
https://.wikipedia.org/
https://netbeans.org/community/releases/82/
https://dev.mysql.com/doc/refman/8.0/en/introduction.html
https://www.sparxsystems.eu/resources/project-development-with-uml-and-
ea/introduction-to-uml/
https://www.sciencedirect.com/topics/computer-science/technical-feasibility
http://www.ofm.wa.gov/resources/ecommerce.asp.

BOOK
Chablis - Market Analysis of Digital Payment Systems by Ricarda Weber.
Fundamental of Software Engineering By Rajiv Mall.

80