Implementation of a Service-Oriented Architecture for a e-WALLET System for Cashless Transactions in the Democratic Republic of Congo

July 15, 2023 Β· Declared Dead Β· πŸ› arXiv.org

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Patrick Mukala arXiv ID 2308.00689 Category cs.SE: Software Engineering Citations 0 Venue arXiv.org Last Checked 5 months ago
Abstract
The Democratic Republic of Congo is a sleeping giant at the heart of Africa. Though endowed with incredible natural resources spanning from significant reserves of gold, diamond, coltan, copper to vast African forests and impressive water resources, it is still considered as one of the poorest countries on the planet. For a long time, its economy has had nothing to show for all these resources as the Congolese people continue to live in extreme poverty. To survive, the Congolese people engage in a range of activities to generate income and most families rely on 'solidarity grants' from family members and relatives that either work or conduct a personal business. Most of these families remain unbanked. Due to the absence of reliable and private financial institutions, almost 90% of all financial transactions are cash-based. However, as the number of banks increases throughout the past few years, there is a possibility to encourage and perform cashless transactions. In this paper, we demonstrate an implementation of a Service-Oriented Architecture approach in the design of a eWallet system. A typical scenario has been presented to highlight the major components of the system to be implemented as contextualized in the ecosystem. A series of models, from the business processes to the technical architecture and service model for the system, has been developed to represent every step of the solution. The paper is structured as follows: In section 1, we give a brief introduction of the paper, section 2 gives a generic description and contextualization of eWallet, section 3 gives a description of the scenario as chosen for this case study, section 4 describes the ecosystem for the scenario, section 5
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering

Died the same way β€” πŸ‘» Ghosted